Will commitment fees really solve the grid connection queue?

Elliott Meighan, Energy Solutions Consultant at Equity Energies, examines whether Ofgem’s proposed reforms to the data centre connection queue could inadvertently disadvantage smaller, credible developers.

Ofgem has opened a consultation on a proposed Data Centre Commitment Fee (DCCF) and a set of ‘readiness’ milestones for data centres applying for a grid connection. The principle behind the proposal is to help sort serious developers from speculative ones, freeing up precious capacity in the grid connection queue for those projects that will actually get built.

From everything Ofgem has shared about the scale of the problem, this feels – in principle, at least – like a constructive approach. The connection queue has increased from 41 GW to 125 GW in only a few months, such has been the increase in demand from planned data centre projects across the UK. Ofgem’s goal is to create a mechanism that distinguishes genuine, viable projects from what is essentially ‘capacity hoarding’, where connections are effectively reserved by projects that ultimately never come to fruition.

However, the immediate worry is that the proposals have the potential to create challenges for the very developers they should be championing. Right now, the proposals remain subject to consultation, which is open until September 16, so the final design and implementation may differ from the current draft.

What does readiness mean within the current proposals? 

Alongside the commitment fee, Ofgem has set out a series of data centre-specific milestones, based on financial capability, technical capability, commercial maturity, procurement activity and a credible commercial arrangement with an offtaker or certificate of intended self-usage. While these have yet to be finalised, they all indicate a clear requirement: developers will need to continually prove their project is real and progressing to hold their connection place.

In practice, the proposed milestones would require developers to demonstrate that a project is progressing beyond an initial connection request, including through evidence of the technical due diligence behind it, for a Distribution Network Operator (DNO) or NESO engineer to deem it a real scheme and not a placeholder. This would likely also mean there has been an ongoing, documented dialogue between the developer and the network operator from the point of application onwards; offtake secured through a signed agreement or, at a minimum, a binding letter of intent from a named end-user; and procurement progress evidenced by orders placed and/or signed framework agreements for long-lead items.

I would suggest offtake is perhaps the biggest identifiable gap across the current queue; plenty of speculative schemes exist, but how many can prove they have a committed customer for their services?

Could the proposed design be a disadvantage to smaller, credible developers?

The readiness test feels like a better differentiator than the fee proposal on its own, but it could still have a more significant impact on smaller operators than larger ones. The issue may be less about the presence of a fee requirement itself and more about how it is structured.

First, there isn’t any phasing of the fee within the current proposal. Ofgem has indicated that it doesn’t favour an incremental version of the DCCF, so effectively the full fee would be due on acceptance of the connection offer, before the developer has had an opportunity to demonstrate anything. But a fee that scaled alongside demonstrable milestone progress would, in my view, allow a smaller and leaner project to build up security as it builds up evidence. As the proposal stands, it rewards whoever has the biggest credit facility at the point of offer acceptance, rather than whoever can prove the most progress over time.

Secondly, the way the fee is calculated uses a standardised capex assumption of £9.5m per MW, applied across the board. Smaller, leaner projects with lower actual costs need to pay the same rate per megawatt as a hyperscale one. Basing the fee on actual, independently verified project costs instead of a sector-wide assumption would better reflect the range of project sizes in the queue.

And third, there may also be a specific impact on developers whose model is to secure a connection, build the site and sell it on to an operator or hyperscaler on completion, instead of operating it themselves. The DCCF needs to be posted within a limited window once the connection offer is accepted, which is often the point at which a sale or funding arrangement might not have been finalised. This presents a timing issue; that is arguably an additional disadvantage, alongside the need to pay the fee.

On top of this, the need to keep evidencing milestone progress is going to take resources: to assemble the technical and commercial evidence, keep it updated and respond to any challenges along the way. A hyperscaler may find it easier to assign a dedicated team to the task, while a smaller developer could be faced with the need to build the capability in-house or contract it in, either of which comes with a cost. While readiness itself may not remove the scale advantage, it does change what the scale advantage is being spent on.

What should the sector be pushing for during the consultation period?

The sector has until September 16 to engage with Ofgem. The four areas I believe are worth pressing on are:

• A milestone-linked release of the security deposit. Instead of posting the full amount upfront, allow it to be phased in as progress is demonstrated. This single design change could do more for genuine mid-tier developers than any adjustment to the fee level, and it’s also a more precise and defensible criticism than the argument that the fee simply favours the wealthy. Ofgem could address this without undermining the purpose of the reform.
• Make the cost basis behind the fee reflect actual project economics rather than a universal assumption. Using project-specific or independently verified costs would support smaller and leaner developers and their projects.
• A clear, proportionate remedy period for milestone failure. The consultation flags uncertainty over what happens when a project doesn’t meet readiness requirements and what a fair appeals process looks like. If losing the queue slot means forfeiting the fee, developers need to know the consequences before they commit.
• Greater scrutiny of the threshold design. Ofgem is consulting on whether the commitment fee applies above a 10 MW IT load or 40 MW import capacity threshold. That is not necessarily bad for smaller developers, but it could create an incentive for larger operators to structure projects just under the line or split one large scheme into several smaller connection applications. If the threshold is set too cleanly, it could become an exploitable loophole.

The principle behind Ofgem’s reform – to sort the queue by readiness rather than by who got there first – is a better system for the sector and for the grid. But the question remains as to whether the current design delivers on that principle for all genuine developers, or if it prioritises those with the greatest financial backing. The consultation window is still open, so there’s time to shape a version of the proposal that rewards progress, regardless of scale.