Picture a referral sent on Friday afternoon. The sender believes it is complete. The receiver thinks someone else is handling it. On Tuesday, everyone searches the same email thread with the confidence of detectives arriving after the evidence has been misplaced.
Handoffs expose the space between individual effort and shared responsibility. “I sent it” describes an action. It does not confirm that another person accepted ownership, understood the need, or had the resources to respond.
Edmondson (1999) links team psychological safety with learning behavior. For handoffs, that invites a concrete question: can a receiver acknowledge missing information without being blamed for slowing the work?
Define what acceptance means
A useful handoff includes the task, the reason it matters, the receiving owner, the required information, and the deadline. Add a simple confirmation step. The receiver should be able to say, “Accepted,” “I need this detail,” or “I cannot take ownership under these conditions.”
- Identify the receiving person or role instead of relying on a large distribution list.
- State the requested action and the time by which it is needed.
- Include essential context through the approved system, protecting confidential information.
- Ask for confirmation and specify what happens if it does not arrive.
For example: “Please review the attached approved summary by Wednesday noon. Confirm receipt today. If your team cannot take this request, let me know so we can redirect it.” In sensitive services, the communication method and information shared must follow organizational privacy requirements.
Measure the gap rather than guessing who failed
Choose one recurring process and examine a small sample of handoffs. How often was ownership clear? Which information was missing? Where did the work wait? A process review can reveal patterns that another reminder to “communicate better” will not resolve.
Agree on an escalation path for time-sensitive work. Urgent concerns should follow the established safety process; a routine inbox should not become an unofficial emergency service. Build coverage for absences instead of relying on one person to remain permanently available.
The aim is a handoff that another person can act on. Keep the checklist short enough to use and revise it when the work changes.
Tellumind’s organizational consulting helps teams turn recurring coordination problems into clearer working agreements. Start with one process this week. Ask both the sender and receiver what they need, then define the moment when responsibility has actually changed hands.
References
Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999
Photo: Redd Francisco / Unsplash.
