Essay #6 made the case that organized opposition works often enough to matter — nearly a third of contested projects get cancelled, suspended, or shut down. This essay is about the specific, repeatable tactics behind those wins. The good news is that this playbook has been tested, refined, and documented by people who have actually stopped data centers, not theorized about it. You don’t have to invent a strategy from scratch.
The Halt the Harm Network has mapped out a strategic framework identifying seven distinct stages in a data center’s development where organized opposition has proven effective. Understanding which stage your local project is currently in determines which tactics will actually work.
The earlier in this sequence you engage, generally, the more leverage you have — but as the Monterey Park and Utah examples in the previous essay demonstrate, meaningful wins are still achievable even at later stages, including after initial approval.
Elena Schlossberg, a former middle school counselor from Haymarket, Virginia, started organizing against data centers at her kitchen table back in 2014. Over a decade, she developed and refined a tactical sequence that other Virginia communities have successfully replicated — what she calls, half-jokingly, “a 12-step program in stopping data centers.” Some communities have stopped projects using only a handful of the steps, suggesting the full sequence is a toolkit to draw from, not a rigid checklist.
The Chesapeake, Virginia case shows how quickly this can work even on a small scale. Residents Dennis and Nancy Cashman learned about a proposed data center half a mile from their home through a neighborhood social media post. They printed 200 yard signs, joined roughly 200 other residents at a single city council meeting, and successfully convinced the council to vote against the rezoning the project required. No lawsuit, no years-long campaign — just sustained visible turnout at the decisive meeting.
One of the most effective and underused tactics is simply requesting the public records a developer is required to file. Permitting and licensing documents often reveal the true scale of a project’s water and power footprint in far more granular detail than what’s presented in public marketing materials or initial community presentations. In Spain, journalists investigating a proposed Amazon Web Services facility uncovered the true extent of its water and power use only after digging through planning and licensing files — information the company had not volunteered.
In the U.S., this same approach applies through state public records laws and freedom of information requests directed at the relevant zoning board, environmental agency, or public utility commission. Don’t wait for a developer’s presentation to tell you what a project will consume. Request the underlying filings.
Communities have multiple distinct legislative tools available, and choosing the right one for your situation matters. The most widely used and effective tactics are local ordinances and zoning changes that ban development outright, temporary moratoriums that pause new applications, outright permit rejections by local legislative bodies, and ballot measures or referendums that let voters decide directly. Monterey Park ultimately used three of these in combination: an ordinance banning data center construction, a declaration that data centers constitute a public nuisance, and a permanent ballot measure — a sequence that moved from temporary to permanent protection.
“Local government has the power to stop infrastructure development that is supporting a national agenda. It speaks to the power of local politics — when there are mechanisms in place for actually wielding that power.” — Common Dreams analysis of the anti-data center movement, April 2026
Not every fight ends in outright cancellation, and that’s a legitimate outcome to plan for. Community Benefits Agreements — legally binding contracts negotiated directly with a developer — can secure tangible, enforceable commitments even when a project is going forward regardless: protected local hiring requirements, caps on water and noise, funding for independent environmental monitoring, or direct community investment funds tied to the facility’s operation. The leverage to negotiate a meaningful CBA is highest before final approval, which is why pursuing one in parallel with outright opposition — rather than waiting until a project is a foregone conclusion — tends to produce the strongest terms.
One of the most strategically useful facts about this movement is that it does not divide along the usual partisan lines. Projects have been blocked in both red states and blue states, opposed by both Republican and Democratic local officials — the Utah case in the previous essay, where a Republican Senate leader publicly pressured a Republican-favored project, is a clear example. When building a local coalition, actively recruit across the political spectrum rather than assuming this is a left-only or right-only issue. Concerns about water, property values, noise, and utility rates resonate regardless of party, and a visibly bipartisan coalition is harder for officials to dismiss as a narrow special interest.
Stopping or meaningfully reshaping a data center proposal is not a matter of luck or unusual circumstance — it follows a documented, repeatable pattern: identify which of the seven leverage points your project is currently at, pull the specific public records that reveal what’s actually being proposed, build visible and sustained turnout at the meetings where decisions get made, and use the full range of legislative tools available rather than assuming only one approach is possible. The communities that have won this fight did not have more money or more institutional power than the developers they faced. They had organization, persistence, and a plan. That combination, the evidence consistently shows, is enough.