Handover Document Before Leave

A handover document is a short written note you leave before going on leave, telling the people covering for you what is open, where each item stands, what you decided and why, and what can wait until you are back. To write one, start with your open questions, then list your open work, recent decisions, and who may decide what while you are away.

Most handover documents are written on the last afternoon, in a hurry, as a list of tasks. They tell the backup what exists. They rarely tell them what to do when the first real question arrives, which is the moment the handover is for.

The handover document template

Section	What to write
Dates	First day away, last day away, the day you are back, and whether you will check messages
Open questions	What you were about to decide, the options, and what you would choose
Open work	Each item, where it stands, the next step, and who owns it now
Recent decisions	What you decided in the last few weeks, and why
Can wait	Items your backup may leave until you return
Decision limits	What your backup may decide alone, and what goes to whom
People	Who is waiting on you, and who you were waiting on
Recurring tasks	Reports, meetings and deadlines that fall while you are away
Links	Tickets, docs, threads and dashboards, in one place
Urgent contact	Who to go to if something cannot wait, and how to reach them

Why open questions go first

Your backup can open a ticket and see that a task is done. What they cannot see is the decision you were halfway through: the vendor you were about to pick, the bug you suspected was in the cache, the reply you were drafting to a difficult customer. Those are the questions that land on them on day two.

For each open question, write the options, what you would choose, and why. Your backup can then decide with your reasoning instead of starting over, or knows enough to make it wait.

What to include before a vacation

A short holiday needs a short handover. For a week away, the essentials are the open questions, anything with a deadline while you are gone, and who to ask instead of you. Add a line for each recurring task, such as the weekly report or a standing meeting, saying whether someone else does it or it is skipped.

For longer leave, add more history: the decisions from the last month and the reasons behind them, so your backup can answer "why did we do it this way?" Team-level coverage, with a backup for each area of work, belongs in a vacation coverage plan.

A last-day checklist

1. Walk your backup through the document, in person or on a call. Fifteen minutes is enough.
2. Set your out-of-office reply to name who to contact for what.
3. Tell the people who are waiting on you who to ask instead.
4. Close or pause anything you do not need to hand over.
5. Move the document somewhere your backup can find it without asking.
6. Decide whether you will check messages. If not, say so.

What a handover never manages to carry

Even a thorough handover misses the reasons. It records what you decided, not the conversations, half-formed doubts and quiet context that led there. The first question your backup cannot answer is usually a "why?" question. That is where they are tempted to message you on holiday.

Two habits close most of the gap. Write a sentence of reasoning next to every recent decision in the handover. And keep that habit going when you are not on leave: a team that writes down decisions as it goes has most of its handover written before anyone books time off. If decisions in your team are scattered across chat, the guide to a decision log is a good place to start.

Handover document vs coverage plan vs engineering handoff

A handover document is personal: your work, your open questions, your decisions. A coverage plan is for the team: which backup covers which area. An engineering handoff is the daily version, for passing work between shifts or time zones; see the engineering handoff template. Most people going on leave need the first two.

For the full picture of covering for someone on leave, including what to ask for when you are the backup, see the guide to covering for a teammate on leave.

Where StandIn fits

StandIn is a personal knowledge base, built on the work that you already do, that answers your teammates when you're away, in chat and email. While you are on leave, your StandIn answers questions from your handover and your work, in your words, with a source under every answer. When the answer is not there, it never guesses: it says so and points to the person who knows. See how it can retire your out-of-office.