Grid access is the real timetable.

Why energy-transition platforms and major projects should know whether energisation, not construction completion, sits on the critical path to value.

June 2026   ·   8 minute read

Boards plan to a build programme and a funding round. But the date that often decides the outcome is one they do not set: the date the asset can be energised.

When that date is on the critical path, much of what the business did control can still earn nothing.

Every infrastructure platform, and every large complex project, runs to more than one timetable. The visible ones are the construction programme and the capital plan. They are reported, scrutinised and challenged because they are the schedules the business appears to control. The construction programme has milestones, a critical path and monthly variance against plan. The capital plan has drawdowns, funding rounds and investment approvals that pace deployment against delivery.

Both matter. Neither necessarily decides the economic outcome.

The economic timetable is different. The asset starts to earn when it can be energised, enter service and convert capital into revenue. In many projects that date is set at the grid. By the network operator, the connection queue, design approvals, contestable works, reinforcement requirements and dependencies that may sit outside the developer’s programme entirely.

A board can compress a construction schedule. It can accelerate procurement. It can approve capital faster. It cannot, by effort alone, move the date at which the network is ready to connect the asset.

That does not mean energisation is always the critical path. Some projects have sufficient programme float, phased delivery options or alternative operating arrangements that allow other activities to set the pace. The key is to understand whether grid access is the constraint that determines value, rather than assuming it is either irrelevant or all-important.

A connection offer is not a connection

Part of the difficulty is that the connection can feel settled long before it is.

A signed connection offer can read like certainty. It carries a date, a capacity and a price. It is easy to treat it as the fixed point around which the rest of the programme can be built. It is not. A connection offer is a commitment inside a wider dependency chain. It has value, but it is not the same as energisation. The date remains contingent on what has to happen before the asset can be connected and live. Is the queue position being protected, are design approvals clearing, are contestable and non-contestable works aligning, reinforcement works completing and third parties delivering their part.

The offer shows when connection might be possible. It does not, on its own, confirm when it will be.

That gap between offer and energisation is where programmes quietly lose time. It rarely appears as one dramatic failure. It accumulates through dependencies: a design re-approval, a delayed reinforcement milestone, a missed information requirement, a third-party interface that was assumed rather than owned. By the time the movement is visible at board level, the date that anchored the model may already have shifted.

When energisation is the master schedule

Energisation paces everything else when it sits on the critical path, whether or not the programme acknowledges it.

Land can complete. Planning can be consented. Construction can finish. Commissioning can stand ready. But the asset still cannot perform the business case until it is connected and live.

A built, unenergised asset is one of the worst positions in the model. It has absorbed capital, triggered holding costs, consumed management attention and still cannot convert into revenue. It waits.

When practitioners say a project is on programme, they often mean the build is on programme. That is the schedule they own and report against. But a build delivered on time into a connection that is not ready is not a project on programme where energisation is the date that matters.

It is a stranded asset with good paperwork.

This is why boards should test whether energisation is the master schedule. Not because construction is unimportant, but because construction is only economically useful when the asset can enter service. On some projects, the critical date is the date the asset is built. On others, it is the date the asset can operate. The discipline is understanding which timetable truly drives value.

Grid access is a join, not a function

Complex infrastructure fails at the joins. At the seams between specialised parties rather than inside any single discipline.

Grid access is one of the clearest joins in a major project or energy-transition platform. It sits between the developer, the network operator, the connection queue, as well as the independent connection provider handling contestable works, land rights, planning conditions, design approval and the wider reinforcement programme, not to mention the independent network operator who may ultimately adopt the scheme.

The same pattern appears across major transportation enhancement programmes, large-scale utility solar and energy schemes, high-power EV charging networks and other critical infrastructure such as data centres. The visible programme may sit in civils, construction, procurement or capital deployment, but the risk that decides the outcome sits at the interface: where grid capacity, design approval, land rights, third-party works, commissioning and operational readiness have to meet.

In transport, that may be possession planning, systems integration or entry into service. In utility-scale energy, it may be connection sequencing, curtailment risk or reinforcement dependency. In EV charging, it may be a site that is built, commissioned and commercially ready, but still unable to energise at the capacity assumed in the model, or technically open to customers but constrained by insufficient grid capacity and therefore delivering a poor charging experience.

The sectors differ, but the lesson is consistent: the asset does not become valuable when the build is substantially complete. It becomes valuable when the whole system is ready and able to operate.

That is why grid access fails in the way joins fail. It rarely fails because one party was simply incompetent inside its own remit. The developer’s team may be capable. The network operator may be diligent. Contractors may be ready. The connection can still slip because the risk lives in the dependency, the handoff and the assumption each party makes about what the other will deliver and when.

