Someone is leaving and half the work is in their head. What do I do before their last day?

By Ranjit Bhinge, founder of Blur Studio · Updated · 7 min read

Short answer: Use the two weeks you have to capture how the work is really done, not what the job description says. Have the leaver keep a task log, record themselves doing the tricky jobs, and turn those recordings into step-by-step notes, with AI doing the first draft. Then a manager checks the notes by trying to follow them cold. Access, files and open work are handed over on the same list, so nothing sits with someone who has left.

Ranjit Bhinge

A person who knows how things actually get done is about to walk out the door, and you need their know-how on paper before they do.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

If you want to find where AI could take the repetitive work off your team for good, the AI Strategy Sprint does that in 3 days.

What a handover is, and what it is not

Most handover advice online is an HR checklist: return the laptop, switch off the email, hold the exit chat. That is offboarding, and you need it. But it does not save you when the person who sends the Friday supplier orders leaves and nobody knows which supplier needs a phone call and which one takes an email.

A working-knowledge handover is different. It captures four things:

  • What gets done, and how often. Daily, weekly, monthly and once-a-year jobs.
  • How it is actually done. The steps, the tools, the shortcuts, the logins.
  • What is half-finished. Open jobs, promises made to clients, things waiting on someone.
  • Who and what they know. The contact at the supplier who always helps, the customer who needs gentle handling.

The two-week plan

If you have two weeks, use them in this order. If you have two days, do steps 1, 3 and 5 only.

WhenWhatWho
Day 1Name the handover owner (a manager, not the leaver). Agree the list of who takes what.Manager
Days 1 to 5Leaver keeps a task log: every job they do, how long it takes, how often.Leaver
Days 3 to 8Leaver records themselves doing the five to ten trickiest jobs.Leaver
Days 6 to 9AI drafts the step-by-step notes from the recordings.Manager, with the tool
Days 8 to 12Successor follows each draft cold. Gaps are fixed with the leaver in the room.Successor and leaver
Days 10 to 12Hand over access, files and open work. Introduce key contacts.Manager
Last dayManager signs off the checklist below. Leaver's access is switched off.Manager

Step 1: the task log

Ask the leaver to keep a simple log for one week: a table with four columns. Task, how often, how long, and where the files or tools are. They add a line every time they start something new. Nobody can list their own job from memory, because half of it is habit. A week of notes as they go finds the quiet jobs, such as "I always check the shared mailbox at 8:30".

At the end you get a list that is usually longer than the job description. Mark each line: keep, hand to someone, stop, or automate. This is also a good moment to ask whether the job needs refilling as it was. The same log helps you write a better description when you train new hires and decide who takes what.

Step 2: record, do not write

People who leave rarely write good notes. They are busy, and writing what you know is slow. Talking while doing the job is quick and keeps the detail. Ask the leaver to share their screen and do the task while explaining out loud, in plain words: "Now I open the supplier folder, and I check the date because this one always arrives late."

Tools that record are common. Google Meet, Google's video-call tool, is one example. Its help page says a Workspace administrator must turn recording on for your account, participants are notified when recording starts, captions can be recorded, and a recording stops automatically after 8 hours. Check the current options and plan requirements for your own video tool. Tell the leaver you are recording, and keep recordings where only the right people can open them, since they may show customer details or passwords on screen. Ask the leaver to keep passwords out of the recording and to hand them over in your password manager instead.

Step 3: let AI draft, then check

This is where AI earns its place. A transcript of a recording is messy. An AI assistant such as Claude, made by Anthropic, can turn it into a clean first draft in a minute. Paste in the transcript and ask for what you need. A prompt that works:

"Here is a transcript of an employee explaining how to do this task. Turn it into a numbered step-by-step procedure for a new person. Keep my company's tool names exactly as spoken. List any steps where the speaker was unclear or skipped something as a separate list of questions. Do not guess."

The last line matters. The questions list is gold: it tells you exactly what to ask the leaver before they go. For more on this approach, see my guides to an AI SOP generator (an SOP is a standard operating procedure, a written set of steps) and to SOP software that can hold the finished notes.

What AI cannot do: know whether a step is right. It writes down what was said, including mistakes and out-of-date habits. It also cannot catch what was never said. That is why the next step is a human one.

Step 4: the cold-follow test

This is the check most handovers skip. Give the draft to the person who will take over, or someone who has never done the task, and ask them to follow it exactly, with the leaver sitting beside them and not allowed to help unless they are truly stuck. Every time the leaver has to speak, the notes have a gap. Fix the note on the spot.

A task passes when the successor finishes it using only the notes. If it takes them three times longer than the leaver, that is normal. If they cannot finish, the note is not ready.

