Not in My Backyard: How Communities Fight Data Centers, Solar Farms and Mega-Projects

When a billion-dollar industrial project is announced, the language surrounding it often makes the development sound inevitable.

The land has been identified. State officials are celebrating the investment. Economic-development agencies are talking about jobs. Renderings are released. Tax incentives may already be under discussion.

Then the people who actually live there find out.

Sometimes they don't want it.

Not a handful of neighbors. Not one property owner angry about the view. An organized community looks at the proposed data center, solar farm, transmission corridor or industrial complex and reaches a remarkably simple conclusion:

Not here.

What happens next is where the story gets complicated.

Because saying no and making that no legally consequential are two entirely different things.

Across the country, communities have delayed, changed and stopped enormous developments. Those victories rarely came from simply packing a public meeting and demanding that elected officials reject the project.

They came from learning a system the developer may have already spent months or years navigating.

Zoning.

Permits.

Public notices.

Environmental reviews.

Utility proceedings.

Tax incentives.

Planning commissions.

Public-records laws.

Administrative deadlines.

Court challenges.

A billion-dollar developer can arrive with attorneys, engineers, consultants and government-relations professionals who already understand that machinery.

Residents may get a public notice and 30 days.

That imbalance is the real story.

The project may be new to you. You aren't new to the project.

By the time residents hear about a major development, considerable work may already have happened behind the scenes.

Land may have been purchased or optioned.

Engineers may have studied the site.

Utilities may have discussed service.

Economic-development officials may have communicated with the company.

Incentives may have been explored.

Environmental consultants may have begun their work.

Corporate entities may have been formed specifically to hold property or develop the project.

Then comes the announcement.

For residents, Day One may actually be Month 18.

That creates an extraordinary informational disadvantage.

The developer knows what it needs.

The community first has to figure that out.

And the clock may already be running.

A community vote isn't necessarily a veto

This is the frustrating part.

Suppose nearly everyone who shows up to a public meeting opposes a project.

That doesn't automatically stop it.

Residents still have to determine which government body actually controls the decision in front of them.

A parish council or police jury may control one approval.

A planning commission may control another.

The Louisiana Department of Environmental Quality may control an environmental permit.

The Louisiana Public Service Commission may have jurisdiction over certain utility infrastructure.

Federal agencies may control wetlands or other federal approvals.

An economic-development board may be involved with incentives.

And sometimes an agency is legally required to evaluate a much narrower question than the one residents want answered.

The community may be asking:

Why are you putting this here when the people who live here don't want it?

The regulatory process may instead be asking:

Does this application satisfy Section 4.3(B) of this particular rule?

That gap is where communities get buried.

The first job is finding every point where the project still needs permission

If a community has decided it wants to fight a project, the first question isn't whether the project is good.

That debate is over for the people opposing it.

Ask these questions:

What does the project still need?

Does the land need rezoning?

Does the project require a conditional-use permit?

Does it need an air permit?

A water discharge permit?

Wetlands authorization?

A transmission line?

A new substation?

A road agreement?

A water extension?

A drainage approval?

A tax exemption?

A development agreement?

A vote by the parish governing authority?

Each unanswered question represents a dependency.

And dependencies are leverage.

A project announced as inevitable can look very different once its approval chain is placed on paper.

Zoning can be the front line

Land-use rules are among the most immediate tools available to local governments where state law leaves the decision under local control.

That can include zoning classifications, setbacks, buffering, noise restrictions, drainage requirements, height restrictions, landscaping, traffic requirements and conditions placed on certain uses.

The important question isn't simply whether the parish has zoning.

It's whether the project can legally do what it proposes to do on that particular property under the rules that exist today.

If it cannot, the developer needs something from local government.

A rezoning.

A variance.

A conditional-use approval.

An ordinance amendment.

Some other discretionary action.

That creates a decision point.

Communities elsewhere have also pushed local governments to adopt new rules governing emerging land uses before applications receive final approval.

