Summary

Data centers were once sold to local governments as low-impact industrial neighbors: quiet buildings, little traffic, strong tax revenue, and no new school demand. The AI buildout has changed that bargain. Hyperscale facilities now arrive with enormous power requirements, water concerns, backup generation, noise questions, and grid-cost implications that communities are no longer willing to treat as routine land-use issues.

The result is a growing wave of moratoria. Montgomery County, Maryland, recently approved an 18-month pause on new data center permits so officials can develop standards for siting, infrastructure, water, noise, and ratepayer protection. Nationally, policy organizations are documenting a broader shift: opposition is moving from individual project fights to systematic pauses designed to reset the rules before the next wave of development arrives.

For years, commercial real estate developers had a reliable pitch for local county boards: data centers would bring substantial tax revenue without the usual residential burdens. No school-aged children. Minimal traffic. Quiet buildings tucked behind tree lines. In the land-use world, that sounded like the ideal light-industrial deal.

That pitch worked—until artificial intelligence changed the scale of the industry.

Today’s hyperscale data centers are not simply windowless warehouses full of servers. They are high-voltage infrastructure campuses with massive electricity needs, cooling demands, backup generation, and regional consequences. Local officials and residents are beginning to see them less as passive real estate assets and more as utility-scale projects that can reshape power planning, water use, ratepayer exposure, and community character.

The political reaction has been swift and revealing: the local data center moratorium boom is here.

From Project Battles to Legislative Pauses

When an industry loses its social license, opposition stops being confined to individual site plans. It becomes procedural. Communities stop asking whether this particular project should be approved and start asking whether the rules themselves are adequate.

Montgomery County, Maryland, offers a clear example. The County Council unanimously approved an 18-month moratorium on new data center permits, extending an earlier executive pause and giving county leaders time to write more durable standards for large-load facilities. The immediate backdrop was a proposed data center campus in Dickerson, but the policy response was broader than one project.

This is the important shift. Instead of treating each data center proposal as a discrete zoning matter, local governments are beginning to freeze approvals until they can answer bigger questions: Who pays for grid upgrades? How much water will be used in peak conditions? What happens to nearby property owners? What safeguards protect residential utility customers? Across the country, those unanswered questions are rapidly eroding the industry’s social license.

The Property Rights Tension Runs Both Ways

Moratoria are politically popular because they sound temporary and cautious. But they also expose a deeper property-rights tension on both sides of the fence.

· The local government and community view: Host communities argue they have the right to pause development long enough to protect shared infrastructure, preserve groundwater and surface-water resources, limit noise and emissions, and prevent residential ratepayers from subsidizing new utility capacity.

· The developer and landowner view: Developers and private landowners argue that sudden legislative freezes disrupt negotiated transactions, chill capital investment, undermine expected land value, and change the rules after substantial planning has already occurred.

Both arguments deserve to be taken seriously. But when developers respond by insisting that a 300- or 500-megawatt campus is “just another warehouse,” they reinforce the very concern driving the backlash: that the industry wants ordinary zoning treatment for extraordinary infrastructure impacts.

The New Playbook: Transparent Resource Budgets Before Site Plans

If hyperscalers and data center developers want to restore trust, they need to stop leading with the old commercial real estate script. The “low traffic, high taxes” pitch is no longer enough.

Before filing a zoning application or site plan, developers should publish a transparent resource budget that answers the community’s core questions in plain language:

1. Power and grid protection: Quantify peak megawatt demand and show, through enforceable tariffs or rate protections, that residential customers will not subsidize the new substation, transmission upgrades, or capacity costs.

2. Water infrastructure: Disclose expected annual water consumption under peak summer conditions and explain whether closed-loop, reclaimed-water, or dry-cooling alternatives can reduce local watershed pressure.

3. Acoustic and environmental controls: Provide realistic noise modeling for cooling systems and backup generator testing, with enforceable limits at neighboring property lines.

4. On-site infrastructure capital: Commit to funding the necessary substations, interconnections, and site-specific utility upgrades rather than shifting those costs to municipal taxpayers or residential ratepayers.

Key Takeaways

· Data centers are no longer being evaluated as ordinary industrial buildings. Communities increasingly view them as energy- and water-intensive infrastructure assets.

· Moratoria are a symptom of lost trust. Once local governments pause approvals across the board, the debate has moved beyond one project.

· The core political issue is cumulative impact. Residents are asking who pays for power upgrades, who bears water risk, and who absorbs noise, emissions, and ratepayer exposure.

· Developers need a new approval strategy. The next successful projects will lead with transparent resource budgets, enforceable safeguards, and early community engagement.

The Bottom Line

A data center is not a warehouse. It is an energy- and water-intensive utility asset wrapped in a real estate transaction.

Developers who continue to treat local communities as passive hosts will encounter more closed doors, longer pauses, and tougher entitlement battles. The path forward requires moving past glossy PR boards, publishing clear resource limits early, and building local trust before asking for a permit.

Call to Action

If your community is facing a proposed data center, do not start with slogans. Start with questions. Ask for the peak power demand, the water budget, the ratepayer protections, the noise model, and the developer’s written commitment to fund the infrastructure it needs. And if you are a developer, publish those answers before the first public hearing—not after opposition has already organized.

Social license is not granted by a zoning code. It is earned in public, before the permit fight begins.

Summary

State-level siting approval can help renewable energy projects move forward, but it cannot replace the legitimacy built through a strong local record. Recent disputes in Michigan and Iowa show that when developers bypass county zoning too quickly, they may gain a state forum while also creating litigation risk, hardening community opposition, and giving opponents a clearer procedural argument. The better strategy is to engage locally first, propose project-specific safeguards, and treat state preemption as a backstop rather than the opening move.

· State approval is not a substitute for local legitimacy. A project can win at the commission level and still face serious local resistance.

· Skipping county process creates procedural risk. Opponents can argue that the project failed to build the record required before seeking state relief.

· Community concerns harden when people feel bypassed. Setbacks, drainage, screening, road use, and decommissioning should be addressed before the fight escalates.

· The best strategy is local-first. Developers should exhaust county pathways, offer project-specific safeguards, and use state preemption only as a backstop.

