When someone leaves, most of what they know is not written anywhere. This template captures it before it walks out the door. The departing owner fills it in during the notice period, then walks the successor through it live — the walkthrough matters as much as the document.

How to use this template

• Start it the day the departure is confirmed; do not leave it for the final week.
• The departing owner writes, the successor reads and asks questions, the manager verifies completeness.
• Link out to existing docs instead of duplicating them — this is the map, not the territory.

Owner and scope

• Departing owner: {{Departing owner name}}, {{Role title}}
• Successor or interim owner: {{Successor name}}
• Handover period: {{Start date}} to {{Last day}}
• Scope of this handover: {{One sentence describing the areas covered}}

Systems and access

Every system the successor needs, what it is for, and who grants access.

Key contacts

The people the successor will need — internal and external — and why.

In-flight work

Everything currently open, its state, and the very next step. Be specific — "in progress" is not a status.

Recurring responsibilities

Tasks that happen on a rhythm and would silently stop without an owner.

Runbooks and documentation

• {{Runbook or doc title}} — {{Where it lives}} — {{What it covers and how current it is}}
• Undocumented know-how the successor should learn in the walkthrough: {{List the things that exist only in your head}}

Known risks and open questions

• {{Risk or open question}} — why it matters: {{Impact}} — suggested handling: {{Suggestion}}

Handover sign-off

• Live walkthrough held on {{Walkthrough date}} with {{Attendees}}.
• Successor confirms access to every system in the table above.
• Manager confirms every in-flight item and recurring task has a named new owner.
• Open items that remain after the last day, and who chases them: {{Remaining items and owner}}