On 29 July 2026, the UK’s Office of Gas and Electricity Markets (“Ofgem”) opened a consultation (the “Consultation”) on its proposal intended to deter speculative, non-viable data centre projects from the UK’s grid connection queue. Ofgem’s key proposals include securing a substantial “returnable” (subject to project completion) commitment fee and demonstration of “genuine” progression through a series of queue management milestones covering compute offtaker demand, long-lead equipment procurement, and financial capability and technical readiness.
What is Proposed?
1. Data Centre Commitment Fee
Ofgem has proposed a lump sum Data Centre Commitment Fee of between £237,500 and £712,500 per megawatt (such final amount yet to be determined by Ofgem) which would be secured from connection offer / bilateral connection agreement acceptance (or if later, from the time the policy is implemented) and released upon energisation of the project. Critically, the fee (or part thereof) becomes payable if the project terminates, reduces capacity or fails to comply with the relevant requirements. The fee may be secured by provision of a cash deposit in a bank account, a performance bond or letter of credit from a qualified bank or a performance bond from a qualified company.
The lump sum “returnable” (subject to energisation) fee option was recommended over an incrementally returnable fee or a progression commitment fee-style model, with Ofgem scoring this option higher (despite other options having higher levels of support) partly on the basis of administrative simplicity.
The proposed queue management milestones put the commitment fee early on in the process, before even an operate, lease or sale Memorandum of Understanding (“MoU”) has been entered into. For a 100 MW project, that means securing between £23.8 million and £71.3 million at the point of accepting a connection offer, on the strength of little more than a decision to proceed.
2. Project Progress Milestones
As well as the commitment fee, developers would have to demonstrate “genuine” progress against several key milestones in order to maintain their position in the queue, including securing a credible end-user of the data centre, procurement of electrical equipment with long lead times (e.g. switchgear), and financial and technical capability to develop a data centre. If a developer cannot provide sufficient evidence at each milestone, the project is treated as having failed that requirement and may be ejected from the connection queue. Material misrepresentation, or a failure to notify the network operator that earlier evidence is no longer valid, is treated in the same way.
The milestones would sit alongside the existing National Energy System Operator (“NESO”) and Distribution Network Operator (“DNO”) queue management milestones, rather than replacing them, and would be sequenced as follows:
- M0.5.Dc – pathway selection (Self-operation, or Lease or Sale) and non-binding compute offtaker evidence, such as heads of terms or a memorandum of understanding, due six months after connection signature.
- M2.Dc – evidence of a “genuine and material commitment” to procure the electrical equipment needed to connect and operate the project, evidenced by a purchase invoice, an executed procurement contract or a binding supplier commitment.
- M6.Dc – financial capability (an investment-grade rating of BBB−/Baa3 or better, or legally enforceable committed credit support) and technical capability (design conformity against EN 50600, TIA-942 or Uptime Institute Tier Certification of Design Documents), plus, for Lease or Sale projects, binding compute offtaker evidence.
The timing of the proposed milestones reference existing NESO queue management milestones points, rather than by specifying fixed calendar deadlines or time periods.
Key Risks for Project Developers
1. Development Risk Capital
The most obvious risk is capital lock-up. Ofgem’s own modelling shows an internal rate of return (“IRR”) impact of up to 170 basis points for the worst case scenario. While performance bonds and letters of credit are permitted, this will consume borrowing capacity that would otherwise support construction.
2. Project Structure Inflexibility
A capacity reduction triggers a liability referable to the reduced MW, a change of use out of data centre triggers the full securitised amount as if the project had terminated. Phasing decisions therefore need to be taken before offer acceptance, not iterated during development. Once the fee policy is implemented, any self-termination after the fee applies leaves the developer liable for payment of the fee, thus potentially disincentivising self-termination at all.
3. Circularity
Project developers may have difficulty securing executed offtake agreements (as required by M6.Dc) without certainty over connection timing and financial backing requirements imposed too early create a dependency loop where financing depends on a connection date which itself depends on financing. Ofgem’s answer is staging, with non-binding evidence at M0.5.Dc and binding evidence at M6.Dc. Whether that is far enough down the development curve for a colocation platform with a multi-customer fill strategy is precisely the question Q30 and Q31 of the Consultation invite the market to answer.
The Engineering, Procurement and Construction (“EPC”) Risk Allocation Problem
A significant point of difficulty is M2.Dc, whereby Ofgem is, in substance, requiring a material procurement commitment for transformers and switchgear as a condition of retaining queue position, at a point which sits well before the M7 project commitment and final investment decision.
- Owner-furnished equipment: where the developer places orders for long-lead items early in order to satisfy M2.Dc, the equipment is likely to become owner-furnished or novated to the EPC contractor on appointment. Otherwise, EPC contractors may agree to reserve long-lead items for a fee ahead of the main EPC contract being entered into. Developers should expect harder negotiation on defects liability, delivery risk, storage and pre-installation loss and any standard of care obligation for equipment the EPC contractor did not specify.
- Technical certification: EN 50600 design-conformity certification, TIA-942 design certification or Tier Certification of Design Documents will need to become a named EPC or designer deliverable, with a longstop date ahead of M6.Dc (financial and technical capability) and a remedy if certification is not achieved.
- Consequences of milestone failure: loss of queue position is potentially a project-ending event, and forfeiture of the commitment fee is a significant quantifiable loss. Developers will press for delay liquidated damages, or a carve-out from the general liability cap, referable to milestone failure caused by contractor default. Contractors will resist exposure to a regulatory sanction they cannot control, and will seek relief for network operator delay, assessment delay and third-party supply chain failure. Both positions are defensible, and this is likely to become a key point of negotiation.
A Likely Accelerant for Behind-the-Meter and Private Wire Power
Ofgem identifies “speed to power” (the gap between deciding to build and securing enough power to run the compute) as a central constraint on data centre delivery. Ofgem’s proposal will make holding a public-grid queue position more expensive and more conditional. This will likely have the effect of improving the appeal of, and we expect to accelerate the level of developer interest in, behind-the-meter (“BTM”) generation, private wire arrangements and on-site microgrids for data centres. The UK, and indeed the rest of the EU, is behind the curve on the adoption of BTM solutions when compared to the US where the adoption of BTM solutions is accelerating in response to constraints on grid power availability and public backlash on data centres in local communities.
Ireland presents a clear illustration of where constraints on grid connections could lead. Faced with the restrictions on new grid connections around Dublin, and the December 2025 large energy user and private wire framework, developers there have moved on-site generation from emergency backup to primary strategy. Pure Data Centres Group’s Dublin campus is a leading example: its 110 MW on-site microgrid, integrating battery storage and billed as Europe’s first, will provide dispatchable capacity to run the facility through initial development, ahead of full grid integration. Whilst Ofgem is not intent on suspending connections, the direction of travel is the same, and a queue that is costlier and more conditional to hold pushes the economics further towards BTM and private wire arrangements.
For developers, investors and contractors, on-site generation, battery storage and microgrid controls are likely to become a key development feature, carrying their own EPC scope and costs, long-lead procurement, grid-code compliance and technical-certification demands, and their own risk-allocation debates over availability, performance and the interface with any eventual grid connection.
What Feedback Do We Anticipate?
We expect the following themes to dominate responses:
- Pushback on lump-sum commitment fee, with respondents re-running previous arguments that incremental release rewards demonstrable progress and avoids tying up capital that could fund early works.
- Challenges to the quantum of the commitment fee and the reliance on a hypothetical IRR model, with respondents likely referring to international comparators which sit at a fraction of the proposed UK levels.
- Cure periods for failure to achieve milestones and relief where a failure is attributable to the network operators, supply chain delay, or confidentiality provisions in compute offtake agreements.
- Arguments for changes to apply on a forward-looking basis only, taking existing projects out of scope.
Practical Steps for Developers
Developers with projects in the queue should be modelling the fee at both ends of the range against their connection date, confirming whether security can be provided, and reviewing whether their intended commercial model maps cleanly onto the Self-operation or Lease or Sale pathway, bearing in mind that only one pathway change is permitted over the life of the project. On the contracting side, procurement strategy, novation mechanics and certification deliverables should be revisited now, on the assumption that M2.Dc and M6.Dc will land broadly as proposed. Responses to the Consultation are due by 16 September 2026.