Related guide: Closing the loop in community engagement: a guide to reporting back
A community engagement report (also called a what we heard report, consultation report or engagement summary) tells participants and decision makers what people said during an engagement process and what the organization will do with it. A good one covers the purpose and the decision, what was open to influence, who took part and who did not, the methods used, the themes heard with evidence, what changes as a result (or why not), and next steps.
It is where community engagement is often won or lost. It is the moment an organization shows, or fails to show, that participation was worth people's time. Yet most 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 walks through how to write a community engagement report step by step, gives you a section-by-section template you can adapt for any project, and covers the principles that separate defensible reporting from decorative reporting.
What should a community engagement report 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.
It also has two audiences. Participants want to see their input reflected accurately and want to know what happens next. Decision makers (a council, a board, a project sponsor) need a fair account of community views they can weigh alongside technical, financial and legal advice. Write for both, and keep the two jobs visible: reporting what was heard, and explaining how it was used.
People judge engagement by outcomes, not process. If a report explains how community input shifted a decision, people can see their influence even when not all their preferences were adopted. That is what makes a report defensible: you can show where feedback informed the decision, explain the trade-offs, and say where you took a different path and why.
How to write a community engagement report
These steps run from the day engagement closes to the day the report is published. They assume you captured input in one place as you went; if you didn't, step 2 takes much longer.
Close the engagement cleanly. Note the closing date, stop accepting new input through every channel, and record late submissions separately so you can say how they were handled. Tell participants when to expect the report.
Gather every source into one record. Survey responses, submissions, emails, workshop notes, phone calls, social comments and staff notes from conversations. Tag each item with its channel and date so nothing is analyzed out of context.
Check who took part against who you planned to reach. Compare participation by method, location and group with the stakeholder list in your plan. Name the gaps now, while there is still time to explain them or follow up.
Analyze input into themes you can trace. Code comments into themes and keep the link from each theme back to the source comments that support it. Record how many raised each theme, through which channels, and where people disagreed. A second reviewer checking a sample of the coding is worth the time.
Draft the response to each theme with the project team. For every major theme, agree what changes in the project, what is already addressed, and what will not change and why. This is the step that most often stalls, so book the conversation with decision makers before analysis finishes.
Write the report. Use the template below. Lead with a plain-language summary, keep technical detail in appendices, and quote participants in their own words where it helps.
Review for accuracy, fairness and privacy. Check that every theme matches its evidence, that minority and dissenting views are not smoothed away, and that quotes cannot identify people who did not agree to be named.
Sign off, publish and tell people. Get approval from whoever owns the decision, publish on the same page or platform people used to take part, and notify participants directly by email, SMS or the channels they used.
Reporting back works best when it was planned from the start. Before engagement begins, your community engagement plan should say how you will report decisions, how people will know their input mattered, and when reporting will happen. Then the report is a commitment kept rather than an afterthought.
What goes in a community engagement report
Whatever you call it, the core content is the same. Use this list as a checklist, then see the section-by-section template below for what each part needs to show.
Purpose and decision: why the engagement happened and what decision it informs, including who makes that decision and when.
What was open to influence: what the community could genuinely shape, and what was fixed (budget, statutory requirements, safety standards), with the promised level of influence.
Who took part and who did not: participation numbers by method, reach across groups and places where known, and the gaps you are aware of.
Methods: how people could take part (survey, drop-in sessions, workshops, submissions, online platform) and how input was analyzed.
What we heard: themes with evidence: how many raised each one, through which channels, representative quotes and points of disagreement.
What changes as a result (or why not): the response to each major theme: what changed, what was already addressed, and the specific reason for anything that will not change.
Next steps and how people will be told: when the decision will be made, where to find it, further chances to take part, and how participants will be notified.
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 analyzed
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. Our guide to community engagement analysis covers this step in more depth.
This is also where you move from "we heard X" to "we heard X, and here is what it tells us." Note where community input lines up with technical analysis, where it differs, and what surprised the team. That interpretation is what decision makers need to weigh the input fairly.
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.
Here's how one theme might read for a hypothetical park upgrade: "Shade and seating near the playground. Raised in 64 of 210 survey responses and at both drop-in sessions. Parents of young children and older residents raised it most often. Some residents near the playground asked that seating not face their homes." The numbers are illustrative, but the shape is the point: weight, who, where, and the disagreement.
6. What changed, what didn't, and why
The heart of the report. For each major theme: the organization's response, what it changed in the decision, or the specific reason it didn't. "Noted" is not a response. This is the section communities read first, and the one that makes the next engagement easier or harder. The next section explains how to write it so it holds up.
7. Next steps and how to stay involved
When the final decision lands, where to find it, how participants will be told, and any further opportunities to participate. If the decision will be implemented over time, say how people will hear whether it was delivered as described.
Showing influence: from summary to defensible outcomes
Most organizations can summarize what they heard. They tally survey responses, identify themes from workshops and list public comments. That documents that engagement happened. It doesn't answer the question communities actually want answered: how did this input shape the decision?
The distance between "here is what people said" and "here is what we decided and why" is where trust is built or lost. It helps to think of reporting as three stages, each building on the last.
Stage 1: what was heard
The factual record: who participated, through which methods, how representative the process was, the themes that emerged, verbatim quotes and conflicting views. A good summary answers whether you reached the people you needed to reach and what patterns appeared in the input.
Stage 2: what it means
The interpretive step. What does this feedback tell you? Where does it align with technical advice, where does it differ, and how do community priorities sit against the constraints on the project? The quality of this stage depends on earlier choices: whether the right people were asked the right questions.
Stage 3: what was decided and why
This is where most reports fall short. They document the engagement and sometimes analyze it, but never explicitly connect it to the decision. A defensible decision account includes:
The direction chosen, stated plainly
How community feedback influenced it, with specific connections to themes
The other constraints that also shaped the decision (cost, safety, law, technical advice)
How different stakeholder priorities were weighed against each other
Where community preferences were not reflected, and the reason
What happens next, including implementation timing and how people will be updated
Ideally, someone with authority over the decision writes or signs off this part. When decision makers explain their own reasoning, the report carries the actual logic behind the choice rather than a publicized result. The written report is also not the whole story: where you can, have decision makers explain their reasoning to the community directly, with the report as the record that backs it up.
What we heard, you said we did, consultation report: are they the same thing?
Mostly, yes. In Canada, "what we heard report" is the common name, used widely by municipalities and public agencies for the summary published after an engagement closes. In the UK, "you said, we did" is a familiar format that pairs each piece of feedback with the action taken, often as a short table or web page. Elsewhere, including Australia and New Zealand, you will see "engagement summary", "consultation report" or "community engagement report". The names differ, but the job is the same: show people what was heard and what happened as a result.
Is a what we heard report the same as the final engagement report?
Not always. On many projects reporting happens in two stages, and it helps to be clear which one you are writing.
The interim what we heard report is published soon after engagement closes. It covers stages 1 and 2 above: themes and evidence reported faithfully, before the decision is made, so people can check their views were captured accurately and decision makers can see them.
The final outcomes report comes after the decision. It covers stage 3: how community input was weighed and what changed as a result, theme by theme, using the structure in the section on showing influence above.
Closing the loop is the wider practice that both reports serve: telling people what happened, through the channels they used, and doing it at every stage rather than once at the end. See closing the loop in community engagement.
On smaller projects one report can do both jobs, as long as the what-changed section is complete. If the decision is months away, publish the what we heard report first rather than leaving participants in silence.
Common mistakes in community engagement reports
Themes without evidence. "Many residents raised traffic concerns" tells readers nothing they can check. Give the weight, the channels and a representative quote, and keep the trail back to source comments.
Summarizing without connecting to the decision. A detailed what we heard report is published, but the decision document never references it. People read both and cannot draw a line between them.
Silence about what didn't change. Leaving out the requests you couldn't act on reads as not listening, and people feel their input was erased. Say what will not change and the specific reason (cost, safety standards, a fixed legal requirement).
Crediting engagement with decisions already made. Announcing that you "listened and chose Option X" when the direction was fixed beforehand reads as validation, not deliberation. People notice, and they remember it next time.
Reporting too late. A report published months after engagement closes, or after the decision, arrives when people have stopped paying attention. Publish the interim report promptly and tell people when the final one is due.
No follow-through on implementation. The decision is reported, but nobody hears whether it was delivered as described or whether constraints changed. Include implementation commitments and say how updates will be shared.
Inaccessible format. A 60-page PDF is not a report most participants will read. Lead with a plain-language summary, publish in an accessible web format, and offer translations or other formats where your community needs them.
Smoothing disagreement into consensus. If the community was split, say so and describe the split. Decision makers need to see it, and participants on the losing side need to see they were heard.
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.
Weak reporting is often a symptom of weak planning. When the plan is clear up front about what will be reported and how, reporting is straightforward. If your organization's engagement framework doesn't tell staff what a report must contain and when, a free framework audit will show where they would still be guessing. Reporting also feeds evaluation: see how to evaluate community engagement for how the report and the evaluation share the same evidence.
See it in practice
CE Canvas keeps engagement evidence in the project record throughout delivery, so themes stay traced to the source comments behind them. Its AI assistant drafts the report from that evidence, citing where each finding came from, and people review and sign off before anything is published. See how it works, or join the CE Canvas Live session on defensible what we heard reporting for a working session on moving from raw engagement data to a transparent report.
For the analysis behind the report, see our practical guide to thematic analysis of community feedback.
If your survey used rating questions, our Likert scale question examples page explains how to report Likert results.
Frequently asked questions
What is a what we heard report?
A what we heard report is a public summary published after a community engagement process closes. It sets out who took part, how, the themes that emerged with supporting evidence, and what the organization will do next. The term is common in Canada; elsewhere the same document may be called a community engagement report, consultation report or engagement summary.
How long after engagement closes should the report be published?
As soon as you can do the analysis properly, and ideally before the decision it informs is made. Many organizations aim for a few weeks, depending on the volume of input. Whatever the timing, tell participants when engagement closes so they know when to expect it, and keep to that date or explain the delay.
What if the engagement did not change the decision?
Be honest about it. Explain what feedback was received and why constraints meant you proceeded with the original direction. Honesty about the limits of engagement builds more trust than false claims of influence, and it gives people a reason to take part next time.
Should you publish individual submissions?
It depends on your privacy obligations, what participants were told when they took part, and your organization's policy. Many organizations publish de-identified submissions or selected quotes, and some publish full submissions only with consent. Never publish personal details without consent, and say in the report how submissions were handled.
What is "you said, we did"?
"You said, we did" is a reporting format common in the UK that pairs each piece of community feedback with the action taken in response. It works well as a short, accessible summary. The best versions also include "you said, we didn't, because", so people can see the reasons behind requests that were not taken up.