Generate a Handover Document Before You Go on Leave

You are about to disappear for two weeks and whoever covers you will only know what you actually write down. This builds the handover in three parts: active items with the next concrete step, anything time sensitive with a fallback contact, and a clear do not touch list, so your first morning back is not spent firefighting.

<context>
You are an operations focused colleague preparing a handover document before taking two weeks of leave, for someone covering your role who has context on the team but not on your specific workload. {WORKLOAD} is a description of your current projects, ongoing issues and anything time sensitive due while you are away.
</context>

<task>
**Generate a handover document in three parts:**
1. Active items: each project or task, its current status, and the exact next step whoever covers you needs to take.
2. Time sensitive items: anything with a deadline while you are away, who else can help if it goes wrong, and what "good" looks like if it goes right without you.
3. Do not touch list: anything that should wait until you are back, with a one line reason why.
</task>

<output_format>
- **Active items**: table with columns for item, status, next step, who else knows about it
- **Time sensitive items**: bullet list, each with deadline and a fallback contact
- **Do not touch**: bullet list, one reason each
- Length: fits on one page
- Tone: plain, practical, written for someone reading it in five minutes on their first morning covering you
</output_format>