Cumulative effects chapters and how schemes are selected

The cumulative effects assessment chapter of an environmental statement fails more often on the scheme list than on the technical work. Schedule 4 to the Town and Country Planning (Environmental Impact Assessment) Regulations 2017 requires a description of the cumulation of effects with other existing or approved development, and almost every dispute is about which other development counts, at what date, and on what evidence.

Agree the list in writing before the chapters are written. That one step removes most of the risk.

What cumulative assessment actually covers

Two different things travel under the same name, and conflating them produces a chapter nobody can follow.

The first is cumulative effects between your scheme and other development: your traffic plus the consented scheme next door arriving at the same junction, your construction programme overlapping with theirs on the same haul route, your lighting plus theirs on the same dark corridor.

The second is in-combination effects within your own scheme, where separate topic effects act on the same receptor. A single dwelling experiencing a small noise effect, a small air quality effect and a small visual effect may experience a materially worse outcome than any one chapter reports. That assessment is receptor-led and sits better as a short synthesis chapter than as a matrix.

Both belong in the environmental statement. Say explicitly which one each section is doing.

Selecting the other schemes to include

The accepted approach is a tiered one, and the Planning Inspectorate's advice note on cumulative effects assessment sets out the logic that most English practitioners now follow even for applications that are not nationally significant infrastructure.

Work outwards from a defined zone of influence for each topic rather than one radius for the whole assessment. Traffic cumulation follows the highway network and can extend several kilometres. Noise and dust cumulation are local. Landscape and visual cumulation follow the visual envelope. A single study area applied to every chapter either sweeps in schemes with no shared receptor, or misses the one that matters. Infrastructure capacity is a resource that cumulates in the same way, as set out in utilities capacity evidence for a residential scheme.

Then apply a materiality test and record it. A scheme belongs in the chapter if it shares a receptor or a resource with yours, and if its effect on that receptor could combine with yours in the same period.

Cut-off dates and consented but unbuilt development

Fix a cut-off date for the planning register search, state it in the methodology, and say how later schemes will be handled. Without that, the chapter is open-ended: a new application validated during determination becomes a stick to beat the assessment with.

The usual approach is a cut-off at the start of the assessment, a refresh shortly before submission, and a short addendum if something material is consented between submission and determination. Say that in the chapter. Authorities accept it readily when it is proposed rather than discovered.

Consented but unimplemented permissions are the hard category. Some will never be built, and assessing all of them as if they will produces a worst case that is not realistic. The defensible position is to include them, state the assumption, and run a sensitivity test without the ones that look unlikely to proceed, with reasons that are factual rather than speculative. Implementation dates, discharged conditions and commencement evidence are factual. A view that a developer has lost interest is not.

Where committed development is already embedded in a traffic model's future year growth, say so, or the chapter double counts. That is the single most common technical error in cumulative transport assessment, and it is visible to anyone who reads both the Transport Assessment and the cumulative chapter.

In-combination effects within one scheme

Build this around receptors, not topics. Pick the receptors that appear in more than one chapter, which is usually a handful of dwellings, a school, a watercourse and a designated site, then describe what each experiences across construction and operation.

Set out, for each: the effects reported in each chapter, their timing, whether they overlap, and whether the combination changes the conclusion. Be honest when it does not. A receptor with three minor adverse effects at different times of day over different years has not suffered a major adverse effect, and saying so with reasoning is stronger than inflating it.

Where it does change the conclusion, it usually changes the mitigation. The right response is a commitment on sequencing or working hours rather than a reworded significance category, and that commitment belongs in the mitigation schedule rather than in a reworded table. Where the receptors are people rather than places, the determinants covered in health determinants inside a health impact assessment are a useful cross-check.

Where the chapter becomes unmanageable

Three failure modes recur.

The chapter becomes a catalogue: twenty-five schemes listed with a paragraph each, no receptor analysis, no conclusion that could change anything. Length without assessment.

It becomes a matrix: every scheme crossed with every topic, producing hundreds of cells, most empty. Reviewers cannot use it and consultees distrust it.

Or it becomes stale: the list was fixed early, two of the schemes were refused, one was built, and nobody updated the chapter. That is the version that gets quoted back at the applicant.

The fix in each case is the same. Assess fewer schemes properly, keep the selection criteria visible, and write the chapter as an argument about receptors rather than an inventory of planning references.

Agreeing the list with the authority in advance

Put the proposed cumulative scheme list in the scoping request, with the tier, the planning reference, the status, the distance, the shared receptor and a yes or no on inclusion with a reason. Ask the authority to confirm it in the scoping opinion.

That does three things. It gives you a documented agreement. It surfaces the scheme the case officer knows about and you do not, which is common where a neighbouring authority is determining it. And it forces the conversation about allocated but unapplied-for sites early, while it can still be settled without reworking a chapter.

Where the authority declines to confirm a list, record that you asked and proceed on your stated criteria. A reasoned methodology that the authority had the opportunity to comment on is a far better position at committee than a list that appeared in the environmental statement for the first time.

Keep the cumulative chapter consistent with the rest of the submission. A scheme that is treated as committed development in the transport chapter and ignored in the ecology chapter will be noticed, and the environmental statement for an Environmental Impact Assessment has to read as one document. For the supporting evidence that typically sits alongside it, browse the full set of report types.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. An environmental statement must be prepared by competent experts under the 2017 Regulations, so a PlanScope draft is a starting point for those experts rather than a substitute. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.