Next Live Local Act project filing in south Lake
Tests whether Minneola Ord 2024-10 + Clermont density-cap reduction hold
Pointe Grande was Pointe Grande. Minneola Ord 2024-10 and Clermont's density-cap reduction were authored as defensive responses inside the SB-180 grandfather window. Each city adopted before the August 2024 SB 180 trigger; the codes are protected. The next Live Local Act qualifying project filed in south Lake is the first test of whether the defensive architecture holds against state preemption, or whether developer-side strategy has evolved past the defensive surface. Leesburg has no defensive code; the next Live Local filing there hits a different exposure profile, with the denial bloc administratively bypassed by the Live Local statute. This watch surfaces the cardinal evidence point on whether south Lake's defensive Live-Local posture is durable across municipalities and developers — the Grandfather Window pattern's first applied test post- Pointe-Grande, and the cardinal calibration moment for the SB 180-class state-preemption response architecture across the corridor.
What's pending
A condition-triggered watch — resolution arrives when a developer files a Live Local Act qualifying project (FS 166.04151 affordable housing density bonuses / FS 420.50872 commercial-zone residential conversions) in any of the four corpus cities. The watch resolves on filing; the outcome assessment captures the city's response posture.
The defensive architecture stack
Each of the four cities enters this window with a different posture:
-
Minneola Ord 2024-10 (March 2024, pre-grandfather-window) — restricted Live Local eligible zones to I-1 + B-1 only; excluded PUDs; capped density at 8 du/acre and height at 35 feet. The most aggressive defensive posture in the corpus.
-
Clermont density-cap reduction (adopted in 2024-2025) — strategically reduced the underlying allowable density in commercial zones to lower the Live Local "highest allowable density in the city" trigger threshold. A different defensive theory than Minneola's — narrowing the trigger rather than restricting the eligible zones.
-
Groveland CDC V5 — still in drafting under SB-180 freeze. No defensive Live Local code currently in force; the city's protection is statutory deference rather than coded standard. Live Local exposure compounds with SB-180 exposure.
-
Leesburg — no defensive code architecture authored under the grandfather window. The denial bloc's filtering operates as the protective mechanism, but cannot override a Live Local qualifying filing, which is administratively approved by statute.
What the next filing tests
Three resolution paths depending on the city of filing and the developer's strategy:
-
Minneola filing — tests Ord 2024-10's I-1 + B-1 zone-restriction architecture. The first developer to file post-Pointe-Grande against the restricted-zone framework signals whether the defensive posture deters or merely redirects. Pulte's Del Webb 846-unit Hills of Minneola phase is the cardinal Live-Local-class development in Minneola — a substantive filing testing density caps against Ord 2024-10's framework would surface defensive-code performance.
-
Clermont filing — tests the density-cap-reduction theory. A developer filing in a downzoned commercial parcel surfaces whether the threshold-narrowing strategy reduces qualifying buildable density to a level where the Live Local pathway is uneconomic, or whether the framework still produces density beyond the city's underlying comp plan.
-
Leesburg filing — exposes the defensive-code absence. The city's only protective mechanism is the denial bloc, which Live Local statute administratively bypasses. A first Leesburg Live Local filing surfaces the structural vulnerability the leesburg-developer-litigation-challenge watch anticipates.
-
Groveland filing — exposes the SB-180 freeze layered exposure. Without CDC V5 in force, Groveland's protection is comp plan-level, which Live Local can override on density. The filing tests whether the city-attorney transition leaves the defensive posture intact during the filing window.
What to look for
- Land-use applications citing FS 166.04151 or FS 420.50872 specifically
- Developer attorney engagements naming Live Local qualifying analysis (Lowndes Drosdick has appeared in Pointe Grande and the Hills/Crooked Can cases)
- Staff-report responses to filings — the city's first administrative posture on the qualifying analysis
- City Commission agenda items announcing receipt of qualifying applications
- Any judicial action against a city's defensive ordinance under SB 180's "more restrictive or burdensome" standard
What it would mean either way
If the next filing is in Minneola and Ord 2024-10 deters or constrains — the I-1 + B-1 restricted-zone framework holds as a regional defensive model. Other cities can study and replicate.
If the next filing is in Clermont and the density-cap-reduction theory holds — the threshold-narrowing strategy gains regional precedent as an alternative defensive posture. Cities with form-based-code authoring capability can deploy.
If the next filing is in Leesburg or Groveland and the city absorbs the project — the defensive-architecture-absent posture surfaces as the structural vulnerability the grandfather-window pattern flags. Future filings target the unprotected cities.
If a court challenges any defensive ordinance under SB 180 — the legal posture of grandfathered codes faces test. The grandfather window's protection is examined against the "more restrictive or burdensome" standard. The outcome shapes whether the four cities' defensive architecture survives the post-sunset litigation cycle.
Calibration significance
This watch generates calibration data on the Grandfather Window pattern's exhibit count. Each Live Local filing is a candidate exhibit. The pattern lifecycle (currently confirmed) is tested against whether defensive architecture authored under the grandfather window holds in operation.