Data centers are a perfect example.

A zoning ordinance written when an "industrial facility" meant a warehouse or fabrication shop may never have contemplated a campus consuming enormous amounts of electricity, operating cooling equipment continuously and potentially requiring substantial new utility infrastructure.

Utility-scale solar and battery storage can create the same problem.

The technology changed.

The zoning ordinance didn't.

Communities that recognize that early can force the question:

Are our existing rules actually adequate for what is being proposed?

Moratoriums buy the one thing residents usually don't have

Time.

Where legally available and properly adopted, temporary development moratoriums can pause particular categories of approvals while a local government studies an emerging land use and writes regulations addressing it.

That can completely change the balance.

Without a pause, residents may be trying to research a technically complex project while hearings, permits and votes continue moving forward.

A moratorium can turn a 30-day scramble into six months of investigation.

Six months means time to obtain records.

Time to hire or find technical experts.

Time to understand utility impacts.

Time to examine drainage.

Time to investigate land ownership.

Time to study noise.

Time to compare ordinances adopted elsewhere.

Time to organize.

For a developer, delay costs money.

For a community, delay can create knowledge.

Public records can erase part of the developer's head start

One of the most powerful tools available to residents doesn't involve a protest sign.

It is a records request.

The public announcement tells residents what officials and developers want publicly known about a project.

Public records can show how the project actually developed.

Instead of asking for everything concerning a project, requests can target specific categories:

communications between developers and government officials;

utility correspondence;

water-demand projections;

wastewater estimates;

traffic studies;

drainage studies;

incentive applications;

development agreements;

memoranda of understanding;

engineering reports;

environmental studies;

meeting calendars;

infrastructure-cost estimates;

draft agreements;

and communications concerning zoning, permitting or land acquisition.

Then there are the records nobody sends in a press release.

Property transfers.

Options.

Leases.

Servitudes.

Corporate registrations.

Utility filings.

Planning agendas.

Regulatory dockets.

Individually, these documents can look mundane.

Put them together and they can reveal who knew what, when they knew it, what was promised and what the project still requires.

Environmental comment periods aren't designed like elections

This is another place communities can misunderstand the process.

A permit hearing can have a room overwhelmingly opposed to a project without opposition itself deciding the permit.

Environmental agencies generally operate under statutes and regulations establishing what they can consider.

That means residents have to translate their opposition into the language of the regulatory process.

Instead of only:

We don't want this.

The administrative record may need questions such as:

What assumptions produced the emissions model?

How frequently will backup generators operate and be tested?

What noise levels were modeled at neighboring properties?

What water consumption was assumed?

What happens under drought conditions?

How was stormwater modeled?

What happens if the facility expands?

Were nearby residences accurately identified?

Are all required cumulative impacts being evaluated?

That can feel absurd to a resident whose position is simply that the facility shouldn't be built beside their home.

But that is how administrative systems work.

The community speaks in ordinary language.

The bureaucracy demands regulatory language.

Successful opposition learns to speak both.

Follow the electricity

For data centers in particular, the facility itself may only be half the project.

The other half is power.

A massive electrical load may require generation, transmission lines, substations or other infrastructure extending far beyond the development site.

That opens another regulatory trail.

Residents can ask:

How much electricity will this facility consume?

What utility will serve it?

What new infrastructure is necessary?

Who pays for that infrastructure?

What assumptions were used to justify it?

Could any costs ultimately affect other ratepayers?

What happens if projected demand never materializes?

Which regulatory docket contains those answers?

A developer may control its property.

It doesn't control the electrical grid.

Follow the money too

Then come the incentives.

Large economic-development projects are frequently marketed using enormous capital-investment figures.

"$2 billion investment."

"$5 billion investment."

"$10 billion investment."

Those numbers make headlines.

They don't tell residents what the public is contributing.

A community investigating a project should determine:

What tax incentives were requested?

What exemptions were approved?

What public infrastructure is being constructed?

Who pays for road improvements?

