Little Rock, Imperial County, and Lee County Make Zoning the Gatekeeper for Power-Hungry Projects
In one week, three local governments moved to write the rules before the next application arrived, and the message for developers is that entitlement now outranks engineering.
By Keith Reynolds | Publisher & Editor, ChargedUp!
The planning counter, not the interconnection queue, is where power-hungry projects now live or die. In one week, three jurisdictions wrote or advanced the rules before the next application arrived. The message is blunt: entitlement outranks engineering. Standards born in data center debates will govern every megawatt-scale use that follows, including EV depots, cold storage, advanced manufacturing. Communities are writing guardrails built to outlast any one withdrawn project.
Key Takeaways
The pattern is rules first, applications second, and the guardrails outlast any single project that gets withdrawn.
Standards written for data centers reach every power-hungry use, from EV depots to manufacturing.
Early, transparent engagement is now part of the scope of work, not a courtesy after design.
What changed this week?
Little Rock, Arkansas (June 3): The Board of Directors approved a data center ordinance after pointed debate tied to a proposed $1B project reportedly backed by Google.
Imperial County, California (June 2): Supervisors weighed a moratorium under CEQA following months of organized community pressure.
Lee County, Georgia (June 9 scheduled): Commissioners set a vote to extend their pause to define/permit data centers—described as “a protection, not an invitation.”
Also in play: Madison, WI held a public meeting on a temporary moratorium; lawmakers in New York floated a multi-year statewide pause; Virginia senators backed rolling back a large tax break in the world’s largest data center market.
Why are cities writing data center zoning before applications?
Sequencing. Communities are setting definitions and standards upfront instead of reacting at the counter. A moratorium buys time to draft rules; the rules outlast any single project. The result: predictable guardrails for electrical load, water, noise, setbacks, backup generation, and community benefit—written once, applied to many.
Rules first, applications second: Jurisdictions focus on clarity before capacity.
Guardrails that persist: If a project withdraws, the standards remain.
Regional spread: From North Carolina (Apex, Chatham) to Texas and Maryland, councils are debating curtailment rules and supermajority rezoning thresholds.
Do these standards apply beyond data centers?
Yes. Energy has become a land-use question. The same thresholds that define a data center ordinance will govern other power-intensive uses:
EV depots: Megawatt-scale charging with peak-coincident demand and potential on-site generation.
Cold storage: Continuous load profiles plus noise and refrigerant safety considerations.
Advanced manufacturing: High-load processes with water, air, and traffic externalities.
What clears the planning counter now? A pre-application dossier
Projects advance when they arrive with answers to the questions communities actually ask—before the first hearing. Treat the following as table stakes:
Load profile & phasing: IT vs. total connected load; MW ramp by quarter; peak/average; curtailment capability.
Interconnection status: Utility letters, queue position, feeder/substation needs, upgrade responsibilities, schedule risk.
Energy source plan: % of annual MWh matched with renewables (PPA/REC), hourly matching if applicable, onsite generation (battery, gas, solar), black start and N-1 contingencies.
Water balance: Cooling technology (air-cooled, adiabatic, hybrid), annual and peak use, reuse/recycled sources, drought-stage operations, zero-liquid-discharge options.
Noise and vibration: Expected dBA at property line (day/night), mitigation (enclosures, barriers), testing protocols.
Backup generation plan: Fuel type (diesel/natural gas), hours/year limits, Tier 4 compliance, refueling logistics, emergency-only vs. economic dispatch commitments.
Site design & setbacks: Buffers from residential/critical receptors, façade/lighting plans, construction hours, dust and traffic management.
Community benefit & fiscal impacts: Local jobs (construction/O&M), training partners, tax revenues vs. abatements, host-community benefits, small-business contracting targets.
Environmental review readiness: CEQA/NEPA triggers, likely EIR/EA topics, survey status (bio, cultural, wetlands), cumulative impact framing.
Decommissioning & resilience: End-of-life obligations, recycling plans, microgrid/islanding options for emergency support.
What should you watch for in new data center zoning ordinances?
Definitions: Do thresholds reference IT load or total connected load? Are small data rooms carved out?
Backup generation limits: Caps on runtime, fuel type preferences, and reporting.
Water-use caps: Peak and annual ceilings; drought-stage restrictions; non-potable sourcing requirements.
Noise standards: Day/night dBA at property line; low-frequency/tonal penalties; commissioning test windows.
Setbacks and screening: Buffers from residential zones, critical facilities, and environmental resources.
Renewables & emissions: Hourly matching language, REC quality, GHG disclosure cadence.
Traffic & construction: Heavy-haul routes, laydown areas, hours-of-work limits, dust control.
Approvals pathway:By-right with performance standards vs. special/conditional use permits; supermajority triggers.
Reporting & enforcement: Annual attestation, third-party verification, penalties for exceedances.
Signals a moratorium may be coming
Public workshops advertised to “gather input” on undefined high-load uses.
Staff reports noting the code lacks a data center definition or permitting pathway.
Petitions citing water, noise, and air impacts; calls for CEQA-level studies.
Agenda language: “temporary pause,” “interim zoning controls,” “time to study.”
Neighboring jurisdictions passing pauses and referencing “regional consistency.”
Key takeaways for owners, developers, and utilities
Entitlement trumps engineering: Sequencing now decides schedule and feasibility.
Standards scale across uses: Today’s data center zoning will govern tomorrow’s EV depots and factories.
Transparency is a deliverable: Bring the dossier, not the talking points.
Early, transparent engagement is no longer a courtesy; it is the path through the counter. The seller side—EPCs, OEMs, and integrators—must translate technical capacity into tangible community benefits and documented mitigations.
Sources
https://arkansasadvocate.com/2026/06/03/arkansas-largest-city-approves-new-data-center-ordinance/
https://inewsource.org/2026/06/04/imperial-county-data-center-moratorium-vote-supervisors-ceqa/
https://www.cityofmadison.com/dpced/about/temporary-data-center-moratorium
Frequently Asked Questions
Why are local governments adopting data center zoning and moratoriums?
To write clear definitions and development standards—covering electrical load, water use, noise, setbacks, and backup generation—before a project hits the counter. Pauses provide time to craft enforceable protections instead of reacting to a filed application.
Do these zoning rules only apply to data centers?
No. The same thresholds and performance standards will also govern megawatt-scale EV depots, cold-storage facilities, and advanced manufacturing because energy intensity has become a land-use issue.
What should a developer prepare before the first hearing?
A pre-application dossier: load profile and phasing; interconnection status; renewable and onsite energy plan; water balance; noise modeling; backup generation limits; site design and setbacks; community benefits and fiscal impacts; environmental review readiness; and decommissioning/resilience commitments.
How long do moratoriums typically last and what happens after?
Commonly 3–12 months, extendable. During the pause, staff drafts definitions and standards. After adoption, applications proceed under the new rules—guardrails that persist even if a pending project withdraws.
Will onsite generation or microgrids improve approval odds?
Often, yes—when paired with clear limits (runtime, emissions), resilient operations (islanding for emergencies), and verifiable renewable procurement. Communities respond to reduced grid stress and credible environmental commitments.
Next Steps
If you manage siting for a power-intensive project, align your schedule to the entitlement arc, not just the build schedule.
Assemble the pre-application dossier and secure utility letters before design reaches 30%.
Benchmark likely limits (noise, water, runtime) against draft or neighboring ordinances.
Schedule a study session with planning staff to test definitions (IT vs. total load) and pathways (by-right vs. CUP).
Develop a community benefit sheet with training partners and local vendors named.
