The “What We Heard” report is where community engagement is often won or lost. It is the moment an organisation demonstrates — or fails to demonstrate — that participation was worth people's time. Yet most What We Heard reports are written in a rush at the end of a project, from fragmented records, under deadline pressure. The result is usually a summary, not a report: broad themes, vague assurances, and no visible line from community input to the final decision.
This guide provides a section-by-section template you can adapt for any engagement project, plus the principles that separate defensible reporting from decorative reporting.
What a What We Heard Report Must Do
A credible report answers four questions communities actually ask: What was heard? How were themes identified? What influenced the decision? And what didn't — and why? If your report can't answer the last two, it's a participation record, not an accountability document.
The Template: Section by Section
1. Executive summary
One page. The decision being informed, who participated, the strongest themes, and the headline outcomes — including at least one thing that changed because of community input, and one thing that didn't.
2. The decision and the engagement scope
State what decision the engagement informed, what was genuinely open to influence, and what was fixed (budget, statutory constraints, safety requirements). Restating the promised level of influence — Consult, Involve, Collaborate — keeps the report honest against the original commitment.
3. Who participated (and who didn't)
Participation numbers by method, demographic reach where known, and — critically — known gaps. Naming under-represented groups builds more credibility than pretending the sample was complete.
4. How input was analysed
The section most reports skip entirely. Explain how raw input became themes: the coding approach, who did the analysis, how disagreement within the community was handled, and whether any tools (including AI) were used. If analysis can't be explained, findings can't be defended.
5. What we heard — themes and evidence
Present each theme with its weight (how many raised it, through which channels), representative quotes, and points of disagreement. Resist the urge to smooth conflicting views into consensus — communities notice when their disagreement disappears.
6. What changed, what didn't, and why
The heart of the report. For each major theme: the organisation's response, what it changed in the decision, or the specific reason it didn't. “Noted” is not a response. This is the section that closes the feedback loop — and the one communities read first.
7. Next steps and how to stay involved
When the final decision lands, where to find it, and any further opportunities to participate.
The Mistake That Undermines Everything
Most weak What We Heard reports share the same root cause: the link between input and decision was never captured during the project, so it can't be reconstructed at reporting time. If you wait until the end to connect feedback to outcomes, you'll be writing from memory — and it shows. Track the thread as you go. We've written more about this in The Thread You Can't Reconstruct and in our guide to defensible engagement reporting.
See It in Practice
CE Canvas keeps engagement evidence organised throughout delivery and generates structured outcome reports that show how community input shaped the decision — with every finding traceable to its source. Our CE Canvas Live webinar series includes a full working session on moving from raw engagement data to a transparent, defensible What We Heard report. See upcoming sessions.