Task batching: what it is, what the research shows, and how to do it well

You open a report to finish one section. A message arrives, so you answer it. That reminds you of an expense form, which you start and abandon when a calendar alert pops up. Twenty minutes later the report is still open on the same paragraph. None of these jobs was hard. The day just kept changing what kind of work you were doing.

Task batching means grouping similar tasks and doing them together in one bounded session, instead of scattering them across the day. The research behind it is real but narrower than most productivity guides suggest. Lab studies consistently show that switching between tasks costs time and accuracy, and that even very short interruptions cause slips. Two field experiments that tested batching directly, one with work email and one with phone notifications, found modest benefits for people's sense of stress and control. Neither found a dramatic jump in output, the email benefit faded within two weeks, and switching notifications off completely brought its own costs. Batching is worth testing, but as a fit for your job, not a universal rule.

This guide explains what task batching is and how it differs from time blocking, what the switch-cost and interruption research actually measured, what the two direct tests of batching found, when batching backfires, and how to run a two-week trial of your own.

What is task batching?

Task batching is the practice of collecting tasks that need the same tools, information or kind of thinking, and handling them in one sitting. Typical examples are answering routine messages, approving expenses, making phone calls, reviewing pull requests or doing small edits across a set of documents. Instead of responding to each item the moment it appears, you let them accumulate and work through them together at a set point.

The idea borrows from manufacturing, where producing items in batches avoids resetting a machine between every unit. In knowledge work the "machine" is your own setup: the open tabs, the rules you are applying, the context you have loaded into memory. A batch is useful when the next item can reuse that setup.

A batch has three parts:

• A shared context. The items need the same information, rules or tools. "Admin" is often too broad. "Approve the expense claims using this month's policy" is a real batch.
• A boundary. The batch has a clear start and a stopping point, such as "the messages that arrived since lunch" or "these six reviews".
• A holding place. Items that arrive between batches go somewhere visible, so you can trust they will be handled later.

Task batching vs time blocking

The two are often mixed up, and many guides present them as one technique. They answer different questions.

• Time blocking decides when work happens. You reserve a slot on the calendar for an activity.
• Task batching decides what belongs together. You group similar items so they can share one setup.

You can have one without the other. A two-hour block labelled "work" can still be full of switching between unrelated jobs. A batch of five quick approvals can happen whenever there is a gap, without any calendar entry. They combine well: a short recurring block for routine messages, filled with a batch of messages, is the most common version of the practice. If you already use timed work sessions, our look at whether the Pomodoro technique works covers the timing side in more detail.

Why switching tasks costs something

The main argument for batching comes from decades of laboratory work on task switching. In a typical experiment, people alternate between two simple tasks, for example classifying shapes by one rule and then by another, or doing one kind of arithmetic and then a different kind. Their speed and accuracy are compared with runs where they repeat the same task.

In four experiments, Rubinstein, Meyer and Evans found that alternating between tasks produced switching-time costs. Those costs grew when the rules were more complex and shrank when people had clear cues about which task came next. A widely cited review by Stephen Monsell summarised the pattern: responses are substantially slower, and usually more error-prone, right after a switch. Being able to prepare reduces this switch cost but does not remove it. A later review by Kiesel and colleagues described how much of the cost comes from the previous task interfering with the new one, not only from the time needed to reconfigure.

Two limits matter here. First, these costs are measured in fractions of a second on simple tasks repeated many times. They show that switching is not free, but they do not tell you how many minutes a real workday loses. Second, people in these studies switch because the experiment tells them to. At work, many switches are your own choice, which turned out to matter too.

Short interruptions cause outsized slips

Interruptions are a kind of forced switch, and they can be costly even when they are tiny. Altmann, Trafton and Hambrick gave people a task that required keeping their place in a sequence of steps. Interruptions averaging 4.4 seconds tripled the rate of sequence errors after the interruption, and interruptions of about 2.8 seconds doubled it. Other kinds of errors did not rise. The interruptions did not seem to wreck attention in general. They made people lose their place.

That fits a common experience at work: a quick glance at a notification seems harmless, but you come back unsure which step you were on. Batching the sources of those glances is one way to have fewer of them during work that depends on keeping your place.

Self-interruptions are costly too

Not every switch comes from outside. Katidioti, Borst and Taatgen compared external interruptions with self-interruptions across three multitasking experiments. Pupil size, a rough marker of mental effort, increased several seconds before people chose to switch, which the authors attributed to the decision to switch itself. In one experiment, people were slower in the self-interruption blocks than in the blocks where the switch was imposed. The authors suggested that when a switch is needed, it can be more efficient to take it at the end of a subtask than to keep deciding in the moment.

