Data center requests usually reach a utility as a load question, a land question, or a tax question. For the water side, the first useful question is how the facility will reject its heat, because that choice sets how much water leaves the system, in what form, and at what hours. The American Water Works Association (AWWA) has released a report to help utilities work through these requests. Water Finance and Management's coverage of the release notes that the subject "continues to occupy discussions across the water sector." The report is titled Cooling the Cloud: Considerations for Water Utilities Evaluating Data Center Development. This article does not restate its findings, which a utility should read in full.
How the cooling design changes the water record
Evaporative cooling towers reject heat by evaporating a portion of the circulating water. The vapor leaves the site, so that share is consumed rather than returned to the sewer. Towers also require blowdown, a regular discharge of concentrated water that keeps dissolved solids from building up in the loop. Blowdown has its own volume, temperature, and chemistry, and it carries the treatment chemicals added to the cooling water. One tower therefore creates two water questions: how much evaporates, and how much returns as blowdown.
Closed-loop and dry cooling designs reduce or remove evaporative loss, but they move the tradeoff onto electricity. Dry coolers rely on fans and heat exchangers, which generally draw more power than evaporative systems during hot weather. A lower water figure can therefore mean a higher power demand, and that demand may land in grid planning rather than on the utility's water side. Hybrid designs sit between the two and switch modes with ambient temperature. The annual water figure then depends on the local climate record and the operating schedule, not only on the nameplate design.
What to obtain before accepting a figure
Single gallons-per-day numbers are common in early requests and rarely give a utility enough to decide. A usable file starts with the cooling technology and the design day, meaning the hot-weather condition the system was sized to meet. It should also record average and peak water demand, with the hours in which peak use is expected, and the makeup water source. Whether reclaimed or other non-potable water was evaluated as an alternative belongs in the same file.
Blowdown needs its own entry: expected volume, temperature, chemistry, the proposed discharge point, and how that discharge would fit the utility's pretreatment requirements. Phasing matters as well, since many campuses add buildings in stages and each stage changes the demand curve. Finally, the file should say whether fire protection storage or other on-site reserves are part of the request, and how those reserves would refill. This list is a checklist for the utility's own model, not a template the developer must sign. Each item should carry the date received and the design version it describes, because later revisions often arrive without a clear note of what changed.
Capacity and contract terms
A peak that arrives in a few hot months can set main sizing, pump capacity, and storage needs long before average use matters. Utilities typically compare the requested peak against available capacity in the service area, including capacity already reserved for other customers. Where the request would require new mains, pumps, or treatment, the question of who funds that work becomes central, and the answer follows the utility's own rate and capacity policies. Terms covering curtailment during drought, minimum bills, or reserved capacity should be reviewed with the utility's rate staff and its legal counsel, since the terms and the governing rules vary by jurisdiction and by utility.
Keep the file the design can change
The request file should be treated as a living record. A developer that switches from evaporative to dry cooling, or adds a building stage, changes the water and wastewater picture, and the capacity assumption the utility first used may no longer hold. Keeping the design basis, the assumptions, and each revision together shows which figure supported which decision, which is more useful later than the first number on the page.
Public information on data center water use remains uneven, and figures are not always reported on a common basis. A utility can ask for the basis behind any number, but the figures it relies on should come from its own modeling and from the conditions of its service area. Where a developer's basis is incomplete, the uncertainty belongs in the record and in the decision, not in the margin.