Inbox zero

Coming back to 1,000 unread emails after vacation.

The post-holiday inbox undoes the holiday in one morning. A two-hour protocol for the pile, and the setup that shrinks the next one.

By Mathias CelisAugust 31, 20265 min readLast updated September 2026
TL;DR

Don't process a vacation backlog oldest-first: most of it expired while you were away. The two-hour protocol: bulk-archive everything automated, scan for your VIPs and active projects, ask key colleagues what actually needs you this week, declare bankruptcy on the rest with a saved search, and process only the last 48 hours normally. Anything truly urgent has already found another route.

The out-of-office was on for two weeks, and now there's a number in a red circle that starts with a 1 and has a comma in it. The standard response (open oldest, grind forward) is how a good holiday gets amortized into a bad week. The backlog deserves a protocol, not a slog.

The two-hour protocol

Minute 0 to 15: delete the automated half. Sort or search by sender and bulk-archive every notification, newsletter, receipt, and digest. No reading. This typically halves the count and costs nothing: none of it was addressed to you personally.

Minute 15 to 45: the VIP and project scan. Search the senders who matter (manager, key clients, active deals) and read only those threads, newest first, because the newest message usually contains the resolution of the older ones. Extract what's genuinely yours into tasks.

Minute 45 to 60: ask the humans. Message two or three key colleagues: "Back today, what actually needs me this week?" Thirty seconds of their summary outperforms an hour of thread archaeology, and they know what died and what's alive.

Minute 60 to 90: targeted bankruptcy. Everything older than your last 48 hours away gets archived in bulk. Not deleted: archived and searchable. The rule that makes this safe: anything truly urgent from ten days ago has already re-sent itself, called, or escalated. Silence since is the answer.

Minute 90 to 120: process the recent tail normally. The last two days get the standard one-touch pass: answer, task, waiting-for, archive. You're current. Go get lunch.

How do you shrink the next one?

Before the next trip: an out-of-office that routes by topic ("invoices: Sam; the Harwell project: Priya"), so threads resolve around you instead of queueing on you. Filters on everything automated, built now, working forever; the Gmail setup covers it. And if Pidgy is watching the account while you're away, the return looks different in kind: arrivals already sorted, tasks already extracted, waiting-fors tracked, and a needs-you list a screen long instead of a number with a comma. The volume playbook handles the everyday version of the same math.

Frequently asked questions

Should I read every email after coming back from vacation?

No. Most of a backlog is automated mail and threads that resolved themselves; reading it all costs a day of vacation-recovery attention on expired content. Triage by sender and recency, and let the genuinely unresolved things resurface, which they reliably do.

How long should clearing a vacation backlog take?

About two hours for a two-week absence, if you work the protocol instead of the pile: bulk-archive the automated layer first (usually half the count), then VIP and active-project scans, then normal processing of the final 48 hours only.

How do I stop the backlog from being so big next time?

Three moves before you leave: an out-of-office that names a colleague per topic (so threads route around you), aggressive filters on everything automated, and unsubscribing from what you skim anyway. Some people also let Pidgy keep sorting while they're gone, so they return to a triaged list instead of a wall.

Pidgy on top of the panel, looking through binoculars

Let Pidgy read your inbox so you don't have to.

Pidgy turns what lands in Gmail and Outlook into clear next actions, waiting-fors, and reference. One place, nothing slips.

Join the waitlistSee how Pidgy works