Free Pre-Vacation Engineering Handoff Checklist

A pre-vacation handoff is the same shape as an OOO handoff but with a longer horizon and stricter rules. The difference: an OOO handoff covers a couple of business days, where the cost of an unanswered question is small. A pre-vacation handoff covers a week or more, where the cost of an unanswered question compounds — the team gets used to going around the absent engineer, and decisions get made or deferred without them.

This checklist is structured to prevent the failure modes that recur on real engineering teams. It is not the same as the OOO checklist; the differences are deliberate. In particular: pre-vacation handoffs need a deeper unwind of pending decisions, because the team will absolutely make decisions while the engineer is gone, and the question is whether they make them well or whether they wait awkwardly.

When to use it

• Any vacation of five business days or more.
• Any time off where you will be genuinely offline (no Slack, no email).
• The week before a sabbatical, parental leave, or extended medical leave.
• Conferences abroad where time-zone overlap makes you effectively unreachable.

The template structure

This is the structure of the template. Copy it into a Notion page, a Linear doc, or a markdown file in your repo — it works in any of them.

PRE-VACATION HANDOFF — [name]
Out:        [start date] – [end date]
Coverage:   [primary owner]
Backup:     [secondary owner]
Reachable:  [No / In emergency only / How]

ONE WEEK BEFORE LEAVING
[ ] Tell your team the dates verbally — not just on a calendar.
[ ] Tell your manager in writing what you expect to ship before leaving.
[ ] Identify decisions that need to be made before you go vs. delegated.
[ ] Identify open PRs that should be merged, reassigned, or closed.

THREE DAYS BEFORE
[ ] Walk the coverage owner through your open work in a recorded call
    or written doc — their choice.
[ ] Confirm on-call coverage in PagerDuty / Opsgenie.
[ ] Reassign all open PRs you authored or were reviewing.
[ ] Decline or hand off all recurring meetings during your absence.
[ ] Confirm coverage owner has access to everything they need
    (repos, dashboards, vendor portals, customer Slack channels).

DAY OF
[ ] OOO message set (Slack, email, calendar).
[ ] Final note posted in team channel:
       - Dates out
       - Coverage owner + backup
       - What is in flight
       - Whether you should be contacted (and how)
       - Link to your handoff doc
[ ] Sign out of Slack on phone. Yes, this matters.

YOUR HANDOFF DOC SHOULD INCLUDE
  Open work, by area:
    [area]:  in flight → [status]  →  who is picking it up
    [area]:  blocked   → on what    →  who is unblocking
  Pending decisions:
    [decision] → who decides while I am out
    [decision] → waiting until I return
  Long-running threads to monitor:
    [customer / vendor]  →  context  →  coverage owner
  Things I expect NOT to happen while I am out:
    (if any of these happen, do contact me)
    - [example: production rollback of system X]
    - [example: hire decision on candidate Y]

How to use it well

• Use the "expect not to happen" list. This is the most important section. It is a short, named list of the events that, if they occurred, would justify reaching you. It replaces vague "if it's urgent" rules with concrete criteria, and it dramatically reduces the rate of unnecessary interruptions.
• Walk the coverage owner through the work — do not just send a doc. A fifteen-minute synchronous conversation three days before you leave catches the items you forgot to write down. There is no async substitute.
• Decline recurring meetings, do not just mark yourself busy. A declined meeting prompts the organizer to think about whether the meeting needs to happen without you. A "busy" block does not.
• Pin the handoff in the team channel. Pinning is the difference between a doc that exists and a doc that the team actually finds at the moment they need it.
• Sign out of Slack on your phone. The single highest-leverage step. If you stay signed in, you will check it, and the vacation degrades into a working vacation.

What to skip

Skip the urge to "leave things in a good state" by trying to finish everything before you go. The week before vacation is when engineers ship their worst code. Reassign in-flight work, do not race to ship it. Future-you will thank present-you.

Skip the apologetic tone in your OOO message. A vacation is normal. The OOO message is operational, not a performance of guilt. "Out until [date]. For anything urgent contact [name]." is the entire message.

Frequently asked questions

Is this template free?

Yes. The checklist above is the whole thing. Drop it into your team's vacation-prep workflow or a personal note.

Can I edit it?

Yes. The most common edits are dropping the on-call section (if you have no on-call) or adding a section for customer escalations (if you have named accounts you own).

Do I need to give my email?

Not for the checklist. The download is just a formatted Notion version of the same content.