Who pays for water and sewer expansion?

Who pays for electrical infrastructure?

What employment promises are attached?

What payroll commitments exist?

What happens if those promises aren't met?

How long do the incentives last?

And what would the project pay without them?

If the public is being asked to host the project, the public should know the deal.

Then map the entire project

The easiest way to understand a mega-project is to stop viewing it as one project.

Break it apart.

LAND

Who owns it?

↓

LAND USE

Can this project legally be built there?

↓

ENVIRONMENTAL

Which permits are required?

↓

POWER

What generation, transmission and substation infrastructure does it require?

↓

WATER / SEWER / DRAINAGE

What does it consume, discharge or change?

↓

TRANSPORTATION

What roads or access improvements are necessary?

↓

INCENTIVES

What public financial support is involved?

↓

FINAL APPROVALS

Who still has to say yes?

Then put names beside every box.

Agency.

Board.

Commission.

Elected official.

Permit number.

Docket number.

Meeting date.

Comment deadline.

That turns an overwhelming billion-dollar project into a series of individual decisions.

The clock is one of the most powerful weapons in the process

This may be the greatest structural advantage developers have.

They know the timeline.

Residents usually don't.

The developer may spend a year preparing an application.

Residents might receive 30 days to respond to it.

The developer has engineers.

Residents have evenings after work.

The developer has attorneys familiar with administrative procedure.

Residents are learning what an administrative appeal is while the deadline approaches.

The developer may have already met repeatedly with government officials.

Residents are speaking to those officials for the first time at a public hearing.

Then everyone enters the same room and the process treats both sides as though they arrived there simultaneously.

They didn't.

That is why successful communities organize early

The communities that stop large projects don't possess some secret veto unavailable to everyone else.

They become organized enough to overcome the head start.

They watch planning agendas.

They monitor property transactions.

They read environmental notices.

They follow utility proceedings.

They request records.

They identify deadlines.

They recruit attorneys, engineers, hydrologists, land-use specialists or other experts when necessary.

They pressure elected officials.

They demand moratoriums.

They propose ordinances.

They challenge procedural failures.

They appeal administrative decisions where the law permits it.

They litigate when there is a viable legal claim.

And sometimes they vote people out of office.

None of that is as simple as standing at a microphone and saying no.

That's precisely the problem.

What this means for Southwest Louisiana

Southwest Louisiana is increasingly being asked to host projects tied to industrial expansion, LNG, electrical generation, transmission infrastructure, carbon management, renewable energy and other large-scale development.

Some communities will welcome individual projects.

Others won't.

When a community overwhelmingly doesn't want one, the interesting question isn't whether outsiders think those residents have correctly calculated the economic benefits.

They're the people who live there.

The question is whether their opposition has any practical power inside a system of zoning laws, administrative rules, permitting procedures, regulatory jurisdictions and short public-comment periods.

That is where the real fight happens.

A billion-dollar company doesn't need everyone in town to like its project.

It needs the necessary approvals.

So when residents decide they don't want something built in their backyard, understanding exactly who can still say no becomes more important than almost anything else.

Find the land.

Find the permits.

Find the zoning.

Find the utility filings.

Find the incentives.

Find the infrastructure commitments.

Find every deadline.

Find every vote.

Find every place where the project still requires permission.

Because by the time the sign goes up announcing what's coming, the developer may already be a year ahead.

The community has to catch up fast.

Dalton Barron is a Louisiana-licensed real estate salesperson with NextHome Bayou Pines and publisher of 337.news. His reporting focuses on land, development, infrastructure, government accountability and the decisions affecting Southwest Louisiana property owners. Reporting and commentary published by 337.news reflect his own work and views and do not represent NextHome Bayou Pines.

Dalton Barron
NextHome Bayou Pines
Jeremy Jones Broker/Owner
C. 337.764.1754
O. 337.202.1018
Licensed by the LREC
Main Office: Deridder, LA
Each office is independently owned and operated.