How to write a handover document that actually works
Most handovers are a brain dump nobody reads. A good one is short, specific and written for the day something goes wrong.
By Kiran Rubab
3 minute read
A handover document that works is one page per task, written for someone competent who has never done it, with the trigger, the steps, the exceptions and who to ask. It is not a manual. It is the minimum a good person needs to do the job without you, and it takes about an hour to write.
Why do most handovers fail?
They fail because they are written from the wrong direction. The person handing over writes down everything they know, in the order they remember it, and the result is twelve pages that answer questions nobody asked and skip the one that matters.
A handover is not a record of your knowledge. It is a tool for someone else's action. Write it for the reader, not the writer.
What should a handover document include?
Five sections, in this order, on one page.
- When this happens. The trigger. "When a new client signs." "Every Friday at 3pm." "When an invoice is 14 days overdue."
- What good looks like. The outcome in one sentence. "The client has everything they need within 24 hours."
- The steps. Numbered, short, one action each. Link to the template or tool at each step rather than describing it.
- The exceptions. The three or four ways this goes wrong and what to do about each. This is the most valuable section and the one most handovers skip.
- Who to ask. One name for questions, one name for emergencies.
If it will not fit on a page, it is two tasks. Split it.
How do you capture the exceptions?
Ask yourself: what happened the last three times this went wrong? Those are your exceptions. If you cannot remember, ask whoever did it last, or watch the next three occurrences and write down what surprised you.
Exceptions are where the founder's knowledge actually lives. The happy path is easy. The unusual cases are why everyone still asks you.
Should you record a video instead?
Record a video as well, not instead. A five minute screen recording of you doing the task once is the fastest way to transfer the feel of it. But video cannot be scanned, searched or updated easily. The written page is the reference. The video is the introduction.
AI makes this easier than it used to be: record yourself doing the task while talking through it, and let an AI tool turn the transcript into the first draft of the written page. Then edit it down.
How do you know the handover worked?
Give it to someone and leave the room. If they complete the task without asking you anything, it worked. If they ask a question, add the answer to the document, not to the conversation. After three rounds of this, the document is complete and you are free.
What about tasks that change often?
Write the handover anyway, and date it. A handover that says "last updated in March" with a note about what changed is far more useful than none at all. Tasks that change every week are usually a sign that the process has not settled, and the act of writing it down often settles it.
What is the difference between a handover and an SOP?
A handover is written for one person taking over from another, usually once. An SOP is the permanent version, written for anyone who will ever do the task. In practice a good handover becomes the first draft of the SOP. Write it in the five part format, test it with the person taking over, then file it as the standard. See how to write SOPs that people actually use for how the library is kept alive.
Where do handover documents live?
In one place everyone can find. A shared folder, a wiki or a project tool, organised by area of the business. Not in email, not in someone's personal notes, and never only in the founder's head.
Building this library is a large part of what a Guided Build delivers. By the end, every repeating task in the business has a page, and the founder has stopped being the manual.
