The Data Center Moratorium Is Not the Strategy — It's the Clock

July 2026

A planning director opens an application for a 300-megawatt data center campus. The completeness clock starts the day it lands — ninety days in many states — and the department's intake checklist was written for subdivisions and gravel pits. There is no line for an interconnection study. No field for water consumption by cooling design. Nowhere to record whether the will-serve letter from the electric utility is a commitment or a courtesy. The board responds the way boards across the country are responding: a moratorium. Six months, a year, sometimes two. Reasonable. But be clear about what it is. A moratorium is not a strategy. It is a clock — and when it runs out, the county either has a review process or the same problem with less goodwill.

What a 300MW Application Actually Asks

The application is a hundred questions with no standard place to put the answers. Requested load by phase, measured against the entire county's existing demand. A water source the county may not control, with peak summer draw nobody has modeled. Tax abatement terms negotiated in side agreements rather than looked up in a fee schedule. Noise at the property line, at night, from cooling plant and backup generators. A facility that will operate for decades, reviewed by a staff that turns over in years. The existing process isn't wrong. It's undersized, and everyone in the building knows it by week two.

The Consultant Report Outcome

A moratorium legally pauses applications. That is its entire effect. It does not answer the water question, define complete at this scale, or build the record-keeping the review will need. The default outcome of a study period is a consultant report: presented at a work session, accepted by motion, filed. The moratorium lapses, and the next application meets the same unprepared process — minus the public's patience. The alternative is a study period that produces operational capability: a defined intake, a record structure, a repeatable review. The difference is not the ordinance. It is whether anyone treated the expiration date as a delivery date.

Where the Record Falls Apart

Most counties will track this the way they track everything: a spreadsheet. Planning keeps one copy, public works another, and the assessor's office is working from a version emailed in March. Nobody can say which set of plan review comments is current, and answering a records request — there will be many — means a week of forwarding email threads.

The worse failure comes after approval. At the hearing, conditions get read into the minutes: a water cap, a noise ceiling measured at the property line, a decommissioning bond, a hiring commitment offered to close the deal. The minutes are adopted. The conditions never land in any tracking system, because there isn't one — the file closes and the spreadsheet stops being anyone's job. Five years later, someone asks for evidence the noise condition was monitored, and the only answer is the minutes themselves. A condition nobody tracks is a condition that was never imposed.

What the Study Period Should Deliver

The deliverable is a working system, not a binder:

  • An intake checklist — the completeness standard, enforced at the counter. An application without a signed will-serve letter and an interconnection study isn't ready for review, and staff can say so with the ordinance behind them.
  • Impact fields — power by phase, water source and peak draw, traffic, noise, fiscal terms — structured, so the second application can be compared to the first.
  • A public record — every submission, comment, and staff finding in one auditable file.
  • A conditions register — every commitment with an owner, a trigger, and a status, built to outlive the approval and the staff who wrote it.
  • A staff dashboard — where each application stands, what it waits on, who holds it.

Defensibility Is the Strategy

None of this is pro-development or anti-development. A county with a defined record set can approve a project and defend the approval, or deny one and defend the denial. A county without one can do neither — either decision becomes a lawsuit argued from meeting minutes. The moratorium was only ever the time to build the record.

If your county, city, or utility is reviewing large-load industrial projects, the study period is the window — and it's already running. I help agencies turn that window into a practical review framework: intake checklist, impact fields, public record, conditions register, and staff dashboard. Before the clock runs out, not after.