A family question can disappear between roles even when everyone involved wants to help. The person who hears it first may pass it on, but the next person may not realize that nobody has accepted the follow-up. Closing the loop makes that gap visible. It means confirming who received the question, who can respond, and what the family has been told to expect. The examples here are fictional and focus on communication within local procedures. They do not replace the site's process for clinical, privacy, or urgent concerns.
Capture the question before routing it
Start by hearing the question the person wants to ask. A statement such as “No one has called me” could refer to who will provide an update, when they should expect it, or which number the team should use. Reflect back the part you understood and ask a brief confirming question. For example, you might say that you heard a question about who will return the call and ask whether that is what they want clarified. This gives them a chance to correct the interpretation before several people act on the wrong assumption.
A person may offer more detail than you need to route the question. Use the organization's appropriate record and privacy process, and keep shared discussion limited to the minimum information necessary. Do not put personal or clinical details into informal training notes. In a fictional practice session, a generic description of the question is enough to learn how the handoff works. In actual work, follow the local process to check what information the team may share and with whom.
Distinguish receiving from accepting
A message can be delivered without being taken up. When a question moves between roles, use a short confirmation that names the action each person will take. The first role can explain what remains open and what has already been promised. The receiving role can say whether they can handle the next step or need to send it elsewhere. If the message is received through an approved system, check how acceptance is recorded or signaled there. Avoid assuming that an unread message or a copied note has created an owner.
For some questions, the next action may be to identify who is authorized to respond. Do not turn that step into a promise that a specific person will call if they have not accepted. Tell the family what the team can confirm, the appropriate route for an update, and how the question will be followed up within the process. This keeps the message clear when the final answer is still unavailable and avoids introducing a second, unsupported promise.
Choose a close-out signal that fits the workflow
Define what counts as follow-up before the question is passed on. It could mean that the assigned role provided the appropriate update, or that they told the family another authorized contact must respond. A person being able to see a message in a queue is different from knowing that the family received a response. The close-out signal should help the team separate tasks that are done from tasks that were forwarded. A small number of clear states is easier to use than a list of labels that coworkers interpret differently.
Build in a way to notice questions that are still open. A desk change or routine team check can provide a natural moment to review unfinished work. Ask which questions still require an owner and what has already been communicated. Keep the review focused on the tasks and follow the approved method for handling sensitive information. If a staff member does not know where the question belongs, give them a route for finding the right role without sending the family from desk to desk.
| Moment | What to do | What to verify |
|---|---|---|
| Hear the question | Reflect back the point that needs an answer | The family can correct the interpretation |
| Transfer responsibility | Name the open action and confirm acceptance | The next role knows what it owns |
| Follow through | Use the approved process to record the outcome | An open question remains visible |
Fictional example: the family asks about a return call
At a fictional care desk, a family member asks who will return their call about an administrative step. The person at the desk listens and confirms that the question is about the expected point of contact, rather than the details of care. They explain the part they can verify and avoid naming a caller before a colleague agrees to take responsibility. They use the team's approved method to pass on the question and note that the family has already been told how to request an update.
The receiving colleague confirms the next action. After following the site process, they give the appropriate update and mark the task complete in the approved place. If the question had needed a different role, they could instead confirm the transfer and keep it open until responsibility was clear. In the example, the family does not have to repeat the original request because the handoff carried forward both the question and the previous conversation.
Practice with one interruption in the scenario
A rehearsal is more useful when it includes a realistic complication. Try the same fictional question during a practice desk change, or introduce an interruption just before a colleague acknowledges the message. Ask a person observing the rehearsal to name the owner at each point. If the observer cannot tell, identify the missing acknowledgment or status update and repeat the scene. Do not use real patient details or score employees based on a single exercise. The purpose is to make the communication process easier to follow.
After the team tries the approach, look for a particular sign that it helped. Perhaps fewer people ask where a question was sent, or a receiving role can explain what a family was told without reading through a long history. If the process still depends on one person being available, adjust the way responsibility transfers. Give that change a clear owner and a time to review it. An improvement is most useful when someone who did not attend the original discussion can still use it.
Review the wording people use when a question must be held overnight or until another service opens. An honest statement about an unavailable role is more useful than a promise that the issue is handled. Explain the approved next contact if there is one and make sure the open item stays visible to the people who can act on it. The important distinction is whether responsibility is clear, not whether the team can answer immediately.
Quick checklist
- Confirm the question in plain language.
- Check that the next role has accepted the follow-up.
- Separate a transfer from a completed response.
For further reading on confirming receipt, see the AHRQ TeamSTEPPS Check-Back guide.

