A township board vote on a large water user settles land use, zoning, and sometimes a service agreement. It does not settle whether the system behind the meter can carry the load. That question sits in asset records, and those records are often thinner than the approval timeline assumes. A Circle of Blue story by Kelly House on a township vote that paves way for Michigan's second hyperscale data center places the issue in a regional frame. The series it belongs to argues that "water quality, affordability, and aging water infrastructure are vulnerabilities" that have been neglected for too long. The headline and summary do not say how the township's decision will be implemented, so what follows concerns the general mechanics rather than the specifics of that case.
What a Usable Asset Record Has to Show
A record that supports a capacity decision needs more than a list of pipes. It needs material, install date, diameter, valve locations, pressure zone assignments, pump and storage data, and a repair history tied to each segment. Each field answers a different question. Material and age indicate corrosion and failure risk. Diameter and zone assignment determine how a new demand moves through the network. The repair log shows where the system has already needed attention, which is often a better predictor than a condition score assigned from memory.
The mechanism matters because large new demand does not simply add a uniform draw. It changes flow direction, velocity, and residence time, particularly at the ends of dead-end mains and in storage that cycles more slowly than the planner assumed. Water age rises where flows fall, and disinfectant residual falls with it. A hydraulic model that was calibrated against field pressure several years ago may still look reasonable on paper while misdescribing the pipes that matter most.
Where the Records Run Out
Most utilities hold partial records. Some segments were verified by excavation, others were inferred from installation practice of their era, and some carry an "unknown" entry that no one has revisited. Condition ratings are frequently estimates built from crew judgment, not measured wall thickness or sampled coupons. None of this means the records are worthless. It means each conclusion should be tagged with how it was reached.
Verification has a cost. Excavating to confirm a service line material takes crew time, traffic control, and restoration, and it can only be done at the pace the budget allows. Desktop review is cheap, but it is biased toward whatever was documented well. A utility that ranks replacements using only the documented segments will tend to repeat the choices of earlier record keepers.
Where Affordability Enters
The affordability point in the series summary connects directly to the record. Capital plans are built from condition and capacity data. When that data is incomplete, replacement priorities tend to follow the loudest complaints, the most recent breaks, or the segments that are easiest to reach. Ratepayers then carry the cost of decisions that the record could not justify. A growth agreement that adds demand without a matching review of the network can shift that burden further, even when the agreement itself is lawful and well drafted.
The Same Arithmetic on Private Supply
Households outside a utility network face a smaller version of the same problem. A private well usually has a single test, often from the year it was drilled or first put into service. A change in taste, staining, or pressure may prompt a homeowner to look for treatment, and some will consult local RO specialists about options. A treatment choice made without a current sample is working from the same thin record that a utility would be using if it relied on undocumented pipes.
Questions to Put to the Utility
Before a growth decision is treated as settled, a utility's staff and its governing body can ask several specific questions. Which segments in the affected zone lack verified material records? When was the hydraulic model last checked against field pressure data? Does the service agreement define peak demand, or only average use? Are capital priorities tied to condition scores and capacity margins, or to complaints and convenience? The answers will not decide whether a project is wise. They will show how much of the decision rests on measured conditions and how much rests on assumptions that no one has yet tested.