Why West Jefferson Rejects Large-Scale Data Centers

When a village council passes a resolution opposing a major infrastructure project, it’s easy to dismiss it as a local story — a footnote in the broader march of data center development across America. West Jefferson's February 2nd decision is neither a footnote nor a surprise; it’s a signal.

The West Jefferson Village Council voted to formally oppose the development, construction, and operation of large-scale data centers in their community. The resolution is blunt by design. While the source details from that meeting are still emerging, the broader pattern this decision represents is already well-established — and worth understanding if you’re tracking where data center development is heading next.

What West Jefferson Actually Decided

Village council resolutions opposing infrastructure projects aren’t rare. What makes West Jefferson notable is the framing: this isn’t a "we need more study" delay tactic or a zoning technicality. The council took an explicit stand against large-scale data center development as a category.

That kind of categorical opposition is harder to negotiate around than a permit dispute — and it sends a different message to developers scouting sites.

Councils that pass resolutions like this are usually responding to something already in motion. A site has been identified, preliminary conversations have happened, and the community heard about it — not from a press release, but from a neighbor. By the time a resolution hits the floor, the opposition is already organized. West Jefferson’s council didn’t get ahead of this; they responded to it. That’s how most of these fights start.

The Concerns Driving the Opposition

Without minimizing the specifics still coming to light from the Feb. 2 meeting, the arguments against large-scale data center siting in smaller communities follow a consistent pattern — and they’re not irrational.

Power Consumption at a Scale Communities Feel

A hyperscale data center can draw anywhere from 100 to 500+ megawatts of power, depending on its size. To put that in context: a single 200 MW facility consumes roughly the same amount of electricity as 150,000 average American homes. When that load gets added to a regional grid that wasn’t designed to absorb it, the downstream effects fall on existing ratepayers and utility infrastructure — not on the data center developer.

Local communities feel this acutely. They’re not opposed to electricity; they’re opposed to subsidizing the grid upgrades that make a facility viable, only to receive minimal tax revenue and few local jobs in return.

Jobs That Don’t Match the Promise

This is the sharpest contrarian point in the data center debate: facilities marketed as economic development engines typically employ somewhere between 30 and 200 permanent workers, depending on automation levels. A 500,000-square-foot facility might run on a skeleton crew once construction wraps. The construction jobs are real but temporary. The long-term employment impact rarely justifies the infrastructure strain — and smaller communities, more than anyone, know how to read the math on that.

Water, Noise, and Land Use

Data centers are thirsty. Evaporative cooling systems at large facilities can consume millions of gallons of water annually — a serious concern in regions already managing agricultural or municipal water demands. Add generator noise, traffic from construction and service vehicles, and the visual and land-use footprint of a campus-scale industrial facility, and you start to understand why residents in smaller communities push back harder than their counterparts in dense suburban corridors.

West Jefferson sits in Madison County, Ohio — a largely rural and agricultural area. The character of that land matters to the people who live there. That’s not sentiment; it’s land value, quality of life, and the long-term economic identity of a place.

Local Councils as the Real Chokepoint

Infrastructure developers — whether they’re building solar farms, battery storage facilities, or data centers — have learned something important over the past decade: federal policy and state permitting matter, but local councils and township trustees are often the real decision-makers in whether a project gets built.

Zoning authority, conditional use permits, utility coordination agreements, and community benefit agreements all flow through local governance. A state that’s officially "business friendly" for data centers can still produce a patchwork of communities that have decided, at the local level, they’re not interested.

Virginia’s data center corridor in Northern Virginia got built because of a rare alignment: favorable zoning, cheap and abundant power, proximity to the internet exchange at Ashburn, and a community that largely accepted the trade-offs early on. That alignment is increasingly hard to replicate. As developers push outward from established corridors — seeking cheaper land, lower power costs, and cooler climates — they’re running into communities that haven’t pre-negotiated their relationship with industrial-scale infrastructure.

Ohio has seen several of these conflicts play out in recent years, across solar, wind, and now data center development. The state legislature has tried to preempt some local opposition to energy projects through centralized siting authority, but the political backlash has been significant. Data centers, which don’t benefit from state-level renewable energy mandates, don’t even have that legislative runway.

Other councils in Georgia, Texas, and the Pacific Northwest have passed similar resolutions or imposed temporary moratoriums while they developed new ordinances. West Jefferson is part of a trend, not an outlier.

What This Means for Developers and the Industry

If you’re on the development side of this industry, the West Jefferson resolution should prompt a specific kind of self-examination. Not "how do we overcome this opposition," but "what did we do — or not do — in the community engagement process that led here?"

The projects that get built in resistant communities almost always share one trait: they did serious stakeholder engagement before the rumor mill did it for them.

That means showing up at town halls before the permit application. It means publishing an honest job creation estimate instead of a headline number. It means commissioning an independent water impact study and sharing it publicly. It means negotiating a community benefit agreement that includes local hiring preferences, infrastructure investment, and noise mitigation commitments — not because regulators require it, but because it’s how you earn a license to operate.

The data center industry is facing a parallel challenge to what the utility-scale solar industry faced five to eight years ago: rapid geographic expansion into communities that have no framework for evaluating these projects and no reason to trust developers who show up with a permit application and a PowerPoint. Solar developers who invested in community relationships built durable project pipelines. Those who treated opposition as a permitting obstacle to route around are the ones with stalled projects and legal bills.

Data center developers expanding into secondary markets — places like Madison County, Ohio — are going to encounter this dynamic repeatedly. The question is whether they learn from it proactively or reactively.

The Bigger Picture

West Jefferson’s council resolution probably won’t stop data center development in Ohio. But it will shape where that development goes and on what terms. Developers will look at the political risk profile of a community before committing capital — that’s rational. Communities that signal organized opposition early will see projects redirected elsewhere.

Whether that’s a win for West Jefferson depends on what they actually want. If the goal is to preserve agricultural land and community character while avoiding infrastructure strain, the resolution is a meaningful first step. If the goal is to attract economic development that fits the community — smaller-scale edge computing facilities, light industrial, renewable energy with local revenue sharing — then the next step is equally important: articulating what they *will* support, not just what they won’t.

Councils that only say no end up with less leverage than councils that say "not this, but here’s what works for us." That’s the posture that produces community benefit agreements, tax revenue, and projects that last.

For anyone watching infrastructure development across the Midwest, this is the dynamic to track: not which projects get announced, but which communities have built the governance capacity to negotiate on equal footing with developers who do this for a living.

West Jefferson made its position clear. What comes next — for them, and for every similar community watching this play out — is the harder and more interesting question.

Call to Action: If you’re interested in exploring the future of infrastructure development and how it impacts communities, visit InfraSale Marketplace for more insights.