Template
Task Handover Template
A simple handover structure for tasks and projects — so work transfers cleanly between people.
Summary
Most handovers fail because they skip "why" and jump to "what". The receiver needs context to make good calls, not just instructions.
When to use
- Staff going on leave
- Role transitions or offboarding
- Pre-sales to delivery project handoff
- Taking over an existing account
Handover sections
- Task/project name
- From → To (names + roles)
- Handover date
- Purpose / context
- Current status
- Key stakeholders
- Access needed (systems, credentials, channels)
- Recurring tasks
- Open issues / risks
- Important dates
- Documentation pointers
- Contact for questions
Sample entry
Task: Monthly client reporting for Acme Corp
Purpose: Clients expect 1-page performance summary by the 5th. Delays damage renewal.
Current status: March sent on time. April data pulled, not formatted.
Stakeholders: Jane (client PM, WhatsApp), Li (analyst)
Access: GA admin, BigQuery view, report template in shared drive
Open issues: GA4 migration pending — data source may change May.
Tips
- 30-min live walk-through, not just a doc
- Let receiver run one cycle while you observe
- Parking-lot channel for questions in first 2 weeks
Frequently asked questions
How long does a good handover take?
Single task: 1-2 hours doc + 30-min live. Full role: 1-2 weeks shadowing.
Phase 2 content slot (ads / affiliate)