The feedback section of a community involvement statement

The feedback section is the part of an applicant's statement of community involvement that officers actually read closely. The methods section tells them what you did. The feedback section tells them what people said and what you did about it, and that is the material a case officer can quote in a committee report.

One clarification first, because the term does double duty. A local planning authority has its own statement of community involvement, adopted under section 18 of the Planning and Compulsory Purchase Act 2004, setting out how it will involve the community in plan-making and in decisions. The document discussed here is different: the applicant's own account of pre-application engagement, submitted with a major application because the council's validation list or its adopted policy asks for one.

What the section is assessed on

Officers are looking for three things, and a section that supplies all three rarely attracts criticism.

Whether the consultation reached the people it should have reached, which the methods section establishes and the feedback section demonstrates through the profile of who responded. Whether the responses have been reported accurately rather than filtered. And whether the scheme changed in response, or whether the applicant has explained why it did not.

The third of those carries the most weight. A consultation that produced no change at all invites the conclusion that it was presentational, and officers are direct about saying so in committee reports.

Summarising responses without editing them

The summary should group responses by theme, report each theme in the words respondents used, and give a sense of how frequently each arose. Themes that recur on most schemes include height and massing, overlooking and privacy, parking pressure, traffic and access, construction disruption, loss of a view, drainage and flooding, and the mix of uses proposed.

Two rules keep the section credible.

Report the uncomfortable themes as prominently as the supportive ones. A summary that devotes four paragraphs to positive comments about the landscape strategy and one line to sustained objection on height will be read as advocacy, and the officer will go to the raw feedback forms.

Use the respondents' own framing. If people said the building would "loom over" the terrace behind, report that, then translate it into the planning issue behind it. Sanitising the language into "concerns regarding massing were noted" loses the information that made the comment useful.

Where a comment falls outside planning control, say so plainly and say why. Loss of property value and disruption during construction are the usual examples, and readers deserve a straight explanation rather than silence.

Showing what changed and what did not

The clearest format is a table that pairs each theme with the response, and it is worth building even where the rest of the document is prose.

That last row is the one to get right. Where a request has not been accepted, give the reason in a sentence or two: the scheme would not be viable, the density is needed to meet the site allocation, the daylight testing showed no material difference, the highway authority objected to the alternative. A refusal to move, explained, reads better than an unexplained silence.

Cross-reference the changes to the drawings and to the design and access statement, with drawing numbers, so that an officer can verify that the change described actually appears in the submitted scheme. Descriptions of changes that the drawings do not show are found, and they damage everything else in the document.

Quantifying responses fairly

Numbers in a consultation report need care, because they are easy to present in a way that flatters.

State the method and the population: how many properties received a leaflet, how many people attended each event, how many feedback forms were returned, how many online responses were received, and over what period. Report the response rate alongside the raw count.

Avoid inferring support from attendance. People who came to an exhibition and said nothing are not supporters, and describing them that way is the single most common overstatement in these documents. Equally, avoid reporting percentages calculated on a small base without giving the base.

Where feedback forms used a scale, report the distribution rather than a single headline. And where the same household submitted several responses, say how duplicates were treated.

Honesty here has a practical payoff. Objectors frequently produce their own count, and a discrepancy between their figure and yours is an easy point for them to make at committee.

Handling organised objection campaigns

Campaigns are a normal part of the process and should be reported as what they are, without disparagement. Record the number of identical or near-identical responses, note that they were part of a coordinated campaign, and address the substance of what they say.

The substance is what matters. The number of objections is not itself a material consideration, and officers will say so in the report, but the planning issues raised are material however many people raise them. A campaign that focuses on highway safety at a junction deserves the same analysis as an individual letter making the same point.

Resist the temptation to characterise the campaign or its organisers. It reads badly, and it hands the objectors a grievance that has nothing to do with the merits of the scheme.

Where a campaign has produced a petition, report the number of signatures, the wording of the petition, and whether signatories were local. Where it has produced factual claims you believe are wrong, correct them with evidence rather than with adjectives.

Appendices that support the summary

The appendices are what make the summary checkable, and a section with no appendices is an assertion.

• Copies of the leaflets, letters and newspaper notices used, with the distribution area shown on a plan.
• The exhibition boards as displayed, and the dates, times and venues.
• The feedback form, so that the questions asked are visible.
• A tabulated log of responses, anonymised, with the theme coding applied.
• Correspondence with ward councillors, the parish or town council and any amenity society.
• Website material and the dates it was available.

Anonymise personal data and remove contact details before submission, because the document goes on the public planning register. That is a straightforward point that gets missed on a surprising number of applications.

Where the section reads as advocacy

The failure mode is a section written by the communications team rather than the planning team. The signals are recognisable: adjectives describing the scheme, quotations selected for approval, "the community welcomed" where the record shows a mixed response, and a conclusion asserting that the proposal enjoys local support.

Write it instead as a factual record with a short analytical conclusion. Say what was done, what was said, what changed, what did not, and why. If the honest conclusion is that local opinion remains divided on height, say that. Officers already know, because they have read the objections on the file.

A statement of community involvement that reports a difficult consultation accurately is more useful to a case officer than one claiming an easy ride, and it is much harder for an objector to attack. Where the scheme raises equalities issues, the same discipline applies to an equalities impact assessment, which draws on the same engagement evidence.

PlanScope drafts statements of community involvement structured to UK planning policy, with your consultation records and response data flagged for you to supply. Browse the report types and start a draft. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.