Water Finance and Management reports that Denver Water is raising its water and drought rates for 2027. The utility serves 1.5 million people and is dealing with what the report describes as "historic drought" alongside ongoing inflation. On Oct. 28, 2026, Denver's Board of Water Commissioners voted unanimously to approve the increased 2027 rates. The item is useful beyond Denver because it pairs a drought charge with a general cost increase in the same budget cycle, a combination many finance offices will recognize. The source is Water Finance and Management's account of Denver's 2027 rate increase.
A Drought Charge Protects a Revenue Line, Not Only a Demand Goal
A volumetric drought charge is often read as a conservation signal, and it may be one. It also changes how fixed costs are recovered. When customers use less water, the utility collects less revenue per unit sold, while debt service, pipe maintenance, and staffing continue on their schedules. A drought charge can recover part of that gap, and it can also discourage the use that caused the shortfall. These two aims pull in different directions, so the reserve record should show which one the rate design is meant to serve. The answer belongs in the utility's own budget documents and board materials, not in a summary of the outcome.
Read the Reserve Before the Surcharge
Several items in the reserve file determine whether a drought charge is a bridge or a permanent feature of the rate structure. Start with the reserve policy target and the current balance measured against it. Then confirm whether drought surcharge revenue is restricted to drought response or flows into general operations. The drought plan should define the triggers that start and end each stage, and the budget should record who declares them. Finally, check the length of time the reserve can absorb a revenue shortfall before a rate change becomes necessary. Bond documents and loan agreements may also set reserve minimums that a voluntary board target does not reach, and those floors can bind before the policy does. Where that happens, the covenant governs the decision.
Keep Drought and Inflation on Separate Clocks
Drought is episodic, and reserves and temporary charges are built to handle it. Inflation is persistent, and it belongs in base rates. When both appear in one increase, the next budget can look like a drought problem when it is really a cost problem, or the reverse. Record each driver on its own line. Chemicals, power, labor, and capital cost growth belong on one side. Lost volume and drought-stage revenue belong on the other. With the lines separated, the board can see whether the rate is expected to fall when the drought ends, or whether the higher level stays because the cost base has moved.
Questions for the Next Budget Session
Before the next rate discussion, a finance officer can bring a short set of questions to the table. What is the reserve balance today, measured against the target written in the reserve policy? Which drought-stage triggers are in the plan, and who declares each one? Does drought surcharge revenue return to the reserve, fund capital work, or cover operating expense? How much of the proposed increase traces to lower sales volume, and how much traces to cost growth? Which covenant or bond requirement sets a floor the board cannot waive? Written answers to these questions make the rate record easier to review when conditions change.
Where Residential Customers Fit
Customers see only the combined figure. A household bill that rises because of both a drought charge and a base-rate change can look like a single decision, even when it reflects two separate funding problems. Households that also manage private wells, point-of-use filters, or appliances will want to separate what the utility charges from what their own equipment costs to run and maintain. For that side of the bill, see our coverage for home systems and appliances.
A rate increase is a funding decision with its own timeline. The reserve record and the trigger record show whether that decision matches the event that prompted it, and utilities that keep both current are better placed to explain the number when it arrives.