What a proper handover note contains

The usual handover note gets written on the last afternoon. It is a list of ongoing items, each one a line long, in the shorthand of someone who has held the work for years. The person covering reads it, understands every word, and still cannot act on any of it.

That is because a handover is not a list of tasks. It is a description of state. What is in flight, where each thing stands right now, who is waiting on whom, and what happens if nobody touches it. Tasks are the easy part. State is what leaves with the person.

Start with the live items. For each one: what it is in plain words, where it stands today, what happens next and by when, and who is on the other side of it. If something is waiting on an outside party, say when you last chased and what they said. A line that only says following up hands over nothing.

Then the rhythm and the access. What recurs, on which days, and what a missed one costs. Where things live, which accounts and folders are needed, and what has to be requested rather than simply opened. Then the people: who to ask about what, who approves what, and who to warn if something slips.

Then the section most notes skip, which is the one that matters. What is fragile. The item that looks calm and is not. The client who reads tone closely. The commitment made verbally in a meeting that appears in no record. Nobody writes this down because it feels like gossip. It is not gossip. It is the operating context, and without it the person covering works blind.

The discipline is to write it as you go, not on the last day, and to keep it in the shared place rather than send it as one long email that dies in an inbox. AI helps with the repetitive half: pulling open items, dates and last movement out of the records into a first draft, so the person spends their time on judgement instead of assembly. Then test it honestly. Hand the note to someone else, go quiet for a day, and see what they had to ask you. Each question is a line the note was missing.