This is one of the more practical findings for batching. A fixed batch time takes away the constant small decision of "should I check now?". The decision has already been made.

Switching also leaves traces after you have moved on. We cover that effect, known as attention residue, in a separate guide, and the site's page on context switching looks at the wider cost of jumping between jobs.

What happened when researchers tested batching directly

Switch-cost studies explain why batching might help. They are not tests of batching. Two field experiments came closer.

Batching work email: a real benefit that faded

In a Dutch financial services organisation, Wijngaards, Pronk and Burger studied a three-week "email challenge" in which one group of workers was asked to check work email at most three times a day. Teams were assigned to the intervention or control group by location, so the study was quasi-experimental rather than randomised, and all measures were self-reported. Of 112 selected workers, 79 completed the first survey and 53 completed the post-test.

The batching group reported fewer email interruptions than the control group. Emotional exhaustion measured right after the challenge was lower, especially for people who handled a high volume of email and people who believed their organisation did not expect instant replies. But the effect on exhaustion had worn off by a follow-up two weeks later, and there was no effect on work engagement. The authors concluded that email batching should not be treated as a universal fix and should only be encouraged where it fits the job and the organisation's expectations about response times. The full paper is open access.

Batching phone notifications: better than none at all

Fitz and colleagues ran a randomised field experiment with 237 smartphone users. Using an app the researchers built, participants received their notifications as usual, in batches three times a day, or not at all. Compared with the usual-notifications group, people whose notifications arrived in three daily batches reported feeling more attentive, more productive, in a better mood, less stressed and more in control of their phones. People who received no notifications at all gained few of those benefits and reported more anxiety and more fear of missing out.

The results are self-reported over a limited period, and the study tested one specific batching schedule. Still, its main lesson carries over to work: predictable batches beat both constant interruption and going completely dark. Cutting yourself off entirely can create its own worry about what you might be missing.

What none of these studies show

Some batching guides promise a fixed percentage gain in productivity. None of the studies above measured anything like that for batching. The direct tests measured interruptions, stress, exhaustion, mood and self-rated focus. The lab studies measured fractions of a second on simple tasks. A fair reading is that batching can reduce interruptions and make some people feel calmer and more in control, for a while, under the right conditions. Whether it raises your output is something to check for yourself.

When task batching backfires

The email study found that batching helped most where fast replies were not expected. That points to the situations where batching can cost more than it saves.

• Your role depends on quick responses. Support, operations, on-call and some client roles exist to respond. Batching their core work can just move the delay onto someone else.
• The batch is too broad. "All the small stuff" mixes jobs that need different information. You still switch context inside the batch, just with less awareness of it.
• Important items get buried. A sensitive message handled at speed alongside thirty routine ones can get less care than it needs.
• The batch never ends. One hard exception can turn a 20-minute batch into an afternoon. Exceptions need their own slot.
• The holding place is not trusted. If you keep checking whether something urgent has arrived, you have added checking on top of the batch.

That last point links to research on unfinished tasks. Masicampo and Baumeister found that unfinished goals caused intrusive thoughts and worse performance on unrelated tasks, and that making a specific plan for those goals removed the interference in their experiments. For batching, the practical version is simple: write down what is waiting and when you will deal with it, so it does not keep pulling at you during focused work. The same idea underpins our guide on how to stop thinking about work at the end of the day.

How to batch tasks: a practical setup

These steps are practical suggestions drawn from the research above, not a tested programme. Adjust them to your role.

1. List your interrupters for two days. Note each time you switch to a small task, what it was and whether it could have waited. This shows which categories are worth batching.
2. Pick one category to start. Routine email or chat is the usual first choice because both direct tests used messages or notifications. Other good candidates are approvals, scheduling, small edits and expense claims.
3. Set the rhythm. Both field studies used three batches a day. That is a sensible starting point, not a magic number. Many people choose late morning, after lunch and late afternoon, leaving the start of the day for demanding work.
4. Agree an urgent route. Tell colleagues how to reach you for something that truly cannot wait, such as a phone call or a named chat thread. This is what makes the batch safe to keep, and it reflects the email study's finding that expectations matter.
5. Define "done" for each batch. "Everything that arrived since the last batch" or "these five items" works better than "catch up".
6. Park exceptions. When an item needs real thought, write its next action and a time to do it, then move on with the batch.
7. Put the batch where your energy is lower. Routine, repetitive work tends to tolerate a dip better than work that needs fresh thinking. Our page on the afternoon slump covers why many people have one.

What to batch, and what to leave alone