Utility-scale renewable energy projects are running into a harder local politics than many developers expected. In response, state legislatures and utility commissions have increasingly offered a tempting workaround: state-level siting approval.

On paper, the logic is straightforward. If a county board will not approve a wind, solar, or storage project, the developer can move the fight to a state forum designed to streamline infrastructure decisions. In Michigan, Public Act 233 created a siting process at the Michigan Public Service Commission for utility-scale wind, solar, and energy storage projects under certain circumstances, and Michigan guidance explains that the law gives the Commission permitting authority unless a local government has adopted a compatible renewable energy ordinance.¹

For developers staring down interconnection deadlines and capital commitments, that can feel like a silver bullet. But the political and legal reality is less forgiving: state preemption may move the approval venue, but it does not manufacture local legitimacy.

The Preemption Trap

Two current disputes show why the “just go to the state” strategy can backfire.

1. Wexford County, Michigan: The preemption pivot

In Wexford County, the local planning process became a flashpoint when officials and residents objected to zoning changes tied to a proposed large solar project. The key issue was not merely whether solar belongs in the county. It was whether broad zoning changes would open agricultural land to industrial-scale use without enough project-specific guardrails.

Under Michigan’s new siting framework, a developer may have a path to the Michigan Public Service Commission. But the moment a project pivots from county deliberation to state override, the story changes. What might have been framed as landowner opportunity and tax base growth becomes a fight over who gets to decide the future of the county.

2. Cerro Gordo County, Iowa: The courtroom escalation

In Iowa, that escalation is already happening. Cerro Gordo County has filed for judicial review after the Iowa Utilities Commission approved a 500-megawatt solar generating facility proposed by River City Energy. Local reporting says the project would cover roughly 3,000 acres, and the county argues the developer did not first apply for a county zoning permit or seek rezoning before going to the state.²

That distinction matters. The county is not simply arguing “no solar here.” According to local coverage, Cerro Gordo County says utility-scale generating facilities are allowed in industrial and commercial districts and that applicants can seek rezoning. Its argument is procedural: the state allegedly allowed the project to leapfrog the local pathway instead of requiring the developer to build a record there first.²

Why the Shortcut Becomes the Long Way Around

When developers treat state preemption as the main siting strategy instead of a last-resort backstop, three predictable risks emerge.

· Litigation risk rises. A state certificate issued over an incomplete or hostile local record invites county-led lawsuits, administrative appeals, and injunction requests. A process meant to save months can become years of litigation.

· Community opposition hardens. Residents who might have accepted a project with setbacks, screening, drainage protections, and decommissioning guarantees often dig in when they believe local self-government has been ignored.

· The ownership narrative changes. Developers may frame siting as a matter of landowners choosing how to use their property. But where outside corporate owners, tenant farming relationships, or large land aggregations are involved, a state override can reinforce the perception that local land policy is being dictated from elsewhere.

The Better Playbook: Local Legitimacy First

State preemption should be a safety net, not the opening move. Infrastructure leaders who want projects that can actually be built should do three things before asking a state agency to rescue them.

1. Offer project-specific rules, not blanket zoning changes. County boards are often more willing to consider narrow conditional-use terms, acreage limits, and enforceable site plans than broad amendments that appear to industrialize entire agricultural districts.

2. Exhaust local pathways first. Even in preemption states, applying locally builds an auditable record of good-faith engagement. That record matters if the dispute later moves to a state commission or court.

3. Put plain-spoken siting standards on the table early. Setbacks, vegetative screening, stormwater and drainage protections, agricultural mitigation, road-use agreements, and decommissioning security should be discussed before—not after—the vote.

The lesson from Iowa and Michigan is simple: bypassing the county courthouse does not eliminate local resistance. It just changes the battlefield—and often gives opponents a cleaner procedural argument.

Potential Challenges

Even a local-first strategy does not guarantee an easy path. Developers, county officials, landowners, and opponents still have to navigate several practical challenges that can derail a project or distort the public debate. Federal and national-lab research emphasizes that large-scale renewable siting can involve multiple levels of government, public involvement requirements, local land-use standards, interconnection and transmission constraints, environmental considerations, and host-community priorities.³

· Timing pressure can push parties toward shortcuts. Interconnection queues, tax-credit deadlines, financing milestones, and equipment commitments can make slow local deliberation feel impossible; Berkeley Lab’s developer survey found that about half of wind and solar projects experience delays of six months or more, with permitting, grid interconnection, local ordinances or zoning, and community opposition among the leading causes of delay or cancellation.⁴

· Local standards may be outdated or unclear. Many county ordinances were not written with modern utility-scale solar, wind, or battery storage in mind, leaving boards to improvise under public pressure; DOE and Berkeley Lab’s national inventory shows that siting authority, standards, timelines, and public-involvement requirements vary widely across states and often depend on project size.³

· Information gaps can fuel mistrust. Residents may not have clear answers on drainage, fire response, glare, setbacks, road damage, property values, or decommissioning until late in the process; DOE notes that siting decisions shape benefits and burdens for local communities, ecosystems, and agricultural areas and that host communities frequently have questions about those impacts.⁵

· State preemption can polarize the room. Once a project appears headed to a state commission, local debate may shift from project design to local control, making compromise harder; research on developer engagement found that communities are often notified only after site control has been secured, limiting how much a project can still change in response to public feedback.⁶

· Legal uncertainty can chill investment. Counties, developers, and financiers may all hesitate when it is unclear whether state approval, local zoning, or a court ruling will ultimately control the project’s fate; the Sabin Center has tracked hundreds of contested renewable projects and reports that local restrictions and lawsuits targeting renewable facilities have become more prevalent across the United States.⁷

Conclusion

Renewable energy projects do not fail only because opponents dislike wind turbines, solar panels, or battery storage. They often fail because the process makes communities feel like decisions have already been made somewhere else. State-level approval can resolve a permitting impasse, but it cannot repair a weak local record after trust has already collapsed. The projects most likely to survive legal, political, and reputational pressure are the ones that treat county process as part of the infrastructure—not as an obstacle to route around.

Call to Action

If you are developing, advising, investing in, regulating, or opposing utility-scale renewable projects, do not wait until the room is already divided. Start with the county record. Ask whether the local process has been exhausted, whether residents can see enforceable protections in writing, and whether the project could survive public scrutiny before it ever reaches a state commission.

