Why data center zoning fights continue after developers promise jobs and tax revenue

A city can gain from a data center while some of its residents experience the project primarily as an industrial neighbor. That difference helps explain why a favorable economic forecast does not necessarily end a zoning dispute.

Virginia’s legislative research commission identified both economic benefits and local impacts in its review of the industry. Its findings are a useful starting point precisely because the public choice cannot be reduced to a single investment figure. JLARC’s data center study.

Land-use resistance concerns a specific location. The question is whether a building, its equipment and its supporting infrastructure fit the surrounding area under conditions a public authority can enforce. That question remains even when digital services are useful and the proposed investment is real.

What a zoning decision actually decides

The scope of a land-use decision depends on local law. A planning authority may consider a change in permitted use, the physical arrangement of a site or a request for special permission. It should not be assumed that every hearing gives officials unlimited authority to reopen every aspect of the project.

For residents, this can create a practical problem. Their concerns may cross noise, water, power and transport, while the meeting before them addresses only one part of the approval chain. The fact that an official refers a question elsewhere does not show that the question has been answered.

A credible public explanation identifies the full set of approvals and the authority responsible for each. It also distinguishes requirements already imposed from commitments offered voluntarily by the applicant. A presentation slide is not the same as a permit condition.

That distinction matters when a developer changes its plans. If a commitment is essential to the finding that a site is compatible with its neighbors, the public should be able to identify where the commitment is recorded and what happens if it is not met.

The regional financial questions appear in our electricity article. A local zoning vote should not be presented as proof that the entire utility system’s costs have been resolved.

Noise is a question of exposure and enforcement

Residents and developers can talk past each other when one describes compliance with a numerical limit while the other describes an intrusive sound. A useful review needs to specify what is measured, where it is measured and under what operating conditions.

The questions include the treatment of nighttime operation, changes in background sound and simultaneous operation of equipment. A facility’s normal cooling system and its emergency equipment may require different analysis.

This article does not assign a sound level to a named facility. That would require the actual measurement or modeling record. The point is that a general assurance of compliance is incomplete unless the standard and measurement method are publicly intelligible.

A proposed barrier or setback may reduce exposure. Its effectiveness should be evaluated against the actual equipment location and neighboring uses. A rendering that shows trees is not a substitute for the analysis, and an objection based only on the size of the building is not proof that the analysis is wrong.

Enforcement also matters. Residents need a clear route for reporting a problem, a responsible agency and a procedure for determining whether a violation occurred. If the solution depends on measurements residents cannot get, the protection may be difficult to use in practice.

The strongest neighborhood argument

The strongest argument from nearby residents is about concentrated burdens and limited exit options. A local government can receive revenue across its jurisdiction while a smaller group lives nearest to equipment, lights, construction activity and altered views.

Property owners may have made long-term decisions under the previous land-use rules. A large change can therefore raise a question of reliance as well as preference. Calling every objection resistance to progress avoids the actual issue: who bears the consequences of a public decision to change the permitted use?

Renters deserve attention alongside homeowners. They can experience noise and disruption without owning the property whose value dominates the public discussion. People living across a jurisdictional boundary can face effects without voting for the officials who approve the site.

Those considerations do not give every neighbor an unlimited veto. They explain why a decision based only on aggregate tax revenue can miss key distributional effects.

A transparent process would describe the affected area and explain what mitigation is intended to protect it. The public should be able to distinguish mitigation from compensation and identify which problems cannot realistically be addressed.

The strongest development argument

Supporters can reasonably argue that a locality needs places for industrial and digital infrastructure. If every site is rejected because some impact remains, a planning system may offer no practical path for a lawful use.

They can also argue that clear rules are fairer than changing requirements after a developer has invested in compliance. A proposal that meets a published standard deserves a clear explanation if officials decide the standard is inadequate or a different approval is necessary.

Those arguments are strongest when the applicant provides a defined project and accepts enforceable conditions. They weaken when the public is asked to approve a broad envelope of development while essential operating details remain unknown.

The alternative also needs to be honest. Rejecting a data center does not guarantee that the site will remain undeveloped. Approving one does not prove that no other viable use could have produced a better result. The comparison should use plausible alternatives allowed by the site and its infrastructure.

