Water use is the single most common reason communities organize against a data center. It shows up in more than 40 percent of contested US projects, more than any other issue. So if you're running community engagement for a data center in pre-development or permitting, water is the concern you have to be ready to answer first, clearly, and on the record.
Addressing it well is not about winning an argument over gallons. It's about disclosing real numbers, answering the specific questions residents are asking, and tracking every water commitment you make so you can prove you kept it. This guide covers how to do that.
Why water use drives more opposition than any other issue
Three things make water uniquely combustible for data center projects.
First, the numbers are large and easy to compare to everyday life. A medium-sized data center can use up to 300,000 gallons of water per day for cooling, roughly the daily use of 1,000 households. Large facilities can reach up to 5 million gallons per day, comparable to a town of 10,000 to 50,000 people. When a resident hears their new neighbor will use as much water as their whole town, the reaction is immediate.
Second, water is local in a way electricity is not. Power comes from a regional grid. Water comes from the same aquifer, river, or municipal system that residents, farms, and existing businesses draw from. In drought-prone or fast-growing regions, that turns a facility into a direct competitor for a resource people already worry about.
Third, secrecy makes it worse. Much per-facility water data is treated as proprietary, and communities know it. When operators will not say how much water a project will use or where it will come from, residents fill the gap with the highest number they have read. Silence does not lower the temperature. It raises it.
The pattern is visible in real projects. A Google facility in South Carolina faced sustained opposition to its proposed groundwater use, prompting a negotiated shift to surface water. In Memphis, a new AI data center raised alarms about daily withdrawals from the aging public water infrastructure. In Minnesota, environmental groups pressed for reuse, recycling, and compensation for potable water use, and the state went on to enact water-efficiency and non-potable-sourcing requirements. These are engagement failures and successes, not just engineering stories.
What water questions do communities ask?
Before you build a single slide, get specific about what people want to know. Generic sustainability language answers none of these. The real questions, in the order they usually come up, are:
-
How much water will this use? Residents want daily and annual figures, not a national average or an industry range. If you give a range, they will assume the top of it.
-
Where does the water come from? Potable municipal supply, groundwater wells, surface water, or recycled and reclaimed water. Most operators currently draw from municipal public water systems. This is often the question that matters most, because drawing potable water in a water-stressed area is what turns concern into organized resistance.
-
How much water is consumed versus withdrawn? Withdrawal is the process of water being pulled from the source. Consumption is water lost to evaporation and not returned to the system. The US Geological Survey distinguishes the two, and so should you, because the honest consumption figure is usually far lower than the withdrawal number residents fear.
-
What happens on the hottest, driest days? Annual averages hide peak demand. A facility averaging 4 million gallons a day can peak far higher when it is hot. Communities in water-stressed regions want the peak, not the average.
-
Who pays for the water infrastructure? New capacity, pipes, and treatment upgrades cost money. Residents want to know whether the developer covers those costs or if they're reflected on the local water bill.
-
What did you promise, and how will we know you kept it? This is the question most projects answer poorly. A commitment with no tracking and no reporting is a commitment residents will assume you broke.
How to address water concerns in your engagement
Lead with real numbers, including the ones that look bad
Disclose projected daily and annual water use, the source, the split between withdrawal and consumption, and peak demand. Put potable versus non-potable front and center. The instinct to withhold or soften these numbers is the single biggest engagement mistake in this category, because non-disclosure is exactly what fuels distrust.
Only about half of operators tracked their water use at all as of 2021, and communities have noticed. Being the developer who shows up with specific, sourced figures is a differentiator, not a risk.
Explain sourcing and cooling choices in plain language
If the project uses recycled or reclaimed water, closed-loop cooling, or air cooling, say so and explain what it means for the local supply. Closed-loop and recycled-water approaches are established practices for conserving potable water in dry regions and can substantially reduce freshwater use.
You don't need to turn residents into cooling engineers. You need to connect each design choice to what they care about: how much local drinking water the facility will and will not affect.
Bring watershed context, not just site numbers
A single facility's use means little without the local picture. Water impact is best understood at the watershed level, relative to local supply and competing demands from homes, agriculture, and existing industry.
Bring that context to the meeting yourself. If you don't, an opposition group will bring their own version, and it won't be generous.
Offer enforceable commitments, and be specific
Vague pledges to be a "responsible water steward" convince no one. Specific, enforceable commitments do: a cap on potable water use, a firm date to transition to recycled water, funding for infrastructure upgrades, or a community benefit agreement tied to water.
Communities and policymakers increasingly expect these to be written down and enforceable, not aspirational. Some jurisdictions are now legislating around exactly this, from consumptive-use permit limits to bans on the non-disclosure agreements that once kept these deals hidden.
Report back on what you committed to
A water commitment is only as credible as your ability to show you met it. That means tracking each commitment, who made it, when, to which community or official, and reporting actual performance against it over time.
This is where most projects lose trust: not at the promise, but at the follow-through nobody documented.
Why tracking your water commitments is the part that holds up
Everything above produces a paper trail: the numbers you disclosed at each meeting, the questions residents raised, the commitments you made in response, and what you delivered. When a project faces a public hearing, a permit challenge, a records request, or an organized opposition campaign, that trail is what proves your engagement was real.
The problem is that on most projects, this record does not exist in one place. Water commitments get made verbally at a meeting, captured in one person's notes, referenced in an email thread, and repeated differently by the project manager, the builder, and the owner, who often engage the same community separately with no shared record. When the challenge comes, there's no single, defensible account of what was promised and to whom.
This is the specific gap Jambo is built to close. Jambo is Stakeholder Relationship Management (SRM) software: a single secure system of record for every contact, conversation, and commitment across a project. For water concerns, that means every disclosure, question, and commitment logged in one place, with automatic follow-up flags so a promised recycled-water transition or infrastructure payment does not slip. Everyone working on the site, including outside consultants, works from the same record, so the developer, builder, and owner tell one consistent story. And when a project faces a hearing or a legal challenge, the full history is there to export.
For teams handling sensitive landowner, sourcing, and political information, where that record lives matters. Jambo stores customer data in the US, processes AI in the US, and never trains AI models on customer data. It runs on Amazon Web Services (AWS) US hosting and holds ISO 27001:2022 and ISO 27017:2015 certification. For a data center developer whose water-sourcing negotiations and community intelligence cannot leak, those are the specifics procurement and IT will ask about.
Address the concern before it becomes the campaign
Water opposition rarely starts with the water. It starts with the sense that a developer is hiding something. The projects that clear permitting are the ones that put real numbers on the table early, answer the specific questions residents ask, and keep a record that proves every water commitment they made.
For a deeper look at why community opposition has become the top risk to data center timelines, see our blog on community opposition and data center development.
If you want to see how a single record of every water commitment holds up under a hearing or a records request, book a Jambo demo.
