The data center water fight is about local limits, not one national average

Opposition to a data center’s water use cannot be answered with a reassuring national average. The questions concern a specific water system. How much spare capacity does it have? What happens during drought? Who pays to expand it?

Virginia’s State Corporation Commission describes its October 2026 reporting assignment as covering contracted electricity demand, data center water usage and generator permitting. The reporting categories matter because a facility’s public impact crosses several systems. They are not themselves a finding that any proposed project is safe or unsafe. Virginia report description.

For a community deciding whether to approve a project, the first challenge is getting comparable information. A developer may describe annual efficiency while residents worry about the hottest week. Both figures can be accurate while answering different questions.

Why the cooling design matters

A data center converts electricity into heat that must be removed to keep equipment operating. Cooling choices affect the relationship between water demand and electricity demand. The political analysis therefore needs to assess the proposed facility as a system, rather than treating a water promise in isolation.

A useful application would identify the cooling technology, source of water, expected operating conditions and assumptions about future expansion. Without those details, a claim of low water use cannot be evaluated against the demands of the actual site.

“Water use” also needs a definition. Withdrawal describes water taken from a source. Consumption concerns water that does not return to that source in the form or period. A return flow may still raise questions about temperature, quality, timing and where it reenters the system.

These distinctions do not weaken a community’s objection. They make it possible to identify the objection accurately. A concern about an aquifer is different from a concern about the capacity of a treatment plant. The remedies and responsible authorities may differ as well.

The broader electricity consequences are explored in our article on who pays for data center power. Reducing one resource demand should not be described as eliminating the facility’s environmental footprint.

Annual totals can conceal the difficult day

A water utility needs to serve customers when demand is high, not only over an average year. An application that provides annual consumption without peak requirements leaves a key question unanswered.

Consider a hypothetical facility with modest average demand. Its use rises sharply when the surrounding water system is already strained. Its annual total would not show whether the shared infrastructure can meet that combined peak. This example illustrates a planning problem. It is not a measurement of an identified project.

The opposite caution also matters. A maximum design capacity is not evidence that a facility will draw that amount every day. Treating the highest technically possible demand as normal consumption can exaggerate the expected effect. A fair assessment presents expected and peak conditions with their different meanings.

Residents also need to know whether a permit covers the initial building or an entire campus. A low figure for an early phase may be accurate but incomplete if later phases require a separate, much larger commitment.

A clear disclosure would show what is allowed and how much water the site expects to use at opening. It would explain when expansion needs another public decision. That makes the boundary of the approval visible before the boundary becomes disputed.

The strongest case for community resistance

The strongest local objection concerns irreversible commitments under uncertainty. A community may be asked to reserve scarce capacity before residents can examine the assumptions behind the request.

Water infrastructure can serve many competing purposes. A town may reserve capacity for a large industrial customer. That can leave less room for housing, existing businesses or other public needs. Whether that tradeoff is material depends on the local system. It cannot be inferred solely from the size of the building.

Residents can reasonably request an explanation of drought restrictions. Does the facility face the same curtailment rules as other customers? Can it operate under reduced supply? Are emergency alternatives technically realistic and already permitted?

Those questions do not imply that industrial users have no legitimate claim to water. They ask whether the public decision has made the allocation explicit and whether the agreement remains workable under difficult conditions.

The distributive issue is equally key. A project may finance a connection but depend on a wider network improvement. The connection payment alone does not show that households will avoid higher charges or that future maintenance costs are fully funded.

The strongest case from developers

A developer can fairly object when opposition assumes that every data center uses the same cooling system or draws from the same kind of source. A site-specific design deserves a site-specific assessment.

A project may reuse an industrial site or draw from another supply. Its contract may also limit its effects on the public system. Those measures deserve examination rather than dismissal because they come from the applicant.

The limitation is that a promise must be connected to an enforceable design and operating condition. If a water-saving approach depends on future equipment, the public should know whether the equipment is required before opening. If the benefit depends on another organization’s infrastructure, that dependency belongs in the record.

Developers also have a reasonable interest in protecting security-sensitive details and legitimate commercial information. That interest does not necessarily require withholding aggregate consumption, the source of supply or the public utility’s financial exposure.

A balanced disclosure regime distinguishes information needed for accountability from information that would reveal the layout or security of a facility. Treating every operational detail as public is unnecessary; treating every material impact as confidential prevents meaningful consent.

