For ABA agency owners and team leads
Three ways to follow up on staff feedback
After a listening session, staff need to know what happened next. Choose the message that matches the actual decision: an action is approved, a question is still under review, or the requested change cannot be made as proposed.
These examples adapt a broader principle from OSHA’s worker safety participation guidance: report back on action taken in response to concerns. AHRQ’s team communication guidance discusses listening and feedback. Use the examples for general team updates and follow your organization’s specific reporting processes.
Four pieces of a useful update
- Describe the shared theme without identifying anyone.
- Explain the actual decision or review status.
- Name the next action and responsible role.
- Give a realistic update date and question route.
Before using a message
- Confirm the facts and approvals. Replace brackets with verified details; distinguish an action planned from one completed.
- Use a theme that cannot identify a person through names, incidents, roles or small-group context. Do not share private employee or client information. Check the whole message in its recipient context: details combined may identify someone. If so, broaden the update or use an appropriate individual route. Explain who can see a report and the actual privacy limits of each available channel.
- Handle every safety or clinical report through its appropriate process; do not hold a report for a group update. For a safety concern, share verified interim protections and an immediate reporting route when relevant, and continue to address the concern while a proposed change is reviewed. For individual care or safety actions, use the required handoff and confirmation process. Obtain the necessary clinical or safety approval before changing practices that affect care or worker safety.
1. An action is approved
Use when the decision and next step are confirmed.
“You raised [non-identifying theme]. We have approved [specific action]. [Responsible role] will [next step] by [date]. We will share what we learn at [next update]. Questions can go to [available reporting options and their privacy limits]. [For safety concerns, include verified interim protections and the immediate reporting route.]”
2. The question is still under review
Use when the decision is not yet made.
“You raised [non-identifying theme]. We have not made a decision yet. [Responsible role] is reviewing [specific question] with [appropriate team]. We will provide an update by [date], even if the review is still open. Questions can go to [available reporting options and their privacy limits]. [For safety concerns, include verified interim protections and the immediate reporting route.]”
3. The proposed change cannot be made as requested
Use when the decision and the reason can be shared.
“You raised [non-identifying theme]. We cannot make [proposed change] as requested because [verified, shareable reason]. We will [approved alternative or next step] and update you by [date]. If there is another approach we should consider, please use [available reporting options and their privacy limits]. [For safety concerns, include verified interim protections and the immediate reporting route.]”
Keep a record in the agency’s approved system of the decision, owner, next action and update date. If the date changes, tell the team what is known and when the next update is expected. Escalate individual concerns through their established route without exposing private details in a group message.
Turn a staff suggestion into an action
Choose a manageable issue, name an owner and review date, and measure what changes.
Open the action plan worksheetExplore the agency training toolkit · More resources for organizations
