Find your situation. Get the right tools. Take action today.
Used by communities across 40 states. Updated based on what is actually working.
What describes your situation right now?
You just found out. Before you do anything else, work through these five steps. Speed matters because developers have been lobbying officials privately for months before any public announcement.
This determines everything. Call your county or city planning department and ask two questions:
If no application has been filed yet, you have maximum time. If a vote is already scheduled, jump to Path 2 right now.
This is the single biggest thing communities miss. In a recent review of Virginia municipalities with data centers, 80% had NDAs between local officials and the developer, signed before the public knew anything.
File a public records request asking for:
An NDA, once exposed, becomes a powerful public argument: officials agreed to keep this secret from you. That framing works across every political line.
File a public records request immediately. In most states you can do this by email. Your state's law may be called FOIA, Open Records Act, Public Information Act, or Sunshine Law.
Request these documents from your county planning department:
Fill in the bracketed fields and email to your county planning department.
| Type | What it means for you |
|---|---|
| Hyperscale (Amazon, Google, Microsoft, Meta) | Largest footprint. Can draw 100 to 500+ megawatts of power and millions of gallons of water per day. Highest impact on water, grid, and tax policy. |
| Colocation (third-party facility) | Rents space to multiple businesses. Smaller than hyperscale. Still significant, but water concerns are lower in most cases. |
| AI Inference / Edge (smaller, often unnamed) | Increasingly common in suburban and rural areas. Often backed by a hyperscaler using a shell company name. Check ownership carefully. |
You do not need a formal organization yet. You need three to five people who will show up and divide the work. Post in your neighborhood Facebook group or Nextdoor tonight.
Try something like: "Anyone else concerned about the proposed facility at [address]? Trying to understand what is happening and what we can do. Reply or message me."
Once you have a few people, assign these roles:
The clock is ticking. Here are the highest-impact moves you can make before a vote or hearing, in order of priority.
Call your county commissioner or council member's office. This is more effective than email at this stage. You want to be a named constituent on record before the vote.
This runs about 60 seconds. Stick to the facts. Your goal is to be on record.
Written comments submitted before a hearing create a permanent legal record. They carry more weight than spoken testimony in many jurisdictions, and they do not require you to stay until 2am.
What makes a written comment effective:
Most public hearings allow 3 minutes per speaker. This script runs 2 minutes 45 seconds at normal pace. Bring your facts. Stick to your time.
Headcount at a hearing moves public opinion and creates media attention, even when it does not directly move votes. Fifty people showing up sends a message that 50 letters cannot replicate.
You will hear this at the hearing, from neighbors, and from officials: "You are going to cost us hundreds of jobs and millions in tax revenue." Here are honest, fact-based responses.
In Warrenton, Virginia, 500 people showed up and a well-known public figure testified against an Amazon data center. The council voted 4-3 to approve it anyway. Two years later the community had replaced the entire council, and the new council buried the project in legal challenges. A lost vote is a recruitment event, not a final answer.
This is your most powerful post-vote tool and it requires moving fast. Most states have deadlines for filing procedural appeals.
What to audit with a local attorney:
This is what happened in Saline, Michigan and it is now a documented playbook developers will use again. The board voted 4-1 against rezoning 575 acres for an OpenAI and Oracle data center. Two days later, Related Digital and the landowners filed a lawsuit alleging exclusionary zoning. Construction broke ground months later despite the unanimous community opposition.
What exclusionary zoning means in this context:
Exclusionary zoning is a legal doctrine that says municipalities cannot use zoning to completely bar a legitimate land use from their entire jurisdiction. It was originally created to prevent wealthy communities from excluding affordable housing and minority residents. Developers are now turning it against rural farming communities to force data center approvals through over democratic votes.
The specific Saline argument: the township had an industrial zoning classification called I-1 on its books but had designated zero acres as I-1. Developers argued that was "window dressing" and that refusing to rezone any land for a valid industrial use was functionally exclusionary. Michigan courts agreed that was a viable legal theory. The township settled rather than fight.
What to do the moment a lawsuit is filed:
This doctrine is state-law specific. The exclusionary zoning argument that worked against Saline Township depends on Michigan's specific zoning statutes. It may not apply in your state in the same way. A local land use attorney needs to assess your exposure before any vote is taken, not after a lawsuit arrives.
The data center approval is only the first step. The developer still needs to connect to the power grid, which requires a separate utility interconnection application filed with your state's Public Utilities Commission (PUC). This process has its own public comment period.
If new transmission lines are required, those need separate approvals with separate public proceedings. Landowners in the path of those lines have independent standing to object.
Most communities only fight the rezoning vote. Here is what actually happens after that vote passes, in sequence. Each stage has its own public proceedings.
The first public fight. Most communities focus here. Once this passes, the developer has legal authority to proceed. Several more approvals are still needed.
State environmental agencies may require an assessment with its own public comment period. Water, air quality, and stormwater objections belong here.
Separate proceeding at your state water agency. Agricultural users and senior water rights holders often have stronger standing here than residential objectors.
The utility must connect the facility to the grid. Requires state PUC approval. New substations and transmission lines may require separate easements and permits.
This is where homes get taken. In Georgia, a utility used eminent domain to acquire over 330 properties, including 20+ homes, to build a 35-mile transmission line serving AI data centers. People who never fought the data center vote suddenly had no home. If your community approved a large facility, find out now whether transmission expansion is planned and whether your property is in the corridor.
Often the last public vote and the best negotiation leverage. The developer needs the tax break. Bring a specific Community Benefit Agreement with binding terms to this meeting.
This is the most durable tool available when everything else has been tried. In Warrenton, Virginia, residents voted out every single council member who supported the Amazon data center. In Cascade Locks, Oregon, voters recalled two Port Authority officials who approved a project. Both projects subsequently died or faced indefinite delay.
After the developer withdrew a proposed 300 MW data center from Apex, North Carolina, the town council passed a one-year moratorium on data centers anyway. The reason: to write rules before the next proposal arrived.
A moratorium does more than buy time. It creates the zoning guardrails that protect your community before the next proposal arrives.
The framing that works with officials: not "ban data centers forever" but "pause new applications for 12 months while we develop data center-specific zoning standards." That is a position most elected officials can support publicly without opposition.
Developers work in your community for 12 to 18 months before any public announcement. By the time news breaks, they have already met with officials, often under NDAs, and may have quietly changed your zoning code. Here is how to detect what is coming and get in front of it.
Check for these signals in your community right now. Each one may indicate a data center proposal is in early development.
Download or request your county's current zoning ordinance and search it for the words "data center." If the term appears as a permitted or conditionally permitted use, find out when that language was added and why.
Saline Township voted 4-1 against an OpenAI and Oracle data center. The developer sued two days later and construction started months after that. The legal weapon they used was the township's own zoning code.
Saline had an industrial zoning classification called I-1 on its books but had designated zero acres as I-1 anywhere in the township. Developers argued that was "window dressing" and that refusing to rezone any land for a valid industrial use was exclusionary zoning under Michigan law. The township settled because fighting would have bankrupted local government.
This vulnerability exists in many communities right now. Here is how to eliminate it before any developer arrives.
Option 1: Define data centers explicitly with specific standards.
Add data centers as a named, distinct use category in your zoning ordinance with specific requirements already written in: minimum setbacks from residential and agricultural land, maximum noise levels, water recycling minimums, job creation requirements, tax contribution floors. Once those rules exist, any developer must meet them. A developer cannot sue you for exclusionary zoning if you have a defined, equal-access path that applies to everyone.
Option 2: Eliminate unused industrial classifications.
If your township has industrial zoning classifications on the books but applies them to zero land, either designate specific limited parcels with comprehensive data center standards, or formally remove those classifications from your code through a public amendment process. A code that has never been applied to any land is the exact vulnerability Saline's developers exploited.
This is the most powerful proactive tool available. A moratorium on data center development gives your community 12 to 18 months to write data center-specific zoning standards before the first application arrives. Once standards exist, any future proposal must meet them.
How to get a moratorium passed:
The communities that move fastest when a proposal arrives already have relationships in place. Do this now.
Pick a tool. All of these are free to copy, use, and share.
Answer two quick questions first. Your answers change the math and the hearing language. Getting this wrong gives opponents an easy way to dismiss everything you say.
Does this facility connect to the public electrical grid?
What cooling system does the developer claim to use?
Request the draft tax agreement from your county to find the actual numbers. If the agreement is not public yet, file a FOIA request.
A Community Benefit Agreement (CBA) is a legally binding contract between the developer and your community, signed before final approval. It is enforceable. These are the terms worth fighting for.
These are the arguments you will hear from developers, officials, and neighbors. Tap each one for a fact-based response you can use in person, on the phone, or at a hearing.
Developers and their attorneys will sometimes use federal AI policy to make communities feel their opposition is now illegal or irrelevant. Here is what the policy actually says, and the critical protection it preserves for local communities.
On December 11, 2025, President Trump signed an executive order directing the Justice Department to set up an "AI Litigation Task Force" to challenge state AI laws, and directing Commerce Secretary Howard Lutnick to evaluate state regulations that conflict with federal AI policy.
What it targets: Software regulation, specifically laws requiring AI models to disclose training data, report outputs, or meet safety standards. This is about how AI systems operate, not where data centers are built.
What it explicitly protects: The order specifically excludes from preemption "state laws relating to AI compute and data center infrastructure." Your community's right to regulate data center siting, zoning, water use, noise, and local impacts is explicitly preserved.
In March 2026, Senator Marsha Blackburn released a 291-page discussion draft called the TRUMP AMERICA AI Act. As of this writing, it has not been formally introduced or referred to a committee. It is a proposal, not a law.
The bill would, among other things, require third-party political bias audits for AI models, modify Section 230 liability protections, and preempt certain state AI regulations. It has significant opposition from both sides of the aisle.
None of these proposals change local zoning authority over data center siting.
In July 2025, President Trump signed an executive order streamlining federal permitting for data center projects over 100 megawatts or $500 million in investment. This is separate from the December 2025 AI executive order and directly affects how fast large projects can move through federal review.
What it does: Large projects meeting those thresholds get expedited review across federal agencies. Environmental reviews, transmission approvals, and federal land use decisions that would ordinarily take years can be compressed significantly under this order.
What it means for communities: Every project large enough to trigger the exclusionary zoning argument, meaning any hyperscale facility, is almost certainly large enough to fall under this permitting order. The window between when a developer files an application and when federal approvals are in place is now shorter than it was two years ago. Communities that are not already organized and engaged before a proposal arrives will find themselves playing catch-up against a faster-moving federal timeline.
What it does not do: It does not override local zoning authority. State and local land use decisions are still local. The order affects federal permitting tracks, not county planning commission votes. Your local process remains the primary lever. But your local process now runs in parallel with an accelerated federal track rather than a slower one.
Data centers that store or process data are subject to lawful government data access requests. Two mechanisms are worth knowing about as a community member:
A data center approved in your community is physical infrastructure that can be legally compelled to comply with these access requirements. Two questions worth asking on the public record at any hearing:
These are accountability questions, not conspiracy theories. They rarely get prepared answers. That is the point.
Every term explained in plain language.
You are not fighting this alone. Communities across 40 states have been through this fight and share what they have learned.
Built and maintained by
Hunter Carrithers
@DigitalOilHunter
digitaloilhunter@gmail.comFree to share with attribution and link to the current version.
Version: May 2026
This section was added in May 2026 following a major investigative report. If you are organizing opposition to a data center, you need to read this before you do anything else.
The honest picture matters here. Overstating the risk makes people afraid to participate in lawful civic processes. Understating it leaves people unprepared.
What the documents show:
What the documents do not show:
Public planning commission hearings, county commission meetings, and town council sessions are constitutionally protected forums for public comment. The following activities are legal and protected regardless of fusion center monitoring:
If you are removed from a public meeting for speaking against a data center, document the incident immediately: time, location, names of officials present, what you said, and what happened. That documentation belongs in the public record and may support a civil liberties complaint.
The documents confirm that for-profit contractors are scraping public social media for data center opposition content and feeding it to federal agencies. This does not mean you should stop posting. It means you should be deliberate about what you post publicly versus what you coordinate privately.
Practical steps that matter now:
If you believe law enforcement or contractors are monitoring your meetings or online activity, you can document that and create a public record of your own.
The surveillance of data center opposition is not an isolated policy. It connects directly to the other things this playbook has documented.
The federal government has designated data centers as critical national security infrastructure. It subsidizes their construction with state taxpayer money through long-term tax exemptions. It has created legal tools to challenge state laws that slow their development. It legally compels these facilities to comply with government data access requests through National Security Letters and FISA orders. And now it monitors and categorizes the people who oppose them as potential extremists.
None of that is a conspiracy theory. Every element of it is in public documents. The FOIA request is in the Wired story. The executive order is in the Federal Register. The NSL authority is in federal statute. The tax agreements are in county commission minutes.
That complete picture, stated clearly and without hyperbole, is the most powerful argument available to communities fighting these projects. Not fear. Not outrage. Just the documented facts about what is actually happening and what accountability would actually look like.