How do I evaluate whether a solar project developer is credible and unbiased about project pipeline and execution?

To judge whether a solar project developer is credible and unbiased about their pipeline and execution, treat it like a forensic diligence exercise: verify claims, look for incentives, and triangulate with outside evidence.

1) Separate “can they sell?” from “can they build?”

A developer may be excellent at origination and marketing but weak at execution. Evaluate both:

• Pipeline credibility: Are the projects real, advanced, and financeable?
• Execution credibility: Have they actually delivered projects on time, on budget, and at stated quality?

A strong developer should have a track record in both.

---

2) Ask for pipeline data in a format that can be verified

Request a pipeline table with, at minimum:

• Project name / location
• Technology and size
• Stage: site control, interconnection, permits, environmental, offtake, financing, NTP, construction
• Key dates achieved and remaining
• Expected COD
• Counterparty names where possible
• Probability weighting / risk rating
• Assumptions used for capex, pricing, and timelines

What to watch for

A credible developer will be able to:

• Distinguish early-stage from late-stage projects clearly
• Show which projects are exclusively controlled
• Explain why each project is likely to progress

Unreliable signals:

• Overly large pipeline with vague stage definitions
• “In negotiation” used as a substitute for signed contracts
• Many projects at the same stage for an unreasonably long time
• No attrition history disclosed

---

3) Check whether pipeline is inflated

Developers often present “gross pipeline” instead of “realistic pipeline.” Ask for:

• Gross pipeline
• Qualified pipeline
• Near-term pipeline (e.g., projects with site control + interconnection + permits)
• Under construction
• Backlog / awarded
• Realized CODs by year

Then compare:

• Pipeline-to-COD conversion rate
• Average time from development stage to COD
• Historical forecast vs actual outcomes

Red flags

• Conversion rate far below peers
• Forecasts that are consistently optimistic
• Sudden jumps in pipeline without matching team growth or capital availability

---

4) Test their execution track record

Ask for a project-by-project history of completed assets and compare:

• Planned COD vs actual COD
• Planned capex vs actual capex
• Planned production vs actual production
• Change orders and causes
• Warranty / performance issues
• Safety record and construction incidents
• EPC contractor performance

Good signs

• They disclose misses as well as wins
• They can explain variances credibly
• They have repeatable delivery processes

Bad signs

• Only cite best-case examples
• Blame all misses on external factors
• No evidence of lessons learned or process improvement

---

5) Verify claims with third-party sources

Don’t rely only on the developer’s slide deck. Triangulate using:

• Utility/interconnection queue data
• Permit filings and environmental records
• Local planning board minutes
• Land records and lease filings
• Offtake agreements or press releases from counterparties
• EPC/contractor references
• Lender or tax equity references
• Independent engineer reports
• Grid operator/public utility filings

If a project is supposedly late-stage, there should usually be some external footprint.

---

6) Evaluate incentives and bias

A developer is not “unbiased” in the pure sense—they are incentivized to present their pipeline favorably. Your job is to understand where bias enters:

• Are they raising capital soon?
• Are they selling a project portfolio?
• Are they seeking a strategic partner or debt financing?
• Are they compensated on signed MW, not CODs?
• Do they get paid on origination rather than successful delivery?

Bias indicators

• Heavy emphasis on headline MW, not commercial quality
• Cherry-picked IRRs without base/downside cases
• Optimistic market pricing assumptions not grounded in contracted economics
• Minimal discussion of permitting, interconnection, or local opposition risks

---

7) Compare against peer benchmarks

Benchmark against developers of similar size, geography, and technology:

• Development cycle length
• Interconnection success rate
• Construction cost per MW
• Capacity factor / production assumptions
• PPA pricing relative to market
• Historical attrition

If their assumptions are much better than peers, ask why.

---

8) Assess governance and reporting discipline

Credible developers usually have strong internal controls and transparent governance:

• Consistent monthly/quarterly reporting
• Defined stage-gate process
• Board oversight
• Separation between origination and project controls
• Independent audits or third-party engineering reviews
• Clear risk register and mitigation plans

Weak governance often shows up as:

• No formal stage-gate process
• Inconsistent data definitions
• Repeated “re-baselining”
• No accountability for missed milestones

---

9) Ask the right diligence questions

Examples:

Pipeline

• What % of pipeline has site control?
• What % has interconnection applications accepted?
• What % has permits in hand?
• What % has executed offtake?
• What % is expected to reach COD in the next 12/24 months?
• How much pipeline has been dropped in the last 12 months and why?

Execution

• Show your last 10 projects: planned vs actual dates and costs.
• What were the top 3 causes of delay in the last 5 projects?
• How do you manage EPC risk and change orders?
• What is your average contingency assumption, and how often have you exceeded it?
• Which parts of the execution process are done in-house vs outsourced?

Bias control

• What assumptions are most sensitive in your business plan?
• Which assumptions have historically proved too optimistic?
• What downside cases do you use internally?
• What independent validation do you obtain?

---

10) Look for “truth tellers” and “stress testers”

The best developers can articulate:

• What could go wrong
• What they don’t know yet
• Which projects are speculative
• What they would not underwrite today

People who are credible usually:

• Quantify uncertainty
• Avoid overclaiming
• Can discuss failures without defensiveness

---

Practical scoring approach

You can score a developer 1–5 on each category:

1. Pipeline quality
2. Stage transparency
3. Historical forecast accuracy
4. Construction delivery
5. Data verifiability
6. Governance/reporting
7. Incentive alignment

A developer with high scores across all seven is much more likely to be credible.

---

Biggest red flags

• Pipeline far larger than their capital/team capacity
• Repeatedly missed CODs with weak explanations
• No independent verification of key milestones
• Claims of “fully permitted” or “shovel-ready” without documentation
• Inconsistent numbers across decks, models, and interviews
• Avoidance of downside scenarios
• Excessive reliance on future policy/subsidy assumptions

---

Bottom line

To assess credibility and bias, verify the pipeline at the project level, compare promises to historical outcomes, and triangulate with independent sources. The most credible developers are not the ones with the most optimistic forecasts—they’re the ones whose forecasts are consistently close to reality and who clearly disclose risk.

If you want, I can turn this into a developer diligence checklist or a scorecard template you can use in meetings.