Data Centers: The Moratorium That Almost Was

Last fall, officials in Spencer floated an idea that sent a quiet shockwave through the infrastructure development community: a full moratorium on new data center projects. Within weeks, they reversed course. The episode was brief enough that most people outside the region barely registered it. But the pattern it represents — local governments reaching for the emergency brake on data center growth, then pulling their hand back — is playing out in communities across the country and deserves a closer look.

The Proposal That Sparked the Debate

Moratoriums on development aren't unusual. Cities and counties impose them on everything from housing construction to cannabis dispensaries when they feel policy hasn't caught up to reality. What made Spencer's proposal notable was the target: data centers, the facilities that underpin cloud computing, AI workloads, financial transactions, and essentially every digitized process modern life depends on.

The officials who floated the idea weren't acting irrationally. When large-scale infrastructure arrives faster than zoning codes, utility agreements, and community input processes can accommodate it, local governments are left managing consequences they never consented to. Data centers carry real tradeoffs — significant power draw, water consumption for cooling, and industrial-scale footprints in areas that may not have anticipated that kind of development. Raising a hand and saying "wait" is, from a governance standpoint, a defensible instinct.

The initial reaction from stakeholders was predictably split. Developers and technology companies pushed back hard — any pause on permitting creates uncertainty, and uncertainty is expensive when you're trying to site a facility that needs to be operational within a defined window. Local officials who supported the moratorium framed it as a responsible timeout. Neither side was entirely wrong.

Why the Reversal Happened

Moratoriums have a way of collapsing under their own weight when the economic stakes get high enough. Spencer's reversal reflects pressures that are structural, not just political.

Data center development generates substantial tax revenue, creates construction jobs (and a smaller but well-paying permanent workforce), and signals to site selectors that a region is open for business. When a moratorium goes up, those signals invert almost immediately. Site selectors move on. Developers who were circling the region start making calls elsewhere. The opportunity cost isn't hypothetical — it's measurable in projects that quietly redirect to the next county or the next state.

The stakeholder pressure that reversed the moratorium almost certainly included voices from the utility sector, commercial real estate, and the broader economic development community — all of whom have direct financial exposure to how permitting decisions get made. These aren't shadowy interests corrupting local governance. They're the same forces that shape infrastructure siting decisions everywhere, and they're usually better organized and better resourced than the community groups raising legitimate concerns about power loads and land use.

There's also a legal dimension worth noting. Moratoriums that target a specific industry type can attract litigation, particularly when they're enacted without a clear sunset clause or a defined policy objective. The legal risk alone gives municipal attorneys reason to counsel caution.

What This Means for Local Policy

Spencer's episode is instructive precisely because it was inconclusive. The moratorium didn't hold long enough to produce any policy reform. That's the most common outcome — a reactive proposal, a reversal, and then a return to the same zoning and permitting framework that prompted the proposal in the first place.

The communities that handle large-scale infrastructure development most effectively aren't the ones that try to freeze it — they're the ones that build the regulatory scaffolding before the development arrives. That means updated zoning classifications that account for the power and water demands of hyperscale facilities, utility impact assessments baked into the permitting process, and community benefit agreements that capture some of the value these developments generate.

What's emerging across multiple jurisdictions is a two-track regulatory trend. On one track, states like Virginia and Texas — which host the largest concentrations of data center capacity in the country — are actively competing for projects with tax incentives and streamlined permitting. On the other track, communities with less experience hosting this kind of infrastructure are discovering that their existing frameworks don't fit. The gap between those two tracks is where episodes like Spencer's happen.

The Real Risks of Hitting Pause

The case against moratoriums isn't just that they're economically costly in the short term — though they are. It's that they often fail to solve the underlying problem while creating new ones.

A moratorium that lasts 90 days doesn't give a planning department enough time to develop meaningful new policy. It does give developers enough time to conclude that the jurisdiction isn't worth the risk and redirect capital accordingly. The communities that most need thoughtful infrastructure policy — places that are feeling the pressure of rapid development without the institutional capacity to manage it — are also the least likely to be able to execute a productive moratorium. They tend to end up where Spencer did: reversed, with no new framework and a slightly bruised reputation among site selectors.

The infrastructure development risks cut deeper than lost tax revenue. Data center capacity is being built to serve AI training workloads, cloud storage growth, and enterprise computing demand that isn't slowing down. When permitting uncertainty delays project timelines, the demand doesn't disappear — it relocates. And the regions that accumulate that capacity accumulate the economic infrastructure that comes with it: grid upgrades, fiber connectivity, and a workforce with relevant technical skills. The places that pump the brakes too aggressively risk being left out of that compounding investment cycle.

There's a technological stagnation risk at the regional level that rarely gets articulated clearly: the infrastructure you don't build becomes the infrastructure your businesses have to reach elsewhere to access.

Where Data Center Development Goes From Here

The Spencer episode won't be the last of its kind. As AI compute demand drives a construction boom in data center capacity — industry estimates put new data center investment in the hundreds of billions over the next decade — more communities will find themselves with proposals on the table that their existing frameworks weren't designed to evaluate.

The developers who navigate this environment successfully won't be the ones who treat local policy concerns as obstacles to be managed. They'll be the ones who show up before the proposal is filed, engage with utility providers and planning departments early, and build the kind of community record that makes a moratorium proposal politically difficult to sustain. Proactive engagement with local infrastructure stakeholders isn't a nice-to-have — it's project risk management.

For professionals working in infrastructure development, the lesson from Spencer is straightforward: the regulatory environment for data centers is still being written in most jurisdictions, and the parties who help write it will have a structural advantage over the parties who simply react to it. Local policy shapes everything from permitting timelines to interconnection agreements to long-term operating costs. Waiting for the framework to finalize before getting involved is waiting too long.

The moratorium that almost was in Spencer didn't change much on its own. But as one node in a larger pattern of regulatory friction around data center development, it's pointing at something real: the infrastructure buildout the digital economy requires is running ahead of the governance capacity to manage it. Closing that gap — through better policy tools, earlier stakeholder engagement, and more sophisticated local regulatory frameworks — is the actual work. And it's just getting started.

Explore the InfraSale Marketplace for more insights on infrastructure development.

[INTERNAL LINK: infrastructure development trends]

[INTERNAL LINK: data center capacity growth]

[INTERNAL LINK: regulatory frameworks for data centers]