The first article in this series argued that governments are accountable for energy transition objectives, but no single actor is accountable for ensuring the ecosystem delivers them. If you haven’t read part one, take a look here: https://www.linkedin.com/pulse/from-coordination-orchestration-pt-1-role-central-orchestrator-ftgxc/

If that gap is real, the obvious question follows.

What does an orchestrator actually do?

Orchestration is not another coordination forum. It is not a stronger project management office. It is active system stewardship. It deliberately shapes how policy, regulation, capital, and delivery interact to achieve government objectives.

Optimising the system, not the asset

Individual projects optimise for their own economics. Network operators optimise for reliability and efficient utilisation. Regulators optimise for compliance with the rules. Each actor behaves rationally within its mandate.

But government objectives are delivered at system level.

An orchestrator therefore looks across the entire pipeline of activity and asks a different question. Not “is this project progressing?”, but “is the system progressing towards the objectives?”

That distinction matters.

Consider sequencing. Two adjacent renewable projects may each want immediate connection, but the network may not yet have sufficient capacity. One option is to progress both slowly and expensively. Another is to deliberately sequence delivery, pause one project for a defined period, complete a shared transmission upgrade, and enable both to connect more efficiently.

The first option protects individual project velocity. The second improves system-level outcomes.

An orchestrator finds ways to incentivise that sequencing. It does not necessarily direct a pause. It aligns funding, approvals, visibility, and incentives so that actors move in ways that improve overall performance.

Local optimisation can slow. System performance improves.

Aligning incentives across the ecosystem

An orchestrator closes the loop between policy intent and delivery experience. It identifies where incentives are misaligned and works across available levers to adjust them.

This might mean refining program criteria to encourage shared infrastructure. It might mean adjusting sequencing assumptions embedded in policy. It might mean creating visibility across agencies so that trade-offs are explicit rather than accidental.

The orchestrator may not own every lever. But it ensures the right levers are pulled.

Using market signals as tools

Curtailment provides a useful illustration of using market signals as tools.

A project proponent seeks to minimise curtailment because it reduces revenue. A network operator seeks to reduce curtailment to manage congestion and maintain reliability. Investors price curtailment risk into their decisions.

Each perspective is logical.

But eliminating all curtailment is not necessarily optimal at system level. Doing so may require overbuilding network infrastructure. It may slow the entry of new generation. It may increase overall system costs.

An orchestrator treats curtailment as a system signal and, at times, a system lever.

A degree of curtailment may be tolerated temporarily to accelerate renewable entry. Strategic tolerance of congestion may encourage geographic diversification. Sequencing shared infrastructure may reduce aggregate curtailment over time, even if short-term impacts increase.

The objective is not to maximise or minimise curtailment in isolation. The objective is to shape how curtailment interacts with investment, reliability, affordability and decarbonisation trajectories.

Markets optimise within the rules, networks optimise within their mandate, and projects optimise within their balance sheets. An orchestrator optimises for government objectives.

Unlocking stalled capital

When investment slows, the immediate response is often to focus on individual projects. An orchestrator asks whether the constraint is systemic.

Is capital constrained because of policy uncertainty? Because connection risk is misallocated? Because offtake is fragmented? Because sequencing across regions is unclear? Because grant programs are not aligned to actual risk?

Rather than treating each project as an isolated case, the orchestrator diagnoses the pattern. It then works across the ecosystem to resolve the underlying constraint.

That may involve shaping new funding mechanisms. It may involve brokering shared infrastructure arrangements. It may involve improving visibility across the pipeline so investors can see credible sequencing.

The intervention is less important than the mindset. The orchestrator looks for the systemic issue and finds a way to address it.

From strategic action to structural reform

Strategic sequencing, incentive alignment, and market shaping improve system performance. But even with strong orchestration, some problems persist across every project.

Delays that repeat. Interfaces that routinely fail. Policy settings that unintentionally undermine delivery.

These are not simply process issues within agencies or projects. They are ecosystem design problems.

In the next article, we will distinguish between process problems and ecosystem problems, and examine why certain blockers persist across the entire system unless they are addressed structurally.

Where are you in your ecosystem maturity journey?

Ask yourself:

• Are the priorities across your system clearly sequenced to achieve objectives?
• Do you have mechanisms to anticipate and resolve systemic blockers before they cascade across projects?
• Are policy, investment, and infrastructure levers deliberately aligned to achieve outcomes, not just outputs?

About the authors

Michael Panich is an Associate Director at Rennie, based in Sydney.

Tim Brunner is an Executive Director at Rennie, based in Perth.