Start with the scoreboard, because the scoreboard is real and it is not friendly. Democrats won the Senate, flipping seven Republican-held seats. They won the House, projected at 219. They flipped four governorships and will hold a majority of them for the first time in sixteen years. In the same election, voters in ten states decided 41 local questions about data centers, and by Wednesday morning the restriction side had won every single one that had reported a count.
The temptation is to read that as a verdict on artificial intelligence. It is not. It is a quotation — the first time the price of local consent has been stated in public, at scale, with a number attached. Understanding the difference is the whole game for the next two years, and it is the difference between a buildout that adapts and one that gets run over by its own press releases.
What actually happened, state by state
Ballotpedia tracked at least 50 local data-center measures across 13 states in 2026: Arkansas, California, Florida, Illinois, Kansas, Maine, Michigan, Nevada, New Hampshire, New Jersey, North Dakota, Ohio and Wisconsin. Forty-one were on the November 3 ballot in ten states; twenty-eight of those, if approved, would have limited development, and thirteen would have facilitated it. Both kinds lost. Voters were not choosing a side of the industry — they were rejecting decisions made without them.
Ohio was the center of gravity, with 21 measures and 18 municipalities voting. At least fourteen passed bans or restrictions. Trenton banned data centers over 25 megawatts with almost 80 percent. Ashville voted 81.6 percent to reverse its council's agreement with EdgeConneX. Perry passed, with 87.1 percent, a requirement that developers seeking tax abatements post financial guarantees to the village. Wilmington rejected rezoning for four separate parcels at roughly 80 percent each. Granville, Pataskala, Sunbury, Urbana, Defiance, Upper Sandusky, Piqua, Hubbard and Conneaut passed bans outright. Grove City — the closest Ohio result — still cleared 54.6 percent for a charter amendment requiring voter approval of any project over 50 acres, 20 megawatts or 500,000 gallons a day.
Maine passed four moratoria: Wells at 81.9, Peru at 76, Eliot at 76.5, Sabattus at 66.4. Kansas banned high-impact data centers in El Dorado (71.5), Ottawa (71.8), Emporia (60) and Americus (68.3) — three of those fights had to go through court just to reach the ballot. Illinois ran seven advisory questions: Bloomington advised a moratorium at 77.6, Joliet Township advised against permitting new AI data centers at 78.9, and four Madison County townships rejected pro-data-center advisories in the mid-70s. California: Alhambra 81.9, Monterey Park 88.3. Florida: Edgewater 77.2. New Hampshire: Canterbury 83.6, Nottingham 90.3. Michigan: Augusta Township rejected a data-center rezoning 89.6 to 10.4 in August. Wisconsin: Janesville required voter approval for any development over $450 million at the former GM site, 62.8; Wrightstown rejected a pro-development advisory at 87.2.
Two results deserve their own paragraph because they are usually reported as footnotes. In Nevada, Boulder City voters were asked to allow data centers in the Eldorado Valley transfer area and were running 70 percent against it. In New Jersey, Downe Township was asked to advise support for data centers and voted 87.3 percent no. When voters reject the permission slip by the same margin they reject the ban, the objection is not to the building. It is to being handed a finished deal.
The Georgia line
Georgia had no statewide data-center question this year, but it was not absent from the ballot. In the May primaries, DeKalb County Democrats voted 94.4 percent in favor of restricting data centers — the single largest restriction share recorded anywhere in the country this cycle. Glynn and Bulloch County Republicans were asked the mirror-image advisory question; those results were never reported. And in the race that mattered most, Keisha Lance Bottoms won the governorship, flipping the office, while Jon Ossoff held the Senate seat. Neither won on a moratorium platform, and neither ran against the industry.
That matters because Georgia is the state where the buildout is already approved and already financed. The Georgia Power structure to serve OpenAI's Effingham County campus cleared the Public Service Commission in August. Federal permit work is underway at the site. The votes that will decide how much of that survives are not ballot questions — they are PSC dockets, county commission agendas and a January legislative session where tax treatment gets written. In other words: Georgia's fight is on terms, and terms can be negotiated. That is the good news buried under a bad-looking headline.
Four reasons this is not the death of the buildout
- These were land-use plebiscites, not demand signals. Forty-six of forty-seven votes were about zoning, thresholds and permitting inside a specific jurisdiction. None of them reduced the amount of computation the world is asking for. In Trenton, the ban applies only to land inside city limits — the Amazon project sits just outside them, and the neighboring township wrote its own ban to close the gap. Capital re-routes. It does not evaporate.
- The state incentives are untouched. Thirty-eight states offer data-center tax incentives, and not one of them was repealed on Tuesday. A ban in a village of 624 people does not change a state's industrial policy. What did change is where the fight now happens — New York's statewide moratorium order, Texas pausing permits, Illinois suspending tax breaks. Those are negotiated instruments, not walls.
- Demand did not vote. The buildout is being driven by inference demand, grid interconnection queues and capital already committed. Georgia's largest project cleared its regulators three months before the election and is still moving. A local advisory question cannot cancel a PSC order.
- The objection is to terms, not to existence. Only 11 percent of Americans say they would support an AI data center in their own community, and 56 percent told exit pollsters that AI and data centers were a crucial or major factor in their congressional vote. That is not a constituency for abolition. It is a constituency with a list of demands: the bill, the water, the noise, the farmland. Every item on that list is a contract term.
Voters did not vote against computation. They voted against being told the deal was already done.
The pattern in all 47 results
The exception that proves the rule
One jurisdiction out of forty-seven moved the other way: Harwood, North Dakota, where 75.6 percent voted against a proposal to add new industrial review requirements for projects above certain land, power and water thresholds. It is tempting to file that as a pro-industry win. It is more accurate to read it as the same instinct pointed the other way: Harwood was asked to add a layer of process to a question that had no project, no number and no counterparty. Voters decline abstractions in both directions.
That is the actual lesson of the night. Where the question was a specific project with a specific footprint, voters said no. Where the question was a generic new hurdle with nothing to weigh, voters also said no. Consent is not a mood. It is a negotiation, and it only works when there is something concrete on the table.
What communities should do now to secure their future
If you are a county commissioner, a mayor or a school board member in a state that just changed hands, the wrong conclusion is that the window closed. The right conclusion is that the window opened onto better terms. Here is what to put in writing before anyone files a site plan.
- Price the megawatt, not the ribbon-cutting. Perry, Ohio passed financial-guarantee requirements for developers seeking abatements at 87 percent — because residents had watched one-time checks evaporate. Ask for a per-megawatt annual contribution into a county-controlled fund, indexed, audited and payable whether or not the project hits its job projections.
- Take the grid question to the regulator, not the dais. Local government cannot set a large-load tariff. Your public service commission can. Intervene in the docket, demand project-funded substations and transmission upgrades, and insist on a written commitment that large-load infrastructure costs are not shifted onto other ratepayers. This is the single highest-value hour of work available to a county attorney this year.
- Specify water before permitting. Closed-loop cooling in the design, not in the brochure. Metered consumption reported publicly, monthly. No new aquifer withdrawals. The towns that wrote this into the permit are not on Tuesday's ballot results, because they never had a fight.
- Set your thresholds in advance, and make them boring. Grove City passed voter-approval requirements at 54.6 percent and Janesville passed a $450 million trigger at 62.8 — the two closest results of the night, both won by writing the rule before the project. A published threshold converts a culture war into a checklist. Pick your numbers: acres, megawatts, gallons per day, dollars of incentive.
- Zone, don't ban. A ban forfeits the tax base, invites litigation and pushes the project one township over — where it still draws on your substation and your roads. A performance standard gets you the revenue and the controls. Say yes, if. Then make the if enforceable.
- Buy the workforce in writing. Paid apprenticeships, dual-enrollment slots at the technical college, and a local-hire percentage with a number in it. Data-center operations is one of the few high-wage fields that does not require a four-year degree — but only if the pipeline is built on purpose, and only if it is in the agreement rather than the press release.
What we are watching next
Ten measures from Tuesday still had not reported a count Wednesday morning, six were mid-count, and two more votes are scheduled: Clarksville, Arkansas decides December 1 whether to uphold two industrial-bond ordinances worth up to $55 billion in support of a data-center project, and Mandan, North Dakota votes December 15 on a 25-megawatt prohibition. Watch the Clarksville bond vote specifically — it is the first test of whether a project can win when the question is money rather than zoning.
Then watch the statehouses. With Congress flipped, federal AI policy becomes a negotiation rather than a directive, and the action moves to thirty-eight states with incentives on the books, to utility commissions setting large-load tariffs, and to county commissions who now know their neighbors will put anything on a ballot if they feel bypassed. Georgia's session opens in January, and the tax treatment of server campuses will be on the table.
The blue tsunami is real, and it is not a verdict on artificial intelligence. It is an invoice, delivered to an industry that spent two years insisting there was nothing to pay. The jurisdictions that read it correctly — and put terms on paper before the trucks arrive — will end up with the tax base, the water and the jobs. The ones that ban first will get the litigation, the same regional load on their grid, and none of the revenue.
Say yes, if. It is the only strategy that survived Tuesday.