Non technical summaries that officers actually use

The non-technical summary is the only part of an environmental statement most people will ever read, and it is usually written last by whoever has the least time. That shows. A non technical summary of an environmental statement is a required document in its own right, not an executive summary bolted onto a technical report, and its job is to let an interested member of the public understand the proposal, its effects and the mitigation without reading a single technical chapter.

Officers use it too, which is the part consultants underestimate. Text from the summary reappears in committee reports, in consultation letters and in the officer's own description of the scheme, so the sentences you write there travel further than anything else in the submission.

What the summary is required to do

Three functions, and they pull in slightly different directions.

It has to describe the development, in terms a reader can picture: what is proposed, where, how big, how long the construction period is, what it will look like and how it will operate.

It has to report the effects, including the ones that remain after mitigation, without burying them and without overstating them. A reader who finishes the summary should know which effects the assessment found to matter and which it did not.

And it has to work standalone. Someone who has only the summary should not need to open a chapter to follow it, which means no cross references that carry meaning, no undefined abbreviations and no reliance on figures held elsewhere.

That third requirement is the one most often breached. A summary that says the assessment concluded effects would be acceptable subject to the mitigation described in Chapter 9 has failed, because the reader cannot see the mitigation.

The statutory basis for the requirement

The Town and Country Planning (Environmental Impact Assessment) Regulations 2017 set out what an environmental statement must contain, and Schedule 4, which lists the information for inclusion, requires a non-technical summary of that information. It is a regulatory requirement rather than a convention, and an environmental statement without an adequate summary is incomplete.

The same regulations require the environmental statement to be prepared by competent experts. That applies to the summary as much as to the chapters, and it is why an Environmental Impact Assessment is not a document any drafting process can produce unaided. A draft can structure it and marshal the content, and the competent experts still have to verify what it says about their own assessments.

Practical consequence: the summary needs sign-off from every chapter author, not just from the coordinator. A summary sentence that misstates a specialist's conclusion is the specialist's problem at inquiry.

Writing for a reader with no technical background

The test to apply is whether an interested resident with no planning or engineering knowledge could read the document once and explain the scheme to a neighbour.

Five habits get you there:

1. Name things rather than categorising them. Write that the scheme includes 180 homes, a two form entry primary school and a park of 2.4 hectares, rather than that it comprises residential, educational and open space uses.
2. Give every measurement a comparison a reader can hold. A building height in metres means little; the same height expressed alongside the height of the existing building next door means something.
3. Explain any term you cannot avoid, in the sentence where it first appears, then use it consistently.
4. Convert assessment language into consequence. Instead of reporting a moderate adverse effect on the local road network, say what a driver would notice.
5. Say who is affected and when. Construction effects on a particular street for a stated period read very differently from effects described at the level of the study area.

Avoid the temptation to reproduce the significance matrix. Terms such as major, moderate, minor and negligible are internal to the assessment method, and a reader who does not know the method reads them as ordinary English, which they are not.

Length, structure and figures

There is no prescribed length. What matters is that it is short enough to be read in one sitting and complete enough to stand alone, and for most schemes that means a slim document rather than a hundred page condensation.

A structure that works:

• What is proposed, with a location plan and an illustrative view.
• Why it is proposed, and what alternatives were considered.
• How the assessment was carried out, in a page.
• The effects, topic by topic, each with the mitigation and what remains afterwards.
• Effects during construction, separately from effects in operation.
• How effects will be monitored and who is responsible.
• Where to see the full environmental statement and how to comment.

Include figures, and choose them for a lay reader rather than for a technical one. A location plan, a site layout, a section through the site showing relationship to neighbours, and two or three views are worth more than any number of contour plots. Where photomontages are used, the methodology behind them still matters, as our note on photomontage methodology in a landscape and visual assessment explains.

Number the figures and refer to them by number in the text. Readers use captions.

Summarising residual effects honestly

Residual effects are the ones left after mitigation, and they are the reason the document exists.

Report them in a table with one row per topic, stating the effect, the mitigation proposed, what remains and whether the assessment judged it to be adverse or beneficial. Keep the wording of the residual conclusion identical to the wording in the chapter, because any divergence will be found and will be treated as an attempt to soften the finding.

Where an effect is adverse and remains adverse, say so plainly in the summary. Two reasons. Regulators and objectors read the chapters, so concealment does not work. And an assessment that admits a residual adverse effect and explains why the scheme is nonetheless proposed is far more credible than one in which everything is mitigated to nothing.

Where the assessment identified one effect as significant in the regulatory sense, make sure the summary says which one and why, because that is the finding the whole exercise was designed to surface.

How committee reports reuse the summary

Officers write committee reports under time pressure, and a well written summary is the most convenient source of a scheme description they will find. That has two implications worth acting on.

First, the description of development in the summary should match the description on the application form and in the Planning Statement word for word where it can. Where they differ, the officer's report may describe the scheme in terms that do not match the permission eventually granted.

Second, whatever you write about effects will be quoted. A sentence that reads well in isolation is worth more than one that depends on the paragraph before it. Write the summary knowing that individual sentences will be lifted from it.

The summary also feeds public consultation, so keep it consistent with anything said in the Statement of Community Involvement about how the scheme responded to comments.

Common failures that trigger a request to revise

Six patterns account for most of them.

Chapter summaries stapled together, with the register, abbreviations and cross references of the chapters still in place. Undefined terminology, particularly significance vocabulary and shorthand such as receptor and baseline. Missing mitigation, where effects are reported and the measures are left in the chapters. Inconsistency with a chapter conclusion, usually because the chapter was revised after the summary was drafted. No figures, or figures that a lay reader cannot interpret. And a document that is not separately available, so a reader cannot obtain it without downloading the whole statement.

Two process fixes prevent nearly all of this. Draft the summary early, from the chapter scoping, and update it as the chapters land, rather than writing it at the end. And circulate it to every chapter author for confirmation that their conclusions are correctly stated, with a deadline, before the pack is frozen.

One honest observation. A good summary sometimes makes objection easier, because it tells people clearly what the effects will be. That is the point of it, and a scheme that cannot survive its own effects being described plainly has a problem the drafting cannot solve. Our note on environmental zones and obtrusive light limits is an example of the kind of technical detail that has to be translated rather than reproduced.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it.

PlanScope can structure and draft the documents that accompany an environmental statement, and the statement itself must be prepared by competent experts under the 2017 Regulations, with any draft serving as their starting point rather than a substitute. For specialist technical reports, qualified professional input may be required.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.