Zoning Signal

Watch

Data Center cross-corpus propagation watch

Whether a second corpus city followed Minneola's draft data center ordinance with a text amendment of its own within 90 days, by August 30, 2026

Resolution (September 27, 2026)

The 90-day window closed on August 30, 2026. The trigger's words: "A second corpus city introduces a Data Center text amendment on a Planning & Zoning agenda within 90 days of Minneola's June 1, 2026 Ordinance 2026-05 hearing (deadline 2026-08-30); also resolves if no second city files in that window."

What the record shows inside the window:

  • Minneola, June 1. The Planning & Zoning Commission chose neither draft of Ordinance 2026-05. Its 4-0 motion directed staff and legal to finalize a data center ordinance "compatible with the new state law," with small or boutique facilities allowed at baseline and special-exception review for larger proposals. The ordinance is absent from the July 6 and August 3 agendas. See the draft-choice watch.
  • Lake County, August 5. The Planning & Zoning Board agenda listed "Ordinance #2026-XX Data Center Moratorium" on consent. The draft ordinance, directed by the Board of County Commissioners on June 23, 2026, establishes a temporary moratorium on data center rezonings, permits and development orders in the unincorporated county for twelve months, or until an ordinance amending the county's code on data centers takes effect. It is a moratorium, not the text amendment it anticipates. The corpus holds no record of its adoption.
  • Winter Garden, August 3. The Planning and Zoning Board packet carried a statutes matrix whose entry for Section 112.231, Hyperscale Data Centers, reads in part that the city "may want to amend LDC to establish site standards." No amendment is on the agenda.
  • Apopka, August 11. The Planning Commission agenda set the scope of a September 8 workshop, opening with "Data center definitions per member Ryan." A workshop topic is not an amendment.
  • Clermont, August 25. The City Council approved Ordinance No. 2026-032, "Data Centers Moratorium," at final reading: "STATUS: APPROVED AS AMENDED," "VOTE: ROLL CALL 5/0." The corpus's Clermont Planning and Zoning Commission records for July 7, July 21 and August 4 list no data center item.

No corpus city introduced a data center text amendment on a Planning & Zoning agenda in the window. Two jurisdictions moved on data centers by moratorium instead, one of them at a council rather than a planning board. The watch resolves as mixed: the attention it expected spread, and the instrument it named did not.

This reading covers the records the corpus holds for the window; it is not a survey of every agenda posted in it.

Calibration

Axis Forecast Outcome
Directional A second corpus city files a data center text amendment inside 90 days Mixed: two jurisdictions moved inside the window, by moratorium; no text amendment
Horizon Imminent; by August 30, 2026 Within: Lake County on August 5, Clermont on August 25
Significance Minneola's pre-coding as a template, read as a Grandfather Window play Overstated: Minneola adopted no standards, and the site's SB 180 brief reads code adopted inside the §28 window as exposed, not protected

The premise did not hold at the start. The watch described Minneola as coding local standards before SB 484 took effect; the June 1 minutes show the Commission sent the drafts back. The protection the watch expected from timing runs the other way under SB 180: as The Window That Reloads sets out, under Chapter 2025-190 §28 a more restrictive land development regulation adopted between August 1, 2024 and October 1, 2027 is the exposed class. Whether the moratoria that arrived instead survive §28 is followed at the Clermont data center moratorium watch.

What the watch asked

The watch opened on May 23, 2026, from the agenda for Minneola's June 1 Planning & Zoning Commission meeting, where Ordinance 2026-05 (Data Centers, version dated May 19, 2026) was set for hearing. Its question was whether other corpus cities would follow with data center ordinances of their own in the 90 days through August 30, 2026.

It set two resolutions:

  • A second corpus city files a data center text amendment on a P&Z, City Commission, City Council, or County PZB agenda within the window, confirming cross-corpus propagation. Promotes the candidate Data Center Defensive Coding pattern.
  • The 90-day window closes (2026-08-30) without a second city filing: the pattern does not propagate. Minneola's posture stays a single-city case.

