What to Do When a Key Employee Quits Your Small Business
A key employee has resigned and holds knowledge nobody else has. A first-week plan to capture it, secure access and keep customers.
When a key employee quits your small business, spend the first day securing access, the second to fifth capturing what only they know, and the rest of the notice period testing that someone else can do the job. The danger is not the empty chair. It is the tasks, passwords, customer promises and workarounds that lived in one head and were never written down. AI can help turn their explanations into usable notes, but the plan has to come first.
Day 1: separate the people side from the access side
Handle the conversation kindly and the access list coldly. They are different jobs.
Thank them and agree the last day. A good ending gets you better handover help.
List every system, account and device they use. Include shared mailboxes, supplier portals, social accounts, the domain registrar, payment tools and anything on a personal phone.
Find the accounts that belong only to them. Those are the ones to move to a company-owned login first. A shared password manager makes this much easier, because you can see what they actually hold.
Decide when each access will be removed. Usually that is their last day, or earlier for sensitive systems if the situation calls for it. The steps in offboarding an employee from your AI tools cover the AI-specific accounts that get missed.
Days 2 to 5: capture what is only in their head
Written procedures capture the easy part. The valuable part is tacit: what they do when a supplier is late, which customer needs a call, why the spreadsheet has a hidden column.
Use short recorded interviews, one task each, no more than 20 minutes. Ask the same five questions every time:
Walk me through this task from the start, as if I had never done it.
What triggers it, and how often does it happen?
What goes wrong, and what do you do then?
Who do you contact, and what do they expect from us?
What would you tell me not to touch?
Record the audio with the person's consent, transcribe it, and ask an AI model to turn each transcript into a numbered checklist with open questions marked. Always read the result alongside the transcript. Models fill gaps with plausible steps, and a procedure with an invented step is worse than none. The approach in prompting AI to write a handover document gives the structure to ask for.
Week 2 onward: test it
A handover you have not tested is a guess. Before the last day:
Have the replacement, or a colleague, run the task from the checklist while the leaver watches and stays silent.
Note every moment where they hesitate or ask a question, and fix the document there.
Pick one task and let the leaver be unavailable for a day to see what breaks.
Customers and suppliers
Tell the people who deal with the leaver directly, before they hear it elsewhere. Introduce the new contact in person or by call where you can. Check for open promises, such as a quote, a delivery date or a renewal, and write each one down with an owner and a date.
If it is worse than a resignation
If losing this person threatens the whole operation, the emergency closure plan is worth skimming, mostly for its list of what has to keep running. For everyday ways AI can reduce this kind of single-person dependence, see AI for small business.
Reduce the risk before it happens
Once the dust settles, ask a harder question: who else could do each critical task for a week? Aim for two people per task, even if the second is only a rough backup. Schedule a short documentation session each quarter. It costs far less than a frantic fortnight.
Frequently asked questions
What should I do first when a key employee resigns?
List their accounts and tools, agree a last day, and start scheduling short knowledge-capture sessions. Handle the access list separately from the conversation about leaving.
How do I capture knowledge that is not written down?
Interview them task by task with the same questions, record it with consent, and turn the transcripts into checklists. Then test the checklists with someone doing the work.
Can AI write the handover document for me?
It can draft one from transcripts, but read every step against the source. Models can add plausible steps that were never said, so check the output before anyone relies on it.
How long before the last day should I start?
As soon as you know. Even two weeks is enough for the core tasks if you begin on day one and keep sessions short.
How did this land?
About the author
Growth & SEO Lead
Manuele covers distribution: SEO, content strategy, and how AI-built products find their first thousand users. He tests everything he recommends.
