GB Grid Connection Queue Tracker: TEC and DNO Changes

See every move in Great Britain's grid connection queue: new projects, capacity changes, connection dates that slip or jump, status and Gate changes, and withdrawals.

The transmission (TEC) register and the distribution networks' Embedded Capacity Registers come back in one schema, so a battery project in the TEC register and a solar farm on a DNO register look the same to your code. Each change carries the values before and after. Change history on the longest-running registers goes back to September 2023.

Run it with the default input: 10 recent changes.

Who uses it

• Battery, solar and wind developers watch the substations they care about and see the day a rival's connection date moves ahead of theirs.
• Grid consultants track queue position and Gate status for clients without diffing register downloads twice a week.
• Land agents see which projects near their clients hold a connection offer, and when it changes.
• Investors and analysts count queued, connected and withdrawn MW by technology, grid supply point, planning authority or licence area, month by month.

Input

Field	What it does
mode	changes (default), snapshot (the current pipeline) or report (monthly totals)
since	Changes published since a date, YYYY-MM-DD. Empty means the last 31 days
sinceLastRun	true returns only changes newer than your last run. Best for schedules
changeTypes	new, capacity_changed, connection_date_moved, status_changed, gate_changed, withdrawn
sources	Pick registers: neso_tec, neso_interconnector, neso_embedded, npg_ecr, ssen_ecr
technologies, minMw	e.g. battery, solar, wind_onshore; minimum headline MW
gate, licenceAreas, statuses	Gate 1 or 2 (TEC), licence areas such as SSEN-SHEPD, project status
month, groupBy, scope	For report: month, grouping (technology, gsp, lpa, licence_area) and transmission, distribution or all
maxItems	Caps the rows, and so the cost

Output

Each change carries change_type, change_date, source, project_name, customer_name, technology, mw, status, licence_area, gsp, postcode_district, lpa, before, after, project_id and data_as_of. Pipeline rows add connection_date, gate, substation, MW import, export and storage figures, a planning reference where one matches, and coordinates where the register gives a location.

A real change from a DNO register, August 2026, trimmed:

{
  "change_type": "connection_date_moved",
  "change_date": "2026-08-07",
  "source": "ssen_ecr",
  "project_name": "CLACHAIG WIND FARM",
  "customer_name": "RWE RENEWABLES UK ONSHORE WIND LTD",
  "technology": "wind_onshore",
  "mw": 52.8,
  "licence_area": "SSEN-SHEPD",
  "gsp": "Carradale",
  "before": { "connection_date": "2026-04-30" },
  "after": { "connection_date": "2028-09-29" },
  "data_as_of": "2026-10-06"
}

A report row gives projects and MW by status for one group, such as all battery projects.

Pricing

Pay per result. See the Pricing tab for current rates; maxItems caps the rows and so the cost. A run that finds nothing charges nothing per item.

FAQ

Which registers does it cover? The transmission TEC, interconnector and embedded registers, plus the distribution registers for the UK Power Networks, SP Energy Networks, Electricity North West, Northern Powergrid and SSEN areas.

How fresh is it? The transmission registers update twice a week and the DNO registers monthly. The actor checks every source daily, and new releases reach it within about 6 hours.

Is a moved connection date a forecast? No. It is what the register published. The actor reports the change, not whether the project will connect.

Built on open data used under each publisher's open licence, including CC BY 4.0 and the Open Government Licence v3.0. Every run carries the full attribution in OUTPUT_SUMMARY. Runs record anonymous usage counts only, never your inputs or results.