Data Center Governance SeriesAnalysis

When Data Centers Come to Town, Who Actually Has the Power to Say No?

A crowded public meeting can look like the center of a local data-center decision.

ANALYSIS  •  FACTUAL, CITED  •  JULY 2026

Residents fill the room. Engineers present maps. Lawyers explain zoning. Elected officials debate water, electricity, jobs, tax revenue, noise, roads and emergency response. A vote is taken.

But by the time that meeting happens, many of the most consequential decisions may already be underway.

Land may have been assembled. Utility studies may have begun. Nondisclosure agreements may limit what officials can discuss. A developer may already expect a tax abatement, road agreement, annexation or water commitment. State law may have narrowed local authority. A lawsuit may be prepared before the final vote is counted.

The growing national conflict over data centers is therefore not simply a dispute between supporters and opponents. It is a dispute over which government has which power, when that power can be exercised and what remains negotiable after a project gains momentum.

Communities do not possess one unified authority called local control. They possess a changing collection of tools:

The effectiveness of those tools depends on state law, project location and whether the developer needs government cooperation.

Hill County, Texas, tried a broad moratorium and replaced it with a narrower approach tied to powers it could more clearly exercise. Saline Township, Michigan, denied rezoning and later entered a court-enforced development framework. Lacy Lakeview, Texas, supports a project but cannot independently create all of the regional utility capacity it may require. West Virginia preserved specified local taxes and service fees while displacing broad categories of local regulation for certified projects. Upper Merion Township, Pennsylvania, is confronting multiple large applications whose combined scale may exceed the limits of ordinary parcel-by-parcel review. Maine rejected a statewide pause partly because one former mill town wanted a specific redevelopment project to proceed.

Together, these cases reveal a basic rule:

The power to influence a data center is usually greatest before land, utilities, incentives and legal rights have been committed.

Hill County: a moratorium meets the limits of county power

On May 12, 2026, the Hill County Commissioners Court unanimously approved a one-year moratorium on data-center construction. The official minutes say the county wanted time to assess the facilities’ potentially far-reaching effects on the local community.

The pause represented the strongest possible message: development should stop while the county studied what was coming.

It did not last.

On June 4, the Commissioners Court unanimously rescinded the moratorium. County materials from the same period addressed the proposed C.R. 3106 Data Center Project and outlined powers the county could more clearly exercise over roads, bridges, drainage, floodplain management, subdivisions, infrastructure protection and public safety.

That transition matters.

Texas counties generally do not possess the same broad zoning authority available to municipalities. A county may regulate certain roads, drainage systems, subdivisions, septic systems, floodplains and public-safety matters, but that is different from possessing a general power to prohibit an otherwise lawful industrial use across unincorporated land.

Hill County’s experience demonstrates the danger of confusing political opposition with durable legal authority.

The stronger replacement strategy was not a universal data-center permit. It was a more targeted review process connected to areas where the county had clearer authority and leverage, particularly when a developer requested:

When a developer needs something from the county, the county may be able to require engineering studies, road protections, drainage analysis, emergency-response planning or financial assurances as a condition of receiving that benefit.

When the project needs nothing discretionary from the county, local leverage may be much weaker.

The Hill County lesson

A county should identify its actual legal powers before declaring a broad prohibition.

The practical question is not merely:

Can the county stop the project?

It is:

What does the developer need from the county, and what enforceable conditions can the county attach to it?

That approach is less dramatic than a moratorium, but it may be more durable.

Saline Township: a local rejection becomes a court-governed project

Saline Township possessed a tool Hill County largely lacked: zoning authority.

Related Digital proposed a data-center development across approximately 575 acres. The developer said fewer than 250 acres would be developed, with the remaining property preserved as green space or landscaping. Township Planning Commission minutes described three principal buildings totaling roughly 575,000 square feet, along with supporting structures. Those project descriptions came from the proposal and planning process and should be understood as proposed specifications.

