Checklist

Knowledge Capture Checklist for Role Transitions

An interactive, saveable checklist and guided interview form to capture critical tacit knowledge during role changes and departures. Includes artifact mapping, shadowing verification, systems/access checks, risk ratings, and a handover sign-off section.

Interactive Tool

Knowledge Capture Checklist for Role Transitions

This guided checklist helps preserve essential operational, contextual, and tacit knowledge when someone changes roles or leaves. Use it during a structured handover interview and shadowing period. Saved responses are stored for later review, follow-up, and organizational learning.

Full name as listed in HR.
Role being handed over.
Enter ISO date (YYYY-MM-DD) or clear text. The platform may later support date fields.
Enter expected last working day or role-change effective date.
Who will take primary responsibility after transition.
List the most time-sensitive or mission-critical duties the role performs.
What is done every day, including timing, systems used, and key steps.
Recurring tasks that happen less frequently and who else is involved.
For each item, include name, purpose, storage location or link, owner, and update frequency. Examples: runbooks, templates, reports, scripts.
List system names, account types, who manages access, and any credentials/vault references (do not paste secrets here).
Check completed items and add notes below.
Was an overlap arranged where successor shadowed the departing person?
Record what was observed, gaps noticed, or suggested improvements.
Name, role, relationship, and why contact matters (e.g., daily escalation, vendor support).
List risks, typical symptoms, likely root causes, and current mitigations.
Be specific about current status, blockers, and recommended next actions.
Decisions that could materially affect outcomes in the short term.
Required confirmations to complete the handover.
List who will do what, by when, and any dependencies.
How critical is preserving this knowledge to ongoing operations?
1.0 10.0
How risky would an incomplete handover be for operations?
1.0 10.0
Use formal HR agreements and respect privacy — record any limits.
Anything else not covered above.
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.