In this guide
- 01Define the work item
- 02Agree receiving needs
- 03Confirm acceptance
- 04Own exceptions and follow-up
A team handoff is complete when the receiving team can understand the work, accept the relevant responsibility and take the next action. Sending a message or moving a ticket does not establish that the transition succeeded. Agree what crosses the boundary, how acceptance is confirmed and what happens when the handoff is incomplete.
Use this guide when work repeatedly waits between departments, people duplicate checks or nobody knows who owns an exception. Stakeholder mapping identifies the people involved; this guide makes one shared operating boundary concrete.
Look at the boundary from both sides
AHRQ’s TeamSTEPPS handoff guidance treats a healthcare handoff as a transfer of information together with authority and responsibility. Ordinary organizational work is a different setting, but the distinction is useful: an information transfer and an ownership transfer are not automatically the same event.
Suppose a hypothetical repair service accepts coffee machines from customers. The intake team opens a case and places the machine in a queue. The technician later discovers that the reported fault is unclear or an accessory needed to reproduce it is missing. Intake believes the case was handed over; repair believes it has not received usable work.
Do not begin by deciding which team is at fault. Trace an ordinary case and a difficult one. Ask what each side needs, what it can know at that point and what it is authorized to decide. The missing item may reflect a service design problem rather than carelessness.
Define what the receiving team needs
For the fictional repair service, useful information may include the machine identity, the customer’s description of the situation, the supplied accessories and any condition that affects the next inspection. Define the required information with the receiving role, rather than adding fields because they might be interesting someday.

Separate three kinds of information. Some items are essential before repair can begin. Others are useful but can be clarified during the work. A third group is not needed for the receiving task and should not burden the handoff. Review the categories when the work changes.
Use a shared agreement:
| Field | Question to settle |
|---|---|
| Trigger | What event starts the handoff? |
| Work item | Exactly what case, object or request is being transferred? |
| Minimum information | What must the receiving role know to act? |
| Acceptance | Who confirms receipt and usability? |
| Responsibility | Who owns the case during clarification? |
| Exception | What happens when information or capacity is missing? |
| Follow-up | How will both sides see the current state? |
This is an original non-clinical work agreement, not a reproduction of a medical protocol. The actual service may need additional technical, confidentiality or other requirements specific to its work.
Confirm understanding without adding ceremony
AHRQ’s check-back guidance describes a closed communication loop in which the recipient acknowledges the information and the sender verifies the understanding. For routine work, confirmation might be a clear accepted state in a shared system. For a consequential exception, direct clarification may be more appropriate.
Choose the confirmation according to the risk and ambiguity. Requiring a meeting for every ordinary item can create delay. Assuming that every automated notification has been read can hide an unowned queue. The goal is a usable transition, not maximum communication activity.
In the fictional repair service, a technician might accept the case after checking that the machine and the required intake information match. If the fault cannot be understood, the agreement should say who contacts the customer and who keeps ownership while that happens. Avoid returning the case repeatedly without an accountable next step.
Active listening helps when the two teams describe different meanings of ready. Ask for a concrete example and check your interpretation. A shared word such as complete can conceal different task requirements.
Follow the whole service, not just the local queue
GOV.UK’s whole-problem service standard recommends working across organizational boundaries around what the user needs to accomplish. Applied by analogy, the coffee-machine customer wants a usable resolution, rather than a sequence of individually closed internal tickets.
Bitner, Ostrom and Morgan’s service-blueprinting account grounds the service view in the customer experience and the work behind it. A service blueprint can reveal whether the handoff problem originates earlier, such as in an unclear collection instruction or a support message that asks for the wrong item.
Inspect both upstream and downstream effects. Moving a check to intake may reduce technician interruptions while increasing the customer queue. That may be reasonable or unreasonable depending on the full service. Decide with evidence about the work rather than declaring that one department’s measure is the organizational outcome.
If the receiving team lacks capacity, more complete information will not by itself remove the queue. The handoff agreement should make capacity constraints visible and explain how priorities are decided. An escalation route needs someone who can actually resolve the resource conflict.
Try the agreement on ordinary and difficult cases
Rehearse the proposed handoff with the roles who will use it. In the fictional service, use a machine with a clear reported fault and a case where an accessory or description is missing. The point is to expose uncertainty before treating the agreement as settled.

Ask the receiving person to show how they decide whether the work is usable. Ask the sending person whether the necessary information can reasonably be obtained at that point. Record any situation in which both follow the agreement but nobody can proceed.
If a live trial is justified, keep its scope bounded and arrange support. Use continuous improvement to compare what was expected with what happened. No outcome is claimed for the hypothetical repair example.
Measure the boundary as well as each queue. Possible observations include clarification requests, waiting before acceptance, repeated transfers and cases with uncertain ownership. Include the work of obtaining missing information. A shorter repair queue is ambiguous if intake now holds the same cases out of view.
Keep the agreement maintainable
Give the interface agreement a named owner on each side and a way to resolve changes. Update it when systems, services or authority change. A handoff that works only because two experienced colleagues remember an informal exception is a dependency worth documenting and rehearsing.
Use knowledge transfer when someone changes roles. Include an actual case walkthrough, the exception route and the reasons behind the minimum information. A folder containing the form does not establish that the next colleague can operate the boundary.
When a handoff fails, investigate the mechanism before adding another mandatory field. Was the requirement unclear, impossible to meet, overlooked under load or irrelevant to the actual difficulty? A process workshop can help if the boundary depends on several roles and competing accounts.
Evidence limits and a first agreement
Healthcare handoff tools concern a specialized setting with different consequences and controls. This guide transfers general ideas about responsibility and confirmation, without claiming transferred clinical effects or offering a clinical protocol. Public-service and blueprinting sources provide additional perspectives, not proof that this exact agreement improves repair performance.
Choose one recurring transition. Write what the receiver needs, how acceptance works and who owns an incomplete case. Walk through it together with a realistic exception. The useful result is a shared next action that both teams can perform, rather than another instruction to communicate better.
Sources:
- Agency for Healthcare Research and Quality (2023). TeamSTEPPS Tool: Handoff.
- Agency for Healthcare Research and Quality (n.d.). TeamSTEPPS Tool: Check-Back.
- Government Digital Service (2026). Solve a whole problem for users.
- Mary Jo Bitner, Amy L. Ostrom and Felicia N. Morgan (2008). Service Blueprinting: A Practical Technique for Service Innovation.