The township rejected the requested rezoning.

That did not end the project.

The developer and landowners sued. The parties later negotiated a consent judgment approved by the Washtenaw County Circuit Court. Saline Township’s official project materials state that the data center must be developed according to the consent judgment.

A consent judgment is more than a political compromise.

It is a court-approved agreement with legal force. It can define what may be built, which conditions apply and how future township regulations interact with the authorized development.

Saline’s official materials indicate that township rules continue to apply except where they would prevent, reduce or preclude the size and scope authorized by the judgment. Other state and county regulators may still retain authority over construction, transportation, health, wastewater and environmental requirements.

The case shows that possessing zoning authority does not guarantee that a local denial will survive.

A developer may argue that the denial is exclusionary, arbitrary or inconsistent with other permitted land uses. Even when officials believe they acted properly, litigation can impose significant financial and political pressure.

By February 2026, the township was warning residents about increased concrete-truck traffic connected with foundation construction. The project was no longer simply a rejected rezoning request. It had become an active development governed partly by a judicial agreement.

The Saline lesson

A local government can win a vote and still lose control over the final outcome.

The most important settlement question is not simply how much money or mitigation a developer offers. It is:

Which future governmental powers are being limited in exchange?

Before accepting a consent judgment, communities should examine whether it restricts later authority over:

A settlement can resolve an immediate lawsuit while creating a long-term governance constraint.

Lacy Lakeview: approving a framework does not create utility capacity

Lacy Lakeview presents a different form of local-control problem.

The city authorized negotiations and execution of a nonbinding memorandum of understanding with Infrakey DC Parks LLC concerning prospective infrastructure development. Later city records documented additional discussions involving annexation, water, sewer service and infrastructure intended to support both a proposed data center and wider municipal growth.

Those actions establish city interest and a framework for continued negotiation.

They do not prove that:

A city may control its zoning and annexation decisions but depend on regional systems for:

Lacy Lakeview may support the project politically, but political support cannot manufacture physical capacity.

A nonbinding memorandum can begin a process. It cannot guarantee that regional water, sewer and infrastructure systems can support the proposed development.

The Lacy Lakeview lesson

The government approving the site may not be the government controlling the infrastructure.

Communities should map every dependent authority before approving a project.

A project is not locally controlled merely because one city holds the public hearing.

Upper Merion: several projects can become one regional impact

Traditional planning review is usually organized around individual parcels.

One applicant submits one site plan. The planning commission considers setbacks, traffic, stormwater, landscaping and compatibility. The project is recommended, denied or revised.

That model becomes strained when several large data-center applications arrive at the same time.

Upper Merion Township’s July 22, 2026 Planning Commission agenda listed three data-center proposals:

Together, those three applications represented 2,530,630 square feet of proposed development before the commission in one meeting.

Each application can be reviewed separately under the township’s normal planning process.

The infrastructure effects may not be separate.

Several nearby facilities can collectively affect:

The relevant unit of analysis should be the complete infrastructure program, not merely the property line around each application.

West Virginia: local revenue without ordinary local regulation

West Virginia adopted one of the strongest state-centered data-center frameworks in the country.

The enacted legislation created certification pathways for high-impact data centers and associated microgrid districts. For projects certified under that framework, the law restricts local governments from enforcing broad categories of local regulation involving zoning, land-use approvals, noise, lighting, viewsheds, building permits, local inspections and licensing requirements.

The statute applies within the certification framework and should not be interpreted as automatically exempting every data center in the state from every local rule.

At the same time, the law preserves specified local taxes, utility charges and service fees.

This creates a revealing division:

A community can receive revenue from a project while losing much of its ordinary authority to regulate how that project fits into the community.

That separation raises a fundamental civic question.

Is local tax revenue an adequate substitute for local authority over siting, noise, lighting, building design, expansion, road access, land compatibility and community character?

The answer may differ among residents, but the tradeoff should be explicit.

