Before the Goodbye Email: Bottling the Know-How That Never Made It Into the Job Description

There's a specific kind of silence that lands on a team a fortnight after someone leaves. The card's been signed, the leaving do's been had, the laptop's gone back to IT. Then somebody asks how the monthly return actually gets filed, and five people look at each other with exactly the same expression.

I've watched this play out more times than I'd like. The formal handover is nearly always fine — passwords, folders, the client contact list. What falls through the gaps is the unwritten stuff. The supplier who only replies before ten in the morning. The spreadsheet with a hidden tab that quietly breaks if you sort column D. The reason nobody books the second meeting room on a Thursday.

None of that is in the job description. All of it matters.

Nobody's fault, everybody's problem

Most people are not hoarding knowledge on purpose. They're just busy. The last week in a job is a blur of exit forms, IT tickets and someone asking if you've got a minute for a quick question. The handover of actual know-how gets squeezed into whatever's left, which is usually nothing.

And the person leaving genuinely doesn't know what you don't know. They've been doing the task for four years. It feels obvious to them, so it doesn't get said.

The fix isn't a longer exit interview. HR has that covered, and it's designed to capture how they felt about the job, not how the job works. What you need is a short, structured session — a proper one, booked in the diary while they've still got a login, ideally a couple of weeks before the last day.

Aim for 45 minutes. An hour if there's tea involved, which there should be.

The 45-minute session

Don't wing this. A handover with no structure turns into nostalgia about twenty minutes in. Lovely, but not useful.

Set it up like this:

• Pick the task, not the person. Ask the leaver to list the five things they'd have to be phoned about if they were on holiday. Those are the ones living in their head rather than anywhere else.
• Book a screen, not a chat. The session works best with their actual work open in front of both of you. Watching someone do the thing catches the workarounds and the bit where they always start in the middle for reasons nobody has ever questioned.
• Have someone else in the room. Two people is the sweet spot: the leaver and whoever's picking it up. Any more and it turns into a meeting. Any fewer and you lose the chance to ask the daft question that turns out to be the important one.
• Narrate out loud. Ask them to talk through what they're doing as they do it, including the boring bits. Especially the boring bits.
• Leave ten minutes for the who-do-I-ring list. Names, numbers, the right person at the supplier. Ten minutes here saves an entire afternoon six weeks later.
• Record it if they're comfortable. Even just audio. Not for formal training — for the moment in March when nobody can remember whether the invoice goes to accounts before or after approval.

The one-page handover sheet

One page. Not a manual. If it doesn't fit on one side of A4, it won't get read and you've wasted everybody's time.

Ask the leaver to fill this in during the session rather than afterwards. Afterwards is a lovely idea that never happens.

• The task, in one sentence — what it is and how often it happens
• The trigger — what tells you it needs doing (an email, a date, someone else finishing their bit)
• The steps that actually matter — three to six lines, in the order they genuinely happen
• The workaround — the bit you do because the system doesn't
• The gotchas — what breaks it, and what it looks like when it has
• Who to contact — internal names and any external ones, with the best time to reach them
• The awkward one — anything you'd normally only say out loud, like the client who prefers phone to email or the approval that technically needs the other form
• What finished looks like — how you know it's done and correct

That last line does more heavy lifting than anything else on the page. Most handovers fail not because people can't do the steps, but because nobody told them what a proper finish looks like.

Wait — isn't this just process mapping?

No. Process maps are for work that runs to a script. This is for the human layer around the script: the judgement calls, the relationships, the workarounds that keep things moving. It's messier, and it's more useful.

If you already have a process document, bring it. The session's job is to add everything the document leaves out — which is usually the exact stuff that gets people stuck.

Do it before the card, not after

The single biggest improvement most teams can make here is timing. Handovers arranged for someone's final two days are a formality. Handovers arranged for their final fortnight are an asset.

Practically, that means building the trigger into the leaving process itself. The moment a resignation is accepted or a role change is confirmed, the 45-minute slot goes in the diary — before the card gets passed round, before the collection email goes out. It's a small administrative habit that pays back for years.

It works just as well for internal moves. Someone shifting from operations into a project role keeps every bit of their know-how in the building, but their old team still loses access to it unless somebody thinks to sit down and ask.

The quiet test

Here's how you know it worked. A few months later, the person who took over the task gets asked a question about it and answers without hesitating. Or better — they answer, then say 'hang on, there's a note about this', and the note is right.

Nobody remembers who ran the session. That's fine. That's the point. The best handovers are the ones nobody has to talk about, because nothing broke.

Book it while they've still got a login. The card can wait an hour.