If this analysis sharpened how you think about renewable siting, subscribe to Politely Losing, share this article with a county official, developer, landowner, attorney, or energy investor who needs to hear it, and send me the local siting fight I should examine next.

Sources

1. State of Michigan, “Renewable Energy and Storage Facility Siting,” explaining that Public Act 233 of 2023 establishes a Commission siting process for utility-scale wind, solar, and energy storage facilities under certain circumstances; University of Michigan Graham Sustainability Institute, “Michigan’s New Renewable Energy Siting Law,” explaining that the law grants permitting authority to the Michigan Public Service Commission unless local governments adopt compatible renewable energy ordinances.

2. ABC 6 News / KAALTV, “Cerro Gordo County files lawsuit against Iowa Utilities Commission over solar farm development,” reporting that Cerro Gordo County filed for judicial review after approval of a proposed 500-megawatt River City Energy solar facility and describing the county’s zoning and procedural arguments.

3. U.S. Department of Energy, “Siting of Large-Scale Renewable Energy Projects,” and Lawrence Berkeley National Laboratory / DOE, “Siting Clean Energy: An Inventory of State Policies and Permitting Authorities,” describing the complexity of renewable siting, including multiple levels of government, public involvement requirements, varying siting standards, and the role of local authority.

4. Lawrence Berkeley National Laboratory, “Large-scale wind and solar developers concerned about social factors affecting deployment,” summarizing survey findings that roughly one-third of siting applications were canceled, about half experienced delays of six months or more, and local ordinances or zoning, grid interconnection, and community opposition were leading causes of cancellations and delays.

5. U.S. Department of Energy, “Large-Scale Solar Siting Research,” explaining that large-scale solar siting requires consideration of interconnection costs, transmission access, zoning ordinances, wildlife and environmental impacts, host-community needs and priorities, and eventual project benefits and burdens.

6. Lawrence Berkeley National Laboratory, “Utility-scale developers seek input from renewable energy host communities, but experience challenges implementing community engagement,” reporting that developers often notify the public after securing site control and that developers report challenges including organized opposition, misinformation, high costs, and uncertainty about the most effective engagement strategies.

7. Sabin Center for Climate Change Law, “New Sabin Center Report Finds that Local Laws and Lawsuits Targeting Renewables Becoming More Prevalent in the US,” reporting increases in severe local restrictions, contested projects, and litigation involving renewable energy facilities through 2024.

Watch the Video

Major infrastructure projects are increasingly running into a basic political problem: the people who absorb the impacts are not always the people who collect the benefits.

When a developer pitches a hyperscale data center, a high-voltage transmission line, or a utility-scale solar project, the conversation often begins with a familiar exchange. The developer promises private investment, construction activity, jobs, and a larger tax base. In return, the host county approves a permit, rezoning, or siting agreement.

On paper, this is the standard host-community bargain. In practice, it is often too narrow.

But infrastructure impacts do not stop at municipal boundaries.

A county line drawn generations ago does not protect a shared aquifer. It does not keep a transmission corridor from cutting across a farm that does not consume the power. It does not prevent neighboring emergency responders, homeowners, water systems, and motorists from absorbing the consequences of a project they had little or no voice in approving.

That mismatch is creating a more visible category of infrastructure resistance: the rise of the impact community.

An impact community is any neighboring jurisdiction, city, district, or local system that carries the physical, environmental, or operational burden of a major development while receiving little or none of the direct tax revenue.

For developers, utilities, and public officials, this is no longer a side issue. Ignore impact communities, and a project that looked politically settled can quickly become a lawsuit, a regional water fight, a permitting standoff, or a decade-long operating headache.

Once you start looking for this pattern, it shows up everywhere.

Two Flashpoints Show the Problem

The impact-community problem is not theoretical. It is already showing up in disputes over data centers, transmission lines, and renewable-energy siting.

When Water Crosses County Lines

In Sangamon County, Illinois, officials approved a major data center project near Waverly. Supporters emphasized the economic-development upside: investment, property-tax revenue, and a new industrial anchor for the county.

The geography complicated the politics. The site sits near Waverly, a community just across the line in neighboring Morgan County. That meant the county positioned to receive much of the tax upside was not necessarily the same community most exposed to questions about water, land-use compatibility, and adjacent-property impacts.

Residents near the site sued Sangamon County and the county board, seeking to overturn the approval. The lawsuit challenged the county’s process and argued that the project’s impacts on nearby farms, residences, and local businesses had not been fully understood before approval.

The lesson is straightforward: if a project depends on regional resources, nearby landowners, or neighboring municipal systems, a single-county approval strategy may be legally sufficient but politically fragile.

When Transmission Lines Cross Working Land

A related dynamic appears in debates over high-voltage transmission corridors. Grid planners may see a line as a regional reliability asset. Landowners may experience it as a direct operating impairment, especially when a proposed route crosses working agricultural land rather than unused open space.

When a proposed alignment crosses productive farmland, the burden is not limited to the acreage under the easement. A transmission corridor can disrupt irrigation, crop rotation, equipment movement, food-safety practices, and the daily logistics of harvest.

That is why standard per-acre compensation can miss the real cost. The project is not merely buying access to land. It is changing how that land functions as a business, an operating system, and sometimes a family asset.

Why State Preemption Is Not a Cure-All

When local opposition slows infrastructure deployment, state legislatures often reach for preemption. The logic is understandable. Some projects serve regional or statewide needs, and a purely local veto can make planning nearly impossible.

Michigan’s Public Act 233 is one example. The law created a state-level siting process for certain large wind, solar, and energy-storage facilities through the Michigan Public Service Commission, while allowing local governments to retain authority if they adopt compatible renewable-energy ordinances.

State preemption can help a project obtain a certificate. But a certificate is not the same thing as legitimacy. If a state override becomes a substitute for engagement with impact communities, three risks tend to follow:

· It deepens political hostility: Bypassing local boards can reinforce the belief that rural communities are being asked to absorb industrial costs for someone else’s benefit.

· It invites legal and procedural resistance: Communities that lose one decision point often look for others, from litigation and moratoria to scrutiny of roads, drainage, building permits, and emergency-response plans.

