Email Batching
Definition
Email batching is the practice of processing email in scheduled blocks (typically 2-4 times per day) rather than checking continuously throughout the workday. The discipline reduces context-switching cost (each check incurs a 23-minute refocus tax per UC Irvine research) and concentrates email work in focused windows where decisions are faster.
The standard batching schedule
The most-cited pattern: three scheduled email blocks per day.
- Morning (after deep work block, around 10-11am) — process overnight email, draft replies
- Post-lunch (around 1-2pm) — handle anything urgent from the morning
- End of day (around 4-5pm) — close the loop, draft replies due tomorrow, sign off
Some practitioners add a fourth block right after wake-up; others skip it entirely to protect the morning for deep work. The exact times matter less than the discipline: no email checks outside the scheduled blocks.
Why it works
The math is in the context switching cost. UC Irvine research (Gloria Mark) measured 23 minutes of refocus time per interruption. A professional who checks email 15 times per day incurs roughly 5 hours of recovery cost. Batching to 3-4 blocks reduces recovery cost to roughly 1 hour — a 3-4 hour daily savings without changing how much email gets handled.
Tim Ferriss popularized the more extreme version in The 4-Hour Workweek: batch to twice per day, total processing time under 30 minutes per batch. Most knowledge workers find this too aggressive for their roles; 3-4 batches is the practical sustainable cadence.
What makes batching fail
Three common failures:
- Out-of-batch peeking. Checking email between batches because “I’ll just take a quick look.” Each peek incurs the full context-switch cost.
- Notifications still on. Push notifications interrupt regardless of intention. Batching requires notification discipline.
- No response time SLA. If your role expects sub-hour email response, 3 batches per day isn’t enough. The discipline has to fit the role.
The fix for (1) and (2) is structural — turn off notifications, treat the inbox as “closed” between batches. The fix for (3) is role-dependent; some roles genuinely can’t batch beyond twice per hour.
How AI assistants change batching
AI email assistants like alfred_ extend batching’s reach by handling email continuously without requiring user attention. The user still batches their email decisions to 2-3 windows per day, but the AI maintains continuous triage and drafting in the background.
This decouples response speed from check frequency. A customer email that arrives at 11am gets a drafted reply by noon — not because the user batched at noon, but because the AI handled it as it arrived. The user’s batch at 1pm reviews and approves.
Where alfred_ fits
alfred_ runs continuous triage and overnight processing. The user batches review time to 2-3 windows per day:
- Morning Daily Brief (10 minutes)
- Midday check-in if needed (5 minutes)
- End-of-day review (10 minutes)
Total user email time drops to 25 minutes per day; meanwhile, the AI has handled 100+ inbound messages continuously. The combined pattern delivers both batching’s focus benefit and continuous processing’s response speed.
What email batching isn’t
It isn’t ignoring email. It’s processing in concentrated windows instead of continuously. It isn’t right for every role — some genuinely need real-time email. And it isn’t a productivity hack; it’s a sustained discipline that requires notification control, structural support, and (often) explicit communication to senders about your response expectations.