Reconciling Environmental Statement chapters that disagree
Chapters written by different firms from different scheme versions contradict each other. Here is the control system that prevents it and the check to run before submission.
Environmental Statement chapters contradict each other because they are written by different firms working to different programmes from different versions of the scheme. The noise chapter assesses 240 flats, the transport chapter assesses 260, and a consultee notices. Reconciling that before submission is the environmental impact assessment coordinator's job, and the mechanism is a controlled set of shared inputs plus a consistency check that somebody is actually paid to carry out.
It matters legally as well as presentationally. The Town and Country Planning (Environmental Impact Assessment) Regulations 2017 require the statement to describe the likely effects of the development, including the cumulative effects and the interrelationship between them, and a statement whose chapters disagree cannot do that coherently.
Where inconsistencies come from on a multi consultant team
Four causes account for most of them.
The scheme moves. Every design change ripples into chapters that have already been drafted, and the chapter authors hear about it at different times through different people.
The programme is staggered. Ecology survey seasons, noise monitoring windows and traffic count periods do not align, so chapters are written months apart against whatever the scheme was at the time.
Each discipline has its own conventions for significance, sensitivity and magnitude, and each applies its own professional guidance.
And the chapters are written by people who never read each other's work. That one is entirely fixable and almost never fixed.
An Environmental Impact Assessment under the 2017 Regulations has to be prepared by competent experts, which is a reason to coordinate rather than an excuse to leave each specialist to their own chapter.
Shared inputs that must match across chapters
Hold a single controlled source for the inputs every chapter uses, issue it with a version number, and require chapter authors to state which version they used.
| Shared input | Chapters affected | Typical failure |
|---|---|---|
| Development description and parameters | All | Unit numbers or heights differ chapter to chapter |
| Construction programme and phasing | Noise, air quality, traffic, ecology | Different durations assumed |
| Construction vehicle movements | Traffic, noise, air quality, dust | Peak movement figures disagree |
| Earthworks volumes and cut and fill | Traffic, contamination, water, waste | Spoil quantities not reconciled |
| Lighting strategy | Ecology, landscape, amenity | Ecology assumes a dark corridor the lighting design does not provide |
| Drainage design and discharge rate | Water, ecology, landscape | Basin size and location differ from the layout |
| Red line boundary and land take | All | Chapters assessing different sites |
| Assessment year and cumulative scheme list | Traffic, air quality, socio-economics | Different baselines and different cumulative schemes |
The cumulative schemes list deserves particular discipline. Fix a cut-off date, record it, and apply the same list in every chapter. Where one chapter legitimately uses a different list, because a scheme is too distant to be relevant to that topic, say so in the chapter rather than leaving a reader to spot the difference.
Utilities and capacity assumptions behave the same way, and our note on utilities capacity evidence for a residential scheme shows how quickly those figures diverge between documents.
Different study areas for different topics
Not every difference is an error. A noise assessment reasonably works to a few hundred metres, an air quality assessment to the relevant receptors and monitoring sites, a landscape assessment to a radius measured in kilometres, and an ecology assessment to a zone of influence defined by the species present.
The problem is unexplained difference. Each chapter should state its study area, the basis for it, and a figure showing it. A reviewer who can see why the Noise Impact Assessment stops at 300 metres while the Landscape and Visual Impact Assessment extends to 10 kilometres has no complaint to make.
Where study areas overlap, the receptors inside the overlap must be described consistently. A dwelling that is a "noise sensitive receptor" in one chapter and a "residential property" in another, with a different address or reference number, forces the reader to reconcile two lists. Use one receptor register across the statement.
Interrelationship of effects under the 2017 Regulations
The Regulations require the statement to address the interaction between the factors assessed. That is not satisfied by a chapter headed in those terms that restates the conclusions already reached.
What it means in practice is identifying where effects combine on the same receptor. A dwelling experiencing construction noise, dust and night-time lighting at the same time may be more affected than the individual chapter conclusions suggest. A hedgerow losing length to the access while also sitting under a new lighting scheme loses more ecological function than either chapter assesses alone.
Build it as a matrix: receptors down one axis, effects across the other, and a short narrative for each combination that matters. That matrix also finds inconsistencies, because filling it in requires reading every chapter against the same receptor list.
Do it before the chapters are finalised, not after. A matrix compiled at the end can only report the problem.
Mitigation claimed twice
Double-counted mitigation is the inconsistency most likely to cost you something. A landscape bund presented as noise mitigation in one chapter, visual screening in another, and habitat creation in a third, is one earthwork doing three jobs, which is fine only if the design actually delivers all three.
Frequently it does not. A bund planted densely enough to screen views may be the wrong habitat type for the biodiversity calculation. A bund high enough to attenuate noise may be too high for the landscape argument. And an attenuation basin counted as open space provision may not meet the open space standard.
Keep a single mitigation register: the measure, which chapter relies on it, what it has to achieve for each, the mechanism securing it, and who is responsible. Then have the designers confirm that one measure can meet all the stated requirements at once.
Where it cannot, choose. A chapter that quietly relies on performance the design does not deliver will be found out at condition discharge, when the measure has to be built.
The consistency check before submission
Programme two weeks for this and give it to one person who has authority to require changes.
- Check the development description in every chapter against the controlled version, word for word on the parameters.
- Check every quantitative input against the shared input register, with the version recorded.
- Reconcile the receptor register across chapters, including names, addresses and references.
- Reconcile the mitigation register, and flag anything claimed by more than one chapter.
- Check that residual effects tables use the same terminology and the same significance terms.
- Check figures and drawings: same north point, same red line, same scheme layout, same revision.
- Read the chapter conclusions back to back and ask whether a lay reader would see a contradiction.
Keep the check as a written record. Where a consultee later alleges inconsistency, a documented reconciliation exercise is a far better answer than an explanation invented after the event.
Who owns the reconciliation
The applicant does, in law, because the applicant submits the statement. In practice the work falls to the coordinator, and the appointment has to say so.
Three things make the role possible. A contract with each specialist requiring them to use the controlled inputs and to respond to coordination comments within a stated period. A single document controller issuing versions, so nobody works from an email attachment. And enough fee for the coordination itself, which is routinely under-priced because it produces no chapter of its own.
My own view, from watching this go wrong: the cost of two weeks of reconciliation is trivial against the cost of a consultee asking for a further information request under the Regulations, which stops the determination clock and can add months. Browse the report types by category to see which chapters your scheme is likely to pull in before the team is appointed.
PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. For specialist technical reports, qualified professional input may be required, and an Environmental Statement under the 2017 Regulations must be prepared by competent experts rather than drafted and submitted unchecked.
Frequently asked questions
Which inputs have to be identical across Environmental Statement chapters?
The development description and parameters, construction programme and phasing, construction vehicle movements, earthworks volumes, lighting strategy, drainage design and discharge rate, the red line boundary, the assessment year and the cumulative schemes list. Hold them in one controlled register with a version number and require each author to state the version used.
Is it wrong for chapters to use different study areas?
No. Noise, air quality, landscape and ecology properly work to different distances, set by their own methods and by the receptors involved. What causes problems is unexplained difference. Each chapter should state its study area, the basis for it and a figure showing it, so a reviewer can see the reason.
What does the interrelationship of effects requirement actually need?
An assessment of where effects combine on the same receptor, rather than a chapter restating conclusions already reached. Build a matrix of receptors against effects, with a short narrative for each combination that matters, and compile it before the chapters are finalised so it can still change the design.
How do I avoid double-counting mitigation?
Keep a single mitigation register recording each measure, which chapters rely on it, what it must achieve for each, the securing mechanism and who is responsible. Then have the designers confirm one measure can meet all the stated requirements at once. A bund dense enough to screen views may be the wrong habitat for the biodiversity calculation.
Who is responsible for consistency across the statement?
The applicant, because the applicant submits it. In practice the coordinator does the work, which means their appointment has to say so, each specialist's contract has to require use of the controlled inputs, and the fee has to cover coordination that produces no chapter of its own.
Sources and further reading
This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.