Electricity

Grid connections

See where projects stall, how reform is changing queue priority, and what a connection offer actually depends on. This route explains the process first, then shows why queue pressure became the defining delivery problem for clean power.

Network map → Digital infrastructure Back to start

The connection process

Queue pressure is not one event. It is the cumulative effect of development risk, reinforcement lead times, and a process that used to reward speed of entry rather than credibility of delivery. Click any step to see more detail.

Connection process from feasibility through to energisation Six steps across developer, network operator, and regulator swim lanes, from feasibility and application through to reinforcement, testing, and energisation. DEVELOPER NETWORK OP REGULATOR 1. Feasibility and land Submit 2. Apply to right operator Application sent 3. Receive the offer Offer issued 4. Accept and secure milestones Works begin 5. Reinforce and construct BOTTLENECK Complete 6. Test Ofgem reform framework Queue priority and milestone rules Sets rules Regulates timescales Months Months to years 1–15 years Final

1. Feasibility and land

Months to years

Developers test site viability, land rights, planning risk, and likely network routes before a formal application lands.

2. Apply to the right operator

Weeks

Large transmission users deal with NESO and the TOs. Smaller or embedded projects usually begin with the local DNO.

3. Receive the offer

Typical quote window varies

The offer sets technical conditions, indicative works, milestones, and the connection date the project is being asked to build to.

4. Accept and secure milestones

Project dependent

Once accepted, the project enters the contracted queue and has to keep planning, financing, and land milestones credible.

5. Reinforcement and construction

Often the longest phase (1-15 years)

This is where network reinforcement, outages, consents, and contractor availability start to dominate delivery risk. This step is the primary bottleneck in the connections process.

6. Testing and energisation

Final commissioning

Testing, protection, compliance, and final network readiness all have to line up before the connection goes live.

Queue pressure

These figures explain why reform became a central delivery issue. The pipeline dwarfs the system's actual capacity needs.

~700GW
Ready-to-build generation and storage

Verified in the React claims system. This pipeline far exceeds what the physical network can deliver.

~450GW
Demand contracted offers

Demand applications have risen sharply as electrification, data centres, and industrial load growth move into the queue.

Pipeline vs peak demand

~50 GW peak demand
~700 GW pipeline
What GB actually needs at peak What is sitting in the queue (14:1 ratio)
Queue figures are drawn from the React claims system, cross-referenced against NESO and Ofgem published queue data. The 14:1 ratio illustrates scale — not all pipeline capacity will or should be built. ● Verified Mar 2026

The old queue allowed many speculative positions to sit alongside credible projects. The result was a sequence problem. The projects the system most needed were not always the ones nearest the front, and downstream reinforcement plans were being distorted by weak commitment signals.

Connections reform

Reform is trying to move the queue from simple chronological ordering toward readiness, strategic value, and credible delivery.

Milestone discipline

Projects now face stronger pressure to show planning progress, land position, financing maturity, and build credibility.

Strategic filtering

Reform increasingly asks whether a project is aligned to wider delivery goals such as clean power, industrial policy, or network efficiency.

Cleaner reinforcement planning

A more credible queue produces better signals for reinforcement timing, outage coordination, and capital allocation.

Reform timeline

Connections Reform Timeline 2024 2025 2026 2027 2028 2029 Queue mgmt CAP Gen pause Demand pause Reorder TMO4 reranking Enduring reform Phase 2 nodal pricing study Strategic connection hubs Complete Active Planned Today (Mar 2026)
Reform timeline is based on published Ofgem and NESO programme milestones available at review time. ● Verified Mar 2026

Who connects where

A connection is not only a technical question. It is also an organisational routing question. Knowing the likely route helps people understand why a project ends up with a DNO, NESO, or both.

New connection application Project size and system impact? Very large or transmission impact Transmission route Apply to NESO Embedded or local Distribution route Apply to local DNO Unclear boundary or escalation Hybrid route DNO + NESO coordination Governed by Governed by Governed by Governed by CUSC TNUoS charges apply Governed by DCUSA DUoS charges apply Both codes may apply Coordination needed Route determines the governing code, charge type, and which operator leads
Connection-routing wording is tied to current institutional role descriptions rather than a generic transmission-versus-distribution shorthand. ● Verified Mar 2026

Connection costs and market participants

Most frustration comes from two things: not knowing what the quote includes and not knowing which organisation is actually making the decision.

Contestable works

Assets that an accredited provider may build, such as some on-site or near-site civils and electrical works.

Non-contestable works

Works the network company keeps, such as core reinforcement, protection changes, outage management, and final system integration.

Reinforcement exposure

The biggest cost swings usually come from upstream reinforcement, long lead-time plant, and shared network works beyond the site boundary.

Programme risk

Even when quoted costs look manageable, date movement can break project economics faster than the capex line item itself.

Key participants

  • NESO sets the system-level route for transmission applications and wider queue reform.
  • Transmission owners deliver the physical works on their assets and plan outages and reinforcement.
  • DNOs handle most embedded and regional applications, then coordinate if transmission impacts emerge.
  • Ofgem shapes the reform framework and the incentives that sit behind readiness, milestones, and consumer value.

Current position

Queue pressure is not only a volume issue. It is also a sequencing and governance issue about how scarce network capacity, reinforcement effort, and delivery confidence are prioritised. That is why current reform language increasingly centres on projects being ready and needed rather than only earlier in the queue.

Why this matters now

One of the most important costs in the connections process often sits behind the initial quote: reinforcement exposure. A project that appears affordable at first can become materially more expensive when upstream works are triggered. That is why better sequencing, clearer milestones, and stronger coordination across operators matter so much for delivery confidence.

Methodology and sources

Last reviewed: 17 March 2026

This page keeps the React queue viewer and verified queue claims, then follows the HTML route order so the user sees process, pressure, reform, and cost logic in a more teachable sequence.

Source Ofgem connections reform - Programme context and reform publications.
Source NESO connections information - Transmission connections and wider system context.
Source DNO LTDS publications - Regional network capability and development statement context.

Next route

Digital infrastructure

See how the data systems behind the grid actually work — from smart metering to settlement and public APIs.