Most companies have an IT checklist for offboarding: collect the laptop, revoke access, return the parking pass. They do not have a knowledge transfer checklist. This is the gap that costs businesses millions of dollars every year in rediscovered processes, repeated mistakes, and customer relationships rebuilt from scratch.

The average cost of replacing an employee ranges from 50% to 200% of their annual salary, depending on the role's complexity. A significant portion of that cost is not recruitment and onboarding — it is the knowledge that walks out the door when the person leaves. Vendor relationships the employee personally managed. Nuanced client preferences built over years of interaction. Processes that only existed in that person's head because they never got documented.

This checklist solves the knowledge transfer piece. Use it for any offboarding scenario: voluntary resignation, retirement, termination, or role change. Start it two weeks before the last day. The goal is to leave behind a usable record of what the person knew, not a stack of half-finished documentation they assembled under pressure.

Phase 1: Pre-Departure Interview (Days -14 to -7)

The most valuable knowledge transfer happens before the exit process starts feeling urgent. Schedule a structured conversation — one to two hours — focused on capturing the person's judgment, not just their tasks.

Knowledge Capture Interview Topics

  • ✓
    Map their decision-making criteria What factors do they weigh when making the key decisions in their role? What signals tell them a situation is risky vs. routine?
  • ✓
    Document vendor and partner relationships Who do they contact for what? What are the unwritten terms? Who is difficult and how do you handle them?
  • ✓
    Identify undocumented processes What do they do that no one else knows how to do? What takes them five minutes that would take someone else a week to figure out?
  • ✓
    Capture client relationship history What is the history with each major client? What are their sensitivities? What went wrong in the past and how was it managed?
  • ✓
    List ongoing projects and their current states Where does each project stand? What decisions are pending? What happens if those decisions are delayed?
  • ✓
    Identify institutional warnings and patterns What mistakes have they seen repeated? What would they warn a new person about in the first week?

Phase 2: Documentation Sprint (Days -7 to -2)

After the interview, the departing employee should have three to five days to document what they learned in their own words. Do not give them a template that forces their knowledge into someone else's structure. Let them capture it naturally — their decision frameworks, their process shorthand, their war stories.

Documentation Deliverables

  • ✓
    SOPs for recurring processes List the top 10 tasks they do on a regular basis, with enough detail that someone new could complete them without asking questions.
  • ✓
    Contact directory with context Not just names and phone numbers — who to call for what, which contacts are critical vs. routine, who is hostile to the company.
  • ✓
    Password and account inventory All shared accounts, credentials stored in their browser, software licenses, and access levels they personally manage.
  • ✓
    Active project briefs One-page summaries of every active project: current status, next steps, decision owners, and what happens if it stalls.
  • ✓
    Onboarding guide for their replacement What they wish someone had told them on day one. The things that only become obvious after three months on the job.

Phase 3: Last Week Handoff (Days -1 to Last Day)

The final week should be used for live handoff, not documentation. The departing employee walks through their active work with the person taking over — real-time, question-and-answer, with the successor doing the work under supervision.

Last Week Activities

  • ✓
    Shadow on critical tasks The successor observes and participates in the departing employee's three most important recurring tasks — live, with questions.
  • ✓
    Introduce key contacts The departing employee introduces the successor to the five to ten most important external relationships personally, while still in the role.
  • ✓
    Review open items together Go through the inbox, the active projects, the pending decisions — the successor takes notes on what was not documented.
  • ✓
    Document known gaps After the handoff, the successor documents what they still do not know and the departing employee answers those questions before their last day.
  • ✓
    Confirm offboarding IT checklist Laptop, email access, Slack, shared accounts, building access — all confirmed revoked or transferred after the knowledge handoff is complete.

What Most Companies Skip

The biggest mistake in offboarding is treating knowledge transfer as a documentation exercise. Documentation captures what the person expects to write — it rarely captures what someone else needs to know. The real knowledge is in the judgment: the years of accumulated context that makes a senior person effective. That does not appear in a process document.

The only reliable way to capture judgment is through conversation. Ask the person how they think about their job, not what they do in it. The difference is the difference between a checklist and an apprenticeship.

AI-powered knowledge capture tools like BrainVault can structure these conversations automatically. Instead of asking the departing employee to write documentation, you conduct a structured interview — questions designed to draw out the tacit knowledge — and the AI generates usable documents from the transcript. This approach captures the judgment that does not appear in process documents.

Why This Checklist Matters

The cost of a knowledge gap after an employee leaves is not just the time to recreate the information. It is the cascade of decisions made without context: vendors who were managed in ways that are now unknown, client preferences that were never documented, institutional knowledge about what has worked and failed in the past that leaves with the person who lived it.

A thorough knowledge transfer checklist does not eliminate all of that cost. But it reduces it significantly — and it signals to remaining employees that the company takes institutional knowledge seriously. That matters for retention too.

Continue Reading

Automate Your Offboarding Knowledge Capture

BrainVault's AI interview mode conducts structured knowledge transfer sessions with departing employees and generates usable SOPs automatically. Takes under an hour.

Start Free — No Credit Card Required