The situation
A DSD team completed listening sessions with families and providers. The notes are rich. The team is unsure what to send back and worries about promising things it cannot deliver.
Fictional worked example
A report-back people can recognize
This made-up four-part response follows listening about a meeting invitation. It demonstrates specificity without inventing a commitment about the program in the scenario.
What we heard
“The reply instructions were hard to find, and a daytime discussion did not work for some participants.” Use a checked theme; quote a participant only with appropriate permission.
What changed
“The draft invitation now puts the reply action first and offers a written contribution route.” Describe an actual change only after it has been made.
What remains open
“An additional meeting time still needs an organizer and available capacity.” Explain the real constraint instead of promising the option.
What happens next
Name the contact role, the next opportunity to influence the work and the agreed time to return with an answer.
Bring it into your work: Prepare a response in the languages, formats and channels used during engagement. Distinguish a completed change, an unresolved request and an agreed next step.
What to notice first
- The report-back is the part most often skipped, and the part that builds trust.
- Honesty about what could not change is more valuable than vague promises.
- Participants' words carry more weight than a summary, with permission and no identification.
Questions to ask before acting
- What changed because of the sessions, specifically?
- What could not change, and which rule, budget, or law is the reason?
- Who is the named contact, and when is the next chance to influence the work?
Practical next moves
Who to involve
The program owner approves the report-back. Send it in the languages, formats, and channels the sessions used.