How to Manage Objections and Community Opposition During Public Consultation
Public consultation does not end when an exhibition closes or an online feedback form is removed. For developers, one of the most important stages comes afterwards: understanding what people actually said and turning that feedback into useful evidence.
A structured approach to analysing consultation feedback can help identify recurring themes, common concerns, positive responses, frequently asked questions and areas where further explanation or engagement may be required. The findings can then be brought together in a clear consultation report that records the engagement process and demonstrates how feedback was considered.
Why Is Analysing Public Consultation Feedback Important?
Consultation can generate a significant amount of information from different sources, including written responses, online questionnaires, emails, conversations at public exhibitions and feedback provided by community representatives.
Simply collecting this information is not enough.
Feedback needs to be reviewed systematically so that meaningful patterns and themes can be identified.
Analysis can help a development team understand:
• Which issues were raised most frequently
• Whether particular concerns were shared by multiple groups
• Which aspects of a proposal received positive feedback
• What questions people continued to ask
• Whether further information or clarification is needed
• Whether feedback suggests potential changes to the proposals
• Which issues may need to be addressed as part of the wider planning process
This provides a more useful picture of the consultation than simply counting the number of responses received.
How Should Public Consultation Feedback Be Collected?
Before feedback can be analysed, it should be collected and organised consistently.
A consultation may involve several different engagement methods, so developers should keep a clear record of where responses came from and when they were received.
This could include:
• Online consultation forms
• Written responses
• Emails
• Public exhibition feedback
Comments made during consultation events
• Responses from local organisations
• Feedback from community groups
• Comments from other relevant stakeholders
Keeping this information organised makes it easier to review the responses and ensures that feedback is not overlooked.
The method used to collect feedback should also be recorded as part of the wider consultation process. This can subsequently help demonstrate how the community was given opportunities to participate.
For a broader overview of the engagement process, see our guide to how to run a public consultation: events, digital engagement and communications.
How Do You Identify Themes in Consultation Feedback?
One of the most useful stages of analysing feedback is identifying recurring themes.
Rather than treating every response as an entirely separate issue, responses can be grouped according to the subjects they discuss.
For example, feedback on a property development may include themes such as:
• Traffic and transport
• Highways and access
• Housing
• Local facilities
• Green space
• Landscaping
• Ecology
• Building design
• Construction activity
• Noise
• Parking
• Drainage
• Local character
• Employment and economic benefits
Grouping responses in this way makes it easier to establish which subjects generated the most discussion and what specific concerns were associated with each theme.
It is also important not to focus exclusively on negative feedback. Positive comments, support for particular aspects of a proposal and constructive suggestions can all provide useful information.
How Can Developers Respond to Consultation Feedback?
The purpose of analysing feedback is not simply to create a record of opinions. It can also help inform the development and planning process.
Where appropriate, feedback may lead to changes to a proposal, additional information being provided or further engagement taking place.
For example, consultation feedback might identify a need to reconsider an element of site access, provide greater information about landscaping or explain how construction activity could be managed.
Where changes are made as a result of consultation, these should be recorded clearly. This helps demonstrate the relationship between the feedback received and the decisions subsequently made.
Not every suggestion will necessarily be capable of being incorporated into a development. Where suggestions cannot be taken forward, the reasons should be explained where appropriate.
This helps ensure that consultation is presented as a genuine process of engagement rather than simply an exercise in collecting comments.
What Should a Public Consultation Report Include?
A consultation report provides a formal record of the engagement process and its findings.
The exact structure will depend on the development and consultation, but a report can typically explain:
• Who was consulted
• How consultation was carried out
• When engagement took place
• Which consultation methods were used
• How many responses were received
• What feedback was provided
• The main themes identified
• Key concerns and questions
• Positive feedback and areas of support
• How feedback was considered
• Any changes made following consultation
• Further actions or explanations where appropriate
The report should provide enough information for someone reviewing the planning process to understand what engagement took place and what was learned from it.
For developments progressing through the planning process, this can form an important part of the wider evidence surrounding consultation.
You can also read our guide to public consultation and the planning process: what developers need to know.
How Should the Consultation Report Present Feedback?
A consultation report should be clear, factual and easy to follow.
Feedback can be presented according to the main themes identified during the analysis. Each theme can then explain the issues raised and, where appropriate, the response from the development team.
For example:
Theme: Traffic and Highways
The report could summarise the concerns raised about traffic, access and road safety before explaining how these matters were considered and whether any changes or further investigations were undertaken.
This approach allows the report to demonstrate both sides of the consultation process: what people said and how the development team responded.
It can also make the report easier for planning professionals, stakeholders and other interested parties to understand.
How Should Frequently Asked Questions Be Handled?
Consultation feedback often highlights questions that arise repeatedly.
If several respondents ask similar questions, this can indicate that additional information or clearer communication may be required.
Frequently asked questions can therefore be recorded as part of the consultation analysis, alongside the answers provided by the development team.
This can also help inform future engagement. If a particular aspect of the proposal generates repeated questions, it may be worth providing more detailed information about that subject during subsequent stages of consultation.
Should Changes Following Consultation Be Included?
Yes. Where consultation has resulted in changes to a development proposal, these should be recorded in the consultation report.
The report can explain:
What was proposed → What feedback was received → What was considered → What changed
This creates a clear record of how consultation contributed to the development process.
Where a suggestion has not resulted in a change, the report can explain the position where appropriate. Not every consultation response will lead to an amendment, particularly where a suggestion is outside the scope of the development or conflicts with other considerations.
What matters is that the feedback has been properly considered and that the report provides a transparent account of the process.
How Can Consultation Analysis Support a Planning Application?
A well-prepared consultation report can help bring together the evidence generated through the engagement process.
It can demonstrate that consultation took place, explain how people were given opportunities to comment and provide a structured summary of the feedback received.
The report can also show how the development team responded to relevant issues and whether the proposals evolved as a result.
For developers preparing a planning application, this can help connect the consultation process with the wider planning strategy.
You can also read public consultation for planning applications: what developers need to know.
What Makes an Effective Consultation Report?
An effective consultation report should be:
• Accurate – feedback should be represented fairly and accurately.
• Structured – information should be organised around clear themes.
• Balanced – positive, negative and neutral feedback should all be considered.
• Transparent – the report should explain how consultation was undertaken.
• Evidence-based – conclusions should reflect the feedback actually received.
• Clear – readers should be able to understand the findings without unnecessary complexity.
• Relevant – the report should focus on matters relevant to the development and consultation.
The report should not simply be a collection of comments. Its purpose is to turn the information gathered through consultation into a useful and understandable record of the engagement process.
Turning Consultation Feedback Into Useful Evidence
Analysing public consultation feedback is an important step between engagement and reporting.
By systematically reviewing responses, identifying recurring themes and recording how issues have been considered, developers can create a clearer picture of the consultation process.
A well-prepared consultation report can then bring this information together, showing who was consulted, how engagement took place, what people said and how the development team responded.
Where changes have been made as a result of consultation, these can also be recorded, helping demonstrate how engagement has contributed to the evolution of a proposal.
For developers planning a consultation, getting the analysis and reporting stage right from the beginning can make it easier to maintain a clear record throughout the process.
How Should Common Concerns Be Recorded?
Once the main themes have been identified, the specific concerns raised under each theme should be recorded clearly.
For example, if highways and transport were recurring themes, the analysis could distinguish between concerns about traffic levels, pedestrian safety, road access and parking.
This provides more useful information than simply stating that "transport was a concern".
The aim should be to accurately reflect what people said without overstating the significance of individual comments. A small number of responses raising an issue should not necessarily be presented as widespread opposition, while frequently recurring concerns should not be overlooked.
The analysis should therefore provide a balanced representation of the feedback received.