Financing the Water Infrastructure Backlog

Every water utility finance director I talk to right now is running the same problem through a slightly different formula: a capital plan that's grown faster than the customer base or the tax base can comfortably absorb, against a financing toolkit that hasn't fundamentally changed in decades. State revolving fund loans, revenue bonds, rate-funded pay-as-you-go capital, and — increasingly — consolidation with a larger neighboring system are all being used to close the same gap. They are not interchangeable tools, and treating them that way in a capital financing plan is where I see the most avoidable mistakes.

State Revolving Funds Solve a Specific Problem — Not the Whole Problem

The federal-state SRF loan programs remain the cheapest debt most systems can access, typically pricing well below market rate and sometimes carrying partial principal forgiveness for disadvantaged systems. That makes SRF financing the right first stop for any capital project that qualifies. But the programs are also capacity-constrained: state allocations are finite, application cycles are competitive, and a system with a $40 million capital plan is not going to fund all of it through a program that might allocate $3-5 million to any single applicant in a cycle.

The mistake I see is treating SRF eligibility as a financing plan rather than one layer of one. A capital improvement plan should stack financing sources deliberately: SRF or other low-cost/grant funding for the portion that qualifies and is awarded, revenue bond or other market debt for the balance, and rate-funded pay-as-you-go capital for smaller recurring replacement work that doesn't justify the transaction cost of debt issuance. When all three layers are modeled together, the blended cost of capital and the resulting revenue requirement are both lower than defaulting to bond financing for everything.

How the layers typically compare

Funding source	Typical cost	Where it fits best
State revolving fund loan / grant blend	Below market, sometimes with forgiveness	Large qualifying capital projects; competitive and allocation-limited
Revenue bonds / market debt	Current market rate, priced to system's coverage ratios	Large capital projects beyond SRF capacity, or timing-sensitive work
Rate-funded pay-as-you-go	No interest cost, but immediate rate impact	Smaller recurring replacement (services, hydrants, meters) and debt service coverage cushion

Debt Service Coverage Isn't Just a Bond Covenant — It's a Planning Constraint

Most revenue bond issuances carry a debt service coverage covenant, commonly requiring net revenue to cover annual debt service by 1.20x to 1.25x or more. That covenant isn't just a compliance checkbox for the trustee — it functions as a hard ceiling on how much new debt a system can layer onto an existing capital structure before rates have to move regardless of political appetite. When I build a multi-year capital financing plan, the coverage ratio test comes before the rate design conversation, not after, because it tells you the minimum revenue requirement path independent of any other consideration.

Systems that skip this step and go straight to "what rate increase will our customers tolerate" sometimes end up approving a rate path that looks reasonable on the surface but doesn't actually clear the coverage covenant in the bond documents once the next debt issuance is layered on. That's a conversation you want to have in a planning session, not from bond counsel three weeks before a pricing date.

Why Consolidation Is Showing Up More in Financing Conversations

The smallest systems — those serving a few hundred to a couple thousand connections — are increasingly running out of financing options entirely. A system that small often can't generate enough rate revenue to support meaningful debt at any interest rate, doesn't have the technical staff to manage a complex capital program, and may not clear the minimum project size that makes SRF administration worthwhile for either side. Acquisition or consolidation with a larger neighboring system is increasingly the outcome, not because of any policy preference for bigger utilities, but because the financing math for a genuinely small standalone system stops working past a certain point.

From an accounting standpoint, a consolidation is not simply "add the customer count together." Acquisition accounting requires establishing fair value for the acquired system's assets, which for an aging small system frequently means recognizing meaningfully more or less value than the seller's net book value would suggest. It also raises rate-setting questions immediately — does the acquired system's customer base move onto the acquiring utility's existing rate structure, or does it stay on a transitional or separate rate schedule for a defined period? That decision has to be made and documented before the deal closes, not worked out afterward.