Email Statistics, Fact-Checked: Which Numbers Are Real

The short answer
The '28% of the workweek on email' figure traces to a real 2012 McKinsey report, but only for the specific worker category it defined, not 'the average person.' Radicati's emails-per-day counts come from a named, long-running firm with a paywalled methodology. The widely repeated '121 emails a day' has no document anyone can point to.
Where email productivity statistics actually come from, and which widely quoted numbers no one can source.
On this page
Type "how many emails does the average person send" into a search bar and a confident number comes back — usually 121, sometimes 126, occasionally rounded into "the average person spends 28% of their day on email." Some of these are real, sourced, and dated. Others have been rounded, regeneralized, and passed through so many blog posts that nobody citing them today could point to the document they came from.
Where email productivity statistics come from turns out to matter more than the digits themselves — a number scoped to one job category in a 2012 report is a different claim than "the average person, right now," even when the figure is identical. This post traces the statistics people quote most often back to source, and says plainly which ones checked out and which didn't.
What actually makes an email statistic "sourced"?#
Every number in this post got checked against the same four questions, and most of the email statistics circulating online fail at least one of them.
A statistic is sourced when you can answer all four. A number can be technically real and still not mean what a headline implies — the McKinsey figure below is the clearest example of that gap.
- Who measured it, and when — a named firm or institution with a publication date, not "a recent study"
- What was actually counted — sent, received, or both; work email, personal email, or unspecified
- What population it covers — everyone, a defined worker category, or one company's own product users
- Whether the methodology is public — a stated sample size and method, or a number asserted without one
How do you verify a productivity statistic?#
The same six-step check works on any number, not just the ones in this post.
- 1
Find the most specific source claimed
"Studies show" is not a source. Look for a named firm, institution, or report — "the Radicati Group's Email Statistics Report" is checkable; "research indicates" is not.
- 2
Go to the primary document, not the post quoting it
Most email-statistics roundups, including several ranking for this exact query, cite each other rather than the original report. Search for the report's own title and publication year directly.
- 3
Check what population it actually covers
"Interaction workers" in a 2012 McKinsey report and "the average person" are not the same claim, even when a later post uses the two interchangeably.
- 4
Check whether the method is stated or asserted
A number pulled from real product usage and a number from a firm's undisclosed proprietary model can both be accurate, but only one shows its work. Treat them differently.
- 5
Check the date, then check it again
A figure from 2012 or 2014 quoted with no year attached reads as current. Several of the most-repeated email statistics are ten-plus years old.
- 6
If you can't complete steps two through five, call it unverifiable
Not wrong, not corrected — unverifiable. Inventing a "more accurate" number to replace one you can't source is worse than repeating the original, because it looks verified when it isn't.
How does each source's methodology actually compare?#
Six sources account for nearly every email statistic in circulation, and they are not interchangeable. A usage count pulled from one company's own product telemetry and a global estimate from a paid market-research model are both "real," but they answer different questions and don't substitute for each other.
| Source | What it actually tracks | Can you check the method | Where it gets misused |
|---|---|---|---|
| The Radicati Group — Email Statistics Report | Global email volume and user counts, updated most years | Executive summary is free; the underlying survey methodology is sold with the paid report | Cited as if the full methodology were public |
| McKinsey Global Institute, 2012 | Time allocation for a category the report calls "interaction workers" | Described as proprietary McKinsey data plus a separate IDC survey, not a single measurement | Generalized to "the average person" or "average professional," a claim the report never made |
| Microsoft Work Trend Index, 2025 | Actual Microsoft 365 usage signals plus a 31,000-person survey | Sample size, exclusions, and collection window are published | Reported as "the average worker" without noting it excludes education and EU tenants |
| Adobe Email Usage Study, 2019 | Self-reported time spent checking email | Sample size — about 1,000 US adults — and method are named | A self-estimate treated as a measured, logged number |
| Pew Research Center | Survey-based adoption and use of email among US adults | Full methodology published for each survey wave | Numbers from 2011 to 2014 cited as if they were current in 2026 |
| US Bureau of Labor Statistics — American Time Use Survey | Broad daily activity categories: paid work, leisure, computer use | Fully public, government-run time-diary survey | Cited as government-confirmed proof of an email-specific number the survey doesn't actually code |
The same 28% turns into different "hours a day" depending who does the arithmetic
That's the pattern worth remembering. Some of these sources publish a stated method next to their numbers. Some publish the number and sell the method separately. And some numbers are real but have already lost their original scope by the third post to repeat them — which is exactly what happened to the McKinsey figure above.

What if a statistic turns out to be unverifiable?#
"121 emails a day" is one of the most repeated numbers in this category, usually attributed loosely to "a recent report by the Radicati Group." We traced it as far as a 2015 news article that cites Radicati with no link to a specific report, and couldn't get further — and we weren't the only ones to hit that dead end during this research. Radicati's own more recent reports state a different, evolving figure for a related but not identical measure: business emails sent plus received per business email user per day, which is a narrower and more precise thing than the loosely worded "121 emails a day" that circulates.
That's a genealogy problem, not necessarily a wrong-number problem — the real Radicati series exists and updates most years. The specific "121" citation just doesn't connect back to a document anyone can produce.
When you hit that kind of dead end, three honest options exist. Cite the current, checkable topline from the source that actually publishes one, instead of an older ungrounded figure. Describe the finding qualitatively without a false-precision number — "professionals handle well over a hundred emails a day" instead of an exact digit you can't source. Or say plainly that the number is unverifiable and leave it out of your argument.
What doesn't belong on that list is inventing a "more accurate" replacement number. That adds one more unverifiable link to the same broken chain, except now it reads as a correction — which makes it more convincing and no more true.
A faster way: check your own inbox instead of the internet's#
Every statistic in this post, even the well-sourced ones, describes someone else's inbox — a 2012 knowledge worker, a Microsoft 365 tenant, a thousand Adobe survey respondents. None of them describes yours, and an average this contested isn't a great foundation for a decision about your own workload anyway.
AI Emaily's AI email assistant can answer the same question directly, against your actual mailbox: how many threads you closed last week, your real median response time, how this month's volume compares to last. That's a number with a sample size of one, a stated method — it's your mail — and a publication date of right now, which is more than most of the figures above can claim.
We build AI Emaily. It won't tell you what "the average person" does. It'll tell you what you do.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- McKinsey Global Institute — The Social Economy: Unlocking Value and Productivity Through Social Technologies (2012)
- The Radicati Group — Email Statistics Report, 2024-2028
- Pew Research Center
- US Bureau of Labor Statistics — American Time Use Survey
- Microsoft Work Trend Index 2025 — Breaking Down the Infinite Workday

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.