Email Response Time Calculator

Email is one of the biggest productivity drains in knowledge work. The McKinsey Global Institute put a number on it in its 2012 report on the social economy: office workers spend about 28% of the workweek reading and answering email, which is roughly 2.2 hours out of an 8-hour day. Response time expectations, though, vary enormously by context.

Typical response time norms:

• Urgent / same-day: target under 4 hours during business hours
• Standard business: target within 24 hours
• Low priority: within 3-5 business days
• Newsletter / FYI: no response required

This calculator estimates three things:

1. Daily email cost: (emails received) x (average handling time per email). If you get 120 emails and each takes 3 minutes to handle (read, decide, act, file), that is 6 hours, or 75% of an 8-hour day. Which explains why a lot of actual work happens after hours.

2. Break-even volume and backlog. Divide the minutes you have by the minutes each email costs and you get the number of emails per day you can actually absorb. At 3 minutes each with 2 hours set aside, that is 40. Every email past 40 becomes backlog, and backlog compounds: it grows by the same amount tomorrow unless something changes. The chart plots your time demand against your capacity so you can see where the two lines cross.

3. SLA (Service Level Agreement) compliance: given your current average response time and your target, what fraction of emails are you likely hitting on time. This assumes response times follow an exponential distribution, which is the standard model for a queue where arrivals are independent and you handle whatever is on top.

That third number surprises people. If your average response time equals your target exactly, you do not hit the target half the time, you hit it 63% of the time. The exponential distribution is lopsided: most replies come back fast, a long tail comes back late, and the average sits above the median. To hit a target 90% of the time your average has to be well under half of it.

The fix is rarely working faster. It is batching. Checking email two or three times a day at set times and processing to zero each session beats continuous monitoring for most knowledge workers, because the reload cost of an interrupted task dwarfs the 30 seconds the email itself took.