QueueWatchby QueueQuant Price my project Get the plan that holds up best for your site, and where that answer flips.
Delays and exits in the transmission queue since 2021How often connection dates move, and how many projects leave the queue. Gate 2 in the transmission queueHow much of the queue has a Gate 2 offer, and what it did to connection dates. The battery queue and CMP470’s commitment feeHow far the battery queue sits above the line that would switch CMP470’s commitment fee off. Changes of customer in the transmission queueHow often connection agreements move between companies, and how those projects fared. Do projects connect on time?How late stages have connected against their connection date in the register. Which connection dates slip least?Which connection dates are pushed back least, allowing for how far ahead they are. Grid outages and the connections due by 2030How many of their planned outages the transmission owners carry out, against the connections due by 2030.

More analyses are on the way.

Delays and exits in the transmission queue since 2021

How often do connection dates move, and how many projects leave the queue? We’ve followed every project in NESO’s TEC register since January 2021 to find out. To see how late projects connect against their connection date, see Do projects connect on time? The figures on this page update with each new register.

Who this page helps, and how

Developers and investors. See how often and how far connection dates like yours have moved, before you plan or value a project.

Data centres waiting for capacity. The Data Centre Covenant plans to give strategic sites the capacity freed when projects leave. See how much has left the queue each year.

Ofgem, NESO and those working on connections reform. See whether projects leave around their trigger date, when their charges and security step up.

The registers behind this page

QueueWatch holds 154 of NESO’s TEC registers, from 29 January 2021 to 16 November 2026: one a month until October 2025, two in November 2025 and twice a week since December 2025. We follow each project from register to register, through NESO’s changes of project ID and site name.

1. How often do connection dates move, and by how much?

In 2025, 17% of projects had their connection date pushed back, by a median of 24 months, and a quarter of those by 36 months or more. In 2021, more connection dates were pushed back (23%), but by less (a median of 13 months). In no year were more than 4% brought forward. Of the 162 projects whose connection date was pushed back in 2026 so far, 73 got the later connection date with their Gate 2 offer.

17%of projects had their connection date pushed back in 2025
24 monthsthe median push-back in 2025

Connection dates pushed back and brought forward

Share of the projects we could compare

Pushed backBrought forward*2026 to 16 Nov

How far the pushed-back connection dates moved

Months

MedianMiddle half of the moves*2026 to 16 Nov
Connection dates moved by year: All technologies
YearProjects comparedPushed backBrought forwardUnchangedPushed back %Brought forward %Median months pushed backLower quartileUpper quartile
202130670523122.91.6131224
2022448110833024.61.8141023
202363488554113.90.8141224
20241,1421843692216.13.2231236
20251,454246211,18716.91.4241236
2026 to 16 Nov1,689162361,4919.62.1191232

What it means: when a connection date is pushed back, it’s usually by a year or more, and the further away a project’s connection date is, the more years there are in which it can be pushed back. A plan or valuation built on a single connection date leaves that risk out.

How we measured it

For each year, we compare each project’s connection date at the start of the year with its connection date at the end (for 2026, on 16 November), so we see how far it moved overall, not each move in between. Only projects that still have MW to connect and a connection date at both points count. If one of a project’s stages connects during the year, we compare the connection dates of the MW still to connect at the end, so a stage connecting doesn’t count as a move. A connection date changes with a project’s Gate 2 offer when it changes in the register that first shows the Gate 2 offer.

2. How much of the queue leaves each year?

The queue held 551.4 GW at the start of 2025, and 10.2 GW of it, 1.8%, left during the year. The highest share since 2021 was 8.6%, in 2023, when most of what left was offshore wind. Counting the 1.6 GW of projects that joined the queue in 2025 and left before the year was out, 11.8 GW left in 2025. Battery storage was the largest part of it, 5.5 GW, and that year 24 battery projects left, against 3 in 2021.

1.8%of the queue at the start of 2025 left during the year
24battery projects left in 2025
Exits byMWProjects

Capacity that left the queue

Still to connect when it left, by technology

StorageSolarOnshore windOffshore windThermalHybridOther*2026 to 16 Nov

Share of the queue that left

Share of the queue at the start of each year that left that year

*2026 to 16 Nov
Exits by year, in MW: All technologies
YearStorageSolarOnshore windOffshore windThermalHybridOtherAllQueue at the start of the yearShare of that queue that left
2021149.7150.0112.54,7803,212.50.008,404.7104,598.17.9%
202255.00.0478.52,0000.00.02,4945,027.5165,012.53.0%
2023258.952.874.919,600299.00.03,61023,895.6241,453.88.6%
20243,860.8707.0282.211,7651,749.94,192.41,50024,057.3432,020.44.6%
20255,481.190.0464.23,000100.01,934.068111,750.3551,364.71.8%
2026 to 16 Nov5,930.00.0162.75000.07,377.03,60017,569.7620,051.82.8%

What it means: only a small share of the queue leaves each year, so a project shouldn’t rely on others dropping out to get an earlier connection.

How we measured it

A project has left when it drops out of NESO’s register for good. One that comes back under the same project number hasn’t left, however long it was missing, and one that NESO renamed, renumbered or listed twice counts as one project. One that comes back under a new number counts as a new project, and the old one as having left, unless it was missing from only one or two registers and came back with the same details or the same NESO project ID. We date each exit to the first register the project is missing from. A project missing from the latest registers could still come back, so this year’s figures may fall as new registers come out. We only count projects with MW still to connect, and the register doesn’t say why a project left. A year’s share is of the queue at the start of the year; what left in a year also counts projects that joined the queue during it. NESO started numbering projects in September 2023. For earlier registers, we follow each project mainly by its name, site and customer, so a few renamed projects may show as exits in the early years.

