When your most experienced employee is leaving next month, spend the next four weeks capturing what they know: list what only they do, record them doing it, turn the recordings into SOPs, hand each one to a named successor, and have the successor run it while the expert is still there. Trainual is Business Operations & SOP Software that turns company knowledge into employee performance, with Training, Operations, and Performance in one place, so what one person knows becomes something the whole team can run.
It's Thursday afternoon, and the resignation email is short and kind. Eleven years, a great opportunity, last day in four weeks. You start a list of what they handle and stop at the third line: the quarterly vendor reconciliation. You ask around. Nobody else has ever done it, and the spreadsheet only makes sense to the person who built it.
Every growing company has someone like this. At 50 to 150 people, it's often several someones, and each departure is a test of how much of the company lives in one person's head. Four weeks is enough time to pass that test, if you start now.
Updated November 2026.
Key takeaways
- Start with an inventory, not documentation. You can't capture what you haven't listed.
- Record first, write second. Watching someone do the task captures details they'd never think to write down.
- Give every responsibility a named successor, and have the successor run it before the expert leaves.
- Make it routine. The best time to capture knowledge is before anyone resigns.
What's at risk when a key employee leaves
When a long-tenured person leaves, five kinds of knowledge walk out with them:
- Recurring tasks nobody else has done, like the monthly close, a vendor reconciliation, or a client report.
- Exceptions and judgment calls: when to bend a rule, which customer gets special handling, and why.
- Relationships with customers, vendors, and partners who call them directly.
- Tools and access they set up or own.
- The "why" behind decisions: what was tried before and why it didn't work.
The first two are where most companies get hurt. For the bigger picture, see what happens when a senior employee quits without documenting.
The four-week knowledge transfer plan
Four weeks is enough for most roles. If you have less, compress each step and start with the highest-risk tasks.
Week 1: list what only they know
Sit down with the departing employee for an hour and work through these questions:
- What do you do every week, month, quarter, and year?
- What do people come to you for? The questions they answer most are the knowledge most at risk.
- What breaks when you're out? Think back to their last vacation.
- Which customers, vendors, or partners contact you directly?
- What workarounds have you built that aren't written down anywhere?
Rank the list by risk: what would hurt most if nobody could do it next month? That order drives the next three weeks.
Week 2: record them doing the work
Recording beats writing. People skip steps when they write from memory, but not when they're doing the task on screen.
- Run one walkthrough session per task, with the successor on the call.
- Record the session so nobody has to take notes. In Trainual, the Notetaker can join Zoom, Microsoft Teams, or Google Meet and deliver a transcript and summary when it ends.
- Ask about the exceptions: "When do you do this differently, and why?"
- Capture screens for software-heavy tasks.
Week 3: turn recordings into SOPs
- Draft an SOP from each recording. AI-powered SOP creation turns a transcript or rough notes into a structured first draft that the expert reviews.
- Name the successor as the owner of each SOP.
- Move the responsibility to the successor's role, so ownership is clear on the role chart.
- Assign the SOPs as training to anyone else who might cover the task.
For tips on getting usable drafts, see how to get better SOPs from AI.
Week 4: hand off and test
- The successor runs each task while the expert watches and corrects.
- Fix the SOP on the spot wherever the successor gets stuck.
- Make warm introductions to the customers and vendors who used to call the expert.
- Hand over tool ownership through IT, and update who owns each tool.
Day 30 after they leave: review
Ask the successor what they had to figure out alone. Every answer is a gap to add to the SOP while it's still fresh.
The knowledge transfer checklist
Use this as the master list during the four weeks.
Knowledge capture at 125 people: make it routine
At around 125 people, departures happen often enough that a four-week scramble every time isn't sustainable. The fix is to make capture part of how the company runs:
- Every role has documented core tasks with a named owner, before anyone resigns.
- Documentation is reviewed on a schedule, so it doesn't drift as the work changes.
- Offboarding includes a knowledge hand-off. Start from the Employee Offboarding Process and Exit Interview Process templates.
- Tools have owners. A tools registry shows who owns each tool, so access doesn't disappear with a person.
With that in place, a resignation becomes a checklist instead of an emergency. How to document institutional knowledge before senior employees leave covers the long-term version in depth.
How to ask for their help
A departing employee owes you nothing beyond their notice period, and most people want to leave things in good shape. How you ask makes a difference:
- Make it about the team, not the gap. "We want the next person to have it easier than you did" lands better than "we're worried nobody knows how to do this."
- Protect their time. Take other work off their plate so the hand-off doesn't feel like an extra job.
- Give them credit. Name them as the author of the SOPs they help create.
- Keep sessions short and scheduled. Two or three focused hours a week beat an open-ended "brain dump."
- Ask what they wish they'd had when they started. Their answer often points to the most valuable thing to capture.
People who feel respected on the way out tend to stay reachable after they leave, which matters when a question comes up in month two.
What not to do
- Don't ask them to "write everything down" in their last two weeks. You'll get a long doc nobody can follow.
- Don't spread the hand-off across "the team." Every responsibility needs one named successor.
- Don't wait until the last week to start. The hand-off and test week is where most gaps show up.
- Don't skip the exceptions. The routine steps are the easy part; the judgment calls are what the successor needs most.
- Don't let the knowledge sit in recordings. A transcript nobody turns into an SOP is just a long file.
How to capture what they know in Trainual
Trainual turns a departing employee's knowledge into something the successor, and every future hire, can run.
Training: make what one person knows teachable.
- SOPs drafted from recordings. AI-powered SOP creation turns a transcript or rough notes into a first draft the expert can review before they leave.
- One current version. Version history tracks every change as the successor improves the SOP.
- Answers for everyone. A searchable knowledge base and the AI assistant answer questions around the clock, using your company's own information in Trainual.
Operations: run the hand-off like a project.
- Recorded transfer sessions. Meetings with the Notetaker capture each walkthrough, and action items from each session roll over until they're done.
- Clear new owners. Responsibilities move to the successor's role on the role chart, and delegation tools help reassign the rest.
Performance: set the successor up to succeed.
- Expectations from the role. The successor's new responsibilities are written down, so everyone knows what they now own.
- Growth areas tied to training. In Performance, any gap in the successor's skills links to the exact training that closes it.
Together, that's the loop:
- Train: so everyone knows how work should be done.
- Operate: so everyone knows what needs to happen today.
- Perform: so everyone knows what's expected and how knowledge turns into better work.
This is how companies stop depending on one person. Ironsmith Fire went from the top 10% to the top 1% after documenting its processes; as CEO Justin Smith put it, "How many times a day can I answer a question about the same thing?" And ProTec Building Services runs 600+ SOPs across nine offices.
Quick wins to start this week
Quick win #1: Book the inventory hour today
Use the five questions above, and rank the answers by risk.
Quick win #2: Name a successor for each responsibility
One person per responsibility, not a team.
Quick win #3: Schedule the walkthrough sessions
One per high-risk task, with the successor on the call and recording on.
Quick win #4: Draft the first SOP from a recording
Start with the task that would hurt most if nobody could do it next month.
Quick win #5: Add a knowledge hand-off to your offboarding checklist
So the next resignation starts from a plan.
Ready to see how Trainual works?
👉 Book a demo and see how Trainual turns what your most experienced people know into SOPs the whole team can run.
Want a sneak peek?
👉 Read customer stories from teams who stopped depending on one person to keep the company running.
Frequently asked questions
How do you capture what an experienced employee knows before they leave?
Use the time you have in four steps: list what only they do, record them doing each task, turn the recordings into SOPs owned by a named successor, and have the successor run each task while the expert watches. Then review the SOPs 30 days after they leave.
What should a knowledge transfer plan include?
A list of the person's recurring tasks, exceptions, and relationships; a recording or walkthrough of each task; an SOP for each with a named owner; a successor for every responsibility; a supervised hand-off; and a follow-up review after the person leaves.
How long does knowledge transfer take?
Plan on four weeks for a long-tenured employee: one to inventory, one to capture, one to document and assign, and one to hand off and test. Two weeks is possible if you focus on the highest-risk tasks first.
What are the biggest risks when a key employee leaves?
Undocumented processes nobody else can run, customer and vendor relationships that live with one person, judgment calls nobody else has made, tools only they can access, and lost context on why things are done the way they are.
How do you capture knowledge at a 125-person company before it becomes a crisis?
Make capture routine: give every role documented core tasks with a named owner, review that documentation on a schedule, and add a knowledge hand-off to your standard offboarding process, so a resignation becomes a checklist instead of a scramble.
Should you record knowledge transfer meetings?
Yes, with the employee's agreement. A recording or transcript keeps the details people forget to write down, and it becomes source material for the SOP. In Trainual, the Notetaker can join the call and deliver a transcript and summary when it ends.
Who should own the knowledge after the person leaves?
A named successor for each responsibility, not "the team." The successor owns the SOP, keeps it current, and is the person others go to with questions.
What if the employee has already left?
Start with what broke first. Interview the people who worked with them most, reconstruct the highest-risk tasks into SOPs, ask the former employee for a short paid consult if the relationship allows, and document every gap as you find it.