· It creates long-term operating friction: A project built over fierce local objection can face years of permit disputes, strained emergency-response cooperation, and a hostile political environment.

The core point: a project can win the legal process and still lose the community.

The Better Playbook: Regional Benefit Sharing

If infrastructure developers want durable approvals, they need to stop treating the host jurisdiction as the only community that matters.

A modern siting strategy should begin with a regional impact framework before conflict hardens. That framework should include four moves:

1. Map the physical footprint, not just the tax footprint: Identify every municipality that supplies water, manages emergency response, hosts access roads, or shares a viewshed with the facility. Treat those communities as core stakeholders from day one.

2. Use regional benefit-sharing agreements: Move beyond single-town host agreements. If a data center’s water demand affects a neighboring utility, create a binding agreement that helps fund water infrastructure, reservoir work, or rate offsets in the impact community.

3. Assess operational impacts early: For farms and linear infrastructure, look beyond static land appraisals. Evaluate irrigation lines, crop rotation, certification impacts, and equipment access before a preferred corridor is locked in.

4. Fund independent technical advice: Do not expect a small township or water board to rely only on a developer’s projections. Give impact communities resources to hire their own engineers, hydrologists, or safety experts.

Key Takeaways

· The host community is not always the impact community.

· County lines do not contain water, traffic, emergency-response obligations, viewshed disruption, or agricultural operating impacts.

· State preemption can produce a certificate, but not necessarily consent.

· Regional benefit-sharing agreements should become standard practice for large infrastructure projects.

The Bottom Line

Major infrastructure will always involve trade-offs. But asking one community to absorb the risk while another collects the reward is not a durable development strategy.

Projects succeed when their benefits, risks, and responsibilities are aligned across every border they touch. That means developers need to negotiate with the full geography of impact—not just the jurisdiction that signs the permit.

What I’d Like to Hear From You

If this has happened where you live, I’d love to hear the story—not just whether the project was approved, but whether the process felt fair. Where did the benefits land? Who carried the costs? And what would a better regional agreement have looked like?

Leave a comment, share this piece with someone working on infrastructure siting, or send me an example from your region. The more we identify impact communities before conflict hardens, the better chance we have of building projects that are not only approved, but actually accepted.

Reader question: If your community had to host the impacts of a major project without receiving most of the benefits, what would fairness look like to you?

Sources and Reference Notes

• Waverly / Sangamon County Data Center Dispute: NPR Illinois & Illinois Times (April–July 2026).

• Howard Solstice Transmission Line & Constanzo Farm: San Antonio Express-News (July 2026).

• Michigan Public Act 233 Siting Analysis: MCL 460.1221 / Clean & Renewable Energy Act (Effective Nov 2024–2026).

• Local Opposition & Transboundary Impacts: Sabin Center for Climate Change Law & Brookings

Local governments are beginning to treat two very different technologies as one land-use problem.

On paper, a hyperscale AI data center and a battery energy storage system, or BESS, are not the same thing. One is a computing campus with enormous power and cooling demands. The other is a grid-balancing facility designed to store and dispatch electricity.

But from the perspective of a rural township board, a planning commission, or a neighborhood that just learned about a major project through rumors, the distinction can collapse quickly.

Both can look like large, externally driven industrial facilities arriving before local rules exist to govern them. That is the political opening for what I call the paired moratorium: a temporary pause that bundles data centers and battery storage into one regulatory timeout.

What Triggers a Paired Moratorium?

1. Unzoned land or code gap: A rumor, land option, utility inquiry, or early site-control move alerts residents before formal rules are in place.

2. Local response: Officials adopt a temporary pause covering both data centers and BESS facilities.

3. End goal: The jurisdiction uses the pause to draft local standards before applications arrive.

The Wave of Paired Pauses

Recent local actions show how quickly this pattern is spreading:

· Hillsboro, Oregon: On July 27, 2026, the City Council enacted a 120-day land-use moratorium on new or expanded data centers and standalone BESS facilities proposed as a primary use. The city said the pause would give officials time to evaluate how these facilities fit into long-term land-use planning and potential Community Development Code updates. [1]

· Kalamazoo Township and nearby Michigan communities: Kalamazoo Township advanced ordinances toward a yearlong pause on data centers and BESS facilities while it studies impacts and drafts standards. Regional reporting shows similar moves across southwest Michigan, including Portage and Oshtemo, as communities weigh infrastructure, safety, and environmental concerns. [2]

· Orangetown, New York: The town scheduled a public hearing on a proposed 180-day moratorium covering both battery energy storage systems and data storage facilities while officials consider siting, noise, fire, energy-use, and health-and-safety standards. [3]

These pauses are not necessarily permanent rejections. In places like Harbor Beach, Michigan, officials moved from a pause-and-study posture toward dedicated zoning rules for utility-scale battery storage, including application materials for decommissioning, land restoration, fire protection, stormwater management, lighting, noise, and setbacks. [4]

In other words: a moratorium has become the default planning tool when technology outpaces the local zoning code.

Why Communities Bundle Digital and Energy Infrastructure

Why are local boards placing computing campuses and grid batteries in the same political category? Because from the public’s perspective, both technologies share several high-friction characteristics:

1. Large Industrial Footprints: Both require substantial acreage, significant electrical interconnections, and visible industrial equipment—often placed adjacent to farmland or residential districts.

2. Limited Institutional Experience: Most small-town planning boards lack dedicated staff or technical consultants trained to evaluate thermal runaway risks, noise contours, or localized grid impacts.

3. High Resource Demands & Safety Questions: Residents voice parallel concerns about water drawdowns, air permitting, emergency response preparation, noise, and long-term site abandonment.

4. The Threat of “Institutional Surprise”: In many communities, opposition begins before a formal application is even filed. A land option, a utility power inquiry, or a rumor is enough to create uncertainty. Uncertainty itself has become the mobilizing event.

Once residents realize their local code lacks explicit guardrails, they rarely wait for the developer’s formal presentation. They ask for a pause so the community can regain control of the timeline.

What Developers and Advocates Should Learn

The spread of paired moratoriums carries a clear lesson: the absence of a filed application is not the absence of community concern.

