Plain-English background on why county moratoriums matter more than they look. A county moratorium is a temporary local ordinance that suspends new development permits or rezoning applications for a specific category of use (in this case, data centers) for a defined period (typically 6-24 months). Every state has slightly different rules for how counties can enact them: Iowa, Indiana, Maryland, and Florida all authorize them by state statute; the specific procedure varies (some require public hearing, some require supermajority, some cap duration). But the practical effect is the same: for the duration of the moratorium, no new data center development application in the covered geography can be filed, processed, or approved. Projects already in the pipeline are typically grandfathered; new ones are frozen. Why county moratoriums matter as a durable friction channel. They require zero signatures, minimal budget, and no distribution requirement (unlike statewide ballot initiatives). They require 3-5 elected county commissioners to vote yes on a single evening after a public hearing. They are politically low-cost for commissioners because residential ratepayers vote and hyperscalers don't. They generate substantial political-narrative payoff (local newspaper coverage, resident testimony, 'we listened to the community' framing). Yesterday's Cliff Daily noted Linn County IA (18-month freeze, 2-1 vote July 1) and Washington County MD (12-month freeze doubled from 6 on the floor, 4-1 vote July 1). Today the ledger extends further. **Clark County Indiana — 1-year moratorium proposed at July 3 commissioners' meeting.** Clark County Commissioner President Bryan Glover raised the moratorium proposal at the end of yesterday's meeting (moved early to accommodate the July 4 holiday weekend). He is asking for the other commissioners' agreement to formally request that the planning and zoning board review the county's unified development ordinance and recommend a 1-year moratorium at the next planning commission meeting. The stated rationale: 'extra time to review the development ordinance and what it means for data centers.' This is the standard procedural setup — a commissioner floats the moratorium at a public meeting, generates local newspaper coverage, and puts it on the planning commission's agenda for a formal recommendation. From proposal to enactment is typically 60-90 days in Indiana. Clark County is directly across the Ohio River from Louisville KY and sits inside MISO-adjacent territory that has been actively courted by hyperscalers looking to route around ERCOT and PJM friction. **Whitley County Indiana — state-law-authorized moratorium already in effect.** Whitley County (northeast Indiana, county seat Columbia City, about 20 miles west of Fort Wayne) has enacted a 1-year moratorium on data centers under Indiana's state statute that authorizes counties to enact temporary moratoriums for up to a year while a zoning code is drafted. The Whitley County Plan Commission is now actively drafting a zoning code and held a listening session with heavy community turnout. Community concerns focus on energy demand — one speaker cited an estimate that a single cloud data center could consume 100% of current Whitley County electrical capacity. **Lakeland Florida — 12-month moratorium first reading Monday July 6, final vote July 20.** The Lakeland City Commission will hold the first reading Monday July 6 at 9 AM at 228 S. Massachusetts Avenue on Ordinance to establish a 12-month moratorium on any data center or 'large load electric customer' using more than 50 MW/month. The moratorium covers acceptance, processing, review, and approval of applications for Development Permits, Development Orders, and other City approvals for data center establishment, construction, expansion, or intensification. Final vote is scheduled July 20. The public purpose per the city notice: 'preserve the status quo while the City evaluates appropriate land use classifications, development standards, infrastructure requirements, and utility impacts.' This is the first Florida city-level moratorium action following Florida SB 484 taking effect Wednesday July 1, and it validates the forecast we made two days ago that FL SB 484 (which took away hyperscaler-favorable subsidy structures) would push friction down to the city and county level in Florida. Lakeland is a mid-size Central Florida city (~115k population, in Polk County between Tampa and Orlando, sits inside Duke Energy Florida service territory). Neighboring Zephyrhills already enacted a 1-year moratorium on June 24. This is now a Florida city-cluster pattern. The compounding read across the week. Six moratorium actions in a single week (Linn IA, Washington MD, Prince George's MD queued for vote, plus Clark IN + Whitley IN active + Lakeland FL first reading Monday) is the highest single-week county-level friction load of 2026 so far. The three-day cluster from Wednesday to Friday overlays cleanly on the July 1 state clocks — the state incentive changes are producing immediate, visible local-level moratorium responses inside a 72-hour window. That is a durable pattern that Cliff should model going forward: expect a county moratorium wave in the 5-10 day window following every major state-level regulatory event affecting data centers.
Why it matters
Three implications. (1) The 6-day / 6-moratorium ratio is the new baseline for post-state-event county-level friction. Cliff should update its regulatory-risk modeling to include an explicit 'post-state-event downstream county moratorium probability' for the 10 days following any state-level data center legislative or executive event. That's a real productizable data field — it converts what looks like random local noise into a predictable time-window forecast. (2) The Florida cluster (Lakeland + Zephyrhills + likely more Tampa Bay area cities) is the first evidence FL SB 484 is producing exactly the local-friction spillover we forecast on Wednesday. If Lakeland's first reading Monday July 6 passes as expected and the July 20 final vote confirms, we'll have a concrete Florida city playbook: 12-month moratorium keyed to a >50 MW/month load threshold. That threshold value (50 MW) is a specific number worth tracking — it's below the ERCOT Batch Zero eligibility floor (75 MW) but consistent with the general 'colocation-scale' definition emerging in FL and OH. Cliff should catalog which state and city moratorium thresholds are converging around 50 MW versus 25 MW versus 75 MW — this becomes a design input for site-selection modeling. (3) The Indiana cluster (Whitley + Clark + Indianapolis prior activity) is a specific warning signal for hyperscaler capex trying to route around Ohio's incentive freeze into MISO-adjacent Indiana. Illinois labor's 'jobs go to IN/KY/OH' argument (from yesterday's newsletter) assumes those states remain open. If Indiana counties adopt cluster-moratorium patterns matching Iowa's, then the 'same PJM/MISO grid, weaker labor standards' opening argument for labor in Illinois loses force — because the alternative jurisdictions may not remain open either. Watch Vigo County, Marion County, and Hamilton County IN over the next 60 days as the load-bearing tests of whether Indiana absorbs the relocated capex or blocks it.
Related filings
T+3 PJM bid close Jul 7 / T+3 Lakeland FL first reading Jul 6 9AM / T-6 ERCOT Form W Jul 10 / T+11 PJM auction results Jul 14 / T+16 Lakeland FL final vote Jul 20 / T+23 MD FERC comment deadline Jul 27 / Prince George's MD 2-year moratorium vote queued next week / NY A11560 not delivered to Hochul / 10-day clock not started / 6 deadline windows 24 days
Plain-English rollup of what didn't change over the July 4 weekend and what's coming next week. **ERCOT Batch Zero Form W Part A — T-6 to Thursday July 10.** No change since Thursday. The Interconnecting Large Load Entity (data center operator) must...
T-7 ERCOT ILLE Form W Jul 10 / T-21 Form W step 2 Jul 24 / PJM 2028-29 auction closes Jul 7 / results Jul 14 / price band $175-325 MW-day / 13-state governor pre-negotiated band / MD FERC ratepayer complaint comment deadline Jul 27 extended / NY A11560 not delivered to Hochul / 10-day clock not started / passive enactment plausible / 4 deadline-anchored windows next 24 days
Plain-English background on why the four operational-track deadlines all matter this month. Each of these deadlines drives a specific action by developers, hyperscalers, or state parties, and each represents a concrete moment where Cliff can produce a...
T-0 Jul 1 2026 / VA $0.011/kWh tax live 12:01 AM SCC collecting / IL DCIP application intake frozen Pritzker fall veto session reform / FL SB 484 live utility cost shift prohibition ≥50 MW full cost of service aquifer permitting tightened / Trump EO 14318 live federal permitting acceleration DC >100 MW or >$500M / IL joins OH AZ ME cluster / VA DEQ water language interim today hard cutover Jan 1 2027 Eastern VA Groundwater Mgmt Area / Data Center Coalition Josh Levi opposed / state-federal misalignment first visible day
Plain-English background. Four separate regulatory clocks all reach 12:01 AM Wednesday July 1, 2026 at the same instant. Three are state-level and point toward friction — they increase cost or reduce access for hyperscalers building in that state. One is...
PA + OR + WI + FL / 14-day cluster
Three regulatory events in the same 24-hour window on May 8 — Pennsylvania PUC's model-tariff vote, PPL Electric's pending rate-case settlement (filed March 13, ALJ recommendation April 17, effective July 1), and Oregon PUC's PGE Schedule 96 directive —...
WHYY / WESA / Utility Dive / KGW / KOIN / Beaver County Radio / RTO Insider ↗