Generation & Storage Connection Queue

Overview

This page tracks the TEC (Transmission Entry Capacity) register connection queue — generation and storage projects that have applied for, or hold, a transmission connection agreement, but aren't necessarily built or operating yet. For already-connected assets, see the Generation & Storage Asset Registry.

Just over half of all queued MW can't be placed on either map below. The TEC register records each project's connection site as a free-text name (e.g. "Bramley 132/33kV BSP"), not a grid reference. We resolve that name to a physical location by matching it against several independent reference sources in order: first a national directory of grid connection points, then NESO's own transmission planning report, and finally open mapping data for major power stations. Around 48% of queued MW resolves this way — most of it (27%) on the first, most direct name match.

The remaining ~52% is disproportionately early-stage: 90% of that unmatched MW is still at the Scoping stage. That's consistent with, though doesn't prove, an explanation where these projects connect to new or planned infrastructure that none of the three sources lists yet. Since neither a GSP area nor an SSEP zone can be assigned to them, they aren't shown on either map below.

Reading the two maps: the GSP area map shows each project's capacity against the single GSP area assigned during that name-matching step above. The SSEP zone map re-aggregates those GSP areas up to zone level. Where a GSP area's boundary overlaps more than one zone, its capacity is split across those zones in proportion to the overlapping area, rather than double-counted in every zone it touches. The zone map covers onshore zones only. Areas shown in grey have no queued capacity at the selected status — they aren't excluded from the data, they simply have nothing to show at that filter.

What the maps are adding up: each project's connection agreement can contribute in more than one way — capacity already built and energised, capacity still awaiting construction, or capacity accumulated as a running total for the whole connection site. The maps below sum only the capacity each agreement adds or removes at its current status, not the site's running total. They reflect queued capacity, not what's already energised.

Individual projects

The two maps total capacity across every project in a GSP area or zone. The table below breaks that total back down into the named projects behind it, filtered to the status you picked above. Find a specific project by its name, applicant, or connection site using the search box.

Capacity (MW) matches what the maps show — each project's own contribution at its current status, not its site's running total. Running site total (MW) is that separate cumulative figure the maps deliberately exclude (see "What the maps are adding up" above); it's shown here so you can trace a project's full connection history without leaving the page.

Data sources

• Connection queue projects: NESO's Transmission Entry Capacity (TEC) register, which lists generation and storage projects that have applied for, or hold, a transmission connection agreement, along with their applicant, connection site, technology, status, and contracted capacity.
• Zone/GSP area attribution: each project's connection site is recorded in the TEC register as a free-text name, not a geographic reference. We match it to a physical grid location using three name-matching sources in order — a national directory of grid connection points, NESO's transmission planning report, and open mapping data for major power stations. Around 52% of queued MW isn't matched by any of the three; 90% of that unmatched capacity is still at the Scoping stage, consistent with, though not proof of, projects connecting to new or planned infrastructure not yet listed anywhere. Where a GSP area overlaps multiple SSEP zones, its capacity is split proportionally by geographic overlap for the zone map only. The GSP area map shows each project's capacity against a single area, unweighted.
• Already-connected assets are excluded from this queue — see the Generation & Storage Asset Registry for what's already built and operating.