Relying on a “no zoning” loophole or assuming that quiet land acquisition will shield a project almost always backfires. By the time a developer officially introduces the project, neighbors may already believe the decision was made privately. That turns a routine land-use matter into a political crusade.

For project sponsors, energy leaders, and advocates, the field playbook needs to change:

• Stop Treating Zoning Gaps as Permission: If a host jurisdiction lacks an updated ordinance for storage or computing, do not treat the vacuum as a green light. Expect a moratorium to fill the void unless proactive engagement begins early.

• Support Independent Local Standard-Setting: Providing model ordinances can be helpful, but communities only trust rules developed through an independent, locally controlled process. Fund third-party technical assistance so township boards can hire their own experts.

• Answer Operational Safety Early: Technical assurances about “low probability events” do not satisfy local fire chiefs or neighbors. Clear plans for emergency response, water monitoring, setbacks, and fully funded decommissioning bonds must precede site announcements.

Communities are not necessarily rejecting technology outright. They are demanding that major change arrive with clear rules, fair notice, and local consent.

Summary

A paired moratorium is not just a procedural delay. It is a warning signal. Communities increasingly see data centers and battery storage as part of the same land-use challenge: fast-moving infrastructure arriving before local governments have clear standards for scale, safety, resource use, emergency response, and long-term accountability.

For developers, the lesson is simple: do not mistake silence for consent, and do not treat outdated zoning as permission. The communities that move fastest against a project are often the ones that feel they were asked to react after the real decisions had already been made.

Call to Action

If you are working on data center, energy storage, utility, or land-use strategy, start the conversation before the application is filed. Use these questions to pressure-test whether the project is ready for public scrutiny:

· Has the host community adopted clear rules for data centers, battery storage, or both?

· If the local code is silent, who is helping the community write standards before the application is filed?

· Has the developer met with elected officials, planning staff, emergency responders, and affected neighbors before announcing the site?

· Can the project explain its water use, power demand, noise profile, traffic impacts, setbacks, fire response plan, and decommissioning funding in plain language?

· Will local fire, planning, and environmental officials have independent technical advice—not just information supplied by the project team?

· What happens if residents first learn about the project through rumors, land records, or a utility interconnection filing?

· Is there a credible plan for public meetings, community questions, written responses, and design changes before opposition hardens?

· Who owns the long-term obligations if the project changes hands, fails, or is abandoned?

Want to avoid becoming the next moratorium headline? Share this with your siting, permitting, communications, or government affairs team—and pressure-test your local engagement plan before the rumor mill writes the story for you.

Citations

1. City of Hillsboro, Oregon, “Land Use Moratorium Enacted on Data Centers & BESS Facilities,” July 27, 2026; City of Hillsboro, “Data Centers in Hillsboro,” updated July 27, 2026.

2. Public Media Network, “Kalamazoo Township Takes First Step Toward a Yearlong Pause on Data Centers and Battery Energy Storage Systems,” July 14, 2026; The Kalamazoo Press, “Southwest Michigan Townships Move Forward with Moratoriums on Battery Energy Storage and Data Centers,” April 8, 2026.

3. Town of Orangetown, “Establishing a Temporary Moratorium on Data Centers and Battery Energy Storage Systems,” July 16, 2026; Town of Orangetown draft local law imposing a 180-day moratorium on battery energy storage systems and data storage facilities.

4. City of Harbor Beach, “City Codes & Ordinances — Utility Scale Battery Storage,” June 20, 2026; Thumbnet, “Harbor Beach Approves Zoning Rules For Utility Scale Battery Energy Storage Facilities,” July 28, 2026.

About the Author

Peter Hamm is the founder and editor of Politely Losing. His career spans more than 30 years across government operations, defense-sector network management, and executive distribution leadership in the insurance industry. Having served as Chief Clerk for the U.S. House Committee on Rules and managed complex field operations across distributed regions, Peter brings a pragmatic, battle-tested perspective to how public policy, land use, and organizational strategy intersect on the ground.

As an author, analyst, and media producer based in the Mid-Atlantic, Peter focuses on the human and institutional dynamics behind infrastructure development—exploring why viable clean energy, data center, and regional projects fail, and how developers, local leaders, and land advocates can build genuine, durable local trust.

Connect & Follow Substack: Politely Losing & The Moral Hinge

Field Reports: Coming soon to Spotify, Apple Podcasts, and video platforms.

Get in Touch: Hit Reply on any newsletter edition or leave a comment to share local ordinance updates, field tips, or project case studies from your region.

I have sat through enough local meetings to recognize the moment when a room changes. People arrive polite. They sign in, find a folding chair, and wait their turn. Then someone asks the question that has been sitting underneath everything: why here?

That is usually when the mood shifts. Not because people hate progress, jobs, or new technology, but because they begin to suspect the decision was made somewhere else and the public meeting is mostly a formality.

When a big energy or computing project runs into local opposition, the easy explanation is often “NIMBY.” That stands for “Not In My Backyard,” and it is usually used as shorthand for people who support progress in theory but object when the project lands near them.

But that label can be too convenient. It can also be wrong.

In Mayes County, Oklahoma, hundreds of rural residents recently gathered to push back against reported large data center developments. One organizer, Kim Ritchie, put the issue in a single sentence:

“If they were developing it in the Mid-America Industrial Park, I wouldn’t be here.”

— Kim Ritchie, Mayes County resident

That is the sentence developers should tape to the wall.

The residents were not saying, “No data centers, ever.” They were saying something much more practical: industrial-scale projects belong in places prepared for industrial-scale projects. Put them where the roads, utilities, buffers, emergency planning, and public expectations already fit the use.

That distinction matters. It is the difference between rejecting progress and asking for basic respect.

The problem with “no rules”

In many rural counties, there may be little or no formal zoning. To a company looking for land, that can look like a green light. If no ordinance says “stop,” the assumption may be that the project can move forward.

But the absence of rules is not the same thing as public permission.

When residents learn that their local government may not have the tools to evaluate noise, water use, traffic, setbacks, or emergency response, they do not quietly shrug. They organize. They call neighbors. They fill meeting rooms. They pressure state lawmakers. And once trust is lost, it is very hard to win back.

This is where many well-funded projects begin to lose politely. The company may have lawyers, engineers, consultants, and a long list of economic benefits. The community may have folding chairs, handwritten signs, and a deep sense that something is being done to them rather than with them.

