The AI data centre backlash has moved from planning meetings into midterm elections, with candidates in both parties distancing themselves from projects their own leaders once courted, as pressure mounts for a binding national settlement between the industry and host communities.
Opposition is scrambling races from Ohio to Wyoming. Pollster Frank Luntz was recently asked on CNBC how to ‘sell data centres to voters’. President Trump said the industry could use ‘a little public relations help’. Both frame the problem as one of communications. Critics say the real issue is what communities are being asked to accept.
Pennsylvania sets the template on AI data centre backlash
Pennsylvania Governor Josh Shapiro removed AI data centres from the state’s fast-track permitting programme and required local approval before projects proceed. His Commonwealth of Pennsylvania Official Newsroom confirms the Executive Order requires developers to make legally enforceable commitments on power, water and community benefits through a Consent Order and Agreement.
The order also bars state agencies from using non-disclosure agreements that can hide project terms.
Pennsylvania’s approach is being watched nationally, in part because the investment stakes are high. The Hill reports that Amazon received permission last year to invest $20 billion to construct two data centres in Luzerne and Bucks counties, illustrating the scale of projects now subject to the new rules.
The scale of the problem
At least 4,000 data centres operate nationwide, with roughly 3,000 more planned or under construction. Lawrence Berkeley National Laboratory, an Energy Department research lab, estimates that data centres could consume between 9.5% and 15.3% of US electricity by 2030, up from about 4.7% in 2024.
Gallup found that 71% of Americans oppose an AI data centre in their area. In a survey of 1,566 voters, Veleonis and co/efficient found that three in four chose no company or were unsure which company they could trust to operate one responsibly. Half cited electricity, water or other environmental effects when asked what they would want to know about a local project.
Many facilities use evaporative cooling, which consumes water to remove server heat. Communities face the risk of higher electricity bills, infrastructure costs, prolonged construction disruption and pressure on local water supplies. The industry’s response has focused on investment totals, construction jobs and competition with China.
What a workable bargain looks like
The core demand from communities is straightforward: companies should pay the costs their projects create, not pass them to existing residents and ratepayers.
On electricity, that means each facility carrying its own contract rather than paying the general commercial rate. The contract should include a minimum payment for reserved capacity, require the developer to finance new substations and grid connections, and impose an exit fee if a project is abandoned. New regional supply should cover the facility’s demand; drawing on existing generation without adding new supply tightens the market and can raise everyone else’s bills.
The White House has issued a Ratepayer Protection Pledge adopting this principle, but voluntary promises need binding utility contracts to carry weight. AEP Ohio illustrates the gap: by the utility’s account, developers initially sought more than 30,000 megawatts, nearly three times its system’s peak demand. The queue fell to about 13,000 megawatts at the paid-study stage and 5,642 megawatts in signed contracts under a new tariff structure.
Every project should publish a plain-English fact sheet before approval, covering electricity and water use, cooling method, power source, public incentives, permanent jobs and contributions to local infrastructure. Independent experts should verify operating data after opening. Agreements involving public money should remain public, with false claims triggering penalties and repayment of incentives.
In return, governments should honour agreed tax and permitting terms and move compliant projects through a clear timetable. Pennsylvania has written much of the protection side of this bargain. The test now is whether any state pairs those protections with a guaranteed speed of approval, to show which developers mean what they say.
