How to Do a Role Handover: A Practical Guide
When someone leaves, resignation, parental leave, internal transfer, long sick leave, their undocumented knowledge walks out with them. The passwords in their head, the client who only trusts them, the spreadsheet nobody else understands. A role handover form forces that knowledge out of one person’s head and into a format the next person can actually use.
This guide explains when a handover is needed, how to complete each section so the successor isn’t left guessing, and the mistakes that turn handovers into box-ticking exercises.
When to Use This
Any time someone vacates a role with more than two weeks’ notice, run a formal handover. That includes resignations, internal moves, maternity or paternity leave, sabbaticals, and planned long absences. For sudden departures with no notice period, do a reconstruction handover, interview the team, pull together what the leaver’s files and emails reveal, and document it anyway. Partial knowledge beats no knowledge.
Start the handover as early as possible. Two weeks’ notice is the legal minimum in many places, but it’s barely enough for a complex role. If you know someone is leaving in two months, start now. The leaver’s motivation to document drops sharply in their final week.
How to Fill It Out
Section 1: Role overview. The departing employee describes what the role actually involves, in their own words, not the job description version, the real version. What takes up most of their time? What are the recurring deadlines? What’s the one thing that would surprise a newcomer? This section captures the gap between the official role and the lived role, which is where most handover failures live.
Section 2: Active work and priorities. List every live project, task, or commitment with its current status and next action. Be specific: “Q3 budget review, draft due to Finance by the 15th, waiting on figures from Sales (ask Marco)” is useful. “Various ongoing projects” is not. Include deadlines, stakeholders, and where the relevant files live.
Section 3: Key contacts and relationships. Who does this role interact with regularly, internally and externally? Note not just names but context: “Sarah in Legal reviews all contracts over $10k, email her directly, don’t use the ticket system, she’s faster that way.” Relationship nuances are the hardest knowledge to replace and the most valuable to capture.
Section 4: Systems, access, and passwords. List every system, tool, and account the role uses, with access levels and how to get provisioned. Passwords themselves should be transferred through your company’s password manager or IT, never written in the handover document. Note any shared credentials that need rotating after the departure.
Section 5: Known issues and watch-outs. This is the section people skip and successors need most. What’s currently broken or fragile? Which client is unhappy? What process falls over every quarter-end? Honest documentation here saves the successor weeks of discovering problems the hard way.
Section 6: Suggested priorities for the successor. The leaver’s parting advice: what should the new person focus on in their first 30 days? What can wait? This isn’t about the leaver controlling the role from beyond, it’s about giving the successor a starting orientation so they’re not paralysed by a blank slate.
Common Mistakes
1. Leaving it to the last day. A handover written on the final Friday afternoon is a rushed summary, not a knowledge transfer. Schedule handover working sessions across the notice period, an hour or two each week beats a frantic final-day dump.
2. The successor isn’t involved. The best handovers are conversations, not documents. Have the successor (or interim cover) sit with the leaver, walk through the form together, and ask questions. The document is the record; the conversation is where understanding transfers.
3. Documenting tasks but not judgment. “Send the weekly report on Fridays” is a task. “The weekly report matters because the CEO reads the variance column first, and if marketing spend is over budget you need to have the explanation ready before the Monday meeting” is judgment. Push the leaver to explain the why behind recurring work.
4. No follow-up after departure. Add a check-in at two weeks and one month post-departure. The successor will have questions they didn’t know to ask during the handover. If the leaver is reachable and willing, a short call beats days of confusion. Agree this arrangement before they leave.
Who Needs to Sign Off
The departing employee completes the form, the direct manager reviews it for completeness (managers know what questions to ask, “you didn’t mention the Johnson account, what’s happening there?”), and the successor or interim cover acknowledges receipt. HR should keep a copy on file.
How Often to Review and Update
The handover form itself doesn’t need scheduled reviews, it’s event-driven. But after each handover, ask the successor at 30 days: what was missing? Feed that back into the template. Most companies discover after two or three handovers that they’re consistently missing the same category of information, and one extra prompt in the form fixes it permanently.
Download the free Role Handover Form template.