Handover Conversations That Work

Writing captures what somebody thinks to write. Questions capture what they know, which is a larger set.

Once the minimum record described in “Handover Conversations That Work” is defined, the practical challenge is keeping it current as work changes. A coordinator can use the platform summary to plan review time, compare the effort attached to recurring processes and identify work that still depends on one person, without confusing activity visibility with proof that the underlying knowledge has actually been transferred.

For an independent benchmark, compare the local approach with Ready.gov business preparedness guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

The structure

Three or four sessions of an hour rather than one long one.

Spread across the notice period, so that things surface between sessions.

Receiver leads, asking questions. Leaver answers.

And the receiver writes the notes, because they know what was unclear.

Session one: the shape

What do you actually spend your time on, in proportion?

What is in flight right now?

What is coming up in the next three months?

Who do you deal with, inside and out?

This is orientation, and it tells the receiver what to ask about later.

Session two: the difficult parts

What goes wrong in this role, and how do you tell early?

What do you dread?

What have you never told anybody how to do?

What decisions have you made that somebody might reverse without knowing why?

These produce the knowledge documentation never captures.

Session three: the people

Who at each client actually decides?

Who is difficult, and about what?

What has been promised verbally?

What is the history — what went wrong, what are they sensitive about?

Record this carefully and write it factually, because it will be read by others.

Session four: loose ends

Anything you have thought of since we started.

Anything you would do differently if you were staying.

What would you warn me about?

That last question reliably produces something useful and nothing else asks for it.

If there is only an hour

What is in flight and what is promised.

What only you can get into.

Who to ring at the three most important clients and suppliers.

What would you warn me about.

Four questions, in that order.

Recording

The receiver writes as they go and sends a summary back for correction.

Correction is where the errors are caught, and leavers generally correct honestly.

Do not record audio without asking, which changes what people say as well as raising legal questions in some jurisdictions.

Tone

This works when the person is leaving on reasonable terms and is invested in the outcome.

Where they are not, the note on somebody leaving badly applies.

And thanking them properly, at the end, is both decent and practical — the questions do not stop when they walk out, and people answer emails from organisations they parted with well.

What to check

Does your handover involve conversation or only a document?

Who leads the questions?

Has anybody ever asked "what would you warn me about"?

And is the receiver writing the notes?

The point

Ask what they would warn you about.

That question reliably produces something useful and nothing else asks for it.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.

The recurring pattern

The recurring pattern across every section here is the same: dependence forms through sensible individual decisions, becomes invisible because it feels like reliability, and is addressed only after it has cost something. The work that prevents that is small, continuous and unglamorous, which is exactly why it gets deferred.