In public life, that feeling is powerful. It can turn a project from a land-use matter into a political cause.

Rules can protect both sides

The better path is not endless delay or blanket opposition. It is clear rules before the application arrives.

Louisville, Kentucky, offers one example. After public concern over data centers, planning officials proposed rules that would limit the largest facilities, steer projects toward industrial areas, require separation from sensitive uses such as homes and schools, and address noise, utility costs, and infrastructure impacts.

Harbor Beach, Michigan, offers another. As communities wrestle with large battery storage projects, the city amended its zoning rules to require basic protections up front, including fire planning, stormwater planning, decommissioning plans, and buffers from homes and wetlands.

These rules are not anti-growth. They are guardrails. They tell developers what is expected. They tell residents what is protected. And they replace late-stage anger with a checklist everyone can see.

The Industrial Park Test

So here is a simple test for companies, local officials, and anyone who wants to build big things without burning local trust:

· Can this go in an industrial park? If yes, start there.

· If it cannot, why not? Explain that clearly before buying land or announcing plans.

· What will change for nearby residents? Talk plainly about noise, lights, traffic, water, views, emergency response, and long-term responsibilities.

· What protections are enforceable? Promises are nice. Written standards are better.

That is the Industrial Park Test. It does not ask whether a project is fashionable, futuristic, or profitable. It asks whether the project fits the place.

Communities are not always saying no to change. Often, they are asking for change to arrive with manners.

The irony is that many of these fights are avoidable. A company can be technically right and still lose the room. It can meet the minimum legal requirements and still fail the public test. It can bring money, jobs, and infrastructure and still create the impression that rural people are expected to absorb whatever the market wants to place beside them.

That is how projects lose politely. Not in a dramatic collapse, but in county meetings, neighborhood conversations, statehouse calls, and quiet shifts in public trust.

The way forward is not to sneer at local resistance. It is to listen for the real question underneath it: does this belong here?

Key ideas

· Local opposition is not always anti-progress; often, it is a request for the right project in the right place.

· Industrial-scale projects should start with locations already prepared for industrial use, including roads, utilities, buffers, and emergency planning.

· The absence of zoning or formal rules should not be mistaken for community consent.

· Clear standards protect both residents and developers by making expectations visible before conflict begins.

· The central question is simple: does this project fit this place?

Conclusion

If there is a lesson in these fights, it is that communities are rarely persuaded by being told they are in the way. They are persuaded when someone shows that their place, their routines, their roads, their water, their schools, and their sense of home have been taken seriously.

Big projects may be necessary. Some may even be welcome. But they still have to earn the right to belong somewhere. The Industrial Park Test is not a way to stop everything. It is a way to ask the first honest question before the last public meeting: does this project fit this place, and have the people who live there been treated as more than an obstacle?

If this piece brought a project, meeting, or proposal in your own community to mind, I would be glad to hear the story. Where did officials build trust? Where did the process break down? And what would have helped neighbors feel like they were being invited into the conversation instead of managed around it?

Because the future does not just need somewhere to go. It needs somewhere it can belong.

Source note

This essay draws on local reporting and public materials about recent siting debates involving data centers and battery storage projects, including 2 News Oklahoma’s July 2026 reporting on Mayes County residents organizing against proposed rural data center sites; Louisville Public Media and WLKY coverage of Louisville Metro’s proposed data center regulations; and City of Harbor Beach materials related to its utility-scale battery storage zoning amendment. It also reflects broader public discussions about zoning, infrastructure, utility impacts, emergency planning, and community consent in fast-growing energy and technology projects.

About the author

Peter Hamm is a Master of Christian Leadership candidate at Leland Theological Seminary, a Wilderness First Responder, and an avid outdoor enthusiast shaped by NOLS and Outward Bound. He also writes at Disciple to Faith, The Moral Hinge, and Search Anna Keller.

Utilities have long relied on a familiar line when they want to run a high‑voltage transmission corridor through someone’s backyard: It’s for grid reliability.

That used to end the conversation. Reliability meant keeping the lights on. But in 2026, with data‑center growth driving unprecedented electricity demand, communities are asking a sharper question: reliability for whom?

Georgia is now the clearest example of how quickly that question becomes a land‑use battle. A proposed 35‑mile, 500‑kV transmission line connecting the Ashley Park Substation in Fayette County to Plant Wansley in Heard County cuts across more than 300 parcels. Nearly 30 homes could be acquired or removed.

Georgia Power says the project supports regional resilience and system‑wide growth. But families in Coweta, Fayette, Fulton, and Heard counties see a different story: roughly 80% of the utility’s new capacity growth is tied to data centers, according to IRP filings and local reporting.

When a family is asked to surrender their home through eminent domain so hyperscale server farms can expand, broad corporate slogans about “system need” don’t build trust — they ignite a firestorm.

1. The Eminent Domain Legitimacy Trap

Eminent domain is the most severe legal tool an infrastructure provider can use. It exists because linear projects — pipelines, highways, transmission lines — cannot be built parcel‑by‑parcel through voluntary negotiations alone.

But the legal right to condemn property rests on a fragile social contract: people must believe the taking serves a genuine public purpose.

When that line blurs, abstract policy becomes human upheaval.

Consider one Coweta County family. Ansley Brown spent months fighting to keep her mother’s childhood home — purchased two decades ago to build generational wealth — from being taken for the 35‑mile corridor. When residents hear that 70% to 80% of the new capacity is slated for hyperscale data centers, the idea of forcing families out under threat of condemnation doesn’t feel like “regional reliability.” It feels like an institutional land grab.

The Broad Corporate Explanation: Georgia Power frames the Ashley Park–Wansley line as essential to regional resilience and grid health.

The Ground Reality: Landowners see tech giants securing massive power allocations while everyday families carry the physical, financial, and emotional burden of lost homes.

When the perceived commercial beneficiary is narrow and highly profitable, invoking eminent domain without overwhelming transparency destroys local legitimacy. Even adequate compensation cannot fix the political fallout when a family feels their home is being sacrificed to subsidize private tech infrastructure.

2. Why Corporate Jargon Fails on the Ground

