Inbox Handover Checklist: Before You Go on Leave

Most pre-leave inbox advice is really out-of-office advice: pick a tone, name a backup, promise a slow reply. That gets your senders a message; it does not get your cover the pack they actually need to run your inbox for two weeks. The deliverable is not the OOO. The deliverable is the short document your cover reads on Monday morning to know which threads are live, who owns each one, what they are allowed to decide on your behalf, and who to escalate to when they hit the edge.

This is a decision-guide, not a template dump. It gives you the five items a real handover pack contains, a way to score whether yours is complete, a worked example for a ten-working-day leave, the failure modes that keep coming up in post-holiday retrospectives, and an honest look at the three ways teams do this — the paper handover, the shared-inbox rota, and the AI-native client that keeps the pack live while you are gone. We build AI Emaily, and we will say plainly where it is and is not the right answer.

What actually goes in an inbox handover checklist before annual leave?#

The five items below are the whole pack. Everything else — the OOO wording, the calendar block, the Slack status — is downstream of these. If any one of them is missing, your cover falls back on guessing, and guessing on your inbox is how a client gets the wrong answer under your name.

• Delegated mailbox access. Your cover reads and, where scope allows, sends from your address without you sharing a password. In Gmail this is the built-in Delegate access (Send-as on your behalf; delegates cannot change settings or read chat). In Outlook/Microsoft 365 it is Delegate Access or Shared Mailbox permissions, chosen by whether replies need to come from you or from a shared address.
• A live list of open threads with a decision-owner marked on each. Not a folder — a document, one line per thread, with the thread link, the person waiting, what they are waiting for, and who owns the next move (your cover, another colleague, or the sender). Ten to twenty lines is normal; more than thirty is a signal you have not closed enough before leaving.
• Explicit authority limits for your cover. What can they send on their own, what has to wait, what has to be escalated. Numbers where you can — approve refunds up to $X, sign proposals under Y, do not commit to any new work, do not renegotiate contracts. A cover with no limits will either freeze on everything or over-commit on something.
• An out-of-office that routes senders instead of apologising. Two lines: when you are back, and who to contact for which topic in the meantime. Not a paragraph of gratitude and vague apology — those go straight into the pile the cover then has to sort. Route by topic and by urgency, not by seniority.
• Named escalation contacts by topic. Who is the backup for billing, for a security issue, for the biggest three clients, for a press enquiry. Names and channels, not job titles. Your cover should not have to look up who owns invoicing at 4pm on a Friday while a client is waiting.

The criteria that actually decide whether the pack works#

Not every item on the checklist is worth the same. A handover fails or holds up on a small number of specific properties, and it is worth scoring your pack against these before you leave rather than after you get back.

• Completeness — every open thread accounted for, every category of decision covered, no "I'll just handle that on my phone" carve-outs. The carve-out is what always turns into the fire.
• Access reality — your cover can actually read the mail and send under a sanctioned identity on day one, tested by them before you leave. A delegation set up but never opened is not access; it is a promise of access.
• Decision clarity — for every open thread, the cover knows whether they decide, wait, escalate, or hand back. Ambiguous ownership is the most common failure and the easiest to fix.
• Freshness — the pack reflects the state on the day you leave, not the state you wrote it in three weeks ago. Anything more than 48 hours old is fiction for a busy inbox.
• Escalation coverage — every plausible urgent scenario has a named human. "Ask the manager" is not a contact, because the manager is also on leave in August.
• Routing at the door — your OOO puts the right sender in front of the right contact without them having to reply first to find out. This is the single biggest lever on how much noise your cover actually has to touch.

Score your handover pack out of twelve#

Score each criterion 0, 1 or 2 — nothing done, partial, or fully done. Anything under nine is a pack that will send someone chasing you on holiday. Ten and up is a pack you can actually leave behind.

A worked example: a ten-working-day leave for a client-facing role#

Below is what a real pack looks like for someone leaving for two working weeks — an account manager with two live prospects, five ongoing accounts, and a shared invoicing address. It is not a template to copy blind; it is a shape to steal.

1. 1

   Two weeks out — thin the pipe

   Close what you can close. Send the pending proposal, book the meeting on the date you actually want, decline the two things you were going to say no to anyway. Every thread you close now is one your cover does not have to hold. Do not start anything new that will land in your absence — a follow-up scheduled for the Tuesday you leave is a gift to no one.

2. 2

   One week out — build the pack skeleton

   Open a shared document. List every open thread you know of, one line each: subject line, who is waiting, what they are waiting for, who decides. Add the five topic-to-contact escalations. Draft the authority limits. Draft the OOO. Share the doc with your cover and their manager. Book a 30-minute walk-through for Friday afternoon.

