What the Community Fights Are Really About? & Who is Responsible?
Listen to what people actually say at the hearings, and the same worries surface again and again. Strip away the local specifics and the concerns sort themselves into a short, consistent list: clean air, clean water, noise, community safety — and the price of electricity.
That list is worth pausing on, because it reveals something the word "backlash" hides. This isn't one undifferentiated wall of opposition. It's two distinct fights, with different causes, different owners, and different fixes. The first is environmental and physical — air, water, noise and safety. The second is economic — electricity rates, cost-shifting, and whether the community gains anything real. We tend to bundle them into a single mood and aim our solutions at the whole blob. But they are not the same problem. Untangle them, and each turns out to be addressable, and it becomes clear who has to do the addressing.
The first fight: air, water, noise and whether the rules have caught up
When residents pack a council chamber worried about a data center's water draw, its diesel generators' noise, or its emissions, it's easy to read this as opposition to the project itself. More often, it reflects something different: a sense that the permitting and regulatory framework isn't yet built for developments of this kind or scale to protect the community.
That distinction matters, because it relocates the problem, and points to a solution that doesn't require fighting anyone. Many communities simply haven't had to evaluate a industrial plant or load before. Their zoning, their environmental review, their permitting processes were written for a different era of development. When residents worry that those rules won't fully safeguard their air and water, they're right, not because the framework has failed them, but because it hasn't yet been updated to match the demands of this new use, the growth of the community around it, and current sustainability commitments. This is especially true where the natural sites for these projects are decommissioned industrial or power-plant properties, whose old permits and zoning may predate both the surrounding neighborhood and the environmental standards now expected of them.
Seen this way, the environmental fight isn't really a fight against development at all. It's a signal that the rules need to catch up before the development arrives. The answer isn't to block the project or to assume the regulator has failed; it's for states and municipalities to do the work of modernizing permitting, review, and auditing so that a granted permit genuinely means what the community needs it to mean — that they are protected to a current, credible standard. The burden sits with the framework to catch up, not with the community to simply accept what's offered.
This is also not a data-center-specific problem, and that's the point to hold onto. A community whose environmental rules haven't kept pace will have the same worry about whatever new development shows up next. Data centers happen to be what's arriving now, so they've become the lightning rod. But the underlying question — are our rules ready to protect our air and water from developments at this scale?
The second fight: economics, and the end of the vacuum
The other half of the opposition is economic — the fear that a data center will raise electricity bills, shift grid-upgrade costs onto ordinary ratepayers, and give little back. These are rational concerns; in some regions, data center load has measurably driven up wholesale power costs. But they are answerable, and they're answerable with numbers.
Here the ownership is shared. The state sets the rules that prevent cost-shifting, and the developer carries the burden of proving, transparently, what the project actually costs and contributes. That second piece — transparent, verifiable disclosure — is where the ground has genuinely shifted. Massachusetts's new framework requires operating data centers above 25 megawatts to file annual reports and disclosures, and applicants must attest they will. The state's Statement of Expectations goes further, calling for public disclosure of location, size, energy and water demand, and employment data — with independent verification. Massachusetts's existing qualified-data-center regulation already requires annual reports to the state, signed under penalty of perjury, on actual jobs created and actual investments made. New York's emerging framework points the same direction, toward community investment funds and standardized reporting.
One reason the economic fight is winnable in New England specifically is that the region's hardest constraint — grid interconnection — can sometimes be solved by reusing what already exists. Retired and retiring power plants come with something enormously valuable: an existing, high-capacity connection to the transmission grid, already permitted, that would otherwise take years and vast expense to obtain. This is the logic behind the Markley Group's purchase of a retired plant's grid position in Lowell, and behind the interest in decommissioned sites across the region. Reusing that connection is not, in itself, a bad option — it can shorten timelines, avoid greenfield disruption, and lower the cost that might otherwise land on ratepayers. But reuse solves only the capacity problem, not the community safety protection as highlighted in the first fight paragraph.
The closing point: this shouldn't be really about data centers
Data centers are the topic of the day. Projects are being paused and canceled across the country, and the political energy is intense. But the deeper problem the fights expose is not specific to this industry.
The environmental half of the opposition is, at its core, a question about whether the rules are ready — whether permitting has kept pace well enough to protect a community's air and water from developments at this scale. That question applies to any development that touches public health and natural resources — and where the rules haven't caught up, the fear is rational and the fight will recur, whatever the next project happens to be. The fix is not a data-center patch. It's modernizing permitting and auditing frameworks, across the board, so that a granted permit genuinely means a community is protected to a current, credible standard.
The economic half is answerable too; through cost rules that stop developers from shifting their burdens onto ratepayers, and through the mandatory, independently verified disclosure that Massachusetts and New York are now building into law, so a community can weigh real value against real, permitted, bounded impact.
Do both well, and the fight shrinks to its proper size. Not "should this be built at all," fought in the dark against a vacuum of information, but "does this specific project meet the standard," argued over numbers everyone can see. That is a smaller, healthier, more honest fight, and it lets communities do what they should be able to do: weigh the jobs, the tax base, the grid support, and the genuine local value a well-built project brings against real, permitted, bounded impact, once the permitting has been modernized and shown to be safe.
Data centers just happen to be the development forcing the question today. Getting the answer right will matter long after this particular wave has passed.