Update on delays to connection dates for some TMO4+ Protected Projects

What this is about

Ofgem has confirmed that some Protected Projects under the Gate 2 to Whole Queue (G2tWQ) reform will miss their original connection dates, and that it will not grant NESO and the Transmission Owners relief from their obligations to deliver those dates. Protected status was the central reassurance offered to developers during TMO4+: projects that qualified would keep their existing connection dates and points of connection while the rest of the queue was reordered around them. NESO and the TOs have now told Ofgem they cannot comply with elements of the Connections Methodologies for a number of these projects. Ofgem's response is a refusal to waive the obligation, plus an admission that it does not yet know why the slippage is "widespread."

This matters because protected status was a promise about certainty, and the promise has not held. Developers were asked to accept a wholesale reordering of the queue on the understanding that their own position was ring-fenced. Some made financing, procurement, and offtake decisions on the strength of a fixed connection date. The value of a connection is binary in the way that matters here: a project either energises when its commercial case assumes it will, or the case erodes with every quarter of delay. A protected date that slips is not a smaller version of the promise; it is the promise failing for the projects that relied on it most.

Key points

- Refusal of relief, not endorsement of delay. Ofgem is declining NESO's and the TOs' request to be relieved of their Connections Methodologies obligations for the affected Protected Projects. The obligation to deliver the original dates remains live; what Ofgem cannot do by refusing relief is make the physical reinforcement happen faster. The regulatory position and the delivery reality have come apart.

- The cause is unknown and possibly systemic. Ofgem states it will "continue to engage" to "ascertain the causes" and to establish "whether there is any systematic problem that needs addressed." That is an admission that the regulator did not anticipate this and does not yet understand it. "Widespread" is Ofgem's own word. This is not a handful of site-specific construction problems; it is a pattern across protected projects that NESO and the TOs flagged collectively.

- No numbers disclosed in the notice. The published letter does not name the projects, quantify the number affected, state the length of the delays, or identify which TOs are involved. Affected developers will know privately; the market does not. The detail sits in the linked "Ofgem Response on Protected Projects Relief Request" PDF, which the notice references but does not summarise.

- The protection was a deliverability claim NESO and the TOs could not underwrite. Protected status was assigned through a process Ofgem oversaw, on the basis of information from NESO and the TOs about what could be delivered. The relief request shows the deliverability assessment behind protection was wrong for some projects. Protection priced certainty that the delivery chain could not supply.

- Relief refused does not mean dates met. A developer reading this should not take "Ofgem will not grant relief" as "the date is safe." It means the breach of obligation is recorded rather than excused. Whether that produces enforcement, compensation, or simply a delayed connection with the obligation formally unmet is exactly what Ofgem has left open.

What happens next

Ofgem will keep engaging with NESO and the TOs on causes and on "how this issue may be handled." No timeline, milestone, or decision date is given, which is itself the signal: there is no remedy on the table yet, only an investigation into why the commitment failed. The open questions are whether Ofgem treats this as a licence-obligation compliance matter against NESO and the TOs, whether affected developers have any recourse, and whether the "systematic problem" framing leads to a structural review of how protected dates were assessed in the first place.

For developers: do not assume your protected date is secure because Ofgem refused relief. Establish directly with NESO whether your specific project is among those flagged, request the revised indicative date, and treat any project whose financial case depends on the original connection date as exposed until NESO confirms otherwise. The relief request was made collectively, so the absence of an individual notification is not confirmation that a project is unaffected.

The wider read: this is the first hard test of whether queue reform can deliver the certainty it was sold on. The G2tWQ bargain asked the queue to accept disruption in exchange for protected projects getting a firm date. If protected dates slip and the cause is systemic in the TO build programme rather than project-specific, the problem is not the reform's design but the delivery capacity underneath it. Reordering the queue does not add transmission. The binding constraint is reinforcement that has not been built, and no allocation rule fixes that. Watch for the follow-up letter that quantifies the affected projects and states the cause; that document, not this notice, will show whether protected status meant anything.