How to Hand Off Your Work Before Vacation (Without Being Messaged Anyway)

The handover document is one of the most reliably wasted hours in professional life. You write four pages the night before you leave, nobody opens it, and on day three of your holiday someone messages you asking where the Figma file is.

"I wrote a full handover. They still messaged me on the second day."

That is not a discipline problem on your colleagues' part. It is a format problem on yours.

Why the usual handover document fails

A handover document is written from the inside out. You list your projects, your responsibilities, your recurring tasks, in the order they exist in your head. It reads like a job description with dates on it.

But nobody picks up a handover document and reads it. They hit a specific problem on a specific Tuesday and need one specific answer. If your document is organised by your projects and their question is organised by their problem, they will not find it, and the fastest route to the answer is your phone.

So invert it. Write the handover as a list of questions with answers, phrased the way someone else would ask them. "Who signs off the client invoices while I am out" rather than "Billing process". You will find you have fewer entries and better ones.

The three things that stall

Whatever the job, absences stall on the same three categories.

• A decision nobody is allowed to make. Someone needs approval and the approver is on a beach. Fix: name the person who decides in your place, and write the limit. "Tomas approves anything up to 2,000 euros. Above that it waits for me."
• A fact only you know. Which vendor we moved off, what the client agreed on the call, why we do it this odd way. Fix: this is the handover content, and the way to find it is in the next section.
• A relationship only you hold. A client who will only speak to you, a supplier who ignores generic addresses. Fix: introduce someone by name before you go, in writing, to the person. Not internally. To them.

The third one is the one people skip and the one that most reliably produces a call on holiday. An introduction sent from your address a week before you go costs five minutes and removes a whole class of interruption.

The two week checklist

When	Do this
Two weeks out	Scroll back four weeks in your messages. Write down every question you were asked. That list is the spine of your handover.
Ten days out	Name an owner per area and tell them, individually. Write the approval limits down.
One week out	Introduce the cover person to every external contact who might need someone, by email, from you.
Three days out	Write the open questions. Not the finished work. The things you do not yet know the answer to.
Last day	Current state of each live thing, in four fields: where it stands, what is open, what is blocked, what is next.

Note what is not on this list: writing up how you do your job. If a colleague needs a full account of your role in order to survive two weeks, the problem is bigger than a holiday and is covered in reducing dependency on the one person everyone asks.

Who answers in your place

The single deputy model is tempting and it usually fails. One person now carries your work plus their own, knows the answer to about a third of what arrives, and spends the rest of the time apologising or guessing. Guessing is the expensive failure, because a wrong answer to a client takes longer to undo than a delay.

Name an owner per area instead. Three or four names, each responsible for something specific, each told directly rather than in a group message they will skim. Then write the list somewhere the team can see it, because the point is for questions to self route rather than pass through anyone.

Say explicitly what has no cover. "Nobody is approving new supplier contracts while I am away. They wait." A stated gap is fine. An assumed gap is how things go wrong.

Write the out of office last

Most out of office replies apologise and give one email address. That address then becomes the funnel for everything, which is the deputy problem again in email form.

A better reply says what is covered, by whom, and what is not. Three lines. It does not apologise, because taking leave is not an imposition. There are examples in out of office messages that actually answer.

The deeper fix is that the questions arriving in your absence are mostly about current state, and current state is exactly what a document cannot hold. This is the gap StandIn is built for. Your daily brief already says what moved, what is open, what is blocked and what is next, mostly drafted from the work itself. While you are away, your StandIn answers from that brief, in your words, with a source under every answer. It never guesses, and when the answer is not there it says so and names who to ask. Nobody has to open a four page document to find out where you left something. See what replaces the out of office.

Common Questions

How far ahead should I start the handover?

Two weeks for a two week absence, and the first thing you do is the question audit, not the writing. Starting earlier does not help much, because the state you write down goes stale.

Should I check messages on holiday?

If you check, people learn that messaging you works, and the handover erodes every time you take leave. If the cost of not checking feels too high, that is the real finding, and it is a coverage problem rather than a holiday problem. See taking a real holiday as a manager.

What about a handover meeting instead of a document?

Useful as a supplement and useless as a replacement. A meeting transfers the things you remember to say in the room, in the order you remember them. Nobody can search a meeting three days later at the moment they need one line from it.

I am the only person who does my job. What then?

Then cover means triage rather than continuity. Name who decides what waits and what escalates, tell clients what the response time will be while you are out, and accept that some things sit. Stated and sitting beats unstated and guessed at.