How to Batch Your Email Writing and Get Two Hours Back Each Week

Most people answer email the way they breathe: continuously, without deciding to. Each new message pulls you out of whatever you were doing, and each return to real work costs a few minutes to get back into it. Over a day, those switches add up to hours.

Batching means writing email in a few deliberate blocks instead of all day. It is one of the simplest productivity changes there is, and it mostly fails for one reason: people batch the reading but not the writing.

Decide Your Blocks

Two or three blocks a day suit most roles:

• Late morning (after your first focused work block).
• Early afternoon.
• End of day, short, for anything that must go out today.

Customer-facing roles may need more frequent checks, but even then, batching writing into blocks beats replying the moment each message arrives. Tell people your rhythm if it helps; most colleagues adapt quickly. For the cost of constant switching, see context switching, the productivity killer.

Triage Before You Write

At the start of a block, sort everything before replying to anything:

1. Two-minute replies: answer now, in order.
2. Needs thought: move to a “to write” folder or flag.
3. Needs someone else: forward or delegate with a clear ask.
4. No action: archive.

Then write the “needs thought” replies in one sitting. Writing similar messages back to back is faster because you stay in the same mode.

Write Rough, Then Fix

The slowest part of email is not typing, it is agonising over phrasing. A faster approach:

1. Write the rough version as fast as you can, in plain words, getting every fact and request down.
2. Fix the tone and structure in one pass.

Before:

no we can’t do the 15th, the team’s off, could do 22nd if they get us the files by 17th otherwise it’s the 29th, sorry

After:

Unfortunately the 15th does not work, as the team is away that week. We can deliver on the 22nd if we receive the files by the 17th. If the files arrive later, the 29th is the earliest date we can commit to.

The facts were all in the rough version. The rewrite just made them easy to read. A Wrivio Context makes that second pass take seconds:

Rewrite this as a clear, polite work email. Direct, short paragraphs, lead with the answer. Keep every date, name, condition and commitment exactly as written. Do not add apologies, pleasantries or offers that are not in the original.

Press Ctrl+Shift+Space, paste the rough draft, check the dates, send.

Use Snippets, Not Templates

Templates make every email sound the same, and recipients notice. Snippets are better: reusable sentences for the parts that genuinely repeat, such as how to book a call, where to find an invoice, or your standard turnaround time. Keep the opening and the specific answer fresh each time.

Close The Loop In The Same Block

Before ending a block:

• Send everything you wrote.
• Note follow-ups with a date (a flag, a task, or a calendar reminder). See how to write a follow-up email that gets a reply.
• Close the inbox.

The last step is the one that matters. An open inbox in another tab is not batching.

When Batching Does Not Fit

Some work is genuinely interrupt-driven: support queues, incident response, executive assistants. Even then, separating “reading and routing” from “writing considered replies” helps. And remember that many questions are better answered once in a shared document than repeatedly by email; see how to write shorter emails and Slack messages.

Research backs up the intuition. The American Psychological Association’s summary of multitasking and switching costs explains why shifting between tasks costs time and accuracy, even when each switch feels instant.

Common Questions

How often should I check email?

For most office roles, two to four times a day is enough. Agree expectations with your team so nobody thinks you have gone missing.

What if my manager expects instant replies?

Ask what genuinely needs a fast response and agree a channel for it, such as a phone call or a specific chat. Everything else can wait for your next block.

Does batching work with Slack or Teams?

Yes, with the same principles: set status, mute non-urgent channels, and reply in blocks. Urgent issues should have a clear escalation path that is not “message me and wait”.

How do I stop rough drafts from being sent by mistake?

Write them in the email body but leave the recipient field empty until the final version is ready.

Download Wrivio for Windows to turn rough drafts into finished emails in seconds, so your email blocks stay short.