Reporting consultation responses in an SCI

A Statement of Community Involvement submitted with a planning application has one job: to show the council what you asked, who answered, and what you did about it. The confusion in the name does not help, because every local planning authority also publishes its own statement of community involvement under section 18 of the Planning and Compulsory Purchase Act 2004, setting out how it will consult. That is a policy document about the council's behaviour. Yours is an evidence document about your scheme, and the statement of community involvement responses section is the part officers actually read.

Write it as a record, not as advocacy. A statement that reports 40 objections and explains what changed carries more weight than one reporting warm support nobody recognises.

What the statement has to demonstrate

There is no general statutory duty to consult before submitting an application in England, outside the narrow categories where legislation requires it. The pressure comes from elsewhere: the National Planning Policy Framework encourages early engagement, many local plans expect it for major schemes, and a council's own statement of community involvement will often set expectations that officers then apply.

So the document has to show three things. That the people affected had a real chance to comment before the design was fixed. That what they said was recorded accurately. And that the scheme responded where it could, with reasons where it could not.

A fourth thing is implicit: that the consultation was proportionate. A 12 dwelling infill scheme does not need an exhibition and a website. A 400 unit regeneration scheme in a multilingual area needs more than a leaflet through 30 doors.

Recording who was consulted and how

Set out the audience and the method in a table, with dates and numbers. Numbers you can actually evidence: letters delivered, addresses in the distribution area, attendees at each event, website visits if you ran one, responses received by channel.

Show the distribution boundary on a plan. Officers and objectors both test it, and a consultation area that stops one street short of the most affected houses is the first thing raised at committee.

Reaching groups that do not come to evening meetings takes deliberate effort, and the reasoning is the same as the evidence gathering we describe in evidence for protected characteristics in an equalities impact assessment. Where a scheme affects a school run, a place of worship or an older population, go to them rather than waiting.

Presenting responses without editing them

Report what people said. Group the comments by theme, give the number of respondents raising each theme, and quote a representative comment in the words used. Do not paraphrase objections into something easier to answer, because the objectors will be reading the document and will say so in their consultation response.

Personal data needs care. Publish the substance, not the names, addresses or any identifying detail, and say in the document that responses have been anonymised. Councils publish application documents online, and a schedule listing named residents and their property addresses creates a problem for everyone.

Where a petition is submitted, report the number of signatures and whether it came from within the consultation area. Where a campaign group sent a standard letter, say how many arrived and treat them as the responses they are rather than discounting them.

Showing where the scheme changed

The most useful part of the document is a single table with three columns: what was raised, what changed, and where to see it. Plain language on both sides.

The discipline is to include the rows where nothing changed. "Residents asked for the scheme to be reduced to two storeys. The scheme remains three storeys, because the density required by policy H1 cannot be achieved at two, and the daylight assessment shows the relationship to number 14 is acceptable. See section 6 of the design and access statement." That row is harder to write and it is the one that persuades an officer the exercise was real.

Cross-reference the technical documents by section rather than by title, so a case officer can check the claim in one click. Where a visual change resulted, show the before and after. The before image must be an accurate record of the existing situation, the same discipline that applies to verified views generally.

Handling objections you cannot resolve

Some objections are unanswerable by design change. Loss of a view, the principle of developing an allocated site, the effect on property values, or a preference for a different use. Two of those are not material planning considerations at all, and the statement should say so plainly rather than pretending to address them.

The tone matters. "Loss of a private view is not a material planning consideration, although the effect on outlook from habitable rooms is, and that is assessed in section 5" is accurate and respectful. Dismissing the comment without explanation reads badly when it is quoted back at committee.

Where an objection identifies a real conflict that the scheme cannot solve, say so and set out the balance you are asking the council to strike. Officers write that balance into the report anyway. Better that they take your version as the starting point.

Timing the consultation to influence the design

Consultation that happens after the drawings are finished is a mailing exercise, and everyone involved recognises it. The pattern that works on a larger scheme is two stages: an early session on principles, constraints and options, then a second on the emerging design, with the gap used to actually change something.

Programme it against the planning application, not against the funding deadline. Allow time to revise drawings between the stages, and allow for the possibility that a technical consultee raises something at the same time. Where pre-application advice is being taken from the council in parallel, share the consultation feedback with the case officer as it arrives rather than presenting it as a finished narrative at submission.

Evidence appended and evidence summarised

Keep the main document readable, around a dozen pages for a major scheme, and put the raw material in appendices: the leaflet, the boards, the feedback form, the full anonymised schedule of comments, the attendance records, and photographs of the events.

Two failure modes to avoid. A 4 page summary with no appendices, which the council cannot verify. And a 300 page dump with no analysis, which nobody reads and which hides the very rows the officer needs. The Statement of Community Involvement page sets out the structure of the document, and the report types by category page shows what else typically sits in a major application pack.

One honest observation: consultation rarely changes an objector's mind about the principle of a scheme. What it changes is the quality of the evidence, the detail of the design, and the officer's confidence that the applicant engaged in good faith. All three are worth having.

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