Why a “water positive” promise needs a boundary

A restoration or replenishment project can provide a real benefit. The question is whether it addresses the impact under discussion. Timing, geography and additionality determine whether the comparison is persuasive.

If an offset occurs in another watershed, it may support a worthy project without restoring the capacity used by the host community. If the benefit occurs years later, it does not automatically solve a near-term supply problem. If the work would have happened anyway, attributing its entire benefit to the data center overstates the contribution.

These are tests for evaluating a claim, not findings that a named company has failed them. A reliable review identifies the company’s actual commitment and the method used to measure it before drawing a conclusion.

The same approach applies to a claim that a facility uses no water on site. That statement may describe its cooling equipment. But it does not by itself account for water associated with the electricity supply. Different boundaries can produce different answers without either calculation being arithmetically wrong.

Public discussion improves when the boundary is stated beside the claim rather than hidden in technical documentation. A reader should not have to guess whether a number concerns direct operations, construction or the wider supply chain.

Disclosure alone is not a permit condition

Information helps a community decide. But reporting does not automatically constrain an operation. An enforceable limit, an operating trigger and a remedy perform different functions from an annual disclosure.

A planning authority might require an applicant to show supply capacity before construction. A water provider might impose contractual charges or restrictions. An environmental agency might have separate authority over withdrawal or discharge. The applicable powers need to be established for the actual jurisdiction.

This is why local zoning decisions and utility agreements should be read together. A land-use approval can leave key water questions to another agency. The water provider may assume someone else has reviewed land-use impacts.

A strong public record makes those dependencies explicit. It states which decision remains outstanding, who can refuse it and whether work can begin before the decision is final. That reduces the risk that residents discover a major unresolved issue only after construction becomes politically difficult to stop.

The role of a temporary moratorium should be assessed in those terms. A pause can create time for a water-capacity review. It cannot substitute for completing that review.

What would show that a project is acceptable?

No universal water-use figure answers this question. A sound finding would compare expected and peak demand with the actual source. It would also assess existing commitments, drought plans and infrastructure.

It would also explain uncertainty. A proposed campus may have no committed operator. That can make it harder to model than a facility with a completed design. The uncertainty should affect the terms of approval rather than disappear from the public summary.

Monitoring after opening is part of the test. Actual consumption can be compared with the commitments that justified permission. If the project changes technology or scale, the agreement should identify whether another review is required.

Community benefits deserve a separate accounting. Tax revenue or construction employment can be relevant to the overall decision. But neither changes the physical capacity of a water source. Our fiscal analysis examines how to evaluate those benefits without treating them as an answer to every environmental objection.

What this analysis does and does not show

This article explains the questions a local water dispute requires. It does not calculate a national shortage, attribute a drought to a specific facility or claim that every data center creates the same burden.

The Virginia reporting description was reviewed November 5, 2026. Its existence supports the case for examining electricity, water and generators together. This article does not treat the report’s listing as verified facility-level consumption data.

Public-hearing complaints can identify issues that require investigation. They cannot show the prevalence of those views across the population. Likewise, an efficiency pledge can identify a proposed solution without proving that it will protect a specific community.

The decision ultimately rests on a transparent comparison between a specific project and a specific local system. Without that comparison, both alarm and reassurance risk running ahead of the evidence.

Photo credit

Representative file photo: Victor Grigas / Wikimedia Foundation, via Wikimedia Commons, CC BY-SA 3.0. The source photo is unaltered; the site may crop its display.

Differing perspectives

What safeguards should govern data centers’ local water demands?

Each position is summarized as its supporters make it, with equal weight and in alphabetical order. A summary is not an endorsement; the evidence for each is weighed in the story above.

• Pause growth until safeguards are adequate

  Who holds it: Food & Water Watch

  New development should pause until a regulatory framework addresses environmental and social harms. The group argues that continued construction risks committing communities before adequate protections exist. Public rules should be clear before construction starts.

  In their words: Food & Water Watch ↗

• Require firm financial commitments

  Who holds it: PUCO’s adopted consumer-protection approach

  New connections should proceed under rules protecting other customers against the cost of underused infrastructure. The regulator presents development and consumer safeguards as compatible objectives. Public rules should be clear before construction starts.

  In their words: Public Utilities Commission of Ohio ↗