Role Handover Document Template
Four documents and five sheets that read the recurring commitments out of a calendar, then put a real deadline against every object the account owns.
Free download · No account needed
Owned Object Register
P. Ostrander, Client Operations Manager
| Last day | 30 October 2026 |
| Successor | S. Krayem |
| Objects she owns | 11 |
| Distinct expiry dates | 4, and the last day is only one of them |
What expires, and when
| Object | What deleting the account does to it | Deadline |
|---|---|---|
| Secondary calendar: Client Renewals | Goes with the owner, and no further transfer is possible afterwards | 30 Oct |
| Two-factor seed for the supplier portal | Lost with her phone, so the portal is unreachable by anyone | 30 Oct |
| 214 Drive files she solely owns | Held 20 days behind restoring the user, then permanent | 30 Oct |
| Mailbox | Kept 30 days, then removed unless a hold was applied first | 29 Nov |
| Cloud project: merridale-pipeline-dev | Bindings linger up to 30 days and the project is orphaned | 29 Nov |
| Group: client-ops@ | Survives her, and keeps routing mail to nobody | none |
| Shared drive: Client Ops | Survives, because the organization owns the files rather than a person | none |
The column no handover checklist has
A knowledge transfer document is a record of what she knows. This one is a record of what she owns, which is the half carrying a date.
The group and the shared drive earn rows precisely because they never expire. Every object moved into that state is one this register stops having to carry.
Nobody who has run the same reconciliation on the last working day of the month for four years experiences it as a task. Ask them to list their recurring work and that row will not appear, which is why every handover template on the internet asks the one question that cannot be answered. So this one reads twelve months of calendar instead, private holds and declined invitations included, then shows them the list and asks what is missing. Recognition works where recall fails.
Then the half with a deadline. What somebody knows can be captured late and still be worth something; what somebody owns runs on a clock that the account deletion starts. Drive files and the primary calendar sit twenty days behind a restore before permanent deletion, and a Microsoft mailbox is gone in thirty. Secondary calendars go on the last day, with no transfer possible afterwards. The supplier portal registered in her name has a password reset going nowhere. Eleven objects, eleven dates.
An internal move revokes nothing at all, so `Review` is a verdict in its own right: NIST asks for a fresh confirmation of ongoing operational need when somebody is reassigned rather than terminated. Send River the calendar export and the last day, or take the documents and CSV sheets blank and work them by hand, next to the procedure library the successor inherits and the audit that ranks what nobody wrote down.
What's in the pack
Recurring Commitment Calendar
One row per series, built from twelve months of calendar rather than from an interview. It carries the organizer, because that is what decides survival, and the next occurrence after the last day, because a quarterly commitment falling in January is invisible to a handover conversation held in October.
Owned Object Register
The countdown. One row per object the person owns, with what deleting the account actually does to it and the date that happens. Shared drives and groups get rows too, precisely because they do not expire, which makes them the destination every other row is heading for.
Task Inventory
One row per task with the source it was found in: a calendar series, an inbox rule, an approval routing, a pager rota. A column records whether the leaver named it themselves, and the count of rows where they did not is the honest measure of how much was about to be lost. A task exactly one person can perform is a continuity risk before it is a handover problem.
Access and Account List
Revocation and retention with more than two verdicts. Freeze rather than delete, retain then delete in sequence, re-register against a role address, and Review for the internal move where nothing expires and nothing prompts anybody.
Open Items Register
In-flight decisions with a named owner for the day after, a due date, and what happens if it slips. Verbal commitments carry a confirm-or-withdraw date on or before the last day, and unassigned is a value the sheet is designed to hold rather than hide.
What Expires and When
The vendor behaviour behind every deadline in the register. The twenty-day and thirty-day windows, plus the sequencing rule that makes a hold worthless when applied late. The search that finds transferred files stranded inside unshared folders. And the three categories with no admin console behind them at all.
Handover Standard
Four rules. Read the commitments rather than asking for them, name a successor and a date on every row, treat validated as a performance rather than a reading, and separate what expires from what merely needs writing down. The internal move gets its own trigger, the same trigger the operating handbook uses to recheck who actually chairs a room once someone new sits in it.
Handover Document and Relationship Notes
A filled handover for a client operations manager, so the format is arguable against something real. The relationship notes narrow a contact list down to the four things that genuinely transfer, including the history the counterparty remembers and you do not, which is the sort of context a written-up walkthrough never captures.
How to use it
- 1
Open in River, or take it blank
Install the pack in River and hand it the calendar, or download the four documents and five CSV sheets and work them yourself.
- 2
Send the calendar first
Twelve months, exported or shared, private holds and declined invitations included. It is the ask nobody expects and the one that finds the annual commitment nothing else records.
- 3
Show them the list
Hand the leaver the commitments already found and ask what is missing. Recognition surfaces the work that four years of routine stopped registering as work.
- 4
Date every object, then sequence
Each owned object gets its real expiry date instead of the last day. Holds land first, seeds and vaults next, calendars before the last day, deletion last.
Frequently asked questions
Is this free, and what do I actually get?
No cost, no signup, no card. You get four documents and five spreadsheets. The AI half is optional: hand River a calendar export and a last day, and it builds the commitment list and puts a date against every object that expires. The rest of the template library works the same way.
Why start with the calendar instead of interviewing the person?
Because the tasks most likely to be lost are the ones the leaver has stopped noticing. A quarterly true-up run for three years reads as background, not as a responsibility. Twelve months of calendar surfaces it as a row, and then the conversation becomes what is missing from this list rather than what do you do.
What is the difference between what someone knows and what they own?
Knowledge has no deadline. It can be captured badly in the last week and still be useful in March. Ownership expires: a calendar, a mailbox, a solely owned file, a vendor login, a two-factor seed and a cloud project each run out on a different date, and every one of those clocks starts when the account is deleted.
Does this work for an internal move rather than a departure?
That is the case the pack treats as first class, because nothing expires on a transfer and no admin console prompts anybody about it. The access sheet carries Review as a verdict alongside revoke and retain, and the person keeps every right from the old role plus the new ones until somebody deliberately looks.
What order should the last two weeks run in?
Holds first, because a retention policy applied after the account is gone converts nothing. Then shared credentials out of personal vaults and two-factor seeds re-enrolled. Then vendor portals onto role addresses, then the secondary and group calendars, then a second owner on every cloud project. Delete the account last.
How do I know a task was actually handed over?
The successor has performed it once, on a real occurrence, with the leaver still reachable. That is what the Validated column holds, as a date rather than a tick. A task with a name against it and no date is a paragraph somebody read, and it surfaces the first time the task comes round.
What about the promises they made that were never written down?
They get rows with a confirm-or-withdraw date on or before the last day. A credit offered on a call, a rate increase approved verbally, an alert threshold quietly raised in July: the counterparty remembers all three and nothing on your side records any of them. Writing the process up properly is the follow-on job.
Find the commitment nobody mentioned
Take the documents and CSV sheets blank, or install this pack in River and send it twelve months of calendar plus a last day.
Edit with AI