The short version
- A handover document stops the questions it anticipated. You get messaged about the ones it did not, which is most of them.
- Write it in four sections: in flight, decisions someone else can make, decisions that wait, and who covers what.
- The reason people message you anyway is that the document cannot be questioned. Nobody can ask a PDF a follow-up.
- Your brief is the handover, and your StandIn answers from it while you are off. That is the difference between a document and coverage.
Most people write a decent handover before annual leave and still get messaged on day three. The document was not the problem. The problem is that a document answers a fixed set of questions, and the questions that arise while you are away are, almost by definition, the ones nobody predicted.
"I write the handover doc and get pinged anyway."
Why you get messaged anyway
Three reasons, in order of how often they apply.
The specific question is not in the document. You wrote about the three things you expected to matter. On Tuesday a customer asks something about a decision you made in June, and nobody knows the reasoning.
The colleague cannot tell whether the document covers it. Reading a ten-page handover to find out whether it addresses their question is more work than messaging you, so they message you.
They are not sure they are allowed to decide. This is the most avoidable one. Most holiday messages are permission-seeking rather than information-seeking: someone could handle it and does not know whether they should.
The handover template
1. In flight. Each piece of work, one or two lines: where it stands, what happens next, who is picking it up.
2. Decisions others can make. The specific calls someone else may make while you are away, and who makes each one. Be generous here.
3. Decisions that wait. What should not be decided without you, and what happens in the meantime. Naming these is what makes section two credible.
4. Who covers what. One name per area, plus who to go to if that person is also away.
One page. If it runs longer, you are documenting your job rather than handing over your fortnight.
The section people skip: decision limits
Sections one and four get written. Two and three usually get a vague line about asking the team lead, which is where the holiday messages come from.
Be specific and generous. "Discounts up to 15 percent: Marc decides. Above that: it waits for me, tell the customer they will have an answer on the 14th." That sentence prevents a message, gives Marc explicit cover, and gives the customer a real date. The vague version, "Marc can handle most things", prevents nothing, because Marc does not know whether a 20 percent discount is one of the most things.
The generosity matters. People overestimate how much needs to wait for them, and a handover that reserves too much authority produces a fortnight of stalled work plus messages asking you to unstall it.
Making the handover answerable
The document handles the predictable. What breaks a holiday is the unpredictable question about something you know and did not think to write.
Your brief is the handover, and it is answerable. Each day you spend ninety seconds confirming one, mostly pre-drafted from the work you already did: current state, open questions, blockers, next actions, decisions made and why. Over months that accumulates into the record of your actual work. While you are off, and two weeks away is the same kind of off as an afternoon meeting, your StandIn answers questions from it in your words, with a source under every answer, clearly labelled, and it never guesses. When the answer is not in the record, it says so and names who to ask.
So the colleague with the question about a June decision asks and gets your reasoning, in your words, on Tuesday, without you seeing a notification. You come back to a summary of what it said rather than to two hundred unread messages. That is the whole idea behind retiring your out-of-office: an auto-reply promises a delay, and a StandIn provides an answer.
What to do the week before
Three things, and none of them is writing a longer document.
Close what can be closed. A decision made on Thursday is worth two days of someone else's confusion next week. Tell people you are away, in the channels where they will need you, twice: a week before and the day before. And make one person visibly accountable rather than the team collectively, because collective coverage means nobody feels the responsibility.
If the person covering will be doing two jobs, read covering for someone on leave before you go, since that failure is what turns your holiday into their bad fortnight.
Common Questions
What should a vacation handover document include?
Four sections: work in flight with its current state, decisions others may make and who makes them, decisions that must wait plus what happens meanwhile, and one named person per area. One page, not ten.
How do I stop colleagues messaging me on holiday?
Remove the two reasons they message: unclear permission and unanswerable questions. Name explicit decision limits, and make sure your record can answer specific questions while you are away, so the only reason left to contact you is a genuine emergency.
Should I check messages on holiday just in case?
No, and the honest reason is that checking is what makes people message you. If it is known that you read things, the threshold for contacting you drops. One named escalation route by phone, for genuine emergencies, is the arrangement that lets you actually stop.
How far in advance should I write the handover?
Draft it a week ahead and finalise it on your last day, since half of it is current state and current state changes. Writing it entirely on the final afternoon is how the decision-limits section ends up vague.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.