No single party owns the whole date. So no single party can guarantee it.

This bites whether the asset is a single major project or a platform of many. On a platform, a single delayed connection damages a site model, and a pattern of them damages the platform model. But a platform at least spreads connection risk across multiple sites, so any one slippage is partly absorbed.

A large, complex single asset has no such diversification. Its investment decision and business case rest on one connection, at one site, on one date. When that date moves, there is no wider portfolio to absorb the loss. The impact is at least as material as on a platform, and often greater, because the exposure is concentrated rather than shared. In both cases, grid timing affects revenue, capital efficiency, investor confidence and the credibility of the case.

Grid access is therefore not a technical workstream to be reported after the main programme. It is the interface that decides the outcome.

The queue is now a contest, not a ticket

The ground has also shifted.

Queue position used to behave more like a ticket. A developer secured a position, held it and waited its turn. That logic is changing. The direction of reform is toward readiness, evidence and progression. Projects that can demonstrate maturity are better placed than projects that merely hold optionality.

The intent is understandable: to release capacity trapped behind speculative schemes and improve the deliverability of the queue. But the consequence for serious developers and asset owners is significant.

Readiness is no longer a virtue. It is a condition of staying credible.

That changes the operating model. A platform or project owner cannot treat grid as an early application followed by a long wait. It has to maintain the evidence required to protect its position. It has to align land, planning, design and commercial commitments with the connection pathway. It has to know which dependencies are inside its control, which are outside it, and which need active management before they become programme-critical.

The stronger developers and owners will not be the ones that simply secured the earliest offers. They will be the ones that can evidence maturity when the system tests it.

They will also be the ones that engage constructively with evolving connection arrangements and reform proposals. Where opportunities exist to accelerate, resequence or improve the deliverability of a connection, owners should understand them early, provide informed feedback and actively participate in the process rather than treating the connection date as immutable.

What boards should require

The response is not to choose between advocacy and management. It is to run both at once.

The first track is to pursue every legitimate route to improve the connection outcome, whether by acceleration, resequencing or engagement with network and regulatory processes. On a large complex asset, even a modest improvement can move the business case, so the effort is worth making. The second track is to manage the date already in hand, on the assumption that improvement may not come. Advocacy without management is hope. Management without advocacy leaves value on the table.

The board question is not simply: do we have a connection offer?

It is: what has to be true for this site or asset to energise on the date in the model?

That question exposes the real dependencies. It brings reinforcement, design approval, contestable works, queue evidence and fallback commercial options into the same conversation. It also exposes whether the business is managing grid as the constraint that decides the case or reporting it as a technical update.

The board should be able to see five things clearly.

First, the offered connection date and the credible energisation pathway behind it. Not just the date in the offer, but the route from today to a live asset.

Second, the dependencies outside the developer’s or owner’s direct control. Reinforcement, approvals, third-party works and network milestones should be visible as part of the main programme, not buried in a separate grid tracker.

Third, the evidence required to protect queue position and demonstrate readiness. Land, planning, design maturity and delivery progression should be sequenced to the connection pathway, not assembled in a hurry when challenged.

Fourth, the commercial consequence of slippage. The model should show what happens if energisation moves by three, six, twelve or eighteen months. Revenue, debt assumptions, holding costs, procurement commitments and investor reporting should all be tested against that movement.

Fifth, the mitigation plan. That may include phased energisation, demand-led first phases, behind-the-meter supply, private wire options, temporary operating models or other hedges where the economics and regulatory position support them. Not every site or asset will have a viable hedge. But every serious owner should know whether one exists.

None of this is exotic. It is the difference between a board that sees the real constraint and a board taking comfort from the wrong schedule.

The board-level consequence

If grid sets the timetable, board reporting has to follow. A business reported primarily around its construction programme is measured against a baseline that may not decide the outcome. Where energisation is the binding constraint, the connection date should sit above the construction programme, not beneath it, reported with its dependencies, evidence requirements and commercial consequences.

Not every grid risk can be removed. But the board should know whether the business case is being measured against the date that actually matters. Grid is not an administrative input to the programme. Where it sits on the critical path, it is the date the business case turns on.

The capital may clear, the steel may arrive and the asset may be built. They don’t set the date the business starts to earn. That date is set at the join between the business and the grid.

The best owners understand this early and build the programme around it. Others learn it late, expensively, with a finished asset and unable to switch it on.

McMillan Maclean Limited   ·   Practitioner judgement. Long-duration capital.

Principal-led independent advisory in infrastructure and energy transition, serving boards, chief executives and long-duration investors.