When utilities face rural opposition over right‑of‑way acquisitions, the default response is often to double down on engineering models, load‑flow diagrams, and regulatory citations.

This misses the human element entirely.

Landowners do not experience transmission lines as a system‑wide megawatt calculation. They experience them as 150‑foot steel towers outside their bedroom windows, cleared tree lines, disrupted cattle pastures, and reduced property values.

When developers rely on general “system need” language while refusing to break down customer‑class demand, residents assume the worst: that something is being hidden.

3. How to Fix the Transmission Playbook

If clean‑energy leaders, grid operators, and transmission developers want to avoid turning regional buildouts into multi‑year legal sagas, they must change how they engage host communities long before condemnations are filed.

Here is the four‑item checklist every community now expects — and every developer should be prepared to meet:

Customer‑Load Attribution

Be honest about what is driving the need. If 80% of new capacity serves commercial data centers, say so — and explain how those customers are paying for the infrastructure they require.

Route Alternatives & Non‑Wires Options

Prove that this specific path — and this level of property taking — was the last resort, not just the cheapest line on a planner’s map.

Transparent Property‑Acquisition Standards

Publish independent appraisal methodologies up front so landowners know they are receiving fair treatment rather than lowball initial offers.

Local Burden Protections

Show how host counties and neighboring parcels will receive tangible protections: upgraded emergency‑response support, rate guarantees, or other enforceable benefits.

This is not public relations. It is the minimum transparency required to maintain legitimacy when asking families to surrender land for regional infrastructure.

The Bottom Line

Infrastructure expansion is mandatory for energy independence and modern economic growth. But public necessity cannot become a blank check against private property rights.

When developers hide behind broad corporate definitions of “grid reliability” to satisfy hyper‑specific commercial demand, they don’t just lose individual land disputes — they lose the narrative. And once they lose the narrative, they lose the project.

Georgia is not an outlier. As data‑center load reshapes regional grids across the country, every state will face versions of this same fight. The question is no longer whether new infrastructure is needed. It is whether the burdens are allocated transparently, equitably, and with genuine public purpose.

Sources & Reference Data (Linked)

• Fortune reporting on Georgia Power’s transmission expansion:

https://fortune.com/2024/07/24/georgia-power-data-centers-eminent-domain/ (fortune.com in Bing)

• CBS News coverage of Georgia Power’s eminent‑domain disputes:

https://www.cbsnews.com/atlanta/news/georgia-power-eminent-domain-data-centers/ (cbsnews.com in Bing)

• Georgia PSC IRP filings (load forecasts and capacity planning):

https://psc.ga.gov/electric/

• Startup Fortune reporting on Coweta County landowner disputes:

https://startupfortune.com/georgia-power-eminent-domain-dispute/ (startupfortune.com in Bing)

• The Cooldown reporting on public‑use challenges:

https://www.thecooldown.com/green-business/georgia-power-eminent-domain-data-centers/ (thecooldown.com in Bing)

Across the country, rural clean-energy development has settled into a familiar and depressing script.

A solar or storage project is announced. The developer arrives with glossy presentation boards and a few carefully rehearsed talking points. A Facebook group forms. Neighbors pack a township meeting. The debate stops being about electrons and starts being about identity, property rights, trust, and whether outsiders are trying to pull one over on the community.

Then the project dies.

That is why what happened in Sussex County, Delaware is worth paying attention to.

On July 26, 2026, Delaware Public Media reported that the Sussex County Planning and Zoning Commission recommended approval for six separate solar farm applications. Most were associated with Turning Point Energy, with one filed by Pivot Energy. The projects advanced without reported opposition.

In the world of local energy permitting, that is not a small thing. It is the dog that did not bark.

The lesson is simple, but too often ignored: trust begins with site selection, not public relations.

The land-use argument came first

When renewable projects run into fierce local opposition, developers often tell themselves the community simply does not understand the technology. Sometimes that is true. More often, the first point of friction is not the solar panel. It is the parcel.

People look at a proposal and ask practical questions before they ask ideological ones. Why here? How close is it to my house? Will it change the view? Will it bring traffic? Is this consistent with what the county already said this land is for?

The Sussex County projects appear to have entered the hearing with unusually legible answers. Commissioners pointed to consistency with the county’s comprehensive plan, proximity to existing electrical infrastructure, limited traffic, forested screening, buffers, and fencing.

That matters because local opposition feeds on ambiguity. If residents cannot understand the land-use logic, they will usually fill in the blanks themselves—and rarely in the developer’s favor.

Respect the property line

Most people do not experience energy policy as policy. They experience it from the back porch.

That is why buffers, setbacks, screening, and fencing are not mere engineering details. They are political communication. They tell neighboring landowners that the developer has thought about what the project will look like from their side of the fence.

In Sussex County, the record highlighted forested areas that naturally screen the projects, 30-foot landscape buffers near residential uses, seven-foot fencing, and the absence of a regular on-site workforce. None of that guarantees support. But it does lower the temperature.

Developers sometimes treat these choices as concessions. They should treat them as insurance.

The narrative is built before the hearing

By the time a project reaches a public hearing, the narrative is usually already set. Either the proposal feels compatible with the place, or it feels imposed on the place.

That is the deeper lesson from Sussex County. The quiet hearing was not magic. It was the result of making the right fights less likely: choosing sites that fit existing plans, staying close to existing infrastructure, making impacts easy to understand, and taking neighbors’ physical experience seriously.

· Pick the right parcel. If the site requires a zoning contortion act, opponents will notice.

· Make the impact legible. Talk plainly about traffic, noise, visibility, operations, and maintenance.

· Buffer generously. A setback is cheaper than a lawsuit, a delay, or a dead project.

· Use existing infrastructure whenever possible. A project that connects cleanly to nearby lines feels less disruptive than one that requires a whole new corridor of wires, roads, and construction activity.

· Design for the neighbor’s view, not the developer’s rendering. A site plan may look harmless from above, but the political question is what someone sees from a driveway, field edge, or kitchen window.

· Explain what will not happen. Communities often fear the unknown, so it helps to be clear about what the project will not bring: no constant workforce, no heavy daily truck traffic, no late-night operations, and no open-ended industrial expansion.

· Let the comprehensive plan do some work. When a proposal lines up with a county’s existing planning documents, it is easier to argue that the project belongs there rather than being forced there.

