Statement of community involvement: when councils demand one
The applicant's statement of community involvement is a validation requirement, not a national one. Here is what officers expect the record to show.
A Statement of Community Involvement submitted with a planning application is a record of who you consulted before you applied, what they said, and what changed as a result. It is not the same document as the council's own statement of community involvement, which is the policy document setting out how that authority engages the public in plan making and applications. The one you have been asked for is almost certainly the applicant's version, and it is usually triggered by the local validation list rather than by national law.
When a council asks for one
There is no national requirement to submit a statement of community involvement with an application. The requirement comes from local sources, and there are three of them.
The first is the local validation list, which sets out the documents a particular authority requires for particular types of application. Where the list requires one above a stated scale, an application without it can be held as invalid, which is the practical reason this document matters.
The second is a policy in the adopted local plan asking for pre-application engagement on major schemes. The third is a supplementary planning document setting out how the council expects developers to engage.
Thresholds are local. Common triggers are major applications, schemes above a set number of homes, and proposals in sensitive locations. PlanScope's own report recommendation engine flags a Statement of Community Involvement at 50 or more units, which is a reasonable working assumption, though the council's own validation list takes precedence over any general rule.
Where the requirement sits in national policy
National policy encourages early engagement and says that applications which follow effective pre-application discussion, including with the local community, tend to be dealt with more quickly. It stops short of requiring a document.
That distinction is useful in two directions. If a council asks for a statement where no local requirement exists, you can ask which validation list item it falls under. And if the requirement does exist, national encouragement of early engagement means it is worth doing properly rather than treating it as paperwork.
For most major schemes the honest answer is that consultation pays for itself. Objections that arrive during the statutory 21 day publicity period are harder to deal with than concerns raised months earlier when the layout could still move.
What officers look for in the consultation record
Officers read these statements looking for evidence, proportionality and honesty.
- Who was consulted, defined by an area or a list, with a map where a leaflet drop was used.
- When each activity happened, with dates rather than a general period.
- How many people responded, through which channels.
- What they said, grouped by theme, including the criticism.
- What changed in the scheme as a result, referenced to drawing numbers.
- What did not change, and the reason.
The last two are the ones that carry weight. A statement that records forty responses and reports no change to the scheme reads as a presentation exercise. A statement that shows the parking layout was revised after feedback, with the before and after drawings referenced, demonstrates that consultation had an effect.
Proportionality matters too. A 60 home scheme does not need the engagement programme of a new settlement, and an over-produced document on a modest application can read as marketing rather than evidence.
Leaflet drops, exhibitions and online consultation evidence
Keep the raw material as you go, because reconstructing it afterwards is painful.
| Activity | Evidence to retain |
|---|---|
| Leaflet drop | The leaflet itself, the distribution area map, the date and the numbers |
| Public exhibition | Boards as displayed, venue, dates, attendance count, feedback forms |
| Online consultation | Screenshots of the site, dates live, visit numbers, response summary |
| Meetings with the parish or residents group | Date, attendees by organisation, notes agreed with the group |
| Statutory and technical bodies | Correspondence with dates and reference numbers |
Anonymise individual respondents. Publishing names, addresses or the text of individual letters in a submitted document raises data protection problems and adds nothing to the planning case. Report themes and counts, not identities.
Where the consultation ran online, be straightforward about reach. A page with a small number of visitors is still evidence, and stating the figure honestly is better than implying a wider engagement than took place.
How objections get answered in the statement
Group the responses into themes, then take each theme in turn: what was raised, how many raised it, what the scheme now does about it, and where that is shown.
Do not argue with the respondents in the document. The statement is a record, not a rebuttal. Where a concern cannot be met, say so plainly and give the reason, whether that is a policy requirement, a technical constraint or a site limitation. Officers find a candid explanation more persuasive than a paragraph explaining why the objectors misunderstood.
Illustrative example: consultation on a 70 home scheme produces 43 responses, of which 28 raise traffic on the village lane and 19 raise the loss of a hedgerow. The layout is revised to retain the hedgerow with a 6 m buffer, and the developer commissions additional traffic counts and offers a junction improvement. Both changes are shown against drawing numbers in the statement, and the traffic evidence is cross-referenced to the transport assessment. The scenario is illustrative.
Drafting the document and getting it reviewed
Keep it short and structured. A workable statement runs to a dozen pages plus appendices: purpose and scope, the engagement programme with dates, the methods used, the responses received by theme, the resulting changes, and the appendices holding the leaflet, the boards and the feedback summary.
Ask the case officer to look at a draft before you submit. Many will, particularly where a pre-application enquiry is already running, and a five minute comment on whether the engagement was proportionate is worth more than another exhibition. Where the council has adopted guidance on developer engagement, cross-reference your programme to it section by section, because that is how the officer will check it.
One caution about timing. Consultation carried out a year before submission ages badly, especially where the scheme has changed in the interval, and officers will ask whether the people consulted have seen what is actually being applied for. A short update round shortly before submission usually answers that.
Write it while the consultation is happening rather than at the end. The document is far more accurate when the notes are fresh, and it forces you to notice what is changing in the scheme as it changes.
PlanScope can draft a Statement of Community Involvement around your engagement record and flag where evidence is still missing, and the full list of report types shows what else a major application typically requires. Before submitting, check the current validation list and the fee position, which our note on working out what you owe covers, and cite the local plan policy on engagement using the approach in our guide to local plan policy references.
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.
Frequently asked questions
Is a Statement of Community Involvement required by law?
Not nationally for planning applications. The requirement comes from the council's local validation list, an adopted local plan policy on pre-application engagement, or supplementary guidance. Where it is on the validation list, an application submitted without it can be held invalid, which is why the document matters in practice.
How is it different from the council's own statement of community involvement?
The council's version is a policy document setting out how that authority involves the public in plan making and in deciding applications. The applicant's version is a record of the consultation carried out before submitting a specific application. They share a name and serve entirely different purposes, which causes regular confusion.
At what scale do councils usually ask for one?
Thresholds are local, and commonly attach to major applications or schemes above a set number of homes. A working assumption of 50 or more units is reasonable for a residential scheme, but the council's own validation list is what decides it, so check the current version on the website before you plan the engagement.
What do officers actually look for in the document?
Evidence and honesty. Who was consulted and where, when each activity happened, how many responded, what they said including the criticism, what changed in the scheme with drawing references, and what did not change with the reason. A statement recording responses but no scheme changes reads as a presentation exercise.
Should I name the people who responded?
No. Anonymise respondents and report themes and counts rather than identities. Publishing names, addresses or individual letters raises data protection problems and adds nothing to the planning case. Retain the underlying material yourself, and present grouped analysis in the submitted document.
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.