The DESNZ Post-Consent Unit creates a new coordination question for nuclear and electricity transmission projects: how will the team demonstrate that each relevant DCO requirement has been addressed?
Check the Post-Consent Unit’s scope first
DESNZ published its guidance on 27 October 2026. It says the Post-Consent Unit will become operational in November 2026, initially covering nuclear and electricity transmission DCOs. The document does not specify the operational day.
The relevant DCO determines which requirements the unit discharges. Requirements assigned to statutory bodies and agreed exceptions remain distinct. Therefore, check the actual consent rather than assuming every energy development or planning condition follows this route.
The guidance also distinguishes administrative validation from technical assessment. A validated application is not confirmation that the requirement can be discharged. Monitoring and enforcement continue with local planning authorities under the arrangements described.
Turn the consent into an evidence register
Start with a controlled copy of the consent and the documents it references. Ask the planning lead to identify each requirement, its trigger and the responsible approving body. Then give the technical authors a clear question to answer.
The following original register structure helps coordinate that work. It is a project-management aid, not the official application form or a substitute for the DCO.
| Field | What the team should record |
|---|---|
| Requirement and trigger | Exact requirement reference, relevant wording and the project activity it controls. |
| Responsibility | Approving body, technical author, coordinator and relevant consultees. |
| Evidence | Report or plan title, drawing number, revision, date and precise supporting section. |
| Open actions | Unresolved question, owner, dependency and required response date. |
| Decision and handover | Decision reference, conditions, approved document set and receiving delivery team. |
First, separate the requirement’s wording from the team’s interpretation. Keep the original text available and record who resolves a scope question. This avoids a shortened action description quietly becoming the only instruction.
Next, identify dependencies between disciplines. An ecology plan, drainage drawing and construction method may describe the same area. Ask their authors to reconcile conflicting assumptions before the coordinator marks the package ready.
Make the document set easy to review
A reviewer should be able to follow a requirement to the evidence without guessing which attachment is current. Use stable names, clear revision histories and a short explanation of material changes. Check links from the receiving team’s perspective.
Also distinguish an outstanding consultation question from an agreed technical position. Record the response, author and resulting change. Where an issue remains open, retain it in the action schedule rather than hiding it in a later report revision.
- Each requirement has a named coordinator and technical author.
- The register points to exact evidence, not a general folder.
- Drawings and reports use consistent site and phase references.
- Changes identify the assumptions that need another specialist review.
- The submission set contains the agreed current versions.
For the wider evidence programme, see ACP’s environmental impact assessment service. Keep post-consent delivery separate from the earlier EIA screening and scoping questions.
Keep approval connected to delivery
A decision has practical consequences for the construction and management teams. Therefore, identify who receives the approved documents and who checks changes against them. Include the decision reference in the handover, together with any remaining hold points.
A fictional phase handover
A team prepares an environmental management package for one work phase. Before issue, the coordinator finds that the ecology plan refers to an earlier access layout. The authors reconcile the files and record the change. After the relevant decision, the contractor receives that coordinated issue set. This example describes information control, not an approved method or a real ACP project.
Where biodiversity requirements are relevant, use the NSIP BNG application and delivery guide as supporting context. Check the project’s actual obligations with the appointed specialists.
Common questions
Does the Post-Consent Unit cover every energy project?
The published initial scope is nuclear and electricity transmission DCOs. Read the relevant consent and current guidance before allocating an application to this route.
Is this the same as obtaining development consent?
No. This article concerns evidence for relevant requirements after consent. Keep the earlier consent decision and subsequent discharge actions clearly identified.
Can a checklist guarantee discharge?
No. A register helps authors organise evidence and resolve gaps. The approving body must consider the relevant requirement and submitted information.
Reference and scope
DESNZ. Guidance on the discharge of requirements for nuclear and electricity transmission Development Consent Orders. Published 27 October 2026; accessed 2 November 2026. Sections 1–2 explain scope; section 7 distinguishes validation; section 10 addresses monitoring and enforcement.
This is an original environmental evidence-coordination guide for relevant DCO projects. It is not legal advice, a statement of UK-wide planning rules or the official discharge checklist. The consent, current authority instructions and project jurisdiction control the route.
Build a traceable environmental evidence package
Discuss your project’s evidence requirements with ACP. Share the consent reference, relevant requirement, phase and current document register.