In short
Treat a notice period as a knowledge-transfer project with a hard deadline. In the first week, list what only this person knows, what they have access to, and which relationships route through them. Then spend the middle of the notice period having them document and hand over, not finish their in-flight work, because unfinished tasks can be picked up and undocumented knowledge cannot. Revoke access on the last day using a written list, not memory, and expect to find forgotten credentials for months afterwards if you skip it.
Key takeaways
- The notice period is a knowledge asset with an expiry date. Spend it on transfer, not on tidying tasks.
- List access before the last day. Credentials discovered six months later are the standard outcome of not doing so.
- Relationships leave too. Clients and suppliers who only know one person need a warm introduction, not an email.
- Have the leaver write the documentation and someone else test it, or you have captured what they already knew.
- The exit conversation is your cheapest source of honest operational feedback, and almost nobody uses it.
The notice period is a window that closes
Most businesses handle departures emotionally and administratively, and skip the operational part entirely. There is a card, a final payroll run, a vague handover conversation, and then the person is gone and the questions begin.
What has actually happened is that a window opened and closed. For four weeks, or eight, someone who holds knowledge that exists nowhere else is still being paid, still has context, and is usually willing to help. That will never be true again. After the last day, the same knowledge costs a favour, a consulting fee, or a rediscovery project, and in many cases it is simply gone.
The predictable consequences of skipping it:
- A process nobody can run, discovered at the point it next needs running, which may be a quarter later.
- A client who had a relationship with a person rather than with the business, and now has neither.
- A subscription nobody knew about, found when the card is declined.
- An account still active six months on, because the list was reconstructed from memory.
The cost of a departure is not the recruitment. It is everything that leaves the building alongside the person, none of which appears on any invoice.
Three inventories to build in week one
The first week of notice, not the last, is when the inventories get built. Leaving it to the final week guarantees that the list is written under time pressure by someone who has already mentally left.
| Inventory | How to build it | Typical surprise |
|---|---|---|
| Knowledge | Ask what would stop or slow down if they vanished tomorrow, then ask their colleagues the same question | Colleagues name things the leaver does not think of as knowledge |
| Access | Every system, credential, shared account, client portal, physical key, and anything on a personal card | Two or three tools nobody in management knew existed |
| Relationships | Every client, supplier and contact who would call this person first | Relationships that were never logged in the CRM at all |
Ask the colleagues as well as the leaver. People are systematically bad at identifying their own tacit knowledge, because expertise stops feeling like knowledge and starts feeling like common sense. The person next to them can usually name three things they always ask this person about.
If any of these lists is long, that is not really a departure finding. It is a key person risk finding that the departure has made visible, and it will be equally true of whoever inherits the role unless something changes.
Transfer knowledge, not tasks
The instinct during a notice period is to have the leaver finish what they started. This is exactly backwards.
Unfinished work can be picked up by someone else at moderate cost, and it will be, because it has a deadline attached and somebody will chase it. Undocumented knowledge cannot be picked up at any cost once the person has gone, and nobody chases it, because nobody knows it is missing until it is needed.
So: reassign in-flight work early, accept the friction, and spend the notice period on transfer. A workable shape for a four-week notice:
- Week 1. Build the three inventories. Reassign active work to named people.
- Weeks 2–3. Document the processes only they run, capturing live rather than from memory, using the format in how to write an SOP people actually follow. Introduce successors to key contacts.
- Week 4. Someone else performs each documented process while the leaver watches without intervening. Every question is a defect in the document, fixed that day.
Week is the one that determines whether any of this worked. Documentation that has never been executed by a second person reliably assumes the knowledge it was supposed to capture, and the test costs a few hours while the author is still available to answer.
Prioritise ruthlessly. Nobody documents everything in four weeks. Rank by frequency multiplied by consequence, cover the top three or four processes properly, and accept that the rest will be rediscovered.
Access: the list you cannot reconstruct later
Access revocation is the part that gets remembered, half-done, and then quietly abandoned. The reason is that the real list is longer than the obvious one.
The obvious items are email, the project tool, and the shared drive. The ones that get missed:
- Client-side accounts. Portals, systems and logins issued by clients, which your business has no visibility of at all.
- Personal-card subscriptions. Tools bought on expenses, where the account is in their name and the renewal is silent.
- Shared credentials. Passwords known rather than assigned. These cannot be revoked, only changed, and if you do not change them they persist indefinitely.
- Recovery routes. Their phone as the second factor, their email as the recovery address for a shared account.
- Anything on their own device. Files, message history, client contact details in a personal phone.
Build the list in week one and work through it on the last day. The recovery-route item is the one that most often outlasts everything else, because it is invisible until an account needs recovering and the code goes to a phone that left the business a year ago.
Relationships leave with the person
If a client's working relationship is with an individual rather than with the business, that relationship is at risk at the moment of departure and is usually handled worst.
The version that works costs a fortnight of attention:
- Introduce, do not announce. A joint call or a message from the leaver introducing the successor transfers some of the trust. An email from an unfamiliar name announcing a change transfers none.
- Transfer the context, not just the account. What this client cares about, what went wrong once, what they always ask for. This is a handoff, and it fails the same way every handoff fails, as described in handoffs are where work goes to die.
- Have the successor make contact before the leaver goes, while questions can still be answered.
Then write it down, because the same exposure will exist next time. A business whose client relationships live in individual heads has a resilience problem that recruitment does not solve.
The exit conversation is free diagnostics
The last thing, and the one most often skipped or wasted on sentiment. A departing employee has no incentive to be diplomatic about how work actually runs, and that makes this the most honest operational feedback available anywhere in the business.
Ask operational questions, not feelings:
- What took longer than it should have, every week?
- What did you work around rather than through?
- What will break when you go, that we have not talked about?
- What would you fix first, if you were staying?
The second question is the highest-yield, for the same reason workarounds are the best evidence in an internal operations audit: a workaround is a functioning solution to a real problem that the official process does not handle, designed by the person who understood the problem best.
Do it a few days before the last day rather than on it, when there is still time to act on anything urgent, and separate it from anything that feels like a performance conversation. The Mayim Ops assessment scores documentation and resilience together for the same reason this checklist exists: what a departure costs is determined entirely by what was written down before anyone resigned.
Frequently asked questions
What should an employee offboarding checklist include?
Three inventories built in the first week of notice: what this person knows that nobody else does, what they have access to, and which relationships route through them. Then a documentation and handover plan for the middle of the notice period, access revocation on the final day, and an exit conversation.
How do you transfer knowledge before someone leaves?
Have the leaver document the processes only they run, and have someone else perform each one from that document while the leaver watches without intervening. Documentation written and never tested reliably assumes knowledge the author forgot they had, which is exactly the knowledge you are trying to capture.
What should someone do during their notice period?
Document and hand over rather than finish in-flight work. Unfinished tasks can be picked up by someone else at moderate cost; undocumented knowledge cannot be recovered at any cost once the person has gone. Reassign their active work early and use the remaining time for transfer.
When should you revoke a departing employee's access?
On the last day, working from a written list built at the start of the notice period rather than from memory. Reconstructing access afterwards is unreliable: personal tool subscriptions, client portals and shared accounts are routinely missed and surface months later, often when a licence renews.
Are exit interviews worth doing in a small business?
Yes, if you ask operational questions rather than sentimental ones. A departing employee has no incentive to soften an account of what wastes time or which process everybody works around, and this is the only moment you will get that answer honestly and for free.