Why most power generation projects fail before construction

One in three clean energy projects never makes it through permitting.

Half are delayed by at least six months.

A 2023 survey of utility-scale wind and solar developers by Lawrence Berkeley National Laboratory found that 33% of permit applications were canceled and roughly 50% faced delays of six months or more.

The main drivers? Local ordinances and community opposition.

The takeaway is simple: technical diligence isn’t enough. If you want predictable permitting outcomes, you need a repeatable way to understand the local landscape, early enough to change course.

Why “good sites” still fail

Most development teams are disciplined about the basics: interconnection, wetlands, setbacks and the usual engineering constraints. Those inputs matter, but they do not tell you how a planning commission will interpret precedent, where the pressure points will emerge or who will set the narrative at the first public meeting.

The Lawrence Berkeley National Laboratory’s findings underscore what many teams have felt in the field: the most decisive risks are often local and often social.

That local reality creates a new development requirement: you need community and political intelligence with the same rigor you bring to environmental and engineering diligence.

A practical framework: the five questions to answer before you advance a site

If you want a permitting process that is faster, cheaper, and more predictable, start by forcing clarity on five questions that traditional diligence often leaves fuzzy.

1) What is the actual permitting pathway here?

Look for:

• Required studies and common triggers (noise, glint and glare, visual impact, cultural resources)
• Where projects typically stall (staff review, special use permits, conditional use, board hearings)
• The “unwritten rules” that show up through precedent, not ordinances

2) Who are the decision-makers and what do they respond to?

You need to know:

• The decision-making bodies and their roles
• Voting records and how often they break from staff recommendations
• Meeting cadence and when public sentiment can meaningfully shift outcomes

3) What are the community dynamics?

Community response is rarely uniform. Opposition and support have structures, leaders and incentives.

Assess:

• Whether organized opposition groups exist and what issues mobilize them
• Who local influencers are (formal and informal)
• The presence of credible local champions and what they care about

4) What happened to comparable projects nearby?

Comparable projects reveal the true temperature of a jurisdiction.

Pay attention to:

• What was proposed, approved or blocked in the region
• Which conditions were imposed, and why
• The “first hearing” signals that predict whether a process will become adversarial

5) What is the coalition strategy and what is the sequencing?

A credible strategy includes:

• Who to engage first and why
• What listening should happen before messaging
• The specific concerns you expect to hear and what you can change early to address them

The bottleneck no one staffs for: research time

Most teams know these questions matter. The issue is bandwidth. The relevant information is scattered across zoning codes, planning decisions, meeting minutes, public comment and local media. Pulling it together can mean hours of manual research per site, and even then, it is easy to miss what matters most.

This is exactly the gap PermitPal’s AI agent Clara is built to close.

Where PermitPal fits: from local records to decision-ready intelligence

Our AI agent Clara makes permitting more predictable.

Clara reads through zoning codes, planning decisions, community comments, and project outcomes, then distills that material into actionable intelligence a team can use during early site screening and pre-application planning.

It is tempting to treat “community engagement” as a downstream activity, something you do after site control is secured. But by then, it is often too late.

Most political and community risks can be priced earlier, mitigated earlier, or avoided entirely if you have the right local context before you commit to a site.

PermitPal’s thesis is that developers should not have to choose between speed and diligence. By putting local context at your fingertips, the goal is to help teams listen earlier, build coalitions with intent and reduce avoidable surprises that derail schedules.

The bottom line

The teams that win in today’s environment treat community and political intelligence as a critical part of project diligence. When you can see the permitting pathway, understand decision-makers, map community dynamics and learn from precedent early, you improve the quality of every development decision that follows.