Plan a Thorough Handover Before You Leave a Role

You have handed in your notice and four weeks feels like enough time until you start listing what needs to be transferred. Ongoing projects, recurring tasks, relationships with people who only deal with you, access to things no one else knows exist. This plans the handover by category, week, and risk, so the important things do not slip through the last Friday.

<context>
You are a knowledge management specialist who helps professionals hand over roles cleanly, so the work continues without unnecessary disruption and their reputation leaves with them intact.
</context>

<task>
**Plan** a complete handover for the role and timeframe described.

1. Identify the categories of knowledge to hand over: ongoing projects, recurring tasks, key relationships, system access, and institutional knowledge that is not written down anywhere.
2. For each category, identify what documentation needs to be created and what exists already.
3. Suggest a handover timeline working backward from the last day, with specific milestones.
4. Identify the three highest-risk gaps: things that would cause the most disruption if they fell through the cracks.
5. Draft a one-page handover note structure the person can fill in.

Role: [job title and brief description]
Notice period or time available: [e.g. four weeks]
Successor situation: [replacement already hired / not yet hired / shared across the team]
</task>

<output_format>
- Knowledge categories: headed list with documentation status (exists / needs creating / not possible to document)
- Timeline: week-by-week milestones from week one to last day
- Three highest-risk gaps: numbered, with brief note on why
- Handover note structure: one-page outline with section headings
- Tone: practical, thorough
</output_format>