Writing a non-technical summary anyone can act on
The non-technical summary is required by the EIA Regulations and is the only part of the environmental statement most consultees open. Written as a compressed technical document, it fails both jobs.
A non technical summary planning readers can act on has to do two things at once: satisfy the requirement in the environmental impact assessment regulations that the environmental statement includes a summary of the information in non-technical language, and serve as the document that a parish councillor, a neighbour or a member of a planning committee actually reads during the consultation period.
Most of them fail the second test. They are written last, by the coordinator, by cutting and pasting chapter conclusions, and they read like a compressed technical report rather than an explanation.
Who actually reads the summary
Four groups, with different needs.
Members of the public responding during the publicity period, who have a few weeks and no background in the subject. Parish and town councils, preparing a response in a single meeting. Elected members, reading shortly before a committee. And, more often than authors expect, officers of consultee bodies using it to orient themselves before turning to the relevant chapter.
None of those readers will open a 900 page environmental statement. Several of them will make a decision, or a recommendation, on the summary alone.
That shapes the writing. The reader wants to know what is proposed, what will change for them, how bad it will be, what is being done about it, and what will still be left. In that order, and without having to hold four technical concepts in their head at once.
What the regulations require
The environmental impact assessment regulations require the environmental statement to include a description of the proposed development, a description of the likely effects, a description of the features and measures to avoid or reduce effects, a description of the reasonable alternatives studied, and a non-technical summary of that information.
Three consequences follow.
The summary must cover all of it, including alternatives, which is the part most often dropped. If the statement explains why three site layouts were considered and one chosen, the summary says so.
It must be in non-technical language. That is a legal requirement, not a style preference, and an authority can treat a summary that is not as a deficiency in the statement.
And an environmental statement must be prepared by competent experts. An Environmental Impact Assessment is a report type where a competent professional is legally required under the 2017 regulations, and an AI-assisted draft is a starting point for those experts rather than a substitute for them.
Length, structure and reading level
There is no prescribed length. A proportionate summary for a mid-sized scheme runs to something like 20 to 30 pages including figures. For a large infrastructure project it will be longer, and for a modest scheme it should be much shorter.
A structure that works:
- What is proposed, with a location plan and an illustrative view.
- Why, in a paragraph, without marketing language.
- What alternatives were considered and why this one was selected.
- How the assessment was done, in half a page.
- One short section per topic, each following the same pattern.
- Cumulative effects with other schemes.
- What happens during construction, separated from what happens once complete.
- A table of residual effects.
- How the mitigation will be secured and monitored.
Keep each topic section to the same shape: what is there now, what will change, how bad and for how long, what is being done, what remains. Readers learn the pattern by the third section and can then find what they care about.
Write for someone reading at pace. Short sentences, no acronyms without expansion on first use, no cross-references to chapter numbers the reader does not have, and units explained the first time they appear. Decibels, micrograms per cubic metre and biodiversity units all need a sentence of context.
Summarising conclusions without losing caveats
The hardest editorial judgement is how much qualification to carry across.
Drop too much and the summary misstates the assessment, which is both a professional problem and a reputational one when an objector puts the two documents side by side. Carry too much and the summary becomes unreadable.
The discipline that works is to keep the caveats that change what a reader would do, and drop the ones that do not. A caveat that the noise assessment assumes a particular construction method changes the reader's response, because they will want that method secured by condition. A caveat about the confidence interval on a traffic count does not.
Where a conclusion depends on mitigation being delivered, say so in the same sentence as the conclusion. "With the acoustic barrier in place, the effect is not material" is honest. "The effect is not material" with the barrier mentioned three pages earlier is not.
And do not upgrade conclusions. If a chapter finds a moderate adverse residual effect, the summary says moderate adverse. Softening it is the single most common criticism consultees make of these documents.
Figures that work without the main text
A summary is read by people who will never see the main figures, so its own figures have to be self-contained.
Every figure needs a title that states what it shows, a scale bar, a north point, a legend in plain words rather than codes, and a caption of one or two sentences explaining what the reader should take from it.
Useful figures for a summary: a location plan at a scale that shows the nearest settlements, an illustrative masterplan, a construction phasing plan, one or two verified views from publicly accessible viewpoints, and a constraints plan showing designations. Resist reproducing technical outputs such as noise contour maps unless you can explain the colours in a sentence.
The residual effects table is the most valuable single item. One row per effect, with columns for the receptor, the effect, whether it is temporary or permanent, the significance after mitigation, and where the mitigation is secured. A reader who takes nothing else away should be able to read that table.
Common failings reviewers flag
Six recur often enough to be worth checking for deliberately.
No treatment of alternatives, despite the regulations requiring it.
Construction and operational effects merged, so a reader cannot tell whether an effect lasts eighteen months or forever.
Mitigation described without saying how it will be secured. A commitment that is not in a condition, an obligation or a management plan is a statement of intent.
Cumulative effects omitted or dealt with in two lines, when neighbouring schemes are exactly what local readers want to know about.
Terminology that varies between the summary and the chapters, so that "moderate" in one place is "medium" in another.
And a summary that is out of date because the scheme changed during preparation. It is written first in the programme and finished last, and the reconciliation gets missed.
An illustrative outline for one topic section
Take noise as an example. The structure below is illustrative:
What is there now. Two paragraphs describing the existing sound climate in plain terms, referring to the nearest homes and what people currently hear.
What would change. Construction activity, described by phase and duration, then the operational sources once complete.
How bad, and for how long. The assessment conclusion for each receptor group, in words before numbers, with the numbers given afterwards and explained.
What is being done. The specific measures, each tied to how it will be secured.
What remains. The residual effect, stated in the same terminology as the table.
That pattern is repeated for each topic, which makes the document navigable and makes omissions obvious.
Where the scheme includes commitments on construction management, the detail sits in a separate document such as a construction environmental management plan, and the summary should say so rather than reproducing it. The same applies to consultation, where the Statement of Community Involvement records what was done and what changed as a result.
Publish the summary as its own file, clearly named, and make sure the council uploads it separately rather than as part of a single combined document. A summary buried inside a 60 megabyte file is a summary nobody reads. Check the wider set of supporting documents is presented the same way.
This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it. 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.
Frequently asked questions
Is a non-technical summary legally required?
Yes. The environmental impact assessment regulations require an environmental statement to include a summary in non-technical language of the information it contains, covering the development, the likely effects, the mitigation and the reasonable alternatives studied. A summary written in technical language can be treated as a deficiency in the statement.
How long should it be?
There is no prescribed length. Around 20 to 30 pages including figures suits a mid-sized scheme, longer for major infrastructure and much shorter for a modest proposal. What matters more than length is that each topic follows the same structure so a reader can find what concerns them without reading the whole document.
Does the summary have to cover alternatives?
Yes, and this is the part most often left out. The regulations require a description of the reasonable alternatives studied and the main reasons for the option chosen, and the summary covers the information in the statement. Two or three paragraphs explaining what was considered and why it was rejected is usually enough.
Can conclusions be softened for a public audience?
No. Use the same terminology as the chapters, and report a moderate adverse residual effect as moderate adverse. Objectors read the two documents side by side, and a summary that understates the assessment damages the credibility of the whole environmental statement and gives the authority a reason to question it.
Who should write it?
Someone who can write plainly, working from the chapters, with each topic author checking their own section for accuracy. The environmental statement as a whole must be prepared by competent experts, so the summary should be reviewed by them before issue even where a specialist writer has drafted it.
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.