Handover Document Template for Job Changes and Holiday Cover
By the SystemaFlow team · Updated November 2026 · Share this
Someone's handed in their notice, or they've booked two weeks away. Either way there's a Friday coming when they stop answering, and a good part of how things work here goes with them.
A handover document is a written record of someone's live work, so the next person knows what's due, who's involved, where things are kept and what they're allowed to decide. Write it while the person who knows can still answer questions, and have the next person try the work before they go.
This post covers two situations: someone leaving or changing role, and someone going away for a while. Near the end there's a short section on project handovers, to a colleague or to the client. Building and shift handovers have their own formats, and we don't cover them here.
Here's the example we'll use. Tamberly Studio is a small design studio we made up for our training material, and Priya runs it. The details are invented.
Which kind of handover do you need?
The template below works for both. What you lean on differs.
| Leaving or changing role | Holiday or other time away | |
|---|---|---|
| Who takes it | A named person, for good | One or more stand-ins, for now |
| What matters most | Recurring duties and what only this person knows | What falls due, and what the stand-in can decide |
| Access | Moved to the new person, removed from the old | Given for the period, removed on return |
| How you test it | The new person does each duty once while the other is still around | You walk the stand-in through it |
| How it ends | Sign-off, then a check a few weeks later | A short catch-up on the first day back |
If someone's leaving, your notice period sets how long you've got. Rules on notice vary by country and contract, so check yours. Nothing here is legal advice.
Handover document template (copy this)
Copy these headings into Word or Google Docs and delete what you don't need. Link to documents that already exist. There's no need to rewrite them.
| Section | What to write |
|---|---|
| 1. The basics | Who's handing over, who's taking over, the area of work, the dates, and whether they can be reached (and how) |
| 2. Live work | Everything in progress: status, next step, due date, who's involved |
| 3. Recurring duties | Every job that comes round: how often, how it's done, when it's next due |
| 4. Key dates | Deadlines, renewals, meetings and reports in the period |
| 5. People | Clients, suppliers and colleagues the next person will deal with, and what each of them needs to be handled well |
| 6. What they can decide | What the next person can settle alone, and what waits or goes to someone else |
| 7. Where things are kept | Files, tools and who can open them. Never the passwords themselves |
| 8. Known problems | What's stuck, what's fragile, what's about to go wrong |
| 9. How it's done here | The unwritten standards that only come out when someone gets them wrong |
| 10. Sign-off | Date it was walked through, the next person's confirmation, and the date you'll check again |
Section 2 and section 3 work best as tables. Copy these:
| Live work | Status | Next step | Due | Who's involved |
|---|---|---|---|---|
| Recurring duty | How often | How it's done (link) | Next due |
|---|---|---|---|
If a duty has no write-up to link to, that's the one to write first. A one-page SOP is enough.
A handover example: two at Tamberly Studio
This is a made-up example with two handovers in it, one short and one permanent.
Priya's two weeks away. She's off from Monday 7 to Friday 18 September, back on the 21st, with Marcus as her main stand-in. She can be reached by text, only if it truly can't wait. The most useful part of her handover is what each person can decide.
| Area of work | Who stands in | What they can decide | Leave for Priya's return |
|---|---|---|---|
| Client projects | Marcus | Approve final designs, move dates by up to a week | Anything that changes a fee |
| Clients and enquiries | Aisha | Reply to clients, book new enquiries in for a call | New proposals |
| Timesheets and bills | Grace | Chase timesheets and late payments, prepare bills | New suppliers |
| Client websites | Leo | Fix faults, make small agreed changes | Changing a hosting supplier |
Her guide also says where things are kept. Passwords live in the company password manager, and Marcus, Grace and Leo each have their own login.
The hardest line to write was what Marcus can decide alone. Her standards needed saying too: "Call first with bad news." A stand-in can follow steps, but how you like things done has to be said out loud.
Invoicing moving to Grace. This one's permanent, so a document alone won't do it. Priya writes the job on one page, then hands it over in three stages: Grace watches in August, they do it together in September and Grace does it alone in October. Priya still answers for the result until that's finished. You can see how that shows up on a RACI chart.
What gets missed in a handover?
The live projects usually make it onto the page. These are what tend not to.
Anything that doesn't come round often. Annual renewals, quarterly returns and the report someone asks for twice a year. Go back through a full year of the calendar if you can.
The access. Someone discovers on Monday that the supplier portal is in the leaver's name. List every login the job needs and sort each one out while the person's still there.
Half-finished conversations. The client who's been promised a call and the supplier who's waiting for an answer. They're rarely in a task list.
The limits. Without section 6, a stand-in either asks about everything or decides something they shouldn't have.
Who's been told. Clients, suppliers and colleagues need to know who to go to, and an out-of-office should name that person.
What only one person knows. Which client always pays late, and which job always changes at the last minute. This is the invisible work that nobody thinks to mention, and the best way to get at it is to ask "what would catch me out?"
Checking it worked. A handover that ends on the person's last day never finds out what was missed. Book a date a few weeks on, or a catch-up on the first morning back.
How ready is your handover?
Tick each one that's true for the handover you're working on now, or the last one you did.
Would this handover survive without you?
Be strict. If you'd have to explain it out loud, it doesn't count yet.
Project handovers: to a colleague or to the client
A project handover template is the same document with a few extra parts, because a project has a scope and an end date that a role doesn't.
Handing a project to a colleague partway through. Use the template above and add four things:
- The scope as agreed, including what's out, so the new lead doesn't promise it back in.
- Decisions made so far, and why, so settled questions don't get reopened with the client.
- Changes and extras agreed, and whether each has been priced and approved. A change request log makes this a copy and paste.
- Time or budget used against what was planned.
Then introduce the new lead to the client yourself, on a call if you can.
Handing a finished project to the client. Now the person taking over is the client, who'll run it without you. Their handover pack should cover what was delivered and where the files are, every account and login moved into the client's name, how to look after it, what support is included afterwards under your agreement, anything still outstanding with an owner, and a sign-off. Walk them through it, as you would a stand-in.
A made-up but typical case: a small web design firm finishing a site hands over the domain and hosting accounts in the client's name, a one-page guide to adding news posts and the date the support period ends. The closing steps at the end of the client onboarding process cover the rest.
How to write a handover document that gets used
- Start early. Begin the day a leaving date or a holiday is confirmed. Handovers written on the last afternoon are lists of whatever came to mind.
- Work from evidence. Look through the calendar, task list, shared files and sent messages. Memory alone misses what's quiet at the moment.
- Get the next person to ask questions. They know what they don't know. Have them read it and mark everything that isn't clear.
- Let them do the work. For a permanent move, watch them do each duty once. Handing work over well takes the same steps here as anywhere else.
- Tell everyone at the same time. Say who to go to from which date.
- Keep it. The next new starter can use it too, alongside your onboarding templates.
If a job only leaves your business when someone resigns, it's probably been sitting with one person for too long. Writing up a few key jobs while nobody's leaving is much easier than doing it in a notice period. What to systemise first will help you choose.
Want the full version?
When work moves for good, the Knowledge Handoff Sheet in the Knowledge and Handoff Hub pack lists the recurring duties, work in flight and access to move, has the receiver do each duty once and ends with a sign-off. It's in the Team and Talent Systems Core Vault. For planned time away, the Handover Checklist in the Operational Clarity pack, part of the Business Foundations Core Vault, names cover for every deadline. Both are done-for-you templates in Word and PDF.
See what's in the Team and Talent Systems Vault →Or get all 352 systems, and every one we add later, with Masterworks: $999, paid once.
Was this helpful?
Frequently asked questions
- What should a handover document include?
- Who's handing over to whom and when, the live work with next steps and dates, recurring duties, key contacts, what the next person can decide, where things are kept, known problems and a date to check it's worked.
- How do I write a handover when I'm leaving a job?
- Start as soon as your leaving date is agreed. Go through your calendar, task list and sent messages for what recurs and what's live, write it up by area of work, then walk the next person through it while you're still there.
- How long should a handover document be?
- As short as it can be while the next person can still do the job. Link to existing documents and don't rewrite them. A holiday handover might be a page or two, and someone's whole role will take more.
- Should I put passwords in a handover document?
- No. Say where access is managed and who can open what. Give the next person their own login, or delegated access, through whatever your business uses.
- What if someone leaves before writing a handover?
- Their manager pulls one together from the calendar, the task list and the shared files, then lists what's still unknown. Tell clients and suppliers who to contact early, because they'll be the first to notice a gap.
- Do I have to do a handover when I leave?
- That depends on your contract and where you work, and rules on notice periods vary by country. We can't give legal advice, so check your contract and local guidance. A good handover is worth doing either way.