Step 5: manager review checklist

  • Every line in the task log is marked keep, hand over, stop or automate.
  • Every kept task has a named new owner.
  • Every recorded task has a written procedure that has passed the cold-follow test.
  • Open jobs are listed with the client, the next step and the date it is due.
  • Promises made to customers or suppliers are written down.
  • Key contacts are listed with how each prefers to be reached, and the leaver has introduced the successor.
  • Shared logins are in your password manager and have been changed or rotated.
  • Files are moved to a shared place. In Google Drive, a Docs, Sheets or Slides file can be transferred to someone it was shared with, and Google notes that you cannot cancel a transfer after the new owner accepts it. Admins on Google Workspace can transfer a user's Drive files too.
  • Scheduled jobs, such as recurring invoices or reports, are listed with the date of the next run.
  • Email forwarding or an out-of-office note is set up for the leaver's address.
  • Access is switched off on the last day, not the week after.

A worked example

Take a made-up business: a six-person landscaping company where the office manager, Dana, is leaving in two weeks. Her task log lists 31 jobs. Nine are daily, such as the booking calendar and answering the voicemail. Eleven are weekly, such as invoicing and ordering materials. Seven are monthly. Four are yearly, such as the insurance renewal and the vehicle registration reminders.

The owner marks 6 of them as stop or automate, hands 19 to the new hire and 6 to the owner. Dana records herself doing the eight trickiest. AI turns the eight transcripts into drafts and flags 23 unclear spots. Dana answers them in one 45-minute session. The new hire then follows three of the drafts cold, and each exposes one or two more gaps. The notes are updated. None of that took a rewrite of the whole job, and nothing sat only in Dana's head by the last day.

Where the handover lives

Put the finished notes in one shared place that a new person can find without asking. A shared folder with one document per task is enough. If you plan to make it searchable and let staff ask questions in plain words, see AI knowledge base and how to build an AI knowledge base from your documents. If you already have old Word files, turning them into staff training gets them used. In Google Docs, hovering over Last edit shows who changed a file last, and anyone who can edit the file can browse earlier versions. Put a "last checked" date on each note, because a note that is a year old and wrong is worse than none.

Privacy and the people side

Recordings and transcripts can hold customer data and personal details. Check what your AI tool does with what you paste in: whether it is kept, and whether it is used for training. Anthropic, the AI company behind Claude, states that it does not train on inputs or outputs from its commercial products by default, and its consumer plans are under separate terms, so check the terms for your own plan with any vendor. If you are in the UK, the ICO, the UK's data protection regulator, publishes guidance on AI and data protection. For employment questions, such as whether you can require a leaver to record, ask a lawyer or your HR adviser.

Also be kind. A leaver who is angry or hurt will not give you their best notes. Say clearly what you need, thank them, and keep the process to a few hours, not a second job.

How I'd approach this

If I were in your seat, I would do the task log on day one and the recordings by day five, because that is when people still have the energy. I would let AI write the first drafts, and I would never skip the cold-follow test. That test is the whole point, because it is the only thing that tells you the notes work.

I would also use the handover as a chance to ask which of these jobs a machine should be doing at all. If you find the same job in the log every week with nobody enjoying it, that is a candidate for automation, and the AI Strategy Sprint is a paid 3-day first step where we find where AI could help most and write down the exact steps, starting with a free 15-minute AI brainstorm call. For wider ideas, see AI for small business.

Questions people ask

What should an employee handover include?

A task log of what they do and how often, written steps for the tricky jobs, a list of open work and promises, key contacts, shared logins and files, and a named new owner for each task. See the checklist above.

How long should a handover take?

Two weeks is comfortable for a role with real depth. Even in two days you can do the task log, a recording of the riskiest job and the access handover. Short notice is when the recordings help most.

Can AI write the handover notes for me?

It can write the first draft from a transcript, and list the places where the speaker was unclear. It cannot tell if a step is right, so someone must follow the notes cold to check them. See AI SOP generator.

How do I document processes if the person is leaving on bad terms?

Keep it short and focused on the work, not the history. Prioritize the task log and the open-work list, and ask a manager to shadow the main tasks now. If there are legal or contract questions, speak to a lawyer or HR adviser.

Where should the notes be stored?

In one shared place with a clear folder name, each note dated. If you want staff to ask questions and get answers from the notes, see AI knowledge base.

What about files in the leaver's own Drive or accounts?

Move ownership before their last day. In Google Drive a file owner can transfer ownership of a Docs, Sheets or Slides file to someone it has been shared with, and a transfer cannot be cancelled once accepted. Google Workspace admins can also transfer a user's files.

More in this topic: Problem solving: automating service business work (21 guides) →

Sources

Ready for the next step?

A free 15-minute AI brainstorm. We find 3 broad areas where AI could help your business.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.
See the AI Strategy Sprint

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…