Async Handover is whether your writing survives your absence — whether the document, ticket or message you leave behind gives the next person what they actually need, without you there to fill in the gaps live. It sounds like a writing skill. In practice it is closer to a prediction skill: guessing, in advance, what someone will be confused about once you're gone.
A Prediction Skill Disguised as a Writing Skill
Good async handover means anticipating the question someone will have before they have it, and answering it in the document rather than waiting for it to arrive as a message. That requires imagining the reader's position without the context the writer currently holds — which is a different skill from writing clearly in general.
It is why two people can write with equal clarity and produce handovers of very different quality: the gap is not in the sentences, it's in which sentences got included.
What Weak Handover Looks Like
It rarely looks like an empty document. More often it looks like a thorough, well-written account of what happened that never quite states the one thing the next person needs — the decision that was made, the constraint that ruled out an option, the person who owns the next step. All the surrounding context is there; the load-bearing sentence is missing.
That gap is easy to miss when reviewing your own writing, because the missing sentence feels implied to the person who already knows it. It is only missing to the reader who doesn't.
More Writing Is Not the Fix
The instinct when handover goes wrong is often to write more next time — more context, more background, more caveats. That usually makes the real problem worse, because it buries the one decision-bearing sentence deeper in material the next reader has to wade through to find it.
The more reliable fix is structural: state the decision or the blocker first, in its own line, before the supporting context — so a reader who is short on time still gets the part that matters.
Reading an Async Handover Score in Context
Async Handover is most informative next to Self-Visibility, since both concern making information available without being asked — one in writing left behind, the other in real-time state. A gap between the two suggests the habit is present in one register and not the other.
The Distributed Work Habits test scores Async Handover out of twelve chances, alongside three other facets, with no total score across them — each is meant to be read as its own signal.