Usually batches well	Usually better handled on its own
Routine replies and acknowledgements	Sensitive or difficult conversations
Approvals that use the same criteria	Decisions that need research or judgement
Scheduling and calendar admin	Writing, design, analysis or code that needs a long run of attention
Small edits across similar documents	Anything ambiguous that needs clarifying first
Phone calls you need to make	Work that is genuinely time-critical

If you notice that the hardest choices keep landing in your batches, it may help to move them earlier. Our guide on whether decision fatigue is real looks at what the evidence says about decisions late in a long session.

A two-week test: does batching help you?

Because the evidence is modest and depends on context, the most useful thing you can do is test batching on your own work. A simple version:

1. Week one, as usual. Work normally. At the end of each day, note three things on a 1 to 5 scale: how interrupted you felt, how much of your most important task you finished, and how drained you felt.
2. Week two, batched. Batch one category, such as messages, three times a day, with an urgent route in place. Record the same three ratings.
3. Compare, and check the cost. Look at the ratings side by side. Also ask whether anyone waited too long for you, or whether you spent the batch-free stretches worrying about what was piling up.

Be careful about reading too much into one week each way. Workloads differ from week to week, and simply paying attention can change how you rate your day. If the batched week looks better, try another round before committing. Remember that the email study's benefit faded after two weeks, so check again a month later. If it looks worse, change the batch or the rhythm before dropping the idea.

Where Zone fits

Zone is a pair of EEG earbuds with an app that summarises work sessions as app brain states, such as Locked In, In Flow, Drifting, Running Hot and Depleted. The earbuds read signals through an in-ear EEG array, described in our explainer on in-ear EEG. If you run the two-week test while wearing Zone, you can set your session summaries from the usual week next to those from the batched week, for example to see whether long stretches of focused work look different when messages are held for set times. Treat these as app estimates, not a measure of productivity or proof that batching works for you, and keep your own ratings and finished work as the main evidence. Zone does not diagnose, treat, or manage any medical condition.

Common questions

What is task batching?

Task batching is grouping similar tasks, such as routine emails, approvals or calls, and doing them together in one bounded session instead of scattering them through the day. The aim is fewer switches between different kinds of work.

Does task batching actually work?

Partly. Lab research shows that switching tasks has real costs, and two field experiments found that batching email or phone notifications reduced interruptions and stress for some people. The email benefit faded within two weeks, and no study found a large, reliable boost in output, so it is best treated as something to test in your own job.

What is the difference between task batching and time blocking?

Time blocking reserves time on the calendar for an activity. Task batching groups similar tasks so they share one setup. They often work together, for example a short block each afternoon for a batch of routine messages.

How many times a day should I check email if I batch it?

Both field studies discussed here used three times a day, which is a reasonable starting point. The right number depends on your role and what your colleagues expect, so agree an urgent route and adjust from there.

Is it better to turn notifications off completely?

Not necessarily. In one randomised field experiment, people who received no notifications reported more anxiety and fear of missing out, while those who received notifications in three daily batches reported the most benefits.

Sources

1. Rubinstein, J. S., Meyer, D. E., and Evans, J. E. (2001). Executive control of cognitive processes in task switching. Journal of Experimental Psychology: Human Perception and Performance, 27(4), 763 to 797. PubMed record
2. Monsell, S. (2003). Task switching. Trends in Cognitive Sciences, 7(3), 134 to 140. PubMed record
3. Kiesel, A., Steinhauser, M., Wendt, M., Falkenstein, M., Jost, K., Philipp, A. M., and Koch, I. (2010). Control and interference in task switching: a review. Psychological Bulletin, 136(5), 849 to 874. PubMed record
4. Altmann, E. M., Trafton, J. G., and Hambrick, D. Z. (2014). Momentary interruptions can derail the train of thought. Journal of Experimental Psychology: General, 143(1), 215 to 226. PubMed record
5. Katidioti, I., Borst, J. P., and Taatgen, N. A. (2014). What happens when we switch tasks: pupil dilation in multitasking. Journal of Experimental Psychology: Applied, 20(4), 380 to 396. PubMed record
6. Wijngaards, I., Pronk, F. R., and Burger, M. J. (2022). For whom and under what circumstances does email message batching work? Internet Interventions, 27, 100494. PubMed record, full text
7. Fitz, N., Kushlev, K., Jagannathan, R., Lewis, T., Paliwal, D., and Ariely, D. (2019). Batching smartphone notifications can improve well-being. Computers in Human Behavior, 101, 84 to 94. doi.org/10.1016/j.chb.2019.07.016
8. Masicampo, E. J., and Baumeister, R. F. (2011). Consider it done! Plan making can eliminate the cognitive effects of unfulfilled goals. Journal of Personality and Social Psychology, 101(4), 667 to 683. PubMed record