Why Hayes Township Extended Its Data Center Moratorium

Hayes Township just hit pause on data center proposals — and the reasons why matter far beyond one small Michigan municipality.

The township recently extended its moratorium on incoming data center proposals to a full 12 months, giving officials time to study whether existing zoning rules can actually handle what these facilities demand. It sounds like a procedural footnote. It isn't. It's a signal that local governments are waking up to the fact that their regulatory frameworks were built for a different era — one that didn't include hyperscale computing infrastructure dropping into residential-adjacent corridors.

This isn't NIMBYism dressed up in bureaucratic language. It's something more substantive, and developers, site selectors, and infrastructure investors should pay close attention.

What Actually Triggered the Moratorium

Data centers don't announce themselves with fanfare. A proposal lands, planning commissioners pull up the zoning code, and the uncomfortable realization sets in: the rules on the books don't cleanly cover what's being proposed.

That's the core tension in Hayes Township. Officials extended the moratorium specifically to create breathing room — time to study whether current zoning classifications and development standards are equipped to evaluate data center proposals fairly and thoroughly. The 12-month window isn't a rejection of data centers outright. It's an acknowledgment that rushing a decision without the right regulatory tools in place is worse than waiting.

A moratorium is often less about opposition and more about preparation — townships that skip this step tend to regret it.

The timeline matters here. Twelve months is meaningful. It's long enough to commission independent studies, hold public hearings, consult with infrastructure engineers, and draft amended ordinances if needed. It's not a delay tactic — it's a development cycle for policy itself.

Why Existing Zoning Rules Weren't Built for This

Standard municipal zoning codes typically sort land use into buckets: residential, commercial, industrial, agricultural. Data centers are awkward fits across the board. They look industrial — large buildings, significant power infrastructure, limited pedestrian activity. But they don't generate the truck traffic or emissions of traditional industrial uses. They're not retail commercial. And they certainly aren't residential.

The mismatch creates real problems. When a facility doesn't fit neatly into an existing category, townships either shoehorn it somewhere inappropriate or discover mid-review that they lack the standards to evaluate it at all.

Consider what a proper data center review actually requires zoning officials to assess: electrical substation capacity and proximity, fiber connectivity, cooling water usage and discharge, generator fuel storage, noise from HVAC and backup systems, setback requirements from neighboring properties, and emergency access. Most zoning codes written before 2015 have none of this. Many written before 2020 are still inadequate.

Hayes Township's decision to study these gaps before approving — or denying — proposals is textbook responsible governance. The alternative, approving a facility under ill-fitting industrial zoning and discovering the problems later, is far more disruptive to everyone involved, including the developer.

The Economic Reality: What's at Stake on Both Sides

Data centers are genuinely compelling economic assets for small municipalities. They generate significant property tax revenue relative to the land they occupy, require almost no municipal services compared to residential development, and create a modest but well-paying local employment base for operations and maintenance roles. A mid-sized facility — say, 50 to 100 MW of critical IT load — can represent hundreds of millions of dollars in assessed value.

That's not nothing for a township budget.

But the infrastructure demands cut hard the other way. A 100 MW facility needs roughly 120 to 130 MW of utility power delivered reliably, which frequently requires dedicated transmission upgrades or new substation construction. Water-cooled facilities can consume millions of gallons annually. Emergency generator systems typically run on diesel, requiring significant on-site fuel storage. These aren't trivial asks from a local grid or municipal infrastructure standpoint.

The economic upside of a data center is real — but so is the infrastructure bill, and townships often discover they've underestimated it.

The study period Hayes Township has created gives officials the opportunity to understand both sides of this ledger before committing. That's exactly the right sequence.

What the Study Period Should Actually Produce

If Hayes Township uses this 12 months well, the output shouldn't just be a yes/no on pending proposals. It should be a durable regulatory framework — one that can handle the next proposal and the one after that.

That means several concrete deliverables. First, a formal data center use classification, either as a standalone permitted use or as a conditional use requiring case-by-case review. Second, clear development standards: minimum lot sizes, setback requirements, noise thresholds at property lines, utility coordination requirements, and screening standards. Third, an impact fee or infrastructure contribution framework so that the cost of grid and road upgrades attributable to a facility are properly allocated.

Jurisdictions that have done this work — and done it before the pressure of a specific proposal — are in a fundamentally stronger negotiating position. They can approve projects faster, with more confidence, and with better outcomes for both the township and the developer.

What townships should avoid is the opposite outcome: a 12-month study that produces a de facto permanent ban dressed up as "further review needed." That outcome damages municipal credibility with the infrastructure development community and often gets challenged legally anyway.

What Other Municipalities Can Learn From This

Hayes Township isn't alone in navigating this. Across the country, rural and semi-rural counties are suddenly attractive to data center developers because of land availability, lower power costs, and proximity to fiber routes — and their zoning codes are equally unprepared.

Loudoun County, Virginia — the self-described "data center capital of the world" — spent years developing sophisticated overlay districts and impact standards specifically for data centers. The result is a jurisdiction that can process proposals efficiently while protecting community interests. That didn't happen by accident. It happened because officials invested in understanding the asset class before being overwhelmed by it.

Smaller townships don't need Loudoun's scale of regulatory machinery. But they do need the equivalent of what Hayes Township is building: a coherent framework that reflects what data centers actually are, what they actually need, and what they actually cost the community to host.

For infrastructure developers, the lesson is equally pointed: municipalities that feel blindsided by proposals react defensively. Developers who engage proactively — sharing technical data, participating in the study process, and offering to fund independent analysis — consistently get better outcomes.

Site selectors working on data center proposals should add "regulatory readiness" to their site scoring criteria alongside the usual power, fiber, and land metrics. A jurisdiction with a thoughtful conditional use process is worth more than a jurisdiction with ambiguous zoning that might blow up mid-entitlement.

The Bigger Picture

Hayes Township's 12-month data center moratorium is a microcosm of a national dynamic playing out county by county across the Sun Belt, the Midwest, and the rural West. The demand for data center capacity is structural and accelerating — AI workloads alone are pushing hyperscalers to build faster than most communities can process the implications.

Local governments that treat this moment as an opportunity to build smart regulatory infrastructure will attract better projects on better terms. Those that either rubber-stamp proposals without standards or reflexively block them will find themselves on the wrong side of both the development community and their own constituents.

Hayes Township chose the harder path — the one that requires actual work. For everyone watching from the infrastructure investment space, that's worth noting not as a cautionary tale but as a model.

Ready to learn more about how smart regulatory frameworks can benefit your community? Explore the InfraSale Marketplace for insights and opportunities: [InfraSale Marketplace](https://infrasale.com/marketplace).

[INTERNAL LINK: data center proposals]

[INTERNAL LINK: zoning regulations]

[INTERNAL LINK: infrastructure development]