Task Batching
Task batching is doing similar tasks together in one block instead of scattering them through the day: all the email at 11 and 4, all the calls after lunch, all the approvals on Friday morning. The idea is old, it is how factories and kitchens have always worked, and it applies to knowledge work for one reason: every switch between kinds of work costs time to reload the context, and a day of scattered small tasks pays that cost dozens of times. Batching pays it once per batch.
The planner below groups a pasted task list into batches, schedules them back to back and counts the switches saved. The rest of the page covers the research on why switching is expensive, which tasks batch well and which do not, how to set up the day, and the point at which batching turns into procrastination with a system.
Task batching planner
Batches are grouped by category and placed back to back with a five-minute gap; small categories under 20 minutes are merged into one "small stuff" batch. Nothing typed here leaves your browser.
Why batching works
Task-switching experiments summarised by the American Psychological Association find that every switch between tasks carries a cost, in time and in errors, and that the cost grows with the complexity of the tasks and the unfamiliarity of the one being switched to. Gloria Mark's field studies of office workers found that after an interruption people typically take a detour through two or three other tasks before returning, and that average attention on one screen has fallen to under a minute. The context switching page goes through that research in detail; the short version is that switches are individually cheap and collectively expensive, and that a working day contains far more of them than people estimate.
Batching attacks the count. Ten emails answered in one block involve one reload of "email mode", not ten; six approvals done together need the expense system open once. The saving is not only the switch itself but the warm-up that follows it: the third call in a row is faster than the first, because the tone, the notes template and the mental checklist are already loaded. Batching also makes the small, formless tasks visible as a block with a size, which is the first step to shrinking them.
What batches well, and what does not
| Batches well | Why | Suggested rhythm |
|---|---|---|
| Email and chat replies | Same tool, same mode, most not urgent | Two or three blocks a day, closed in between |
| Phone calls and voicemails | Warm-up effect; one quiet room booking | One block early afternoon |
| Approvals, expenses, timesheets, admin | Same systems, low thought, interruptible | One block, Friday or end of day |
| Reviews and feedback | Same critical mode; standards stay consistent across items | One block, mid-morning |
| Writing and other deep work | Long warm-up, high switch cost | One block, first thing, protected; see deep work |
| Errands and personal admin | Leaves the desk once | One block, lunchtime |
| Planning and scheduling | Calendar open once | Friday afternoon for the week; five minutes each evening |
What does not batch: anything with a real deadline inside the batch window, support and on-call work where the job is responsiveness, and creative tasks that need a different state of mind from each other (editing someone else's text and writing your own in the same block tends to flatten both). Batching is a default, not a rule; the prioritising guide is where the genuinely urgent gets identified before the batches are built.
Setting up the day
- Categorise the list. Five to seven categories are enough; the planner merges anything smaller than twenty minutes into a single small-stuff batch.
- Put the deep batch first. Writing, analysis and review go in the morning block before the inputs start; the planner's default does this.
- Fix the communication batches and tell people. "I check email at 11 and 4" is a boundary only if colleagues know it and urgent matters have another route. The team charter is where response-time norms are written down.
- Close the tools between batches. A batch with the inbox open in the next tab is not a batch.
- Put the blocks on the calendar. Batching is a form of time blocking with the blocks defined by task type; the daily schedule generator holds them.
- Review weekly. If a batch keeps overflowing, the category has a volume problem that batching cannot fix: too much email means too many lists, too many approvals means thresholds set too low.
When batching becomes avoidance
Batching has one characteristic failure: the batch that never comes. Email checked twice a day becomes email checked once, becomes an inbox of four hundred, and the batching system has become a way of not doing the task. The same happens with approvals that block other people and calls that were dreaded in the first place. Two rules prevent it. A batch with other people waiting on it has a maximum interval, usually a day, whatever the system says; and a batch that is consistently skipped is not a batching problem but a procrastination one, and is handled as such.
The other limit is role. For managers, support staff and anyone whose job is to be available, the batches are smaller and the rhythm faster, and the saving comes from batching the deep work into one protected block rather than from batching the responsive work at all.
Key takeaways
- Task batching groups similar tasks into one block so the context is loaded once per batch instead of once per task.
- Switching costs are individually small and collectively large; attention on one screen now averages under a minute.
- Email, calls, approvals, reviews, errands and planning batch well. Deadlines inside the window, on-call work and dissimilar creative tasks do not.
- Deep work first, communication batches fixed and announced, tools closed between batches, blocks on the calendar, weekly review.
- A batch that other people are waiting on has a one-day maximum; a batch that keeps being skipped is procrastination, not scheduling.
Frequently asked questions
What is task batching?
Grouping similar tasks and doing them together in one block of time instead of spreading them through the day: all the email at set times, all the calls together, all the approvals in one sitting. It reduces the number of switches between kinds of work, each of which costs time to reload the context.
Does task batching actually improve productivity?
The research on task switching says yes for the switches it removes: every switch carries a measurable cost that grows with task complexity, and a scattered day contains dozens. The saving is largest for people with many small, similar tasks and smallest for people whose job is responsiveness. It does not make the tasks themselves shorter.
What tasks should I batch?
Email and chat replies, phone calls, approvals and admin, reviews, errands, and planning. Each uses one tool or one frame of mind. Deep work such as writing is batched in the sense of being done in one protected block first thing. Tasks with deadlines inside the batch window, on-call work, and dissimilar creative tasks should not be batched together.
How often should I check email if I batch it?
Two or three fixed times a day for most office roles, announced to colleagues with another route for genuine emergencies. Once a day is too rare if people are waiting on replies. The interval should be the longest that does not make other people's work late.
What is the difference between task batching and time blocking?
Time blocking assigns tasks to calendar blocks; task batching decides which tasks share a block, by similarity. Batching is a way of filling time blocks. Most people use both: the week is blocked, and the blocks for communication and admin are batches.