Grove City Holds 310-Acre Data Center Plan, Exposing Limits of Local Pauses

Grove City, Ohio, has placed a preliminary plan for a 310-acre data-center campus on hold under Ordinance C-22-26. The move captures the real force of many local data-center pauses: they can freeze a project at a permit gate without automatically stopping construction that has already cleared one.

That distinction changes how the current wave should be read. In a bounded ledger of 17 jurisdictions, 15 had an operative local pause at the September 6 cutoff. Imperial County’s adopted pause had been set aside by a court, while San Joaquin County had ordered a study but had not adopted a moratorium. The evidence supports a narrower description than a nationwide construction freeze: these are mainly temporary planning and permitting controls.

The word moratorium hides several different interventions

A local measure can affect whether an application is accepted, whether staff process or review it, whether final approval is issued, or whether an already operating facility may expand. Those are materially different controls. Grove City’s development page calls Project Maple a preliminary development plan and marks it “HOLD SUBJECT TO MORATORIUM.” It is direct evidence that a pending proposal has been stopped at that stage; it is not evidence of a stop-work order for a completed or approved facility.

Mendocino County’s September 1 legislative record shows another version of the same mechanism. It proposed an urgency ordinance to prohibit processing and approval of new data-center uses in unincorporated territory while the county evaluates public-health, environmental and fiscal effects and considers further rules. The displayed record identifies adoption as possible action, rather than confirming final adoption. Its significance is the proposed scope: both processing and approval, not a stated shutdown of existing work.

Exemptions decide who bears the delay

Frederick County draws its line clearly. It is not accepting new data-center applications, but exempts properties with qualifying development approvals that predate the County Council’s June 17, 2025 consideration of CB 25-09. The county also says the pause does not stop projects currently under construction, including ongoing Quantum Frederick work. It has separately required applicants to show registration with Maryland’s Public Service Commission large-load customer registry during development review.

Durham’s threshold is a policy choice about scale, not simply a scheduling detail. County officials said they considered an absolute ban but were concerned it would unduly constrain smaller enterprise and edge data centers. The adopted measure instead targets new facilities and expansions beyond 100,000 total square feet. That leaves smaller sites able to proceed while placing large projects in a nine-month rulemaking window.

The ledger also identified named or case-numbered exemptions in at least two of 16 enacted or implemented pauses. Independence exempts the Nebius project. DeSoto County exempts one approved planned unit development and two pending rezonings. These provisions, alongside Frederick’s criteria-based carveout, show why an ordinance’s exceptions can be as consequential as its nominal prohibition.

The legal and political clock is still unsettled

No reviewed measure was shown to terminate construction that already held applicable approvals. That finding is limited to the measures reviewed, but it is a useful corrective to claims that every local pause blocks active builds. Imperial County illustrates a separate constraint: its 45-day moratorium on final approvals was extended by 10 months and 15 days, then set aside after the Superior Court found the supporting findings insufficient under applicable state-law requirements. The county says it is reviewing next steps.

San Joaquin County remains one step earlier. Its board directed staff to conduct a study expected to take about six months, with public input and research into whether new land-use rules are needed. The county had no active applications or operating data centers in its unincorporated area when it acted. After initial findings in October, the board is expected to consider a 45-day pause on approvals while an ordinance is considered; that remains a prospective decision, not a current moratorium.

What to check in the next local pause

• The operative gate: whether the rule affects application intake, processing, approval, expansion or construction.
• The carveouts: whether prior approvals, projects already being built, named cases or smaller facilities remain eligible to proceed.
• The route to permanent rules: whether the measure has a sunset, a nonbinding staff timetable or a legal challenge that can alter the pause before regulations arrive.

A temporary pause is not a binding timetable for permanent regulation. No reviewed record established a mandatory deadline for lasting data-center rules. Durham staff anticipate a draft ordinance by December and aim for an amended ordinance by May 2027, but those are targets. For Project Maple and similar proposals, the next meaningful signal is the precise permit gate, exemption or court decision—not the presence of the word moratorium alone.