How to Analyze Battery Storage Project Pipelines

Short answer: a battery storage project pipeline is useful only when every project has a clear status, source, date and identity. Counting announcements is not the same as measuring executable opportunity.

What should a project pipeline show?

A pipeline should help a team answer three questions: which projects are real, which projects are moving, and which projects are relevant to the decision at hand. That requires more than project names and megawatts.

• Where is the project and which market does it serve?
• Who owns, develops, builds and supplies it?
• What technology, power, energy and duration are planned?
• What is the current stage and when was it last verified?
• What commercial or regulatory event could move it forward?

Why use a consistent status model?

Separate announced, site-control, interconnection, permitted, contracted, financed, under construction, operating and cancelled. Do not collapse these into one “pipeline” total. A project that appears in a press release and a project under construction represent very different opportunities.

Record both the reported status and your normalized status. If the source says “targeted for development,” preserve that wording rather than upgrading it to “planned.”

Why build a project identity before counting?

One project can appear under a developer name, an owner name, a site name and a later phase name. Create a stable record using location, owner, developer, capacity, technology and source dates. Link aliases and phases to a parent project where appropriate.

A practical record includes project name, aliases, country, state or region, owner, developer, EPC, system integrator, power in MW, energy in MWh, duration, use case, status, expected operation date, announcement date, last verified date and source URL.

How should you grade the evidence?

Use an evidence grade so decision-makers can distinguish a verified opportunity from an early signal. Primary sources such as regulators, tender authorities, grid operators, permits, filings and company releases should carry more weight than unattributed databases or copied news.

Keep a source register with the original URL, publisher, publication date, access date, quoted evidence and the fields supported by that source. A record without a source date should be treated as stale until rechecked.

How do you turn the pipeline into an opportunity view?

After normalization, filter the pipeline by geography, status, size, use case, customer type and timing. Add a next action: verify permit, identify EPC, check procurement, monitor interconnection or qualify the account. The output should tell a commercial team what to do next, not just how many megawatts exist.

What quality checks should you run?

• Remove duplicate announcements and separate project phases.
• Keep announced capacity separate from operating capacity.
• Check whether MW and MWh refer to the same project scope.
• Flag records that have not been verified within the chosen review period.
• Preserve the original wording when status is ambiguous.
• Document exclusions, assumptions and confidence.

FAQ

What is a battery storage project pipeline?

It is a normalized, time-stamped set of storage projects tracked by identity, location, capacity, status, source and next decision-relevant action.

How do you avoid double-counting storage projects?

Match project aliases and phases using location, owner, developer, capacity, technology and source dates, then link related records to one parent project.

Which storage projects are most valuable to track?

Track projects that match the decision: for example, projects with a credible status, relevant geography, identifiable decision-makers, suitable size and a next commercial or regulatory milestone.

For a repeatable project and market-sizing workflow, see the Projects, Tenders & Market Sizing Toolkit.