A local vote that clears the way for a large data center is usually reported as a land-use decision. For a water utility, it is also the start of a service request that can run for decades. Circle of Blue, part of the Great Lakes News Collaborative, reported on a township vote that paves the way for Michigan's second hyperscale data center, and the headline is a useful prompt for utility staff, municipal attorneys, and anyone who reviews these agreements. The reporting available here is limited to the headline and a short summary, so what follows describes the questions a utility should ask about this class of project, not what any particular agreement contains.
The summary frames the regional context in a pointed way. It describes the Great Lakes as a place with abundant water, then states that "water quality, affordability, and aging water infrastructure are vulnerabilities" that have been overlooked. That pairing matters. Abundance at the watershed scale does not guarantee capacity at the pipe, the pump station, or the treatment plant that a single customer connects to. A lake can be full while a pressure zone is tight.
Start with the water balance
Large facilities reject heat through cooling systems, and the design choice determines where the load lands. Evaporative cooling towers consume water through evaporation and discharge blowdown to the sewer. Closed-loop designs usually need less makeup water but may draw more electricity. Air-cooled equipment reduces water demand at the cost of higher power demand and different peak behavior. Each design moves the burden between the water side and the power side, and a utility cannot evaluate the request without knowing which design was assumed.
The utility should obtain the design basis in writing, including average day, peak day, and any seasonal swing. Cooling demand often rises in hot weather, which is also when residential demand and irrigation peak. A projection that looks modest on an annual average can be significant on the hottest week of the year, and the service agreement should be built around the peak, not the mean.
Wastewater is part of the request
Cooling tower blowdown carries concentrated dissolved solids, treatment chemicals, and in some cases biocides. Whether that flow can enter the sanitary sewer depends on local discharge limits, the pretreatment program, and the receiving plant's capacity for conductivity, chemistry, and flow. Ask who sets the limits for this user, whether the facility needs an industrial user permit or equivalent authorization, and what happens to plant residuals and biosolids handling if the strength or volume changes after startup.
The discharge side often carries the longest tail of obligations. Monitoring points, sampling frequency, reporting forms, and the penalty path for exceedances should be defined before connection, not after the first upset.
Capacity and cost allocation
Pipe diameter, pressure zones, storage, pumping, and fire flow all enter the calculation. A single large customer may require a main extension, a booster station, or a storage upgrade that the utility builds ahead of revenue. The agreement should state who pays for that capacity, whether the customer posts security, how minimum bills are set, and whether the utility can reallocate capacity during a shortage.
Rate design determines whether growth pays for itself. If capital costs are spread across the broader customer base, existing residential customers may carry part of the expense. That is the affordability question the summary raises, and it is answered in the rate study and the special contract, not in the zoning record.
Shortage and curtailment terms
Specify curtailment priority in writing. Decide whether the facility is interruptible during declared shortages, what notice it receives, and how it reduces use. Require metering that reports customer-level consumption at a stated cadence, with a right to audit the meter and the data. Require notice before any change in cooling design, since a later switch to evaporative cooling can change the load after approval.
Reclaimed water can be offered as a supply alternative, but it is not a free substitute. It brings its own treatment, storage, distribution, and quality controls, and the terms for supply, pressure, and backup should be explicit.
What the record should separate
The summary does not describe the township's agreement, the cooling design, the expected water volume, or any conditions attached to the vote. A utility responding to this project should wait for the record and avoid assuming any of those details. A land-use approval establishes that a use may proceed under local rules. It does not confirm that water and sewer capacity exists, that discharge limits can be met, or that the costs of new capacity are allocated fairly. Those are separate determinations, and the file should show which body made each one, on what data, and under which terms.
For staff preparing a response, the practical step is a short list: design basis, peak demand, discharge characterization, capacity owner, cost recovery, curtailment priority, and metering rights. Each item should have a document behind it before the utility commits to service.