What 150MWh Approval and 1GWh Submission Really Mean for BESS

The contrast in this update is what makes it valuable for developers and investors. In Australia, a 150MWh battery energy storage system from Foresight has been granted approval in NSW, while a 1GWh development from Banpu has been submitted for federal consideration under the EPBC Act. Those two milestones may appear similar in headlines because both sit inside the same storage growth story. In practice, they represent very different levels of project maturity, risk, and financing readiness. One is moving through the market with a major permitting step completed, while the other is still entering a critical review pathway. For project sponsors, understanding that difference is not administrative detail. It is central to valuation, schedule confidence, procurement timing, and the credibility of any commercial roadmap presented to lenders or equity partners.

This is why we consistently argue that utility-scale BESS development is won or lost before construction starts. The market often focuses on duration, revenue strategy, or equipment selection, but permitting discipline is what turns a storage concept into a financable project. A 150MWh approval means the project has advanced beyond slideware and entered a more concrete risk profile. A 1GWh submission under the EPBC Act, on the other hand, signals scale and ambition, but it also confirms that federal environmental and planning exposure still needs to be worked through. In other words, nameplate size does not automatically equal project readiness. In many pipelines, the biggest value gap is not between smaller and larger systems. It is between projects that have been properly prepared for scrutiny and projects that are still assembling the evidence required to withstand it.

From a development standpoint, approval and submission should never be treated as interchangeable markers. Approval changes the conversation with investors because it reduces uncertainty around timing, conditions precedent, and downstream execution planning. Submission marks the start of a test, not the end of one. It tells the market that the project is real enough to enter review, but it does not yet eliminate the risks that matter most for schedule and capital deployment. This distinction is especially important in storage because revenue windows can be sensitive to delays, and procurement decisions can quickly become disconnected from development reality if teams get ahead of the permit path. We see many sponsors underestimate this gap. They talk about engineering and commercial readiness as if they can advance independently from permitting, when in fact the project’s overall risk profile is still being shaped by environmental, land-use, and approval conditions.

The EPBC angle matters because federal consideration introduces another layer of discipline. When a project enters that pathway, the developer is no longer managing only a technical storage concept or a local planning narrative. The project company now needs a much more structured evidence base around site characteristics, environmental impacts, stakeholder issues, documentation quality, and response readiness. That is not a burden to be managed passively. It is a development workstream that can materially influence schedule logic, contract timing, board decisions, and the sequencing of external commitments. For a 1GWh BESS, the scale only heightens that requirement. Larger storage projects attract more attention from investors and offtake counterparties, but they also amplify the consequences of weak permitting preparation. If key assumptions are challenged late, the whole commercial stack can move out of alignment.

Planning success also has direct consequences for procurement and delivery strategy. Once a project begins to secure meaningful approvals, sponsors need to transition from conceptual ambition to executable packaging. That means validating whether permit conditions affect site layout, access, construction windows, safety case assumptions, grid connection dependencies, or documentation obligations that will later flow into EPC and supply contracts. Too often, development teams celebrate an approval milestone but fail to translate it into contract architecture and implementation controls. The result is a handoff gap between development and delivery. In BESS projects, that gap can be expensive because equipment commitments, installation sequencing, testing protocols, and grid compliance expectations all need to reflect what was actually approved, not what the early business case assumed. Strong projects connect permitting outcomes directly into procurement and construction governance.

The sector-wide risks are familiar, but storage projects compress them into a fast-moving timeline. Schedule slippage can weaken commercial assumptions. Incomplete site or environmental files can slow approvals. Fragmented document control can undermine lender confidence. A poorly managed interface between permitting, grid studies, safety planning, and contract negotiation can leave the project legally advanced but practically unready. These are not theoretical issues. They are the everyday reasons large storage pipelines fail to convert momentum into closed transactions and disciplined execution. For investors, the lesson is simple: do not confuse market excitement around storage with project readiness. For developers, the more useful question is whether the project has a traceable path from submission to approval, from approval to procurement, and from procurement to financial close without governance gaps between those stages.

At BEIREK, this is where we add value. We structure the development process so that permitting is not treated as a standalone compliance task, but as a core part of finance readiness and delivery preparation. We build requirements libraries, approval matrices, document traceability, and executive reporting that allow sponsors to see exactly what has been submitted, what remains open, which conditions could affect schedule, and how those conditions should shape procurement and contracting decisions. We also support data room readiness for lenders and investors, because large BESS projects are increasingly evaluated on development quality, not only on market narrative. Our role is to connect site assessment, permitting, project finance logic, and contract preparation into one governed pathway that can withstand scrutiny from boards, financiers, counterparties, and regulators alike.

The difference between a 150MWh approval and a 1GWh federal submission is bigger than one headline cycle. It captures the real discipline required in utility-scale storage: sequencing matters, evidence matters, and permitting maturity changes project value. In our view, sponsors who treat development milestones as strategic control points will build stronger portfolios than those who treat them as administrative hurdles. If your BESS pipeline is moving from concept into approvals, this is the right moment to pressure-test the permit roadmap, the documentation stack, and the transition from development to execution. That is how we help clients avoid false readiness and move toward bankable, deliverable projects.