Chapter 15.4
Water Stewardship
Water is no longer something you site around — it is something you engineer out, account for end-to-end, and earn a social license against; the fork between evaporative cooling and closed-loop is a multi-decade commitment to either a PUE penalty or a water-politics risk, and you cannot escape both.
What you'll decide here
- Whether this site evaporates water (low-PUE, water-exposed) or runs closed-loop/dry (zero-process-water, energy penalty) — the irreversible fork that sets your basin risk, your social license, and roughly 0.05–0.10 of your annualized PUE for the asset's life.
- Which water source you contract for — potable, reclaimed/non-potable, or harvested/grey — because reclaimed water is the difference between a defensible permit and a denied one in a stressed basin, even when it raises capex.
- What you commit to disclose: source-split, on-site (Scope-1) vs total/embodied (Scope-3, including the water behind your electricity) water footprint — and whether 'water-positive' is a credible volumetric-replenishment program or a marketing claim a regulator will pierce.
- Your blowdown, cycles-of-concentration, biocide, and ZLD/discharge strategy — the operating decisions that determine whether you have a Clean Water Act permit problem, a Legionella liability, or a salt-disposal cost nobody budgeted.
- Whether a basin-level water-risk screen gates the site at all — run it before, not after, you contract power (the siting gate lives in Chapter 3.7).
For two decades water was a footnote in data-center design: cheap, abundant near the cheap-power and cheap-fiber sites operators already wanted, and invisible to the public. The AI build-out ended that. A single hyperscale AI campus can consume up to ~5 million gallons a day — the municipal draw of a town of 10,000–50,000 people — and it does so in exactly the arid, power-rich basins (Texas, the US Southwest, the Gulf, inland Spain) that the power-bound era pushed operators toward. The result is that water has hardened from a siting footnote into a top-three permitting pillar, alongside power and zoning, and into the most visible front in the community fight over whether a campus gets built at all.
This chapter is the stewardship view of water — the operating, accounting, and social-license discipline that an operator owns for the life of the asset. It assumes the upstream siting gate (is there water, of what seniority, in what basin, under what regulator?) has been run in Chapter 3.7, and that the cooling-plant and cooling-tower engineering lives in Chapter 5.8. Choosing wrong costs you in PUE, in permit risk, in capex, and in the social license that is now as binding a constraint as the interconnection queue. The governing tension is one you cannot make disappear, the energy–water nexus: the cooling design that saves water spends energy, and the one that saves energy spends water. Stewardship is the practice of choosing which one to spend, per site, and accounting for it honestly.
The energy–water nexus: why you cannot win both
Heat rejection is the seam where energy and water trade against each other, and the trade is close to zero-sum. Evaporative (open-loop) cooling — cooling towers and adiabatic assist — exploits the latent heat of vaporization: evaporating a gram of water removes ~2,260 J, an enormous thermal lever that lets a tower reject heat at a wet-bulb temperature far below the dry-bulb air. That is why evaporative plants deliver the best PUE (a well-run evaporative or hybrid plant lands in the ~1.1–1.3 band), and why ~85% of the water a data center withdraws is consumed — it leaves as vapor, not as discharge. Closed-loop and dry (air-cooled) designs reject heat to the air through a dry cooler or a sealed liquid loop with no evaporation, consuming essentially zero process water — at the cost of a higher approach temperature, more compressor hours in hot weather, and a PUE penalty that commonly runs ~0.05–0.15 higher annualized, concentrated in the summer peak that also stresses the grid.
This is the fork that defines a water-stewardship strategy, and it is irreversible in the same sense the cooling-modality decision is: you plumb and permit a campus for towers or you do not. Choose evaporative and you have bought the best energy number and a permanent water-consumption line that a regulator, a journalist, and a county board will all scrutinize for thirty years. Choose closed-loop/dry and you have neutralized water-politics risk and unlocked arid, power-rich sites — at a standing energy tax on every hot-weather hour for the life of the building. There is no free corner of this design space; stewardship is choosing the right penalty for the basin you are in.
WUE drivers and the source-strategy decision
Water Usage Effectiveness (WUE) — liters of water consumed per kWh of IT energy — is the headline metric, defined in ISO/IEC 30134-9 and treated in full alongside the rest of the metric stack in Chapter 15.1. The industry average for evaporatively-cooled facilities sits around ~1.8–1.9 L/kWh; best-in-class evaporative designs reach ~0.3–0.7 L/kWh; and closed-loop/dry designs trend to ~0. Microsoft reported a fleet WUE of ~0.30 L/kWh in FY2025 (down from a 2.3 L/kWh baseline) and rolled out next-generation closed-loop, zero-water-evaporation designs that save over 125 million liters per facility per year. The headline number, though, hides three drivers an operator actually controls.
Driver one — cooling modality. The evaporative-vs-closed-loop fork above is the dominant lever; nothing else moves WUE as far. Driver two — cycles of concentration. In an evaporative plant, the same makeup water can be recirculated several times before dissolved-solids buildup forces a blowdown. Running more cycles of concentration cuts makeup and blowdown but raises scaling, corrosion, and Legionella risk — a direct water-vs-chemistry trade managed in Chapter 5.8. Driver three — water source. WUE counts consumed liters regardless of quality; the stewardship question is not just how much, but which water — and that is where the source strategy becomes the most defensible lever you have.
The source decision is a fork in its own right. Potable water is the path of least engineering resistance and the path of greatest political resistance — Loudoun County data centers drew ~899 million gallons of potable water in 2023 (a ~250% jump), and ~57% of US data-center water still comes from potable sources, the single fact that most reliably mobilizes community opposition and ratepayer-cost arguments. Reclaimed / non-potable water (treated municipal effluent, industrial grey water) costs more in treatment, conveyance, and sometimes a dedicated purple-pipe agreement, but it is increasingly the condition of the permit itself: water-stressed jurisdictions now mandate reclaimed sourcing, and a reclaimed-water commitment is often what converts a contested rezoning into an approved one. Harvested / on-site sources (rainwater capture, condensate recovery, treated process water) are marginal in volume but valuable in the disclosure narrative. The fork's downstream cost is asymmetric: potable is cheap to build and expensive to defend; reclaimed is expensive to build and cheap to defend.
| Strategy | Annualized PUE | WUE (L/kWh) | Water source fit | Basin / siting fit | Primary downstream cost |
|---|---|---|---|---|---|
| Open evaporative (towers + adiabatic) | ~1.1–1.3 (best energy) | ~1.5–1.9 typ.; ~0.3–0.7 best-in-class | Reclaimed strongly preferred; potable is the political liability | Water-abundant, cool, power-constrained basins | Permanent consumption line; blowdown/ZLD; Legionella program; social-license exposure |
| Hybrid (dry + adiabatic trim on peak days) | ~1.2–1.35 | ~0.2–0.6 (water only on hottest hours) | Reclaimed for the trim; small makeup volume | Hot-but-not-extreme; the pragmatic 2026 default | More plant complexity; still permits as a water user |
| Closed-loop liquid + dry coolers (zero-evap) | ~1.2–1.4 (penalty in summer) | ~0 process water | Potable fine — tiny one-time loop fill, not ongoing draw | Water-stressed, hot, or politically exposed basins | Standing energy/PUE tax on hot-weather hours; higher heat-rejection capex |
| Full air-cooled / dry (no liquid) | ~1.3–1.5+ | ~0 process water | Potable fine; negligible | Arid sites; density-capped, legacy or low-density inference | Cannot reach AI rack densities; worst energy/carbon per unit work |
The table is the same kind of cascade the workload archetype drives in Chapter 1.1: the leftmost column is the input you control, and everything to the right is a consequence you inherit for the life of the asset. The crucial 2026 shift is in the third row. Direct-to-chip liquid cooling — now the default at AI rack densities (Chapter 5.4) — is frequently confused with water consumption because it is 'water cooling.' It is not. The technology-cooling loop is a sealed, recirculating circuit; its water is filled once and topped up rarely. What consumes water is the heat-rejection stage at the back of that loop — and a closed-loop liquid plant rejecting to dry coolers consumes essentially none. This is why the dense-liquid future is, if anything, easier to make water-neutral than the air-cooled past: the heat is already in a contained loop, and you get to choose how to reject it.
Water quality, blowdown, Legionella & discharge compliance
An evaporative plant is not a closed system; it is a continuous flow of water in (makeup) and water out (evaporation plus blowdown). As pure water evaporates, dissolved minerals concentrate in the recirculating loop, and at some threshold — the cycles of concentration — the loop must dump a fraction to drain (the blowdown) and replace it with fresh makeup. That blowdown is a regulated discharge: it carries elevated total dissolved solids, conditioning chemicals, biocides, and corrosion inhibitors, and in the US it falls under the Clean Water Act NPDES (Section 402) permitting regime if discharged to surface water, or a local pretreatment/sewer-use agreement if sent to a POTW. Underestimating blowdown chemistry is how a campus that cleared its withdrawal permit gets blindsided on the discharge side.
The other side of cycling water harder is biology. A cooling tower is a warm, aerated, nutrient-bearing aerosol generator — textbook habitat for Legionella pneumophila, the pathogen behind Legionnaires' disease, and an outbreak traced to a data-center tower is a reputational and legal event of a different order than a permit dispute. ASHRAE Standard 188 is the governing answer: it mandates a written Water Management Program built on a risk-assessment of every device where water contacts air, with defined control limits (temperature, biocide residual, conductivity), routine monitoring, validation, and documented corrective action. ASHRAE Guideline 12 supplies the supporting risk practice. This is not optional hygiene — in many jurisdictions an ASHRAE-188-conformant program is the de-facto standard of care, and its absence is what plaintiffs and regulators point to after an incident.
Deep dive: ZLD, blowdown minimization, and the salt-disposal cost nobody budgets
In a water-stressed basin with no surface-water outfall and a POTW that will not take saline blowdown, the operator is pushed toward Zero Liquid Discharge (ZLD) — treating the blowdown stream (brine concentrators, evaporators, crystallizers) until the only output is distilled water for reuse and a solid salt cake for landfill. ZLD eliminates the discharge permit problem and maximizes water recovery, and it is increasingly the price of admission in arid jurisdictions. But it is energy- and capex-intensive — evaporators and crystallizers are among the most energy-hungry equipment on a site — and it converts a water problem into a solid-waste problem: someone has to truck and dispose of the salt cake, a recurring opex line and a regulatory exposure of its own that rarely appears in the headline water narrative.
The decision tree is therefore: (1) can you discharge blowdown to a POTW or surface water under an achievable permit? If yes, optimize cycles and chemistry and discharge. (2) If no — saline basin, no outfall, or a no-net-discharge mandate — you are in ZLD territory, and the right move upstream is often to avoid the evaporative plant entirely (the closed-loop/dry fork), because eliminating evaporation eliminates the concentration problem at the root. ZLD is the expensive way to keep evaporating in a place that does not want you to; closed-loop is the way to not have the fight. → cooling-tower water chemistry in Chapter 5.8.
Water-positive accounting: the honest footprint vs the marketing claim
'Water-positive' has become the headline sustainability commitment of the hyperscaler era — Microsoft reports having met its water-positive goal in 2025, five years early; Google has committed to replenish 120% of the water it uses across its data-center watersheds by 2030 (~19 billion gallons/year of replenishment); Meta announced a water-positive-by-2030 strategy in December 2025 built on dry cooling and watershed restoration. The claims are real programs, and they are also the part of the water story most vulnerable to being pierced by a regulator or a skeptical community — because the accounting hides three distinctions that determine whether the claim is meaningful.
Distinction one — on-site vs total footprint. The water you withdraw and consume at the campus (call it Scope-1 water) is the visible number. But the electricity that powers the campus is itself produced with water — thermoelectric and hydroelectric generation evaporate enormous volumes — so the total footprint includes a large off-site / embodied (Scope-3) water term behind every kWh. A site that runs zero process water on-site can still carry a substantial water footprint through its grid mix. Honest disclosure reports both; a water-positive claim that quietly ignores the energy-embodied term is incomplete by construction.
Distinction two — replenishment vs reduction. 'Water-positive' is usually a volumetric claim: the operator funds watershed projects (wetland restoration, irrigation-efficiency, leak repair, aquifer recharge) that return more water to the basin than the campus consumed. That is a legitimate and valuable thing — but it is offsetting, not reduction, and the offsets are only as good as their additionality, permanence, and — critically — their locality. Replenishing a watershed in a wet basin does nothing for a stressed basin where the campus actually draws. The credible programs explicitly target same-basin replenishment; the weak ones average across geographies in a way that lets a thirsty site hide behind a wet one.
Distinction three — basin-level risk and social license. Water is the most local of all the sustainability variables. Carbon is global and fungible; a ton avoided anywhere counts. Water is not: the only basin that matters for a community's drought, its wells, and its ratepayers is their basin. This is why water dominates the social-license fight even when the absolute volumes are modest against agriculture or municipal use — and why source/total footprint disclosure, same-basin replenishment, and a reclaimed-water commitment are worth more to a project's license than any global metric. The disclosure frameworks that formalize this — CSRD/ESRS, ISSB, and the ISO 30134 WUE standard — are treated in Chapter 15.7.
Deep dive: the Scope-3 water term, or why 'zero-water on-site' is not zero-water
The cleanest illustration of why total-footprint accounting matters is the closed-loop, dry-cooled campus that reports ~0 L/kWh on-site WUE and then draws its power from a grid heavy in thermoelectric generation. Conventional thermoelectric plants (coal, gas, nuclear) reject waste heat through cooling towers or once-through cooling and consume water in the process — on the order of ~1–3 L/kWh of generation depending on technology, with evaporative-cooled thermal plants at the high end. A data center that has driven its on-site water to zero but consumes that grid power has simply moved its water footprint upstream to the power plant; the basin impact is real even though it is invisible on the campus meter.
This produces two non-obvious stewardship moves. First, clean-power procurement and water stewardship are coupled: shifting to wind and solar (which consume negligible operational water) reduces the embodied-water footprint at the same time it cuts carbon — one of the rare places the energy–water nexus points the same direction. Second, an operator that wants a defensible water-positive claim has to be explicit about scope: reporting on-site WUE alongside a total/embodied water footprint, the way leading disclosures now separate Scope-1/2/3 carbon. A claim that conflates the two — counting only the on-site number while running on water-intensive thermal power — is the kind of thing a CSRD auditor or an investigative journalist will surface. Honest scope discipline is the difference between a credible program and a claim that ages badly. → metric definitions in Chapter 15.1; clean-power procurement in Chapter 15.3.
Building a defensible water-stewardship program
Pulling the threads together, a water-stewardship program that survives a contested rezoning, a CSRD audit, and a drought year is built from a small number of decisions made early and documented honestly:
- Run the basin-risk screen before contracting power. Water-stress mapping, water-rights seniority, and basin-security under drought are siting gates, not afterthoughts — 63% of the US was in drought at points in 2025, and a groundwater-certificate denial (the Arizona model) can strand a campus regardless of how good the power deal was. → Chapter 3.7.
- Make the evaporate-vs-design-out fork explicitly, per basin. Default to closed-loop/dry in any stressed or politically exposed basin and accept the PUE penalty; reserve evaporative cooling for water-abundant, power-constrained sites where the energy win actually relieves the binding constraint.
- Commit to the most defensible source you can engineer. Reclaimed/non-potable wherever a treatment and conveyance path exists; treat a potable-only design in a stressed basin as a permitting liability to be eliminated, not a cost to be defended.
- Own the ASHRAE-188 Water Management Program and the blowdown/discharge chain as one system — cycles, chemistry, Legionella control, and NPDES/ZLD strategy optimized jointly, not by whoever reports the KPI.
- Disclose source-split, on-site WUE, and total/embodied footprint — and, if you claim water-positive, back it with same-basin, additional, permanent replenishment whose volumetric benefit a third party can verify.