Box Elder referendum / LaPorte ordinance / Sheboygan / Charlotte

Why it matters

Four updates. (1) The Box Elder UT referendum filing is the first observed case of citizen-referendum-as-rollback-mechanism for a *single approved* hyperscale data center. The Ohio constitutional initiative (covered Friday/Saturday) and the 5 ballot measures Ballotpedia tracks for 2026 are categorical ban proposals. The Box Elder referendum is structurally different: it would invalidate a specific commission approval decision, leaving the underlying zoning unchanged. The 5,000-signature threshold is reachable (Box Elder County voted ~28,000 in 2024), and the procedural path is well-established for non-data-center referenda in Utah; the legal-review stage is the primary remaining gate. The implication for Cliff's risk module: 'commission approval' is no longer the end of the entitlement clock in Utah — there's a 30-day-or-so referendum-petition window during which a project can still be subject to a citizen ballot rollback. Update firm-equivalent-mw-underwrite.md to add 'referendum vulnerability window' as a 30-60-day post-approval risk surface in states with county-level referendum mechanisms (UT, WA, OR, CA, CO, ID, MT). (2) LaPorte County's ordinance is the new template for the *responsive* (not preemptive) county action — pass an ordinance after a city annexation in your county has triggered a hyperscaler proposal. The pattern is structurally different from preemptive county ordinances (Oneida WI, Tazewell IL): LaPorte's ordinance was driven by Microsoft's existing data-center expansion plus the city annexation, not by a generalized concern. The implication for Cliff's regulatory-risk module: when a hyperscaler successfully annexes farmland into a city for data-center use, the surrounding county has a ~3-6 month window during which it is likely to pass a restrictive ordinance — and that ordinance will typically be MORE restrictive than the city's own zoning. The city/county jurisdictional gap (annexation creates a one-way ratchet for the project but a separate political signal for the county) is now the second canonical pattern alongside the Durham NC city/county coordination issue. (3) Sheboygan WI's referral to the Plan Commission by 7-3 is the procedural template for preemptive moratoria in Wisconsin — sister to Madison's February moratorium and Oneida County's May 8 framework. Wisconsin is becoming the canonical 'preemptive moratorium with PSC-approved ratepayer-protection-tariff backstop' state — the strongest combination of restrictive frameworks of any state in the country. Cliff's customers underwriting Wisconsin sites should treat all WI counties as defaulting to preemptive-moratorium-eligible until each county explicitly rejects the framework. (4) Charlotte's May 11 discussion-only / May 18 specific-project sequence is the slowest moratorium debate in the NC cluster (Durham, Apex, Northampton, Bulloch all moved faster). The May 18 East Charlotte vote is the de-facto policy battleground given Mayor Lyles's tie-break against the broad public hearing in late April; a denial would push Charlotte into the NC restriction cluster, while an approval over public objection would test whether a major NC city can sustain a no-moratorium policy through the May tape.