Maine: local control can also mean the right to say yes

Many national discussions assume that communities want greater power so they can stop data centers.

Maine demonstrates why that assumption is incomplete.

The Maine Legislature passed LD 307, which would have created a Data Center Coordination Council and temporarily restricted state and municipal permitting of data centers with loads of 20 MW or more until November 1, 2027. Governor Janet Mills vetoed the bill on April 24, 2026. She said she supported a temporary moratorium in principle but objected because the legislation did not exempt a proposed redevelopment at the former Androscoggin Mill in Jay. The Legislature sustained the veto on April 29.

Supporters described the Jay proposal as a roughly $550 million redevelopment expected to create more than 800 construction jobs and at least 100 permanent positions. Those were projected benefits, not completed outcomes.

Maine then moved toward another model: a state advisory and policy-development process rather than an immediate blanket pause.

The Maine lesson

Statewide precaution can conflict with local economic recovery.

Local control includes the right to demand safeguards. It can also include the right to support a project that state policymakers might otherwise delay.

Pine Island: secrecy can move the decision before the hearing

Pine Island, Minnesota, adds another dimension: the role of nondisclosure and environmental review.

The proposed Project Skyway development has been associated with a roughly 482-acre site. Public controversy grew around the project’s environmental review, the identity of the end user and how much information residents received before important decisions advanced.

Minnesota legislative materials later identified Google as the intended end user and documented broader concerns about local officials using nondisclosure agreements during major data-center negotiations.

Environmental litigation temporarily interrupted project activity, but the final merits of that dispute should not be treated as resolved.

The broader lesson is about timing.

Public disclosure should begin before private commitments narrow the available choices.

Local control is a layered system

The national cases show that no single legal tool is sufficient.

A zoning ordinance cannot create water.

A moratorium cannot survive if the government lacks authority to adopt it.

A development agreement cannot replace environmental permits.

A public vote cannot undo a consent judgment.

A tax payment cannot restore local regulatory authority displaced by the state.

An environmental lawsuit can pause construction but may arrive after years of private planning.

Communities need a layered framework.

A practical local-control framework

  1. Early project registration
  2. Restrictions on nondisclosure agreements
  3. Cumulative-impact review
  4. Independent engineering review
  5. Utility-capacity certification
  6. Public incentive hearings
  7. Emergency-service agreements
  8. Settlement guardrails
  9. Decommissioning and financial security
  10. State minimum standards that preserve stronger local rules

The decision often happens before the public vote

Data centers can bring real benefits:

They can also create major obligations:

The proper democratic question is not whether every project should be approved or rejected.

It is whether communities receive accurate information and meaningful authority before their choices narrow.

The common lesson is timing.

By the time land is assembled, utilities are engaged, incentives are discussed and lawyers are involved, a public hearing may no longer decide whether a project happens.

It may decide only how expensive it will be to change course.

Local control is most meaningful before the project becomes an expectation.

Sources

Hill County, Texas — Commissioners Court minutes (May 12, 2026; June 4, 2026) and Major Industrial Development Review Policy.

Saline Township, Michigan — Data Center Update page, consent judgment and project records, and Planning Commission minutes.

Lacy Lakeview, Texas — City Council records and nonbinding MOU materials.

Upper Merion Township, Pennsylvania — July 22, 2026 Planning Commission agenda.

West Virginia — enrolled HB 2014 and West Virginia Code provisions for high-impact data centers and microgrid districts.

Maine — LD 307 bill history, Governor Janet Mills's veto message, and the executive order establishing the Data Center Advisory Council.

Pine Island, Minnesota — Minnesota House legislative materials and Minnesota State Law Library court-access guidance.

You may also be interested in
Prairie View A&M Has Engineers, Land and an Innovation Plan. Will the AI Infrastructure Boom Strengthen It? Beyond Tax Revenue: What Does a Data Center Leave Behind?
@legion_rd  |  Praevoium