The Handover That Does Not Lose Anything

Work changes hands constantly: between people, between teams, into and out of leave, at the end of a project, when somebody joins and when somebody goes. Every one of those is a place where context falls out, and nobody notices at the time.

You notice three weeks later, when the client says "we told you this already" and they are right. It is buried somewhere, in a message thread, in a call nobody wrote up, in the head of the person who moved on.

What actually leaks

Not the facts. The facts are usually in a system somewhere. What leaks is the layer above them.

The exceptions. "We normally invoice on completion; this client is monthly because their finance team asked." Exceptions live in people's heads almost by definition, and they are the single most common cause of a handover going wrong.

The reasoning. Someone receives a decision without its argument, hits a case that is nearly the same, and cannot extend it. So they either guess or escalate.

The unfinished conversations. Three things were raised and not resolved. They are in nobody's task list because they are not tasks. They surface later as surprises.

The relationship. Who to call, who is difficult about what, which promise was made warmly and which was made through gritted teeth.

The state of trust. Whether this client is happy, worried, or on their second strike. Nothing in a project tool carries this, and it changes how the next conversation should open.

The one page

Every handover, whatever the size. If it will not fit on a page, the thing being handed over has not been thought about clearly enough yet.

Where it stands. One paragraph, plainly. Not a status color: what is actually true.

What is committed. What we owe, to whom, by when. Including anything promised verbally.

Exceptions. Every place this deviates from how we normally do things, and why.

Open threads. Raised and unresolved. Each with the person who raised it.

Where the decisions are. Links to the records, not a summary of them. See Decision Records.

What I would worry about. The honest one. What is nagging at you, even if you cannot justify it.

That last field is the one people skip and the one that most often turns out to matter. Nagging is usually pattern recognition that has not finished forming yet, and it is the only field where the outgoing person's judgment is irreplaceable.

Run it as a conversation, not a document

Write the page, then talk it through for twenty minutes, both people present.

The document alone fails because the receiver does not yet know what to ask, and the conversation alone fails because nothing survives it. You need both, in that order: the page makes the conversation specific, the conversation surfaces what the page missed.

The receiver drives. They read it first and come with questions. If the outgoing person talks for twenty minutes, you have a briefing, not a handover.

Book it before the last day. A handover on someone's final afternoon is a formality. Two weeks earlier, the receiver can come back with the questions that only occur once they start doing the work.

The handovers nobody runs

Into and out of leave. Two weeks is long enough for three things to go wrong. Most people leave a note about urgent items and nothing about state.

Between meetings. Every meeting hands work to whoever was not there. If your meeting produces no record of what was decided and who owns it, you are running an unwritten handover every week.

Onto yourself, later. Coming back to something after three months, you are the receiver and past-you did not leave a page. Writing one when you PUT something down is cheaper than reconstructing it when you pick it back up.

Out of the organization. Someone leaving takes context that was never anywhere else. See Asking Someone to Leave for the exit; the handover is the part most groups forget while handling the emotion.

Where it goes wrong

A template nobody reads. Long forms get filled in mechanically. Six fields, one page, or it becomes a ritual.

Handing over only tasks. The task list is the least valuable part and the only part most handovers contain.

No named receiver. "The team" receiving a handover means nobody received it. One name.

Skipping it because the person is still around. "Just ask me" is not a handover; it is a promise to keep being the bottleneck, and it expires the moment they are busy or gone.

Treating the worry field as unprofessional. It is the most professional field on the page. Judgment is the thing you are actually transferring.

What good looks like

Three weeks after a handover, the receiver hits an unusual case and finds the exception written down, with the reason, and handles it without calling anyone.

Nobody says "we told you this already", because nobody had to be told twice.

Try this week

Take the last handover you received and write down every piece of context you have since had to ask for.

That list is exactly what your handover format is missing, and it is different for every organization.