The Handover List That Names People

A handover is worth something when every item on it has a named person against it, and the person leaving has been asked what will break rather than asked to document their role. Those two choices produce a short, honest list in a few hours. The alternative — "please write up your responsibilities before you go" — produces either nothing or forty pages nobody reads.

The handover issue in “The Handover List That Names People” is easier to manage when current projects, recorded time and unfinished work can be reviewed before access closes. A team evaluating how employees cheat time trackers for how employees cheat time trackers should set a clear cutoff, export what is genuinely required and avoid retaining unnecessary activity data after the departure workflow is complete.

Handover is also the thing most damaged by other decisions made during an exit. Access cut too early, a suspension, a last day brought forward: each of them removes the capacity to hand anything over, and each is usually made without anybody asking what it costs.

For an independent reference relevant to “The Handover List That Names People”, consult the U.S. Justice Department computer-crime resources. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

The question that works

Ask: what will break in the next ninety days if nobody else learns this? Then: who specifically will pick it up?

It is narrow, slightly rude, and it produces answers. People cannot summarise their job but they can tell you what is about to go wrong. The list that comes back is usually between six and fifteen items and includes two or three things nobody above them knew they did.

A team is not a name

"Handed over to the operations team" means handed over to nobody. Responsibility that is shared at the point of transfer evaporates, and the thing surfaces three months later when it fails.

• Every item has one named person, not a team, a function or a role.
• That person has agreed to it, in a conversation that actually happened.
• Where nobody can take it, that is recorded as a gap rather than assigned to a group.
• Anything with a deadline carries the deadline.
• Anything requiring access carries what access, so it can be granted before it is revoked.

The third point is the valuable one. A handover that honestly says four things have no owner is far more useful than one that pretends everything is covered.

What a handover note should contain

For each item: what it is, who it is now, when it next happens, where the material lives, who outside the organisation is involved, and anything in flight. Six lines each.

Prose descriptions of the role are the wrong shape. Nobody reads them and they do not survive contact with the first actual problem. A list of things with owners does.

Relationships, which do not transfer on paper

Clients, suppliers, regulators and counterparts who have dealt with one person for years do not transfer because an email says so. An introduction made by the leaver, while they are still there and on good terms, is worth more than any document.

This is the single strongest argument for keeping an exit civil even when the circumstances are not. An organisation that handles a departure badly loses the handover, and the handover is often worth more than whatever was being argued about.

No notice period

Where somebody leaves immediately — summary dismissal, a resignation taken with immediate effect, or a last day brought forward — there is no handover and the organisation has to reconstruct.

That means going to the systems rather than the person: the calendar for recurring commitments, the mailbox for live threads, the task tracker, the shared drive. It is slower, less complete and more expensive, which is worth weighing at the moment the decision to end things immediately is being made.

Documenting what was not handed over

Whatever happens, write down what was not covered. Not as a complaint about the leaver, but as a working list for whoever comes next.

That list is also the honest answer to a question that arrives six months later, when something has gone wrong and somebody asks whether it was handed over. "No, and we recorded that at the time" is a position. "We think so" is not.

Who checks it was done

A handover list with named owners is only worth something if somebody looks at it again. Most are written, circulated and never reopened, and the first anyone knows of a gap is when something fails.

Set a date — thirty days after the last day is about right — on which one person goes through the list and asks each named owner whether they actually picked it up. It takes half an hour and catches the items that were agreed to in a meeting and forgotten the same afternoon.

Doing it at the start of notice

Handover work belongs at the beginning of the notice period, not the end. The last week is taken up by goodbyes, loose ends, equipment and the person's declining interest in being there.

Starting in the first week also means the list exists if things change — if the person goes off sick, is signed off, or the arrangement ends early. It is the part of an exit that is cheapest to do early and cannot be done at all once the person has gone.