Coweta County GA / 180-day ban / 5 projects vested-rights exempt / fourth exemption pathway
Coweta County, Georgia commissioners voted unanimously on June 17 for a 180-day data center moratorium expiring December 23 — but five proposed data centers already in the pipeline are exempt under Georgia statutory vested-rights law, a fourth distinct exemption pathway alongside municipal annexation, preemption-workaround executive orders, and state special authorities like Utah's MIDA
Coweta County is southwest of Atlanta and is the second metro-Atlanta county after DeKalb to pause data centers. The vote was unanimous. Scope is data centers only (no battery storage bundling), but the pause is broad within that scope — it halts new permits, rezonings, conditional uses, variances, and the public hearings that would let any of those move forward.
The pattern-relevant detail is the carve-out. Five data center projects already in the Coweta pipeline are exempt from the moratorium, not because the county chose to exempt them, but because Georgia vested-rights law automatically grandfathers projects that have reached a certain point in the entitlement process. The county had no discretion on those five — the statute does the exempting.
That is a fundamentally different exemption mechanism than the ones already tracked in the corpus. Boone County Indiana's Meta LEAP carve-out worked through municipal annexation (the parcel left county jurisdiction). Nashville's EO 59 worked through state preemption (state law blocked a clean ban so the executive used other levers). Box Elder Utah's MIDA carve-out worked through a state special authority that bypasses county land use entirely. Coweta's exemption works through statutory vested-rights doctrine, which exists in every state but with very different thresholds for when a project becomes vested.
Atlanta Journal-Constitution ↗
Why it matters
Vested-rights is the most consequential of the four exemption pathways because it is automatic and statutory rather than discretionary. The corpus implications are concrete. (1) Every state has its own vested-rights threshold — some trigger at building permit, some at site plan approval, some at substantial investment, and the case law is decades deep. The regulatory graph needs a per-state vested-rights doctrine page that captures the trigger event for each state, because that trigger determines which projects survive a moratorium and which die in it. (2) Per-project metadata has to include 'date of vesting trigger event' alongside the annexation-as-of-date field added yesterday, so a moratorium-impact query can answer not just 'is this parcel inside an annexation' but 'has this project crossed its state's vested-rights threshold yet.' (3) For Coweta specifically, the five exempt projects are now the most strategically valuable parcels in the county for the next six months — they are the only data centers that can move forward, which inverts the usual moratorium-as-deal-killer assumption. That inversion is worth surfacing as a search query: 'show me every vested-but-pre-construction project in a currently-moratoriumed jurisdiction.'
GeorgiaIndianaUtahMoratoriumHyperscaler
Luther OK / 6-month ban / bundles DC + BESS / no vested-rights carve-out / 23% of population at hearing
Luther, Oklahoma's Board of Trustees voted on June 17 for a six-month moratorium through December 31 covering both data centers AND battery storage — held in an outdoor meeting on Main Street after the previous week's hearing was postponed for overcrowding, with ~400 of the town's 1,700 residents attending — and explicitly with no vested-rights carve-out, blocking pending rezonings and special-use permits as well as new applications
Luther sits in eastern Oklahoma County, about 25 miles northeast of Oklahoma City. The town has roughly 1,700 residents, which means ~400 attendees represented about 23% of the entire population — and the meeting had to be held outdoors on Main Street because the previous week's session was cancelled mid-hearing for fire-code overcrowding.
The ordinance is a six-month moratorium running through December 31, 2026, and the scope choice is the meaningful one. Luther bundled data centers and battery energy storage (BESS) into the same pause, which is now the third jurisdiction in five days to use that bundled scope (Anderson County TN on June 15, Plymouth County IA on June 16, Luther OK on June 17). Three independent jurisdictions in three different states converging on the same scope inside a week is the opposition generalizing the target from 'data center' to 'large industrial energy load.'
Unlike Coweta, Luther's ordinance has no vested-rights carve-out written into it — it blocks both new applications AND approvals of already-pending rezonings and special-use permits. Whether Oklahoma's vested-rights doctrine still grandfathers any of those is a separate legal question, but the ordinance itself is the maximally restrictive version.
The trigger was an unnamed 'massive' data center complex proposal that the residents organized against. Cited concerns: water, electrical demand, noise, heat, air quality — the same five-issue cluster that has come up in nearly every moratorium hearing tracked this week.
News 9 Oklahoma City ↗
Why it matters
Two pattern-level signals. (1) The DC+BESS bundled scope is now in three states in five days (TN, IA, OK), which is fast enough convergence that any new ordinance template circulating among county attorneys probably already includes the bundle by default. The corpus has to treat 'large industrial energy load' as the queryable category, with DC and BESS as sub-types, rather than tracking them separately. (2) The 23%-of-population attendance number is the kind of leading indicator that should be encoded as a structured field on every hearing record in the docket database, because it predicts the vote and the durability of the ordinance against later challenge. Hearings that draw under 5% of population tend to produce easily-amended ordinances; hearings that draw over 20% tend to produce ordinances that survive litigation and renewal cycles. That field does not exist in any public dataset today.
OklahomaMoratorium
Pennsylvania HB 2496 / state enables local moratoriums / first of its kind / bipartisan
Pennsylvania HB 2496 — a bipartisan bill that affirmatively authorizes local governments to enact 180-day data center moratoriums during zoning review — cleared committee, becoming the first state-level enabling bill in the country (opposite direction from the Box Elder UT / MIDA state-preempts-local pattern, and the inverse of the Tennessee state-blocks-ban pattern)
Pennsylvania HB 2496 is bipartisan and would explicitly authorize any Pennsylvania local government to enact a 180-day moratorium on data center development while it conducts zoning review. The bill cleared committee this week and is heading toward a floor vote.
This is structurally different from every other moratorium item the corpus has tracked. The previous moratorium pattern was bottom-up: counties and cities pausing on their own initiative, often against state preemption, with state law as the antagonist. HB 2496 inverts that — Pennsylvania at the state level is affirmatively arming localities with a moratorium tool that they would not otherwise have unambiguous authority to use.
The contrast with three other state-level patterns the corpus is already tracking is the strategic frame:
• New York: state-level statewide moratorium (≥20 MW, one-year freeze) — top-down ban. Bill passed legislature, awaiting Hochul signature.
• Tennessee: state law preempts local bans on data centers — top-down block on local action, the pattern Nashville EO 59 had to work around.
• Utah: state-level special authority (MIDA) preempts local zoning for specific projects — top-down exemption.
• Pennsylvania (new): state-level enabling legislation that hands moratorium authority to localities — top-down empowerment of bottom-up action.
Four different state-vs-local relationships in four states inside one month. The federal layer (yesterday's FERC order) sits above all of them.
ABC27 Harrisburg ↗
Why it matters
The state-vs-local jurisdictional axis is now four-way: state bans top-down (NY), state blocks local bans (TN), state preempts via special authority (UT), state enables local bans (PA). That is enough variance to deserve its own typology in the regulatory graph, because the same project in two states with identical local sentiment can have totally different permitting timelines depending on which state-local relationship governs it. The PA model is the one to watch most closely for replication, because it is bipartisan and it is the easiest legislative lift in any state where the legislature is sympathetic to localities but hasn't passed a statewide ban. If HB 2496 becomes law, expect similar bills to surface in MI, OH, NC, and OK over the next two quarters — those four have active local moratorium activity and state legislatures that have not yet committed to a top-down approach.
FERCUtahTennesseeMoratoriumFERC action