Every rate increase invites comparison. A board approves a new schedule, a neighboring utility posts its own, and someone in a council chamber or a customer service queue places the two side by side. Denver Water's move is a useful case for that exercise. According to Water Finance and Management's report on the 2027 increase, the utility is "raising water and drought rates for 2027," and its Board of Water Commissioners approved the change on Oct. 28. The utility serves 1.5 million people. Before anyone sets a Denver figure beside a figure from another city, the comparison needs matching terms, because a headline percentage rarely describes what a household pays.
Match the Meter Before the Rate
A bill is the product of several inputs, and a peer comparison only means something when those inputs line up. The first is meter size. Accounts on different meter sizes can carry different fixed charges, so a volumetric price printed for one utility cannot be read as a total bill for another without that base in view. A comparison should name the meter size it assumes and use the same size on both sides.
The second input is the billing period. Some utilities bill monthly, others bimonthly, and the same annual cost can look larger or smaller depending on the cycle used to present it. Convert both schedules to a common period before any total is shown, and write the conversion method in the note.
Match the Tiers, Not Just the Unit Price
Tiered schedules add a second layer. Two utilities can post identical per-unit prices for their first block and still produce different household totals, because the block edges sit at different volumes and the number of tiers differs. A comparison that uses only the lowest tier will flatter one utility and penalize the other.
The working method is to choose a reference household volume, run it through each published schedule for the same period, and report the total with the schedule version and its dates beside it. That keeps the number tied to a specific document rather than to a remembered bill from last year.
Record Three Dates, Not One
The effective date matters in a second way. A rate approved in one month may not appear on customer bills until a later cycle, so a comparison written during the approval window can describe a schedule that residents will not see for some time. Record the approval date, the effective date, and the first billing cycle that carries the new figure as three separate entries. A reader who sees only one date will assume the rest.
Show Conditional Charges Apart From the Base
Some utilities attach charges that apply only under declared conditions. The Denver announcement pairs water rates with drought rates, and a comparison should first establish whether the neighboring utility uses an equivalent charge and how that charge is described in its own documents. A conditional component is not the same as a permanent rise in the base schedule, so the note should show the base total alone and then the conditional add-on as a separate line.
Write the Comparison Note Before the Meeting
A useful note has five fields: the reference household volume, the meter size, the schedule version with its approval and effective dates, the billing period, and any conditional charges shown separately. It also states what the comparison leaves out, such as sewer or stormwater charges, which vary by community and may be billed separately. Without that boundary, a reader may assume the total is a complete municipal bill.
The scale of a system does not guarantee comparability. A large utility with a long rate history and a smaller one with a recent restructuring can both publish schedules that look orderly on the page, and neither number, on its own, tells a council whether its own customers would pay more. The discipline is to finish the matching work first and let the comparison speak afterward. Where a schedule has changed recently, the note should say so, and the result should not be called a benchmark until the terms match.