Vacation chaos is almost always built in the two days before you leave, not while you're gone. Engineers who come back to working inboxes share a small set of habits — and engineers who come back to disasters skipped the same three or four things. This is the checklist.
Two weeks out: declare the dates and the coverage
Two weeks before you leave, post your dates somewhere queryable — team channel, calendar, wrap, wherever your team finds things. Include the dates, who is covering each surface you own, and what they are empowered to decide.
The phrase that matters: "For decisions about X while I'm out, ask Y. Y has authority to ship/revert/escalate as needed." If you don't name the authority, every decision becomes "let's wait for them to come back."
One week out: do the unglamorous closing work
The week before vacation is not for new features. It is for closing loops:
- Merge or close any PR you've been sitting on. Don't leave an open PR on a branch that may rot.
- Reply to any thread you owe a response to, even if the response is "I'm out next week, follow up with Y."
- Write up the state of every in-flight project — not a status report, a state transfer with next actions and open questions.
- Document any service or runbook your covering engineer might touch. If they get paged, they should have the runbook open in 30 seconds.
The day before: one final wrap
On your last working day, write one comprehensive wrap. The six fields from the handoff format apply, plus three vacation-specific additions: what fires might happen, what is safe to defer to your return, and what should you absolutely not be pinged about.
The third one is the one engineers skip and regret. Be specific. "Do not message me about the dashboard redesign — it can wait. Do message me only if production is down and Y can't reach me." Without that, you'll get pinged about everything.
Delegate authority, not tasks
The pattern that fails: "can you pick up these three tickets while I'm gone." The pattern that works: "you have decision authority over X surface for the next two weeks — work the queue as you see fit."
Tasks delegated without authority bounce back to you in DMs. Authority delegated cleanly lets the covering engineer actually own it.
Vacation Without the Backlog
StandIn captures decision authority and open threads before you leave — so the team keeps moving and your inbox doesn't explode.
See the Workflow →Set the actual out-of-office signal
Status set to OOO with dates. Notifications off, or at least muted for non-page channels. Auto-reply on email pointing to the coverage person. Your calendar blocked. If you're on call, swap the rotation.
Sounds obvious. About a third of engineers skip one of these and pay for it.
While you're gone: do not check in
The single biggest predictor of post-vacation chaos is checking Slack on vacation. Every check creates a thread you owe a response to, a decision you half-make and don't document, and a signal to the team that you're reachable.
If your team has good handoff hygiene, you don't need to check in. If they don't, checking in won't fix it — it just teaches them to wait for you.
The day you return: read, don't react
First two hours back: read the wraps from your time off. Read the decisions that were made. Don't reply to anything yet. Don't fire off opinions. Get the state loaded.
Then write your own "I'm back" wrap: here's what I'm picking up, here's what stays with Y, here's what I'm reversing or revisiting. That single document prevents three weeks of catch-up confusion.
What to do tomorrow
If you have vacation in the next two months, post your dates today. Pick the covering engineer per surface today. Write down their authority today. The rest of the prep gets done in the last week; this part has to happen now.
Frequently asked questions
How long should my coverage list be?
One person per surface you own. If you own three surfaces, three names. Coverage lists with one person for everything fail the moment that person is also out for a day.
What if my team can't function without me for two weeks?
That's a continuity problem, not a vacation problem. The fix is structural — declared state, queryable decisions, distributed authority. Don't solve it by not taking vacation.
Should I read Slack on the plane home?
No. Read it the next morning, with coffee, in chronological order, from a queryable record if you have one. Phone-scrolling Slack on a plane creates half-formed opinions and missed context.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.