“Why can’t they just use recycled water?” is becoming a standard question whenever a data center proposal reaches a public meeting. It is a fair question. And sometimes, reclaimed water is part of the answer.
But it is not a magic phrase that makes the water question disappear. Recycled water can reduce demand on a drinking-water system. It can be a meaningful part of a community’s water portfolio. It does not eliminate the need for a dependable source, treatment that fits the cooling system, pipes and storage, a plan for residuals, permits, operating agreements, or clear public accountability.
That distinction matters because the public can tell the difference between a real water plan and a reassuring slogan. For a developer, utility, or local government, the work is not simply deciding to “reuse water.” It is showing how the specific site will do it, what the arrangement means for the community, and what will be reported as conditions change.
Reuse is a water strategy, not an infinite loop
Cooling systems need water of a quality that protects equipment and reliably moves heat. In an evaporative system, some water leaves as vapor. As water cycles through equipment, minerals and other constituents can concentrate. A portion may need to be removed as blowdown so the system can keep operating. That water then has to be treated, discharged, managed, or reused again under an approved plan.
EPA’s recent case study of Quincy, Washington makes the point well. The City of Quincy and Microsoft built a utility that treats data-center cooling-water blowdown and returns it to the campus for cooling. EPA describes a closed-loop arrangement with dedicated treatment systems, more than 30 miles of pipe, and brine management to address the salts removed during treatment. It has reduced reliance on local potable groundwater. It is also a purpose-built utility system — not water circulating forever without make-up water, treatment, or a residuals plan.
That is not a criticism of reuse. It is why reuse deserves to be explained accurately. A project can obtain reclaimed water from a municipal wastewater facility, treat water on site, recirculate cooling water multiple times, or combine those approaches. Each pathway depends on the local source, water chemistry, climate, cooling design, infrastructure, and operating commitments.
The infrastructure comes before the promise
The Quincy example also shows the difference between a good idea and a deliverable project. EPA says the system took more than a decade to plan, design, construct, and test. The city owns and operates the reuse utility; Microsoft financed the capital investment and related operating costs under a long-term agreement. That may be the right model for one location. It is not a universal blueprint.
For another site, the central question may be whether a nearby treatment plant has dependable reclaimed-water capacity. It may be who pays for a new purple-pipe connection, a storage facility, or water-quality upgrades. It may be how the project handles seasonal demand, drought restrictions, treatment downtime, concentrated residuals, or future expansion. These are utility-planning and commercial questions as much as environmental ones.
They should be resolved with the water and wastewater providers early, before a public presentation turns an aspiration into an apparent commitment. Our data center development timeline explains why public-affairs work belongs alongside site selection, utility coordination, permitting, and construction planning — not at the end of the process.
Cooling choices shift the question; they do not end it
It is also too simple to treat “less water on site” as the only measure of a responsible cooling design. The peer-reviewed research is clear that cooling choices can involve trade-offs between direct water use and energy use, with indirect water and carbon impacts associated with power generation. Those trade-offs are site-specific. A technology that lowers local water use may change electricity demand; a design that works in one climate may not perform the same way in another.
That is why useful public information should distinguish among annual estimates, peak-day or seasonal conditions, water source, treatment, discharge or residuals management, and the conditions under which the operating plan changes. It should also say what has been decided, what is proposed, and what still depends on engineering, utility, or regulatory review. Precision builds more trust than a broad claim about being “water positive” or “water neutral.”
Permitting is local — and still developing
There is no single national reuse permit a data center can obtain. The Congressional Research Service notes that states generally hold the primary authority over water reuse and that treatment and monitoring requirements can vary by source and end use. The same report notes that operators have encountered unclear permitting pathways for recycled water in data-center cooling.
That context makes EPA’s April 2026 Water Reuse Action Plan 2.0 timely. One of the plan’s new actions is to help states and the regulated community share best practices so states can more readily permit recycled water for industrial and data-center cooling. It is an acknowledgement that reuse has real potential — and that the institutional pathway is not yet equally straightforward everywhere.
A credible project team should not imply that a federal initiative, a corporate target, or an early utility conversation settles the local approvals. It should identify the relevant agencies and providers, the applicable standards, the questions that remain, and the point at which a proposed water arrangement becomes final.
What communities should be able to see
A public-facing water plan does not need to become a technical specification. It does need to give people enough information to understand the decision in front of them. Before a data-center proponent says reclaimed water resolves the issue, the project team should be prepared to answer:
What is the source? Is it treated wastewater, on-site recycled water, potable water, another non-potable supply, or a combination? Is the source contracted, available subject to approval, or still being evaluated?
What is the expected demand? What are the projected annual and seasonal demands, and what facility or weather conditions materially change them?
What treatment and infrastructure are required? Who will build, own, operate, and pay for the necessary pipes, storage, treatment, and monitoring?
What happens to the water after cooling? How will blowdown, wastewater, brine, and other residuals be managed, and which entity has responsibility for that work?
What protects existing customers? How are costs, capacity, water-quality requirements, drought conditions, and curtailment triggers being addressed so that ratepayers are not left with an unclear exposure?
What will be reported after approval? Project information should not end at the permit hearing. The Bipartisan Policy Center and the National Association of Counties both point to accessible resource-use information, monitoring, and clear project updates as practical tools for communities and local decision-makers.
The communications work begins with the engineering record
The goal is not to overwhelm residents with water chemistry. It is to create a public record that is as specific as the underlying plan: a clear source, a clear pathway, an honest account of unknowns, and a way to follow up when the project changes. That is the foundation of a constructive conversation about water, infrastructure, and local benefits.
For teams preparing that conversation, our guide to data center water use and community concerns offers a practical public-information framework. Our data center public affairs strategy guide addresses the wider permitting, elected-official, utility, media, and stakeholder work around a proposal.
Sigler’s Global Data Center Brand case study reflects the firm’s market-positioning and communications work for a global data center company entering new markets. We also bring long-standing experience in water infrastructure communications and energy and infrastructure public affairs to help teams make complex project facts understandable before they become a source of distrust.
Sources
EPA: Water Reuse Case Study — Quincy, Washington · Congressional Research Service: Data Centers and Water · EPA Water Reuse Action Plan 2.0 · Privette et al., AGU Advances: Data Centers Water Footprint · Bipartisan Policy Center: Key Considerations for Data Center Development · National Association of Counties: Data Center Primer.
