Stakeholder engagement · Analysis
From consultation to decisions: writing a stakeholder engagement findings report
A findings report should let readers trace what was heard, how it was analysed and what it means for the decision. Participation totals alone cannot provide that account.
Explain the question and the process
Open with the decision the engagement supported and the questions participants were invited to consider. Record dates, methods, recruitment and the information provided. Explain changes to the process where these affect interpretation. A reader should understand how the evidence came into existence.
Describe participation without overstating reach. Distinguish responses, participants and organisations, and explain whether the same person could contribute through several channels. State relevant gaps and limitations. A large voluntary response count does not on its own establish a representative account of the community.
Describe how themes were developed
Set out how comments were reviewed, grouped and checked. Clarify whether a count refers to people, comments or references to a theme. These are different units and can produce different impressions. Preserve the original context when summarising contributions.
Show differences between groups or methods when the information supports it. An interview may provide detail about a barrier, while a survey indicates which issues respondents selected. Do not force both into a single percentage. Record contrary views and explain how incomplete or ambiguous comments were handled.
Connect findings with the choices ahead
Use a decision table to connect each finding with its evidence, implications and options for response. Identify whether the recommendation arises directly from participant input, other evidence or the project team’s interpretation. Keep those relationships clear so decision-makers can interrogate the advice.
For example, participants might identify difficulty attending weekday activities. The finding can inform a trial of alternative times, but does not establish the staffing or funding needed. Describe those dependencies. BetterEvaluation’s guidance on framing work highlights the value of specifying intended users and uses [1]; apply that discipline when deciding what the report must help its readers do.
Prepare the public explanation alongside the report
Create an accessible summary that explains the main findings and next decision. Agree who checks quotations, protects confidential material and approves publication. Participants should not have to locate a long technical report to understand what happened to their contribution.
After the decision, provide a response that identifies what changed and why some suggestions were not adopted. Retain an evidence trail for future reviews. Soft Infrastructure can support engagement planning, thematic analysis and reporting that connect community knowledge with organisational decisions, while keeping the limits of the evidence visible.
- Methods, participation and limitations are clear.
- Themes are traceable to the analysis.
- Findings and recommendations are distinguished.
- A public summary and organisational response are planned.
Put this into practice
Community engagement and co-designRelated articles
Sources and further reading
Sources checked 9 October 2026. Numbered references support the factual statements identified in the text. The suggested workflows and illustrative scenarios are Soft Infrastructure’s practice guidance.