Why it looked like a signal: the SB 484 timing

Governor DeSantis signed SB 484 (CS/CS/SB 484, Hyperscale Data Centers) into law on May 7, 2026, in Lakeland, with primary effect July 1, 2026. As reported at signing, the law:

  • Preserves local zoning and permitting authority: cities and counties can deny data center projects and establish stricter local standards
  • Prohibits utilities from passing data center costs onto residential ratepayers: large-scale data center users pay their full cost of service
  • Limits confidentiality on site-development negotiations: a transparency framework for site selection
  • Addresses water use: provisions on data center water consumption

Minneola's hearing fell 25 days after the signing. The watch read it as a city setting local standards ahead of the state frame, the posture the Grandfather Window pattern follows. The Resolution and Calibration above record how that reading fared: Minneola set no standards in the window, and under SB 180 the timing that mattered was §28's, not SB 484's.

The pre-coding pattern parallel

The corpus had already observed a regulatory pre-coding pattern at a different surface: Recovery Residences Regulatory Pre-coding documented Clermont (Ord 2026-013, March 2026), Leesburg (CRR CUP at 2007 Butler St., March 2026) and Lake County PZB (LDR text amendment, March 2026) all coding for SB 954 Recovery Residences in a single 8-week window. Three jurisdictions, one state surface, one short window.

The watch tested whether the same mechanism generalizes to a new state surface (SB 484, hyperscale data centers): is coding ahead of a state framework's effective date a corridor behavior, or was Recovery Residences specific to SB 954? In this window the answer was a moratorium, not a code.

The Fort Meade calibration

On April 14, 2026, the Fort Meade City Commission unanimously approved a development agreement for a data center campus in Polk County, which FOX 13 reported as a $2.6 billion project on a 1,300-acre former phosphate mine. Before the vote, Spectrum News 13 reported it at 1.9 million square feet with room to grow to 4.4 million. Polk is the county whose Haines City sits in the Zoning Signal corpus on the US-27 South Lake corridor extension. The watch read the approval as corridor-adjacent pressure behind Minneola's drafts.

What to look for in the resolution period

  • Clermont: P&Z Commission monthly and City Council; any text amendment or LDC update touching data centers, hyperscale facilities, large-scale industrial users, or commercial intensity caps
  • Lake County (Unincorporated): PZB monthly and BCC; any LDR amendment establishing a data center use class, or any specific data center application
  • Leesburg: Planning Commission and City Commission; any text amendment touching large-scale industrial or hyperscale uses
  • Groveland: CDC V5 ongoing adoption; whether the Agrarian Code's commercial sections explicitly address data centers
  • Apopka: Planning Commission and City Council on the SR-429 corridor; any Wyld Oaks-style large-scale code addition with data center provisions
  • Polk corpus cities (Haines City, Davenport, Lake Wales): any data center pre-coding response to the Fort Meade approval

A specific data center application on any corpus agenda in this window also counts toward the resolution: code activity and application activity both signal corridor positioning.

Resolution criteria

This watch resolves when:

  • A second corpus city introduces a Data Center text amendment on any planning agenda within the window (2026-05-23 through 2026-08-30): propagation confirmed; promotes Data Center Defensive Coding pattern
  • The window closes without a second city filing: propagation not confirmed; pattern remains single-city
  • An actual data center application is filed at any corpus city in the window: resolution accelerated; the corridor's data center pressure is now corpus-visible at the application surface

The outcome assessment will capture:

  • Which city moved second (if any)
  • Whether the second move was a code amendment or an application
  • Whether the substantive code language differs from Minneola's (more permissive / more restrictive / structurally similar)
  • The voting block at the second city, confirming or contradicting the Minneola posture

Source trail

Connected records

14 connected records

Patterns4

Watch2

Corridors1

Entities1

Places6