3. 3

   Friday afternoon — hand over, test access, refresh the pack

   Walk the doc with your cover. Ask them to open the delegated mailbox and send a test reply from it while you are watching. Answer their questions on the authority limits — every real question they ask uncovers an ambiguity you should fix in the doc, not in your head. Update the thread list one last time from the state the inbox is actually in as you close your laptop.

4. 4

   Sunday night — turn on the routing

   Enable the OOO. Set your calendar to show fully-booked, not just out-of-office. Silence work notifications on your phone. Post the same routing message once in the team channel your cover watches. Then close the laptop and leave.

How to write an OOO that routes instead of apologises#

The OOO is the front door of the pack. Its job is to move each sender to the right onward destination before they add another message to the pile. Two lines is enough for most people; three if you genuinely have multiple topics that route differently.

Red flags — how good handover packs quietly fail#

These are the failure modes that show up in retrospectives after leave. Not the obvious ones ("they forgot to set an OOO"); the ones that happen even when the pack looks complete on paper.

• The rules-brain that keeps triaging while you are away, into folders your cover cannot see. Any auto-filter that sorts into your personal folders becomes invisible to a delegate — turn off, or reroute to a shared label, before you leave.
• The client-specific email address that goes to only one inbox. A dedicated address like [email protected] routes only to Sam. Add a forward, or a delegate on that address specifically — the general mailbox delegation does not cover it.
• The calendar shared with your cover but not the meeting notes. Your cover can see you have a Tuesday call, but not what it is about. Add a one-line note to every meeting in the two weeks after you return, so a rescheduled call has context.
• The mobile app still logged in. You will check. You will reply to "just one urgent thing." You will then own that thread again from a beach, and your cover will assume they no longer own it. Log out of the mail app on your phone, or move it off the home screen, before you leave.
• The Autopilot rule you forgot you set. If you use an AI agent to auto-reply to a category, decide before you leave whether it keeps running (and whose name it acts under) or pauses. An agent quietly sending under your name for two weeks while you are gone is either a huge win or a landmine — never leave it ambiguous.
• The cover who is also on leave for three days in the middle. Check their calendar before you name them. Two covers is fine; two covers who both disappear at the same time is not.

Which approach is right for your handover?#

Three shapes actually work for a real inbox handover: a paper pack against native provider delegation, a shared-inbox rota if you already run one for the team, and an AI-native client that keeps the pack live while you are gone. They are not competing on quality — each is right for a different situation. This section is honest about which is which.

What we'd pick and why (honest)#

We build AI Emaily. Naming it here is a placement, and we will earn it by saying which reader we are right for and which reader should stop reading this section and go set up native delegation instead.

AI Emaily is the right pick for a client-facing individual whose inbox spans Gmail and Outlook (and maybe an IMAP address), who has enough open threads that a static paper pack goes stale during the leave, and whose cover would benefit from drafts pre-written in the account owner's voice rather than a blank composer. The relevant mechanics: the assistant sits across every connected provider (see /features/ai-email-assistant), it triages incoming mail so your cover opens a sorted view instead of a pile, and Copilot mode drafts replies for approval so the cover is editing rather than authoring from scratch (/features/copilot-autopilot). Every action is logged and reversible, which is what makes trusting someone else with your mailbox for two weeks a decision you can actually audit when you return. If your leave is long enough or your inbox loud enough that you would otherwise be checking on holiday, the pricing at /pricing is easily paid back by not doing that. Start on the 7-day free trial from the homepage at / — card required, no charge if cancelled before day 7 — and cancel if it is not obviously helping by the end of the week.

Concession: if your team is 100% inside Google Workspace, your role is well-scoped, and you have run this handover twice before with only a paper pack and native Gmail delegation, we are honestly not much of an upgrade for a single two-week leave. Google's built-in delegation is genuinely good, your cover already knows the Gmail interface, and adding a new client to learn the week before you go is friction with no matching payoff. Same story for a team where the inbox in question is already a shared queue in a help-desk tool — the rota shift is the handover, and bolting another layer on top is process for its own sake.

If you want the pack itself and are not looking for a tool, the paper approach above is complete. The five items in the checklist, tested delegation, and a routing OOO will get most people through most leaves. The tool question only matters when the volume or the stakes make the static pack the bottleneck — and that is a real situation, not one every inbox is in.

Frequently asked questions#

The questions people ask most when putting together a pre-leave inbox handover — on delegation, OOO, authority limits, agents, and what to do when the pack starts to break.