Our examination of tax incentives addresses that counterfactual problem. Public benefits should be compared with realistic alternatives, rather than with either an empty parcel forever or an imagined perfect employer.

Local control has competing meanings

For opponents, local control may mean the ability of residents to refuse a project. For supporters, it may mean allowing elected local officials to accept a project without a statewide prohibition. These positions can conflict even when both use the same phrase.

The issue becomes more complex where the consequences cross boundaries. A local government may approve a facility whose power demand requires infrastructure elsewhere. Conversely, a state policy might constrain a municipality that wants the tax base.

A sound division of authority asks which government can evaluate which impact. The host locality is well placed to assess neighboring land uses. A regional or state body may be better placed to assess shared utility investment or cumulative demand.

Neither level automatically represents every affected person equally. State officials can overlook a specific neighborhood, while local officials can overlook costs outside their boundary. The approval record should explain how those gaps are addressed.

This is one reason moratorium debates are more complex than a contest between local democracy and economic growth. A pause’s scope and the authority imposing it affect whose choices it protects and whose it restricts.

Transparency before a decision becomes difficult to reverse

The timing of information can matter as much as its existence. A technical report released shortly before a final vote may be public in a formal sense but difficult for residents to assess.

Early disclosure allows questions to shape the design. Later disclosure can turn a solvable planning issue into a dispute over whether the process was fair. This is an analytical observation about decision-making, not a finding that every contentious project was handled improperly.

Confidential business information may be legitimate. Still, officials can explain the proposed land use, scale, general infrastructure demand and enforceable limits without necessarily revealing proprietary computing arrangements.

The public should also know who owns the applicant, which entity is making the promises and whether those promises bind future owners. A project can change hands after permission is granted. Conditions attached only to a presentation by the original applicant may provide less certainty than conditions that run with the approval.

Where an agreement offers community benefits, the record should identify recipients and timing. A promised payment does not show who will administer the money, how its use will be reported or whether affected neighbors can influence the allocation.

Cumulative impacts need their own review

A facility may look manageable in isolation while raising different questions alongside other approved projects. Cumulative effects can concern roads, sound, water or the supporting electricity system.

That does not justify adding together every speculative proposal as though each will be built. A cumulative review needs to distinguish operating sites, approved projects, applications and preliminary inquiries.

The same caution applies in the other direction. Evaluating each application as if the surrounding projects do not exist can understate shared demands. The goal is a realistic scenario, with the assumptions visible.

Our water article explains why peak demand and local capacity belong in that assessment. An annual average at one facility cannot answer every question about a cluster of developments.

What would resolve the dispute?

Some disagreements can be narrowed by a different site layout, a stronger operating limit or a clearer enforcement arrangement. Others involve a real choice between incompatible uses. A fair report should allow for both possibilities.

Approval can be justified where the evidence demonstrates compatibility and the benefits withstand scrutiny. Rejection can be justified where the standard is not met or the impacts cannot be acceptably managed. Neither outcome follows automatically from the project being a data center.

This article does not measure the national prevalence of neighborhood opposition or estimate an effect on nearby property values. Those claims would require different evidence. Public comments reveal the arguments presented by participants. They are not a representative opinion survey.

The records reviewed for this analysis were accessed November 5, 2026. The central question for a future decision is concrete: what can this authority require at this site, and will the written conditions protect the people asked to live with the result?

Photo credit

Representative file photo: Victor Grigas / Wikimedia Foundation, via Wikimedia Commons, CC BY-SA 3.0. The source photo is unaltered; the site may crop its display.

Differing perspectives

How should local governments decide whether a data center fits a site?

Each position is summarized as its supporters make it, with equal weight and in alphabetical order. A summary is not an endorsement; the evidence for each is weighed in the story above.

• Pause growth until safeguards are adequate

  Who holds it: Food & Water Watch

  New development should pause until a regulatory framework addresses environmental and social harms. The group argues that continued construction risks committing communities before adequate protections exist. Public rules should be clear before construction starts.

  In their words: Food & Water Watch ↗

• Require firm financial commitments

  Who holds it: PUCO’s adopted consumer-protection approach

  New connections should proceed under rules protecting other customers against the cost of underused infrastructure. The regulator presents development and consumer safeguards as compatible objectives. Public rules should be clear before construction starts.

  In their words: Public Utilities Commission of Ohio ↗