Reporting back is the step most often squeezed once a decision is made and the project moves toward implementation. The team is tired, the next project is waiting, and a thank-you email with a link to a summary feels like enough. It is not. Reporting back is where the promise made at the start of the engagement is either kept or broken.
This guide brings together the site's practice writing on reporting: the what-we-heard report, the decision report, getting the result back to participants, showing influence honestly, keeping the commitments of your chosen level of engagement, and using evaluation to improve the next project. It assumes the engagement was planned and delivered with reporting in mind; if it was not, the earlier guides on community engagement planning and community engagement analysis are the place to start.
What does closing the loop actually involve?
Closing the loop involves three things: an account of what was heard, an explanation of how it was considered, and a statement of what was decided and why. A newsletter, a project update or a list of themes can support that, but none of them closes the loop on its own.
- What we heard. The concerns, ideas and perspectives participants raised, specific enough that someone can recognize their own contribution.
- How we considered it. How input was weighed alongside technical advice, budget, legal requirements and policy, and who made those judgments.
- What we decided. The decision, where community input shaped it, and where it did not and for what reason.
The common mistake is to publish the first part and stop. A participant who raised a concern about traffic on her street learns nothing from a report that lists "traffic and safety" as a theme. The longer case for treating follow-through as part of the engagement, not an extra, is made in closing the feedback loop and community trust.
Why does reporting back decide trust in the next engagement?
Reporting back decides trust because people base their next decision to take part on what happened to their last contribution. Each invitation asks for time and knowledge; each loop closed well gives something back, and each loop left open costs more than the original request.
Repeated failures to report back damage trust and make it harder to rebuild. Across projects and years, a community learns that participating does not produce visible influence and stops responding. That silence is often read as apathy, but it is a reasonable response to experience. The next engagement then starts with fewer and less representative participants, produces weaker evidence, and leads to decisions that confirm the community's view. The slow erosion of community trust traces how this compounds and what rebuilding looks like.
Plan the report-back at the start
Decide how, when and through which channels you will report back while you are designing the engagement. Commitments written into the plan are far more likely to be kept than ones left to the end of the project.
What should a what-we-heard report include?
A what-we-heard report should show the themes with their evidence, explain how raw input was turned into those themes, and say what changed because of the input and what did not. A report that cannot answer the last two questions is a participation record, not an accountability document. When the report goes out before the decision is made, summarize the findings and any changes already confirmed, and where decisions are pending, say when participants will hear how their input was considered.
- The decision and its scope. What the engagement informed, what was open to influence, what was fixed, and the level of influence that was promised.
- Who took part and who did not. Participation by method, reach across groups where known, and the gaps. Naming under-represented groups is more credible than implying the sample was complete.
- How input was analyzed. The coding approach, who did the analysis, how disagreement was handled, and whether any tools, including AI, were used.
- Themes with evidence. How often each theme was raised and through which channels, representative quotes, and the points where people disagreed. Do not smooth conflict into a consensus that did not exist.
- What changed, what did not, and why. For each major theme, the response and its effect on the decision. "Noted" is not a response.
- Next steps. When the final decision is due, where to find it, and how people can stay involved.
The what we heard report template sets this out section by section, and writing a what-we-heard report covers the move from a summary of comments to a defensible account of what the input changed. Most weak reports share a root cause: the link between input and decision was never recorded during the project. The thread you can't reconstruct explains why that link has to be logged as decisions are made.
How is a decision report different from a what-we-heard report?
A decision report is written for the people making the decision, and it carries the evidence trail from community input to the recommendation in front of them. The what-we-heard report speaks to participants; the decision report gives elected officials, boards or executives what they need to decide with the engagement properly in view.
A useful decision report states the recommended direction, connects it to specific findings, lists the other constraints that shaped it, and explains how competing priorities were weighed. It should make clear where the recommendation departs from what the community asked for and why. Decision-makers who can see that reasoning are better placed to defend the decision in public, and the two reports should agree with each other. If a participant reads both and cannot draw a line between them, the engagement will look like a formality.
Keep the evidence trail reachable. A decision that can be traced back through themes and analysis to the original submissions is far easier to stand behind if it is challenged later. Our page on defensible community engagement sets out what that record needs to hold.
How do you report back to everyone who took part?
Report back through the same channels you used to invite people in, in formats they can actually use, and while the decision still feels current to them. A report posted on a project page reaches the people who check project pages, and that is rarely everyone you heard from.
- Match the outreach. If you reached a group through a community organization, a drop-in session or a partner network, take the result back the same way.
- Translate and simplify. Offer plain-language summaries and translated versions for the groups you engaged in other languages.
- Speak to specific concerns. Where a group raised a distinct issue, tell them directly what happened to it rather than leaving them to find it in a long report.
- Use people, not only documents. A short briefing or conversation where a decision-maker explains the reasoning often does more than a written report.
- Keep it timely. Report back while people still remember taking part, and give a date for the final decision if it has not yet been made.
Groups reached through deliberate outreach deserve particular care. They often took part because someone made the effort to include them, and a generic report-back can undo that effort quickly.
How do you show influence without overclaiming it?
Show influence by pointing to specific changes and naming the input that led to them, and be just as plain about where input did not change the outcome. Claims that the community "shaped" a decision, with nothing to point to, are easy to see through.
Three patterns undermine reports. The first is silence about input that was not adopted; people notice when their view disappears. The second is crediting engagement with a direction that was already fixed, which leaves participants feeling used for validation. The third is stopping at the decision, with no word on whether it was implemented as described or whether constraints changed later.
If the engagement did not change the decision, say so and explain why. Honesty about the limits of influence earns more trust than overstated influence, and it protects the organization when the same people are asked to take part again.
How do you keep the commitments of your level of engagement?
Restate the level of engagement you promised at the start, then report against it. The IAP2 Spectrum of Public Participation describes each level, from inform through consult, involve and collaborate to empower, as a different promise to the public, and the report-back is where you show whether that promise was met.
- Consult. You committed to listen, acknowledge concerns and report how input influenced the decision, so the report must show that feedback.
- Involve. You committed to reflect concerns directly in the options developed, so show where they appear.
- Collaborate. You committed to incorporate advice and recommendations as far as possible, so account for each one.
- Empower. You committed to implement what the public decided, so report on that implementation.
If the level shifted during the project, explain when and why. Choosing an honest level in the first place makes this far easier, which is why the community engagement strategy and planning work matters so much to reporting.
How do you evaluate an engagement and carry the lessons forward?
Evaluate the engagement against criteria you set before it began, covering both the process and its effect on the decision. Criteria chosen after the fact tend to be the ones the process happened to meet, which describes activity rather than testing whether it worked.
- Reach and inclusion. Did you hear from the groups your stakeholder mapping said you needed, and were barriers addressed?
- Process quality. Were methods, timing, communication and facilitation fit for the project?
- Influence. Did input change options, recommendations, mitigation or implementation?
- Follow-through. Did participants hear back clearly, and was the reasoning communicated?
Attendance and response counts tell you the scale of an engagement, not whether it improved the decision. A small number of people from groups you had not heard from before can matter more than a large number of people who were already involved. How to evaluate community engagement covers evidence sources and proportionate evaluation, and why engagement evaluation becomes post-rationalization explains why criteria must be fixed before delivery.
Lessons are only useful if they reach the next project. Record what you would change, and when the same lesson appears more than once, take it back into your engagement framework: the default methods, timelines, outreach approaches and reporting commitments that every project starts from. Across a program of projects, outcomes reporting can then show more than a single project can: which groups are consistently missing, where commitments are being met, and whether community input is making a visible difference to decisions over time.
How CE Canvas supports reporting back
CE Canvas keeps the engagement record in one place so reporting does not depend on reconstruction. The what-we-heard report is drafted from the project record, with each finding linked to the submissions behind it. The decision report carries the evidence trail from input through analysis to the recommendation. AI helps with drafting, but staff review, edit and sign off before anything is published; how that works is covered in the guide to AI in community engagement. Lessons are captured at the end of each project and can be compared across projects, so recurring gaps show up and can be fed back into your framework. Teams can try this on a live project through a guided pilot.
Last reviewed October 19, 2026 by the CE Canvas practice team.