How to write a handover note before you go on vacation

A handover note answers the questions people would otherwise send you while you are away. Everything about the note follows from that. Write down what is live and who owns each thing until you are back, then stop writing.

Most handovers fail in the opposite direction. They describe the whole job instead of the next two weeks, and they go unread. The messages arrive anyway, because the one answer somebody needed was buried on page four.

Write for someone mid-problem

Write the note for a reader who is already mid-problem, because that is the only reader it will ever have. Nobody sits down with a handover calmly on Monday with coffee. Your real reader opens it on Wednesday, holding a broken thing or a client question. They are scanning for the one line that covers their situation.

Build the note for that person. Call things by the names people use in chat, whatever the official project titles say. Keep sections short. Put the answer at the top of each one, with the background underneath for the rare reader who wants it.

The runbooks I write for Unvent's plumbing all follow one rule: the fix first, the explanation second, because whoever opens a runbook is in a hurry by definition. A handover is the same document. It is a runbook where the system is you.

Five things go in

The note needs five things: the state of live work, the decisions in flight, an owner for each item, the dates that land while you are out, and where everything lives.

• Each live piece of work, its state in one sentence, and the next step.
• Each decision that is waiting on someone, and what happens if it keeps waiting.
• Every date that falls inside your time away, with what must happen before it.
• Links to where things actually live, because "in the drive" is not a location.
• The things you have decided can wait for you, listed by name.

The one-sentence state is the hard part, and it is a muscle you may already have. It is the same compression that makes a standup update people actually read. If the state of a project will not fit in one sentence, congratulations: you have found the project most likely to interrupt your vacation.

Give every item exactly one name

Each item in the note gets one owner who agreed to the job before you wrote it down. A name someone discovers in the note after you have left is a surprise, and surprised owners tend to wait for you anyway.

Resist listing a second name as backup. Two people watching an item read each other as the primary, and the watching stops.

Hand over authority along with the work. "The owner can decide this without me" is the single sentence that prevents the most messages, and it costs the most pride to write. If every real decision still routes through you, nothing was handed over. You have just scheduled the pings for later.

Shorter beats complete

A handover should fit on one page. If it will not fit, the problem sits upstream of the note.

A handover that takes a full day to write is a symptom, not a virtue. It means that much of your work lived nowhere but your head, and the note is the first time any of it has touched paper. That is worth knowing about your job. The week you leave is simply a bad week to find out.

Long notes also lie about themselves. They feel thorough while you write them and read as fog to everyone else. Every paragraph of context makes the load-bearing line harder to find, and the reader mid-problem grades you on exactly one thing: how fast they found their answer.

Write it two days before you leave

Finish the handover two days before your last day. The reason is what the writing digs up.

Writing the note forces a scan of your own commitments, and the scan will surface loose ends you had stopped seeing. With two days in hand you can close them, or walk over and hand them off properly. Written in the last hour, the same note is a list of anxieties with an out-of-office stapled to it.

Sending it early also lets the owners read it and ask questions while asking is cheap. A question on Thursday costs you two minutes at your desk. The same question next Wednesday costs you an afternoon of your trip, plus the hour you spend pretending it did not.

Say what can wait

The most useful line in a handover says what not to do. Urgent, in my experience, usually describes the sender's mood, and the work itself survives two weeks untouched more often than anyone admits. The note is your one chance to say so in advance without sounding dismissive.

So spell out the waiting list by name:

• New feature ideas wait, however good they look on arrival.
• Renewals and paperwork wait unless a date is printed on them.
• Anything marked urgent that contains no deadline waits too.

Your most conscientious teammate needs this list in writing, because silence about priorities never reads as "use your judgment". It reads as "ask me". The list is a no, written in advance and in bulk, which is the cheapest form a no comes in. Declining ten hypothetical interruptions in one line is painless. Declining one real interruption from a beach chair is not.

Then add two lines at the bottom for a reader nobody plans for: you, on your first morning back. Where you stopped, and what to pick up first. The return is a handover too, from the person who left to the person who came back, and the second one always arrives knowing less than they expected.