The notice period is a deadline for knowledge transfer
When someone resigns, the clock starts on everything only they know. A task-by-task plan for knowledge transfer before their last day.

When someone in a finance team resigns, the first conversations are about the replacement: the job advert, the recruiter, the salary band. The more urgent question gets less attention. What does this person know that nobody else does, and how much of it will still be in the building on their last day? The notice period is the only window for knowledge transfer you are guaranteed, whether it is four weeks or three months. This post argues for treating it as a deadline with a plan, task by task, rather than a vague hope that a handover document appears in the final week.
Why the last week is too late
The usual pattern is familiar. The leaver keeps doing their job at full speed, because the work does not stop. Someone asks them to "write up a handover" with no structure and no time set aside. In the final days they produce a long document from memory, between farewell lunches and clearing their inbox. Then they go.
That document is rarely wrong, but it is almost always thin. It describes what the person does, not how. It skips the steps that feel obvious to them and the judgements they make without noticing. And nobody tests it while the author is still there to answer questions.
There is also a calendar problem. A month of notice covers one run of each monthly task and none of the quarterly or annual ones. If the person owns the VAT return and leaves in the middle of a quarter, the next run happens after they have gone. Anything not written down by then has to be worked out again from old files.
Start with their task list, not their job description
A job description says "responsible for management accounts and payroll". That is no use for a handover. What you need is the list of recurring tasks the person actually runs, with the frequency, the next due date and who else can do each one.
If your firm already keeps a recurring task list, filter it by owner. If not, sit down with the leaver in the first two or three days and build their list together. Our post on building the recurring task list in a week has a template that works here too. Expect the list to be longer than anyone assumed, including the leaver.
Then sort it. For each task, ask two questions:
- Can anyone else already do this? If a named backup has run it recently, the risk is low.
- Does it run before their last day? If yes, you get a live handover. If no, you only get a written one.
The tasks that answer "nobody else" and "not before they leave" are where the notice period should go first. They are the single-owner tasks you will otherwise lose.
A knowledge transfer plan, task by task
Take a hypothetical bookkeeping firm where a senior bookkeeper hands in four weeks' notice. They own, among other things, the monthly payroll check for six clients, two quarterly VAT returns, and the annual accounts prep for a client with a March year end. A workable plan might look like this.
Week one: list and rank
Build the task list together and rank it by risk. Agree who will take over each task, even provisionally. A handover to "the team" goes to nobody, so name a person per task.
Weeks two and three: shadow, then reverse shadow
For tasks that run during the notice period, the successor watches the leaver do it once, then does it themselves with the leaver watching. The second run is the one that matters. It shows what the written steps miss, because the successor stops at every gap.
For tasks that do not run in time, the leaver walks the successor through last period's working papers step by step, and the successor writes the method down in their own words.
Week four: test the gaps
Give the successor one task to run alone while the leaver is still available but not involved. Every question they need to ask is a gap in the written method. Fix it on the spot.
What to capture for each task
The written method should follow the same shape as any good manual. For each task:
- Inputs. Which reports, systems, client contacts and files feed it, and where they live.
- Steps in order. The order the person actually works in, not a tidied summary.
- Judgements and thresholds. Where they decide something, how they decide it. "Query any payroll variance over 5% unless it is a known bonus month" is a method.
- Exceptions. The client who always sends files late, the account that never reconciles first time, and what they do about it.
- Contacts. Who at the client or in the business they ask, and for what.
- History. What went wrong last time and how it was fixed.
The exceptions and history are the most valuable lines and the ones most often left out. Our earlier piece on keeping an exceptions log covers why.
How to ask, and how not to
The leaver is doing you a favour by doing this well. Treat it that way. Take work off their desk to make room for the handover, rather than expecting it on top of a full load. Thank them for it in front of the team.
Do not frame the handover as a test of the person or as extracting what they know before they leave. It is the firm catching up on documentation it should have had already. Say that plainly. A resignation tends to expose know-how that has sat in one head for years, and that was the firm's risk to manage, not the leaver's fault.
Better still: do not wait for a resignation
Every point above is easier if the work was already written down. A team where each recurring task has a named backup and a current manual can absorb a resignation in a few conversations. A team where it does not spends the notice period on emergency documentation.
The same documented tasks also matter for anything you want to hand over in future, whether to a new hire or, eventually, to an AI agent that drafts the work for a person to check. Know-how in one head cannot move to anyone. In Beaks, each recurring task carries its owner, its backup and its manual, so a resignation shows up as a short list of tasks to reassign rather than a scramble.
One thing to do this week
Pick the person on your team whose resignation would worry you most. Without making a fuss, list the recurring tasks they own and mark the ones with no backup. Choose one of those and ask them to walk a colleague through it this month. You will have done one task's knowledge transfer before anyone needs it.


