Principle
Do not transfer ownership until the receiver accepts it
Forwarding the message is not the same as transferring responsibility.
When it fits
- A task, incident or customer issue changes hands across a shift, team or person.
When to avoid it
- Organizational policy may require additional formal transfer or approval beyond conversational acknowledgment.
Why it matters
Name what is being handed over, who is taking it and when the transfer becomes effective. The sender remains responsible until the receiver has acknowledged the handoff and has enough information to act. If nobody explicitly accepts, the ownership has not moved just because a message was sent.
An example
An on-call engineer sends the incident state and waits for the incoming engineer to confirm ownership before leaving.
Check your result
At any moment, one accountable owner can be named without guessing from message history.
Keep this limit in mind
- Organizational policy may require additional formal transfer or approval beyond conversational acknowledgment.
Connected ideas
Useful withHand off the uncertainty, not just the status
Evidence and sources
Supports
AHRQ TeamSTEPPS states that responsibility in a handoff remains with the sender until the receiver is aware of and accepts the transfer.
Formal authority structures may impose additional transfer requirements.
Tool: Handoff · Transfer of responsibility and accountability; acknowledgment by receiver