Checklist

Succession & Exit Knowledge Retention Checklist

An actionable, interactive checklist to capture, validate, and preserve essential role knowledge during exits, transfers, and reorganizations. Collects links to artifacts, records tacit knowledge, verifies access handling, and captures a sign-off for verification.

Interactive Tool

Succession & Exit Knowledge Retention Checklist

Use this checklist to capture essential operational and decision-making knowledge when someone leaves a role, transfers, or the team reorganizes. Fill the fields, paste links to artifacts, schedule or attach tacit knowledge sessions, and obtain a verification sign-off. Saved submissions become structured entries that your team can review, search, and act on.

Full name of the person leaving the role or changing responsibilities.
Formal role title as used in org charts or HR.
Team, department, or site where the role operates.
Choose the type of change.
Date the role change takes effect (YYYY-MM-DD).
Is a named successor or interim assigned?
Name of successor or interim (leave blank if none assigned).
List the top 6–8 duties that must continue without interruption. Use bullets.
Describe decisions the role makes, recurring workflows, reports, cadence, and primary recipients.
Paste links to standard operating procedures, checklists, diagrams, or repo paths. Note any missing or outdated docs.
Have knowledge transfer conversations, shadowing, or recorded walk-throughs been scheduled or completed?
Summarize hard-to-document knowledge: heuristics, key relationships, escalation cues, troubleshooting tips, and exceptions.
Paste links to recorded sessions, screenshots, whiteboard photos, or attachments.
Have account credentials, system access, and device ownership been handled per policy?
List systems, privileged accounts, service accounts, and any special access notes (who owns recovery, where secrets are stored).
Is there a plan to notify or transition customers, vendors, or stakeholders?
Names, contact preferences, ongoing issues, contracts, SLAs, and handoff plan.
Were operational, compliance, or security risks identified and recorded?
Summarize risks, mitigation actions, deadlines, and owner names.
Select actions completed or required.
Name of the person verifying the checklist and artifacts.
Verifier's role or relationship to the work (manager, knowledge owner).
Date the verifier confirmed completeness (YYYY-MM-DD).
Anything else the successor or knowledge team should know (remaining open items, recommended improvements).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.