The feedback log in a statement of community involvement

The feedback log in a statement of community involvement is the table that records what people said about a scheme and what the applicant did about it. It is the only part of the document a case officer reads closely, because the rest describes process and the log describes outcome. On schemes of 50 or more units, where most authorities expect pre-application engagement as a matter of course, a thin log is a visible weakness.

The log is evidence, not a courtesy. It demonstrates that the engagement had a purpose and that the scheme in front of the officer is the scheme the engagement produced.

What the statement is evidencing

A Statement of Community Involvement does three jobs. It shows that engagement took place and who it reached. It records what was said, accurately and without filtering. And it shows the causal link between what was said and what changed.

Only the third matters to the decision. Attendance figures and leaflet numbers establish reach, which is a precondition rather than a conclusion. An officer writing a committee report wants to be able to say that a specific concern was raised and that the scheme responded, because that sentence answers objectors who say they were ignored.

So structure the whole document around the log rather than appending the log to a narrative. Put reach and method first, briefly, then the log, then the issues that did not change the scheme with reasons.

Recording methods, reach and response rates

Record methods and reach factually, with numbers, and resist presenting them as achievement.

What to record for each activity: what it was, when it ran, how it was publicised, how many people were notified, how many attended or responded, and what material was available. A public exhibition over two days with a leaflet to 1,400 addresses and 86 attendees is a fact. A statement describing strong local interest is not.

Three things improve the credibility of this section:

• Give the geographic extent of the notification, with a plan showing the area leafletted.
• Record the digital reach separately, including website visits and online form responses, and be honest where the numbers are low.
• Record who was consulted beyond residents: the parish or town council, ward members, local amenity and civic societies, the school, the surgery, and local businesses.

Response rates on residential consultations are commonly low, and an honest low figure reported plainly is better than an inflated one. Officers see enough of these to know the usual range.

Categorising the issues raised

Raw comments are unusable. Categorise them, count them, and keep the original wording available in an appendix.

Use planning categories rather than topic labels, because the officer's report is structured that way: highways and parking, drainage and flooding, design and height, amenity and overlooking, trees and landscape, infrastructure capacity, construction impacts, affordable housing and mix, and ecology. Then a residual category for matters outside planning control, which should be named rather than hidden.

Count the comments in each category and show them in a short table with the number and the percentage of respondents raising each. That table tells the officer where the pressure is, and it usually matches the objection pattern once the application is publicised, which makes the rest of the document more credible.

Keep immaterial matters in the log rather than removing them. Property values, competition, the identity of the developer and private rights all come up, and recording them while explaining that they are not planning matters shows the log is complete.

Showing which issues changed the scheme

This is the section that earns the document its place. For each change, give four pieces of information: the issue as raised, the number of respondents raising it, the change made, and where in the submitted drawings that change can be seen.

A worked illustration, with the detail chosen to show the format. Residents raised the three storey element on the eastern boundary as overbearing on rear gardens. Eleven respondents. The eastern block was reduced to two storeys over its northern 18 m and the top floor set back 2 m elsewhere. Drawings 102 revision C and 205 revision B.

That level of specificity does two things. It lets an officer verify the change rather than take it on trust. And it makes the change part of the planning case rather than a courtesy, which matters if the application goes to committee and members ask what the engagement achieved.

Changes do not have to be large. A relocated bin store, a repositioned pedestrian link, a retained hedgerow and a revised construction access are all real responses, and a log of several modest changes reads better than a claim of a fundamental redesign.

Explaining issues that did not change the scheme

Most issues raised will not change the scheme, and the log has to say so and why. Omitting them is the error that makes a statement look like marketing.

Four honest reasons, each of which is acceptable when stated plainly:

1. The issue is not a material planning consideration, such as an effect on property values.
2. The scheme already addresses it, and the explanation says where in the submission.
3. The change requested conflicts with a policy requirement or a consultee's position, such as reducing density below the plan's expectation or removing an access the highway authority requires.
4. The change is not deliverable, with the constraint stated rather than asserted.

Write these as short, specific paragraphs. A single line saying a concern was considered and could not be accommodated is worse than nothing, because it tells the reader the log was written to be filed.

Where the issue relates to infrastructure capacity, point to the evidence that answers it, such as the material covered in utilities capacity evidence for a residential scheme.

Hard to reach groups and the equalities angle

Open public events reach a self-selecting group, usually older, usually resident, usually with time. On a scheme of 50 or more units the population affected is wider than that.

Record what was done to reach beyond the usual audience: sessions at different times including evenings and weekends, material in plain language and in other languages where the local population requires it, direct approaches to a school, a youth group, a faith organisation or a care setting, accessible venues, and an online route for people who will not attend a meeting.

Then record what those groups said, separately, because their concerns usually differ. Younger respondents raise affordability and transport. Families raise play space, school places and safe routes. Older residents raise construction disruption and parking. Disabled residents raise step-free routes and parking bays.

This connects directly to the equalities evidence, since the public sector equality duty applies to the authority's decision, and access and inclusion in an equalities impact assessment sets out how that material is presented.

Where a thin log damages the application

Three concrete consequences follow from a weak log, and all of them are avoidable.

The officer's report has nothing to cite. Where objectors say the developer did not listen, a report with no evidence to the contrary leaves the point standing, and at committee that becomes the narrative.

The parish council and ward members treat the engagement as a formality. Once that view forms it is difficult to shift, and a parish that feels managed rather than consulted objects in stronger terms.

And the scheme loses the benefit of changes it actually made. Applicants frequently make real design responses and then fail to record them, so the officer never knows the earlier scheme existed. That is the most common and the most wasteful failure in these documents.

Keep the log from the first meeting rather than reconstructing it before submission. A contemporaneous log takes minutes to maintain and cannot be written convincingly from memory six months later.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. Browse all 66 PlanScope report types and start a draft.