Skip to content

Estimating email time: telling a two-minute thread from a two-hour one

On this page

You can usually tell a two-minute thread from a two-hour one before you open it. Five signs show in the inbox list: what it asks, who sent it, whether there’s a file, how many people are on it and how long it already is. Each one has been measured to slow replies down. Then a short formula turns any thread into minutes you can plan around.

Most of your mail is small. Microsoft’s 2025 Work Trend Index says the average worker gets 117 emails a day, “most of them skimmed in under 60 seconds.” The hours come from a handful of threads. Estimating is how you see those coming.

Sarah has seven people in her firm and about a hundred emails landing each day. She isn’t slow. A few of her threads are simply big, and they’re big before she opens them. This page shows how to spot them, how to size them, and how to check your sizing against the clock.

Five signs a thread will take a while

The best measurement here is a Microsoft Research study of one real company’s mail. Yang, Dumais, Bennett and Awadallah studied 938,035 emails from 279 accounts at an IT firm. Their paper, Characterizing and Predicting Enterprise Email Reply Behavior, from SIGIR 2017, found:

“emails with requests or commitments get more but slower replies while longer emails tend to get fewer and slower replies.”

Here are the five signs, where you see each one, and what the study measured.

SignWhere you see itWhat the study measured
It asks for somethingThe subject and preview lineMedian reply 81 minutes with a request, 55 without
It’s from outsideThe sender’s addressMedian reply 135 minutes for external mail, 66 for internal
It carries a fileThe paperclipMedian reply 23.81% longer with an attachment
Several people are on itThe names in the listMedian reply rose from 44 to 95 minutes as recipients went from 1 to 8
It’s already longThe message count beside the subjectMedian reply time rose as the email body got longer

Reply time isn’t working time. It includes the hours a message sits before anyone touches it. That’s the one caution worth holding onto here. Still, the authors read the delay as work. On requests, they say people “may need to do some work like searching information, reading or writing before they can reply.” On attachments, they say people “need to open the attachments and spend more time reading or replying.”

So the signs tell you which way a thread leans. They don’t tell you the minutes. The formula below does that.

Putting minutes on a thread

Every thread costs three things, and then it costs them again for each round.

Thread minutes = (words to read ÷ reading speed) + minutes to find what you need + (words to write ÷ writing speed), for each round you expect

Two of those speeds have good numbers behind them.

  • Reading: about 238 words a minute. That’s the average adult silent reading rate for English non-fiction, from Marc Brysbaert’s 2019 meta-analysis of 190 studies.
  • Typing: about 52 words a minute. That’s the mean from Dhakal and colleagues’ CHI 2018 study of 168,000 volunteers. They were copying sentences, though.
  • Writing a reply: slower than typing, because you’re deciding what to say. This page assumes 20 words a minute for a careful reply. Time one of yours and use your own figure.

Finding is the line nobody prices. It’s opening the engagement letter to check a date, or pulling last month’s numbers. It’s often the biggest of the three.

Rounds multiply everything. A reply that answers the question and says what happens next can end a thread in one round. A reply that leaves something open usually comes back.

Four threads, sized

Here’s the formula on four threads Sarah might get on a Tuesday. Every figure is an assumption you can replace.

ThreadSignsReadFindWriteRoundsAbout
A colleague asks, “Does Thursday at 2:00 work?”130 words, under 10 seconds1 minute on the calendar10 words, 30 seconds12 minutes
A client asks for a copy of last year’s engagement letter260 words, 15 seconds3 minutes to find the file40 words, 2 minutes15 minutes
A client questions a line on an invoice, PDF attached3650 words with the invoice, 3 minutes10 minutes in the time records200 words, 10 minutes230 minutes
A vendor’s contract change, six people, 14 messages57,400 words with the contract, 31 minutes20 minutes against the old version300 words, 15 minutes42 hours

The work behind the last two rows:

  • The invoice question. The first round is 3 + 10 + 10, or 23 minutes. The client writes back with one follow-up. Reading it, checking one figure and writing 80 words takes about 8 more. That’s 31 minutes.
  • The contract change. The first round is 31 + 20 + 15, or 66 minutes. Three more rounds follow. Each one is a minute of reading, about 10 minutes of thinking and 150 words of writing, so about 19 minutes. That’s 57 more, and 123 minutes in all.

