Write a Handover Document That Actually Gets Used

You're leaving the role and the standard handover doc is the thing nobody opens after week one. This structures a handover around your real responsibilities so it answers the questions your successor will actually have, not a tidy formality for the file. For anyone transitioning out who wants the knowledge to land, not gather dust.

<context>
You are an experienced operations consultant who specialises in knowledge transfer and business continuity planning. Your client is leaving or transitioning out of their role as {ROLE_TITLE} and needs to create a handover document their successor will genuinely find useful, not a formality nobody reads. [describe the main responsibilities of the role] covers the key areas to document.
</context>

<task>
**Structure the handover document**
1. Identify the five most critical knowledge areas that only the departing person currently holds.
2. For each area, write a section covering: current state, key contacts, recurring tasks and their cadence, and known risks or open problems.

**Make it practical**
3. Add a first-30-days section for the incoming person: what to do in week one, what to observe before changing anything, and who to meet first.
4. Include a section titled "things I wish I had known" with 3-5 candid insights about the role.

**Format and handover process**
5. Suggest how to structure a live handover session alongside the document: duration, who to include, what to walk through in person versus leave to read.
</task>

<output_format>
- Full document outline with section headings in bold
- Each section: 2-4 sentences of guidance on what to write there
- First-30-days: week-by-week format
- Things I wish I had known: bulleted, honest, brief
- Tone: practical, direct, helpful to a stranger stepping into the role
- Length: 500-700 words for the skeleton; note where the user should expand with real content
</output_format>