3. Do projects leave around their trigger date?

Under the current connection rules, holding a place in the queue gets much more expensive at a project’s trigger date, usually three to four years before it’s due to connect. If owners respond to that cost, more of them should leave around it. This chart shows how often projects have left at each distance from their trigger date since January 2021.

2.7left per 100 projects a year around their trigger date
2.7left per 100 projects a year from 1 to 7 years before it
Measured inProjectsMW

When projects left, against their trigger date

Projects that left per 100 in the queue at that distance from their estimated trigger date, per year. The shaded band is around the trigger date.

See the numbersSee less
Projects that left per 100 in the queue, per year, by time from the estimated trigger date: All technologies
Time from the estimated trigger dateProjects that leftProject-years in the queueLeft per 100 in the queue, per year95% range
7 years or more before449864.53.2 to 6.0
78 to 84 months before51473.41.1 to 7.9
72 to 78 months before11820.50.0 to 3.1
66 to 72 months before22320.90.1 to 3.1
60 to 66 months before42241.80.5 to 4.6
54 to 60 months before52472.00.7 to 4.7
48 to 54 months before122175.52.9 to 9.7
42 to 48 months before12410.40.0 to 2.3
36 to 42 months before122085.83.0 to 10.1
30 to 36 months before72323.01.2 to 6.2
24 to 30 months before112254.92.4 to 8.7
18 to 24 months before22590.80.1 to 2.8
12 to 18 months before92513.61.6 to 6.8
6 to 12 months before63111.90.7 to 4.2
0 to 6 months before53011.70.5 to 3.9
0 to 6 months after143324.22.3 to 7.1
6 to 12 months after43001.30.4 to 3.4
12 to 18 months after123053.92.0 to 6.9
18 to 24 months after82663.01.3 to 5.9
24 to 30 months after52512.00.6 to 4.7
30 to 36 months after51882.70.9 to 6.2
3 years or more after84391.80.8 to 3.6

By MW, a range is blank where no project left in the window, as there is nothing to weigh.

What it means: on this data, projects haven’t clearly left more often around their trigger date, when holding a place gets more expensive, than in the years before it.

Read our study: Will CMP470’s commitment fee clear the battery queue?

What is the trigger date, and why is it a band?

Under the current connection rules (CUSC Section 15), a project’s trigger date is when holding its place in the queue starts to cost real money. Until then, a project faces relatively low or no liabilities and securities. From then on, the cancellation charge it would pay to leave, and the security it has to put up against that charge, become substantial.

Trigger dates aren’t published, so we estimate each one from the rule: 1 April, three financial years before the start of the financial year in which the project is due to connect, so usually three to four years before it connects. If a project signs its agreement less than three financial years before it’s due to connect, its trigger date is the day it signs, which we take as the date of the first edition of NESO’s TEC register it appears in. We use each project’s connection date as the register gives it at the time.

Our estimate can be out by a few months, and owners don’t all act on the day itself, so the band takes in the year before the estimated date and the six months after it. Owners know their trigger date from their agreement and may leave ahead of it. After it, the higher security first applies for the six months from the trigger date, so a project that won’t put it up may leave then, and an exit only shows once NESO records it.

Each bar is a rate, not a count, meaning it shows how often projects left, not how many. So a bar of 3 is 3 projects leaving over a year for every 100 in the queue that far from their trigger date. Measured in MW, a bar of 3 is 3 MW leaving over a year for every 100 MW in the queue. Counting exits alone would make a bar high just because more projects were in the queue at that distance. The chart covers generation and storage projects in NESO’s TEC register since January 2021, not interconnectors, and counts a project that NESO renamed, renumbered or listed twice as one project.

NESO’s TEC register, monthly editions from January 2021 to November 2025 and twice-weekly since, as QueueWatch holds them. Supported by National Energy SO Open Data.

What if your connection date is pushed back?

QueueQuant values your project across thousands of possible futures for its connection date and the market, and tells you whether to hold, cut MW, sell or walk away, and what would change that answer.

Price my projectSee use cases

How to cite this page

You’re welcome to quote our figures, charts and findings with this credit:

QueueWatch by QueueQuant, ‘Delays and exits in the transmission queue since 2021’, queuequant.com/queuewatch/delays-and-exits/ (data to 16 November 2026). Contains data from NESO’s TEC register. Supported by National Energy SO Open Data.

Supported by National Energy SO Open Data. Registers from 29 January 2021 to 11 August 2026 are copies NESO released to QueueQuant on 19 October 2026 under the Environmental Information Regulations 2004 (request FOI/26/226). Later registers are QueueWatch’s own downloads from NESO’s Data Portal.

Status definitions (NESO)

Scoping: NESO is not aware that a planning application has been made.

Awaiting Consents: NESO is aware, or the customer has told it, that a planning application has been made.

Consents Approved: NESO is aware, or the customer has told it, that the planning application has been approved.

Terminated: used by NESO only in its register of 30 April 2021, for two projects that left the register the next month.

These statuses are NESO’s, not QueueWatch’s, and NESO describes them as “as far as we are aware”, so a project may be further along than its status shows.

Source: NESO