The Grid Code is the technical rulebook that the National Energy System Operator (NESO) maintains for the GB transmission system. A generator meets the European Connection Conditions (ECC) for design, the Planning Code (PC) for data and studies, and the Operating Code (OC) once running. Whether a plant is bound depends on its registered capacity, its connection voltage and whether it is embedded in a distribution network.
Short answer: what the GB Grid Code asks of a developer
The GB Grid Code is the technical rulebook for the transmission system of Great Britain. The National Energy System Operator (NESO) maintains it, and the regulator Ofgem approves each change. A generation developer meets it in three places: the European Connection Conditions (ECC) set what the plant must be able to do, the Planning Code (PC) sets what data and studies the developer provides, and the Operating Code (OC) governs the plant once it runs. Compliance is shown through the processes covered in the compliance guide.
The version in force
On 15 November 2026 the latest text was Grid Code Issue 6, Revision 46, dated 8 October 2026. The code is a living document: NESO issues a new revision whenever the regulator approves a modification, and modifications are tracked on the NESO website. Two practical consequences follow:
- Cite the issue and revision in your design basis, with the date.
- Check the modification tracker for proposals that touch your project. Open modifications on topics such as fault ride through can change wording that a design relies on.
The UK series starts at the UK codes overview, which places the Grid Code next to BS 7671 and the ENA documents.
How the code is organised
The Grid Code has a Glossary and Definitions section and then a set of codes. The ones a developer meets most are:
| Code | What it covers |
|---|---|
| Planning Code (PC) | Planning data and information a user supplies to NESO |
| Connection Conditions (CC) | Technical conditions for connections made under the older rules |
| European Connection Conditions (ECC) | Technical conditions that apply to plants under the European-derived generator requirements now kept in GB law |
| Operating Codes (OC) | Operation, outages, events and testing once connected |
| Balancing Codes (BC) | How a user takes part in balancing the system |
| Data Registration Code (DRC) | The registered data a user keeps current |
| Compliance Processes (CP) and European Compliance Processes (ECP) | How a user proves compliance before and after connection |
Which plants meet the ECC
A new plant normally meets the ECC. The classification into Types A, B, C and D follows registered capacity and connection voltage, as set out in the G99 table of the UK overview. Three points matter for a developer:
- Capacity is the sum of the module. All the units of a power park module count together, not each inverter alone.
- Voltage can decide the Type. A plant connected at 110 kV or above is Type D whatever its capacity.
- Embedded plants are still in scope. A plant on a distribution network can be bound by the Grid Code as well as by the distribution rules. The connection offer states which.
The Grid Code also sets how plant with inverters shows its fault ride through, reactive capability and, if offered, grid-forming capability. Each of those topics has its own guide: fault ride through, reactive capability and voltage control and grid-forming requirements.
Worked example: does this plant meet the ECC as Type D?
An illustrative project with assumed values.
- 28 inverters, each rated 4.3 MW.
- One power park module behind a single 33/132 kV transformer station.
- Connection voltage 132 kV.
Step 1, registered capacity of the module: 28 × 4.3 MW = 120.4 MW.
Step 2, test by voltage: 132 kV is above the 110 kV threshold, so the plant is Type D whatever the capacity.
Step 3, test by capacity: 120.4 MW is also well above the 50 MW threshold for Type D quoted in the UK overview, so both tests agree.
A neighbouring case shows why the sum matters. Ten of the same inverters connected at 33 kV give 10 × 4.3 = 43 MW. That is below the 50 MW figure and below 110 kV, so the plant is not Type D by either test, and the lower Types apply instead. Registered capacity is a defined quantity, so use the figure the connection offer records and not a rounded one.
Common misreadings
- Treating the code as one document for one voltage level. The Grid Code covers transmission users and also reaches larger plant inside distribution networks, so a 33 kV project can still be in scope.
- Reading an old revision. A design basis that cites a revision from the start of a development may be several revisions behind by the time the application is made. Re-check the text at each major submission.
- Confusing the code with the offer. The Grid Code sets general rules, and the connection offer sets the conditions for the site. When the two differ in detail, raise it with the network operator before design freeze.
- Leaving data until late. The Planning Code data and the models take time to prepare. Starting them when construction starts leaves the compliance steps on the critical path.
Checklist for the engineer
- Record the Grid Code issue and revision, with the date, in the design basis.
- Compute registered capacity for the whole module and compare it with the Type thresholds.
- Confirm the connection voltage and whether the plant is embedded or directly connected.
- List the ECC clauses that apply: reactive capability, fault ride through, frequency response, and any optional grid-forming capability.
- Read the Planning Code data list and start the model and data package early.
- Identify the compliance steps in the ECP and plan the evidence for each.
- Check the modification tracker for open changes that affect your design.
- Read the connection offer for conditions that go beyond the code.
Related guides
For short-circuit contribution see inverter fault current in solar plants. For voltage quality at the point of connection see IEEE 519 with inverter-based generation. The pre-energisation checks are covered in commissioning tests for solar plants.
From the code to a design your chartered engineer can sign off
A Grid Code compliance plan starts with a clear list of what applies to the plant. We prepare the engineering design and the power-system studies behind a GB connection: single-line diagram, protection and control concept, and the study inputs the code asks for. The package is ready for your chartered engineer to review and sign off before it goes to the network operator. Tiza does not sign or certify designs in the UK. Contact us with the site data and the connection offer.
Frequently asked questions
What is the GB Grid Code in simple terms?
It is the set of technical rules that generators, large users and network owners follow when they connect to, plan around and operate on the GB transmission system. NESO maintains it under its licence, and changes need the approval of the regulator, Ofgem.
Does the Grid Code apply to a solar farm connected to a distribution network?
Often yes, in part. A large embedded plant can still be bound by the Grid Code, and the distribution network operator applies its own Distribution Code and the ENA documents as well. The registered capacity and the voltage decide which requirements apply, so confirm this in the connection offer.
Where do I find the current version of the Grid Code?
On the NESO website, in the Grid Code documents page. The code is revised several times a year, so cite the issue and revision in force on the date of your application. On 15 November 2026 the latest was Issue 6, Revision 46, dated 8 October 2026.