The 30-Day Knowledge Transfer Checklist When an Employee Leaves

Someone on your team just gave notice. They're critical to the operation. You have 30 days — maybe less — to capture years of accumulated knowledge before it walks out the door.

Here's the checklist that actually works. Not the idealized HR version. The one that acknowledges reality: departing employees are mentally checked out, you're scrambling to backfill, and knowledge transfer always gets pushed to the last minute.

Days 1-3: Immediate response

☐ Schedule the knowledge capture sessions

Don't wait. Get these on the calendar now, before their final weeks fill up with transition tasks and goodbye lunches.

Block time for:

2-3 focused interview sessions (30-45 min each)
1 systems walkthrough (passwords, access, where things live)
1 relationship handoff (key contacts, client context, ongoing projects)

☐ Identify what you're most at risk of losing

Talk to their manager and teammates. What does this person know that nobody else does?

Critical areas:

Client relationships and history
System knowledge and workarounds
Ongoing projects and context
Tribal knowledge ("why we do it this way")
Key contacts (internal and external)

☐ Decide who's inheriting what

Don't try to replace them 1:1. Split their responsibilities across 2-3 people based on who's best positioned to take each piece.

This isn't just "who has time" — it's "who needs this knowledge to do their job next month."

Days 4-10: First knowledge capture session

☐ Interview them about their primary responsibilities

Use AI-guided interviews (like Understudy) or do it manually. Don't ask them to write documentation — have a conversation.

Questions to ask:

"Walk me through a typical week. What do you do daily, weekly, monthly?"
"What are the 3-5 most critical things you're responsible for?"
"What breaks if you're not here?"
"What questions will your replacement ask in their first month?"

☐ Capture the decision-making frameworks

This is the stuff that never makes it into written docs:

"When do you escalate vs handle it yourself?"
"How do you prioritize when everything is urgent?"
"What's your process for X? What about when Y happens?"

☐ Document the edge cases

Every role has weird exceptions and one-off situations. These are gold:

"What are the 3 most common problems you deal with, and how do you solve them?"
"What always trips up new people?"
"What's the one thing you wish someone had told you when you started?"

Days 11-17: Systems and access

☐ Create a systems inventory

Every tool, login, integration, dashboard they use. Don't assume you know them all.

For each system, document:

What it does and why it's used
Where the credentials are (password manager, shared doc, etc.)
Who needs access after they leave
Any quirks or things that break

☐ Walkthrough of critical workflows

Screen-share session where they show you how things actually work:

"Show me how you run the monthly report"
"Walk me through how you handle a customer escalation"
"What do you do when the integration breaks?"

Record it. Even if you're also taking notes.

☐ Transfer ownership in systems

Update account owners, admin access, notification emails. Do this now, not on their last day when you're already stressed.

Days 18-24: Relationship handoff

☐ Map the key relationships

Who do they talk to regularly? Who depends on them? Who do they depend on?

For each key relationship:

Name and role
Why this relationship matters
Current status / ongoing projects
Context the new person needs to know
Any sensitivities or important history

☐ Introduce their replacement

Don't wait until they're gone. Warm handoff is 10x better than cold.

Internal: Email intro, brief meeting, explain the transition External (clients, vendors): Joint call where departing person endorses the new contact

☐ Document ongoing projects

Everything in flight needs to be handed off with context:

For each project:

What it is and why it matters
Current status
Next steps
Blockers or risks
Who's involved and who cares about it

Days 25-30: Final capture and loose ends

☐ Second knowledge capture session

Now that you've processed the first session, you'll have follow-up questions. This is where you catch the stuff that didn't come up the first time.

Questions that work well here:

"We've been going through your notes. Can you explain more about X?"
"What did we miss?"
"If your replacement calls you in 3 months with a question, what will it be about?"

☐ Password and access audit

Verify credentials for everything. Test logins. Don't discover on day 31 that a critical password is wrong.

Shared passwords that need to be changed after they leave? Change them now and document the new ones.

☐ Final Q&A with the team

Open session where anyone who'll be affected by their departure can ask questions.

This catches edge cases: "Oh yeah, you need to know about the weekly report I send to finance" or "The client database does this weird thing on the 1st of the month."

☐ Create the emergency contact agreement

Be realistic: there will be something you didn't capture. Set expectations now:

"Can we call you in the first month if something critical comes up?"
"What's the best way to reach you?"
"Is email okay, or would you prefer we don't contact you at all?"

If they're willing to be a resource, offer to pay for their time. ($200/hour consulting rate for the first 3 months is cheaper than the cost of not knowing.)

After they leave: Week 1-2

☐ Test the documentation

Have their replacement (or someone unfamiliar with the role) try to follow the playbooks you created. Where do they get stuck?

This is your chance to fill gaps while the knowledge is still fresh.

☐ Update with real-world usage

The first two weeks will reveal what's missing. Keep a running list of questions that come up and update the documentation.

☐ Scheduled check-in with their replacement

Week 1 and week 2 after departure: "What's unclear? What are you struggling with? What questions can't you answer?"

Add those answers to the playbook so the next person doesn't hit the same gaps.

What makes this different from the usual "exit interview"

Most companies do exit interviews on the last day. The departing employee is mentally gone. The HR person asks generic questions about "why are you leaving" and "how can we improve."

That's not knowledge transfer. That's box-checking.

Real knowledge transfer:

Starts immediately when they give notice
Focuses on tribal knowledge, not feelings
Captures decision-making, not just steps
Involves the people who will inherit their work
Produces usable documentation, not just meeting notes

The role of tools

You can do this manually — structured interviews, Google Docs, recorded walkthroughs. It works, but it's slow and requires discipline.

AI-powered tools like Understudy make this much faster:

Structured interviews that probe for edge cases
Automatic conversion to step-by-step playbooks
Version control and searchable documentation
Easy handoff to the replacement

The time savings matter because knowledge transfer always competes with "just getting work done." Faster capture = more knowledge preserved.

Common mistakes to avoid

Waiting until week 3 to start. By then they're coasting, their calendar is full, and you're in panic mode. Start on day 1.

Asking them to "write everything down." They won't. They'll write 3 pages of high-level notes that don't help. Interview them instead.

Only capturing the happy path. The value is in the edge cases, exceptions, and "here's what you do when X breaks." Probe for those.

Not involving the people who'll inherit the work. The new owner should be in the room for these sessions, asking their own questions.

Assuming you got everything. You didn't. Plan for follow-up questions and ongoing refinement.

The hidden value

Done right, this checklist doesn't just prevent knowledge loss when someone leaves. It reveals:

Single points of failure. If you're scrambling to capture knowledge from one person, that's a risk you should have addressed earlier. Now you know.

Undocumented processes. Half the stuff you learn during exit knowledge transfer should have been documented already. This is a forcing function to finally capture it.

Succession planning gaps. If nobody can step into this role, that's a problem. Use this as a template for cross-training and redundancy.

The best companies don't wait for someone to quit to do this. They capture knowledge continuously. But realistically, turnover is often the catalyst that finally makes it happen.

Start now

If someone just gave notice, you're already late. Get these sessions scheduled today.

If nobody's leaving right now, use this checklist anyway. Pick your most critical person — the one whose departure would hurt the most — and capture their knowledge now, while they're still here and motivated to help.

That's the real win: treating knowledge transfer as a normal part of operations, not a crisis response.

Capture your first exit interview with Understudy →

Download the checklist

Want this as a printable PDF or Notion template? Get the knowledge transfer checklist →