· Start with respect, not persuasion. Engagement after the layout is fixed feels like salesmanship. Good site selection feels like listening.

These choices are not cosmetic. They are the difference between a project that arrives as an argument and one that arrives as a reasonable next step. In local permitting, opponents do not need to prove a project is bad; they only need to make it feel risky, careless, or imposed. Thoughtful siting, clear limits, and visible respect for neighbors make that story much harder to tell.

The bottom line

Local consent is not won by explaining a bad siting decision more elegantly. It is earned by making better siting decisions in the first place.

Sussex County is a reminder that the best public-affairs strategy may be the one that keeps the public fight from happening at all.

Summary

The Sussex County solar approvals offer a useful lesson for clean-energy developers: the easiest public fight to win is the one that never forms. By choosing parcels that fit existing plans, sit near infrastructure, limit visible impacts, and respect neighboring property owners, developers can reduce distrust before a hearing ever begins. The point is not that every renewable project will avoid opposition. It is that trust is often built through practical land-use decisions long before anyone starts making the case for clean energy.

Call to action

If you work in clean energy, local government, land use, or community advocacy, I would like to hear from you: what makes a project feel like it belongs in a place, and what makes it feel imposed? Reply with examples from your community, share this with someone working on siting or permitting, and subscribe to Politley Losing for more writing on how public decisions are won, lost, and misunderstood.

Sources: Delaware Public Media reporting on the Sussex County Planning and Zoning Commission’s July 2026 solar recommendations; Sussex County comprehensive-plan references cited in the public proceedings; broader renewable-siting and interconnection context from public land-use and energy-sector research.

Subscribe now

Every month across the country, viable, well-capitalized clean energy and rural infrastructure projects quietly stall or disappear.

They do not always fail because the engineering is flawed or the financial models fall apart. They are not always canceled because landowners oppose solar lease payments or because clean energy is unnecessary on the grid.

Many fail because of a predictable and avoidable sequence of events: local communication breaks down, trust erodes, and the project story is shaped by others before the facts are fully heard.

The Interconnection Graveyard

If you look at the available industry research, a consistent pattern emerges:

· The Queue Bottleneck: Interconnection queues remain a major filter for proposed generation projects. Lawrence Berkeley National Laboratory’s Queued Up research reports that most projects applying for interconnection are ultimately withdrawn, and that the projects reaching commercial operation are taking longer to move through the process.

· Local Restrictions Are Growing: The Sabin Center for Climate Change Law at Columbia Law School reports that, by the end of 2024, at least 459 counties and municipalities across 44 states had adopted severe local restrictions on renewable energy siting. USA Today has also reported increased use of bans, moratoria, setbacks, and other local restrictions affecting utility-scale wind and solar development.

· Early-Stage Project Risk: A Berkeley Lab survey of utility-scale wind and solar developers found that local ordinances or zoning, grid interconnection, and community opposition are among the leading causes of project cancellations and significant delays.

Taken together, the research points to a practical conclusion: local engagement is no longer a side issue. It is a core project risk that needs to be managed early, honestly, and locally.

The Outdated Corporate Playbook

When concerns surface in a rural township or suburbanizing county, the standard response often looks like this:

· The Passive Phase: Keep the project quiet as long as possible to protect site control.

· The Late Open House: Arrive months into the process with polished display boards, outside consultants, and broad talking points about regional energy needs.

· The High-Stakes Public Hearing: Enter a county board or planning commission meeting expecting a technical presentation to resolve concerns that have already become emotional, local, and personal.

This approach can unintentionally make landowners and residents feel managed rather than respected. It also gives local concerns time to harden before developers, advocates, or participating landowners have made a clear case grounded in the community’s own priorities.

When communication feels distant, people assume there is something to hide. When the message relies on general corporate language, it can miss the specific concerns that matter most to the community.

In short: good projects are losing local trust before they have a chance to earn it.

A New Approach: Local Sovereignty and Property Rights

Earning local trust requires moving beyond the default corporate communications template and grounding engagement in values that resonate on the ground:

· Property Rights: A landowner’s fundamental freedom to lease or use their land as they see fit without government overreach.

· Local Sovereignty: Respecting the character, heritage, and economic realities of the surrounding community.

· Honest Engagement: Showing up early, speaking plainly, and addressing legitimate local concerns—about setbacks, viewsheds, decommissioning, and community impacts—before misinformation fills the void.

This is not just a communications preference. Research from NREL and Oak Ridge National Laboratory emphasizes that renewable energy engagement is most effective when it accounts for community concerns, equity, participation, and local decision-making dynamics.

When clean energy is framed through the lens of individual liberty, local economic stability, and property rights, the conversation can change in a meaningful way.

What Politely Losing Is About

This publication is built on a simple premise: local communities deserve honest engagement, landowners deserve respect, and energy independence requires earning trust on the ground.

Through regional case studies anchored in the Greater Richmond area and the broader Mid-Atlantic corridor, we will examine the recurring friction points that shape local development debates. We’ll share:

· Field-Tested Playbooks: Practical frameworks for land advocates, developers, and local stakeholders.

· Regional Case Studies: On-the-ground analysis of county hearings, zoning disputes, and shifts in local opinion.

· Tactical Analysis: How to identify emerging concerns early and respond with truth, transparency, and local value.

Join the Journey

If you believe sound projects deserve a fair hearing—and that local communities deserve more than polished talking points after the fact—you’re in the right place.

Subscribe to follow the field reports, study the playbooks, and join a practical conversation about how local energy engagement can start earlier, speak more plainly, and earn more trust.

Sources

· Lawrence Berkeley National Laboratory, Queued Up: Characteristics of Power Plants Seeking Transmission Interconnection.

· Sabin Center for Climate Change Law, Columbia Law School, Opposition to Renewable Energy Facilities in the United States: June 2025 Edition.

· USA Today, reporting on county-level restrictions, bans, moratoria, and setbacks affecting utility-scale wind and solar development.

· Lawrence Berkeley National Laboratory, Survey of Utility-Scale Wind and Solar Developers Report.

· National Renewable Energy Laboratory and Oak Ridge National Laboratory, Community Engagement and Equity in Renewable Energy Projects: A Literature Review.