Water affordability is moving from a utility-board agenda item toward a campaign issue. Circle of Blue reports that legislation on water affordability has stalled while the cost of basic goods and services keeps climbing, and its summary describes rising costs as "a leading issue in the midterm elections" (Circle of Blue, reporting by Brett Walton). The same summary says advocates are already preparing for the lame-duck sessions that follow the midterms. That timing matters for utilities. A bill that is not moving today may still be moving before most finance teams have finished their own analysis. Circle of Blue's report on the stalled affordability legislation is the source for the status described here.
A stalled bill is not a settled question. It is a deferred one. The arithmetic a utility faces does not change with legislative status. Capital renewal, treatment upgrades, purchased water, and labor costs continue to flow into rates whether or not an assistance mandate passes. Affordability, in practical terms, is a metric the utility can calculate on its own, and the value of calculating it now is that the answer is ready when the question arrives from a council member, a regulator, or a legislative committee.
Pick the metric and record its source
The most common approach expresses the annual water and wastewater bill as a share of household income. The ratio is simple, but each input carries a choice. A median household income shows the typical customer, while a lower-income quantile shows where strain concentrates. The median can hide the households that feel a rate increase first. The lower-income figure depends on the quality of the income data and on whether the income source matches the service area. Utility boundaries rarely follow census tract lines exactly, so the result is an approximation, and the file should say so.
Record the income source, its vintage, the geographic area used, and the bill definition, including whether stormwater and wastewater are included. Two utilities can report different affordability ratios from the same rates because one of them counted a fee the other did not. A metric without its definition is a number that cannot be defended in a public hearing.
Model the bill by class and usage level
A single average bill conceals most of the distribution. Build the bill impact for residential customers at several usage levels, then add multifamily, small commercial, and any customers on fixed-charge structures. Fixed charges carry a tradeoff. Shifting revenue toward fixed charges stabilizes utility finances against falling sales, but it reduces the usage-based relief that conservation can offer, and that relief matters most to low-usage households. Show both the fixed and volumetric components so the effect of each design choice is visible in the table rather than argued from memory.
Run each scenario for the proposed rate path, not only for the current year. A single-year increase that looks modest can compound across a capital program. The file should show the cumulative effect at the lower-income level, because that is the figure any affordability provision will test.
Record arrears and assistance enrollment before anyone asks
Arrears, payment plans, disconnection notices, and assistance enrollment are the operational evidence behind an affordability claim. They are also the records most likely to be incomplete. Compile counts by month, by class, and by program, and keep them in aggregate form that protects individual customer information. The aim is to show trends and program reach, not to identify households. Note where data is missing, such as customers who never enrolled in assistance or accounts transferred between billing systems, because gaps in the record will be read as findings unless the utility names them first.
Keep the legislative file separate from the rate file
Track the bill's status as a monitored item, not as a rate assumption. Do not assume passage, and do not assume failure. The Circle of Blue summary does not describe the stalled legislation's provisions, so the file should not attribute any provisions to it. Once the official text is read, record each provision separately and model the rate effect of each one that could apply to the utility. Where a provision is uncertain, model two outcomes side by side: the rate path with an assistance requirement and the rate path without one. The comparison gives the board a clear view of the exposure without treating a pending bill as law.
The practical step this quarter is modest. Fix the metric definition, pull the lower-income ratio for each rate scenario, assemble arrears and assistance counts in aggregate, and date every source. A utility that has done this work before the lame-duck session will not need to rebuild the analysis under pressure when the next bill arrives.