The sign count rises with the minutes. That’s the pattern the study predicts. It’s a sorting aid built on the study’s directions. Your own tally, below, is what turns it into a rule you can trust.

What one big thread does to a day

How long email should take each day counts a day in four lines. One of them is long threads. Its worked Tuesday gives Sarah 5 long threads at 12 minutes each, so 60 minutes.

Now say one of the five is the contract change.

  • The contract thread: 123 minutes.
  • The other four at 12 minutes each: 48 minutes.
  • The long-thread line: 171 minutes, or about 2 hours 51 minutes.

An average of 12 minutes was fine until one thread was ten times that. This is why estimating pays. The day’s total turns on spotting the one big thread.

It also tells Sarah when to look. A two-hour thread doesn’t fit between two meetings. Sized before she opens it, it gets a slot that fits. Sized after, it eats whatever slot it landed in.

Size isn’t the same as importance. A two-minute email can matter more than a two-hour one. Important versus urgent covers how to rank them. This page only measures them.

Checking your estimates for one week

Your first estimates will run short. The two-minute rule for email covers the research on why, and that piece leaves the verdict on the rule there. The fix is a tally.

For one week, do this with every thread that takes more than a glance.

  1. Before you open it, count the signs and write a guess in minutes.
  2. When the thread is done for the day, write the real minutes.
  3. At the end of the week, add each column for each sign count.
SignsThreadsGuessed minutesReal minutesReal ÷ guessed
0 or 1
2 or 3
4 or 5

The last column is your multiplier. Say your four- and five-sign threads come out at 1.8. Next time you guess an hour for one, block close to two.

A week of tallies also shows which sign matters most for you. For some firms it’s the attachment. For others it’s the number of people on the thread.

How Point sizes a thread before you open it

Point reads each thread as it arrives, so most of the sizing is done before you look.

  • Every thread carries a plain summary. You see what’s being asked, by whom and by when. That’s most of what the five signs were trying to guess. Reading a summary before you open shows what one holds. For a forty-message chain, catching up on a long email chain covers the rest.
  • The work a thread creates becomes a task. The ask turns into a dated task that waits for your go. That makes it easy to give a two-hour thread a slot. A task in five seconds shows the step.
  • The small ones arrive drafted. Point writes short replies in your voice, and by default each one sits ready until you’ve read it and pressed send. Why the draft waits for you covers that setting.

The finding minutes stay yours. Point can’t open the old contract for you and decide what changed. It can make sure you know that’s the job before you start. Point is in private beta with per-seat pricing. What Point does has the rest, and the home page has the beta.

Common questions

How do you estimate how long an email will take?

Count the five signs first: a request, an outside sender, an attachment, several people, and a long thread. More signs mean more time. Then put minutes on it with reading time, finding time and writing time, multiplied by the rounds you expect.

How long does it take to read an email?

At the average adult reading rate of 238 words a minute, a 200-word email takes about 50 seconds. A 2,400-word chain takes about 10 minutes. Attachments are extra, at the same rate.

How long does it take to write an email?

Typing averages about 52 words a minute when copying. Composing is slower. At an assumed 20 words a minute, a 40-word reply is 2 minutes and a 300-word one is 15. Time one of your careful replies to get your own rate.

Why does a long thread take so much longer than it looks?

It costs you more than once. Every round brings new reading, new thinking and a new reply. A thread that runs four rounds at 20 minutes each is 80 minutes, even if no single message looks hard.

Is it better to do the long threads first?

That’s a question about method. The two-minute rule for email covers the order in which people work through mail, and where each order breaks.

How many long threads should I expect in a day?

There’s no reliable published average, so count your own. How long email should take each day has a one-morning count that gives you the number of long threads and the minutes they take.

The short version

  • Five signs in the inbox list predict a slower thread: a request, an outside sender, an attachment, several people and a long thread.
  • A Microsoft Research study of 938,035 emails measured slower replies on each of the five.
  • Thread minutes are reading plus finding plus writing, for every round. Reading runs about 238 words a minute.
  • One two-hour thread can nearly triple a day’s long-thread time. Spotting it saves more than shaving the small ones.
  • Tally your guesses against the clock for one week. The ratio is your multiplier.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.