A special utility district may be the logical long-term water partner for a campus and still be unable to fund the extension or capacity required for its first tenant. The resulting stalemate is often described as a service problem when the unresolved issue is who bears capital and demand risk. The solution needs to protect both the campus opening and the provider's existing customers.
The campus problem
Illustrative scenario, not a claimed client result.
An illustrative campus has completed its demand study but cannot obtain a reliable service date. The SUD’s existing distribution main cannot serve the proposed peak and fire-flow requirements without storage and pumping improvements. A neighboring community could also benefit from parts of the upgrade. The district cannot responsibly build the whole ultimate campus system against an unsigned tenant pipeline. The developer cannot wait indefinitely for the district’s ordinary capital improvement plan.
Translate the provider's limitation into a specific investment
Start by separating supply, treatment, pumping, storage and distribution. A new extension is useful only if the upstream system can support the requested service. The provider and engineers should establish the first-stage operating basis, the capacity consumed by the campus and the upgrades required for later demand. That work gives commercial negotiations a scope. Without it, a capital contribution can fund an asset without closing the actual service gap.
A provider also has recurring obligations after construction. A large new asset can increase maintenance, power use, staffing and replacement needs even when the campus takes less water than forecast. A proposed minimum payment or reservation charge should therefore be examined alongside its legal basis, service obligation and duration. The owner needs to know what it pays for a delayed ramp, while the provider needs to know it is not depending on speculative occupancy to operate the new system.
Texas framework: SUD economics differ from a MUD
TCEQ’s general guide describes SUDs as providing water, wastewater and firefighting services without authority to levy taxes. Chapter 65 contains the general-law SUD framework, including revenue-backed borrowing provisions. That makes service revenues, contributions and debt terms central to the proposed package; do not import a MUD tax-reimbursement model into an SUD negotiation. Verify the particular district’s enabling law, service authority and financial covenants.
TCEQ general guide: SUD services and tax limitations, page 5 · Texas Water Code Chapter 65: SUD authority and debt
A financing route worth testing, not a promised subsidy
TWDB’s DFund lists districts among eligible political-subdivision borrowers and supports eligible water and wastewater components through loans, not grants. Its page currently lists a September 30, 2026 application deadline and calls for a pre-application conference. Eligibility is project- and applicant-specific. The applicant would be the eligible provider or public entity, not automatically the private campus developer. The private sponsor should not promise a tenant that public funding will arrive on its schedule.
TWDB DFund: borrower and project eligibility, current application window
Treat provider revenue and campus credit as different risks
The SUD needs supportable service revenue and a funded asset plan; the campus needs delivered capacity by a date. Minimum payments, contributions and capacity reservations can bridge those interests only when their amounts, start conditions and remedies align. Ask who is liable if the serving entity completes its works but the tenant postpones occupancy, and who bears the reverse delay.
Match the capital contribution to capacity, timing and ownership
Consider a first tenant with a supported demand profile and a second tenant that has not committed. The parties can evaluate a campus-funded extension accepted by the provider, a provider-financed project supported by enforceable payments, or a staged combination. The agreement should identify which contribution is nonrefundable, which might be recovered from later connections and which buys a defined service reservation. These are separate economic rights, not synonyms for paying toward infrastructure.
Sitebraid would coordinate the scope, phase demand and contribution alternatives so the owner can negotiate against a common technical basis. Asset acceptance needs to cover design standards, testing, title transfer, maintenance and the service-start conditions. If later growth does not arrive, the first tenant's service should not depend on an unbuilt second-stage project unless that dependency is explicit and funded. If the incumbent route remains unworkable, the owner needs a separate assessment of lawful service alternatives rather than an assumption that it can simply select another supplier.
Solutions and their tradeoffs
Campus-funded extension with district acceptance
The owner funds agreed works that the district will accept and operate once conditions are satisfied.
Conditions to resolve: Set design standards, procurement obligations, inspection rights, transfer documents and the date service can actually begin.
Provider borrowing supported by a negotiated service commitment
Test a district-led financing route for qualifying shared assets with appropriately approved charges or contractual support.
Conditions to resolve: Confirm borrowing eligibility, rate and contract authority, customer protections and what happens when campus consumption ramps more slowly.
Smaller water envelope plus a revised cooling basis
Reduce the first phase’s demands while protecting room for a later system upgrade.
Conditions to resolve: Have the tenant and designers accept the operating tradeoffs. A supply reduction cannot be imposed on an unchanged cooling specification.
A missing tenant leaves the provider's fixed costs in place
Hypothetical annual fixed-cost allocation, not a SUD tariff or financing offer. Excludes variable water charges; actual rates, authority and agreements must be confirmed.
Swipe or scroll to compare all columns.
| Obligation | Annual amount | Who carries the difference? |
|---|---|---|
| Accepted shared-system fixed cost | $1.2m | Must be supported independently of assumed later connections. |
| Tenant A's committed payment | $0.7m | The first signed obligation does not cover the full fixed cost. |
| Tenant B is forecast but unsigned | $0.5m expected | Treat as zero committed recovery; the sponsor/provider agreement must allocate the gap. |
| B arrives two years late | 2 x $0.5m = $1m | Fund a defined backstop or reduce first-stage fixed obligations; do not quietly transfer the gap to A. |
| Backstop expires before B arrives | $0.5m annual exposure resumes | Set a renewal, resizing or other agreed response before expiry. |
This is the development problem behind our water solution blocked challenge. Our Water & cooling capability explains the scope Sitebraid can take on.
Putting the analysis to work
Establish the existing CCN and service arrangements, supply contracts, treatment and hydraulic capacity, discharge route, operating staffing and debt restrictions. Separate peak cooling demand, domestic demand, fire storage and future optional load. Produce a staged engineering scope with public and private benefits identified. The district and its advisors need a defensible revenue commitment, not a nameplate MW figure converted into a guessed water demand.
How Sitebraid would support this decision
Make the constraint measurable
Agree whether the blockage is source quantity, treatment, pressure, storage, financing or a combination. Reconcile the provider’s model with the tenant’s design basis.
Build a term sheet that survives a missing tenant
Allocate upfront contribution, minimum commitments if lawful and negotiated, capacity reservation, operating costs and expansion triggers. Test delayed occupancy and the anchor leaving before infrastructure costs are recovered.
Align the funding and construction clocks
Obtain provider and advisor decisions on financing before treating it as committed. Advance only those design and easement actions the owner has separately authorized. Keep an unfunded-source register beside the construction schedule.
Deliver to the service boundary
Coordinate the approved works with the district and project specialists. Close testing, asset transfer, operating readiness and the formal release of the accepted service capacity.
How we protect the decision
Existing customers should not unknowingly absorb speculative campus expansion costs. Show the district a benefit and cost allocation it can defend publicly. Public governance, procurement and financing requirements stay with the relevant entity. A development agreement must distinguish obligations that are enforceable now from an intention to consider a future upgrade.
The result the owner should require
A signed and appropriately approved service package identifies the available phase demand, delivery conditions, public/private ownership line, operating responsibilities, funding sources and fallback. Water infrastructure acceptance and tenant cooling acceptance reconcile. A positive meeting or an application for finance is an intermediate milestone, not the completed outcome.
How to measure progress
- Unreserved provider capacity against accepted demand
- Funding commitments versus applications
- Owner contribution at risk before service
- Tested service conditions at the campus boundary
The decision to take forward
Build the partnership around a deliverable first-stage service and sustainable operating obligations. A good contribution agreement tells the campus what it receives, tells the provider what it must operate and makes the missing-tenant case affordable to the parties who agreed to bear it.
If your site sits in a SUD's territory, our Water & cooling work helps you work out who pays for the water your campus needs before you sit down with the district.
Continue with Solve the water system, not just the water request. to examine the connected decision.