CMP471 Urgency Request Letter
This consultation is open for responses
Closes 30 Jun 2026 (40 days remaining)
Summary
Muirhall Energy has raised CMP471, a temporary CUSC amendment letting Users adjust connection dates and contract elements before the first CMP434 Gated Application Window and the 1 April 2027 liability trigger. The CUSC Panel unanimously recommended urgent treatment on 15 May 2026; if Ofgem agrees by 19 May, implementation lands 31 July 2026 instead of an undated 2027 slot. Without it, queue holders enter Gate 2 carrying contractual connection dates that no longer match deliverable programmes.
Why it matters
This is a relief valve for queue holders facing the 1 April 2027 liability cliff: Gate 2 rejection rates and termination costs fall if Users can pre-adjust. It softens the discipline CMP434 was designed to impose, so incumbents with stale contracts win and the queue stays fatter for longer than the connections reform intended.
Key facts
- •Proposer: Muirhall Energy, raised 17 April 2026
- •CUSC Panel recommended urgency unanimously on 15 May 2026 (7 industry + NESO)
- •Ofgem urgency decision due by 5pm on 19 May 2026
- •Backstop implementation: September 2026; recommended urgent implementation: 31 July 2026
- •1 April 2027 liability trigger is the binding deadline driving urgency
- •Workgroup Consultation under urgent timetable: 3-9 June 2026 (<15 BD)
- •Code Administrator Consultation: 23-30 June 2026 (<15 BD)
- •DFMR issued 7 July 2026; Panel vote 10 July 2026; Ofgem decision 17 July 2026
- •Standard timeline would push Ofgem decision into mid-2027 with implementation TBC
Timeline
Areas affected
Related programmes
Memo
What this is about
CMP471 is a temporary CUSC fix that lets queue holders adjust connection dates and other contract elements before the first CMP434 Gated Application Window opens. Muirhall Energy raised it on 17 April 2026. The CUSC Panel considered it on 15 May 2026 and unanimously recommended urgent treatment. Ofgem's decision on urgency is due by 5pm on 19 May 2026. If granted, the modification implements on 31 July 2026. If refused, it slips into the standard timetable with implementation "TBC" sometime in 2027, after the 1 April 2027 liability trigger has already fired.
The trigger matters. From 1 April 2027, Users carrying connection dates in their contracts face a step change in liability exposure tied to those dates. Connections reform (CMP434) then funnels them into Gated Application Windows where their contractual dates are tested against Gate 2 criteria. The Proposer's case is that many Users hold contractual connection dates that no longer reflect what their projects can actually deliver, and that without a pre-Gate 2 window to amend them, they will either reject Gate 2 Offers or absorb cost exposure tied to programmes they cannot meet. The Panel agreed this is a significant commercial impact (Ofgem Urgency criterion (a)) with a fixed deadline that a standard 11-month timetable cannot meet.
The substantive question for Ofgem is not really the timetable. It is whether to soften the discipline CMP434 was designed to impose. CMP434's logic is that contractual connection dates should mean something, and that Users carrying undeliverable dates should bear the cost of having claimed them. CMP471 lets those Users rewrite the contract before the bill arrives. That helps the queue holders who currently sit on stale dates. It also extends the life of contracts that the reform was built to flush out.
Options on the table
The Panel paper presents one substantive proposal (CMP471 itself) with two timetable variants. The choice Ofgem actually faces is binary: grant urgency or refuse it.
Grant urgency, implement 31 July 2026
This is what the Panel and the Proposer want. Workgroup runs through May and early June, code administrator consultation closes 30 June, Panel votes on the Draft Final Modification Report on 10 July, Ofgem decides by 17 July, and the new variation process is live on 31 July. That gives Users roughly eight months between implementation and the 1 April 2027 liability trigger to use the interim variation process to align contractual connection dates with deliverable programmes.
Who wins: existing queue holders with stale dates, particularly those whose original contractual connection dates were set on optimistic delivery assumptions and who would otherwise enter Gate 2 carrying programmes they cannot defend. Developers who have been holding queue positions on capacity they cannot bring forward also win, because the variation process lets them reset the date without losing the position. NESO wins to the extent that Gate 2 rounds run more cleanly when Users arrive with credible dates rather than rejecting offers on arrival.
Who loses: the integrity of the CMP434 timetable, and by extension the consumers who fund the reform. The 1 April 2027 trigger was set to impose a cost on holding undeliverable dates. CMP471 lets Users avoid that cost by amending the dates before the trigger fires. New entrants who would gain queue access faster if incumbent holders were flushed out via Gate 2 also lose. The slower the queue clears, the longer they wait.
The compressed timetable itself carries process costs. Workgroup consultation drops below 15 business days. Code administrator consultation drops below 15 business days. There are fewer than 5 clear business days between the Draft Final Modification Report and the Panel recommendation vote, and fewer than 5 clear business days for Panel to verify the vote was recorded correctly. These are not nominal abbreviations. They reduce the time available for industry parties to scrutinise the drafting of the variation process itself, which determines how broad the relief actually is, what counts as a permissible adjustment, and how NESO assesses each request. Drafting errors locked in on this timetable are harder to catch.
Refuse urgency, follow the standard timetable
The standard timetable presented in Appendix 2 has implementation date "TBC" but the path leads through Ofgem decision in April 2027 at the earliest. That is after the 1 April 2027 liability trigger has already passed. On this path, CMP471 either lands too late to do its intended job or is abandoned.
Who wins: the CMP434 reform programme. Users who cannot defend their contractual connection dates enter the first Gated Application Window with those dates intact and are tested against Gate 2 criteria as the reform designed. Termination payments and Gate 2 rejections fall on the parties whose original date claims were optimistic. The queue contracts. New entrants gain access faster.
Who loses: existing queue holders carrying stale dates, who face larger cost exposure than they would under the urgent route. Some of those holders will be projects that genuinely could deliver but on a revised timetable, and the standard route gives them no orderly exit. The crudeness of the test is the point of CMP434, but it is also the cost.
Questions being asked
The letter itself is a Panel request for an urgency decision, not a consultation document with numbered questions. Ofgem's decision is binary (urgency granted or refused) with a defined deadline. The substantive consultation questions on the policy content of CMP471 will follow during the Workgroup Consultation (3-9 June 2026 on the urgent timetable) and the Code Administrator Consultation (23-30 June 2026 on the urgent timetable). Those question sets are not in this document.
For respondents who want to influence the policy content rather than the urgency decision, the relevant inputs are:
On urgency
Whether the imminent 1 April 2027 liability trigger and the first CMP434 Gated Application Window together constitute a significant commercial impact under Ofgem Urgency criterion (a), such that the modification cannot wait for a standard timetable. (The Panel says yes, unanimously. Ofgem's call is whether the commercial impact is significant enough to override the procedural costs of the abbreviated timetable.)
On policy content (for the consultations that follow)
What contract elements should be amendable under the interim variation process. (Connection date is the headline. Whether the variation can also cover capacity, technology, or other commercial terms shapes how far the relief reaches and how much of CMP434's discipline it dilutes.)
How NESO should assess each variation request. (A high bar limits use to projects that can show genuine programme slippage. A low bar makes it a routine reset for any User who wants one.)
Whether the variation process should sunset on a defined date or persist into the Gated Application Window regime. (The Proposer frames CMP471 as temporary and pre-Gate 2. The drafting needs to make that stick.)
Whether Users who variate under CMP471 should face any consequence (forfeited security, reduced priority, fee) or whether the variation is cost-free. (Cost-free variation maximises the dilution of CMP434. A fee or security adjustment preserves some of the discipline.)
How to respond
This letter is addressed to Nadir Hafeez at Ofgem and signed by Anthony Pygram, Independent Chair of the CUSC and Grid Code Panel. It is a Panel request for an urgency decision under CUSC Section 8.24.4, not an open consultation. Ofgem's response on urgency is due by 5pm on 19 May 2026.
For industry parties wanting to engage with the substance of CMP471 rather than the urgency decision, the relevant routes (assuming urgency is granted) are:
- Workgroup Consultation: 3 June 2026 to 9 June 2026. Less than 15 business days. Open to all CUSC parties and interested stakeholders. Submitted via the CUSC modification page on the NESO website. - Code Administrator Consultation: 23 June 2026 to 30 June 2026. Less than 15 business days. Same submission route. - Workgroup attendance: Workgroups 1-3 run 26 May, 29 May, and 2 June 2026. Workgroups 4-5 run 11 June and 15 June 2026. Workgroup nominations open 15-19 May 2026.
If urgency is refused, the standard timetable opens Workgroup Consultation from 8 October to 29 October 2026 and Code Administrator Consultation from 8 February to 1 March 2027, but on that path the modification likely arrives too late to serve its purpose.
All CMP471 documentation is on the NESO CUSC modifications page. Questions on the letter or the proposed process should go to Anthony Pygram in his capacity as Independent Chair of the CUSC and Grid Code Panel. Contact details are not given in the body of the letter; the standard route is via the CUSC Code Administrator at NESO.
Source text
Public Nadir Hafeez Ofgem By email Anthony Pygram Independent Chair CUSC & Grid Code Panel 15 May 2026 CMP471 Request for Urgency Dear Nadir Connection and Use of System Code (CUSC) Modification Panel Request for Urgency and Recommended Timetable for CMP471: Interim Contract Variation Process Ahead of CMP434 Gated Application Window. On 17 April 2026, Muirhall Energy raised CMP471. The Proposer sent a request to the CUSC Panel Secretary for this modification to be treated as urgent. CMP471 proposes a temporary, limited amendment to the CUSC allowing Users to adjust elements of their NESO contracts before the first CMP434 Gated Application Window. All documentation for this modification can be located via the following link. The CUSC Modifications Panel ("the Panel") on 15 May 2026, considered CMP471 and the associated request for urgency. This letter sets out the views of the Panel on the request for urgent treatment and the procedure and timetable that the Panel recommends. The Proposer set out their rationale for Urgency against Ofgem’s Urgency criteria (a) which is as follows: a) A significant commercial impact on parties, consumers or other stakeholder(s). This modification meets Ofgem’s urgency criteria as it relates to an imminent and time-bound issue with significant commercial implications for Users. Users require the ability to amend connection dates ahead of the first CMP434 Gated Application Window and prior to the 01 April 2027 liability trigger. Without this, Users may be exposed to increased cost and liability profiles that do not reflect deliverable project timelines. The timing of implementation is therefore critical. A backstop implementation date of September 2026 is required to ensure that Users can utilise the proposed variation process before the relevant liability milestone is reached. Without urgent implementation, Users will be required to enter the first CMP434 Gated Application Window with contractual connection dates that do not reflect current project delivery assumptions. This misalignment may lead to inefficient Gate 2 outcomes, including an increased risk of Users rejecting Gate 2 Offers due to inaccurate programme assumptions and associated cost exposure. The inability to amend connection dates ahead of the Gated Application Window Public creates a clear timing constraint. If not addressed in advance of this window, Users will lose the opportunity to make proportionate adjustments within the scope of this proposal, resulting in avoidable inefficiencies and increased cost risk. Panel Consideration of the Request for Urgency The Panel considered the request for urgency with reference to Ofgem Guidance on Code Modification Urgency Criteria. The unanimous view of the Panel is that CMP471 does meet Ofgem’s Urgency criteria1. Therefore, the recommendation of the Panel is that CMP471 should be treated as an Urgent CUSC Modification Proposal. Panel members set out their rationale behind this decision: • Seven Panel members agreed with the Proposer’s justification for urgency. • The view of NESO Panel member was that the figures presented by the Proposer during Panel, show that it's clear this issue presents a significant commercial impact to some industry parties, which would not be solved in time by a modification progressing under a standard timeline. As such, NESO agrees with the case for urgency. Procedure and Timetable The Panel discussed an appropriate timetable for CMP471 in the instance that urgency is granted. The Panel agreed that CMP471 subject to Ofgem’s decision on Urgency should follow the attached Code Administrator’s proposed timetable (Appendix 1 Urgent recommendation). In Appendix 2 of this letter, the Code Administrator has also provided the timeline if this follows standard timescales with the assumption that Panel prioritises this high in the prioritisation stack. Panel noted that if urgency is required, there would be; o A Workgroup Consultation period of less than 15 Business Days o Code Administrator Consultation period of less than 15 Business Days o There would be less than 5 clear Business Days between publication of the Draft Final Modification Report and Panel’s recommendation; and o There would be less than 5 clear Business Days for Panel to check that their Recommendation Vote had been recorded correctly 1 Ofgem’s current view is that an urgent modification should be linked to an imminent issue or a current issue that if not urgently addressed may cause: a) A significant commercial impact on parties, consumers or other stakeholder(s); or b) A significant impact on the safety and security of the electricity and/or gas systems; or c) A party to be in breach of any relevant legal requirements. Public Under CUSC Section 8.24.4, we are now consulting the Authority as to whether this Modification is an Urgent CUSC Modification Proposal. Please do not hesitate to contact me if you have any questions on this letter or the proposed process and timetable. I look forward to receiving your response Yours sincerely Anthony Pygram Anthony Pygram Independent Chair of the CUSC and Grid Code Panel Appendix 1– Urgent Timeline Modification Stage Date Modification presented to Panel 15 May 2026 Workgroup Nominations 15 May – 19 May 2026 Ofgem decision on Urgency By 5pm on 19 May 2026 Workgroups 1- 3 26 May 2026 29 May 2026 02 June 2026 Workgroup Consultation 03 June 2026 – 09 June 2026 Workgroups 4-5 11 June 2026 15 June 2026 Workgroup Report issued to Panel 17 June 2026 Panel sign off that Workgroup Report has met its Terms of Reference 19 June 2026 (Special Panel) Code Administrator Consultation 23 June - 30 June 2026 Draft Final Modification Report (DFMR) issued to Panel 07 July 2026 Panel undertake DFMR recommendation vote 10 July 2026 (Special Panel) Final Modification Report issued to Panel to check votes recorded correctly 10 July 2026 Final Modification Report issued to Ofgem 10 July 2026 Ofgem decision 17 July 2026 Implementation Date 31 July 2026 Appendix 2 – Standard Timeline Modification Stage Date Public Modification presented to Panel 15 May 2026 Workgroup Nominations 26 May – 19 June 2026 Workgroups 1- 4 01 July 2026 05 August 2026 03 September 2026 01 October 2026 Workgroup Consultation 08 October 2026 – 29 October 2026 Workgroups 5-7 12 November 2026 10 December 2026 07 January 2027 Workgroup Report issued to Panel 21 January 2027 Panel sign off that Workgroup Report has met its Terms of Reference 29 January 2027 Code Administrator Consultation 08 February 2027 – 01 March 2027 Draft Final Modification Report (DFMR) issued to Panel 18 March 2027 Panel undertake DFMR recommendation vote 26 March 2027 Final Modification Report issued to Panel to check votes recorded correctly 31 March – 07 April 2027 Final Modification Report issued to Ofgem 12 April 2027 Ofgem decision TBC Implementation Date TBC See separate attachment Appendix 3 – Panel Urgency Vote