Executive Time and Decision Systems

Executive Email Statistics: Workload and Response-Time Benchmarks

Executive email statistics on workload, deferral, revisits, and response behavior, with source methods and practical inbox measures.

Published | Reviewed | ExecutiveSupportStaff Editorial Team

executive email statistics

Email workload dashboard showing message volume, reply time, and deferred messages

Abstract

No authoritative dataset supplies a universal email count or reply-time target for executives. The best disclosed evidence covers broader commercial users and information workers. Microsoft telemetry from March 2023 found that the heaviest quartile of email users spent 8.8 hours a week reading and writing email. [1] A separate study of 40,000 enterprise users found that 3 percent of messages were deferred and that 16 percent of active users deferred at least one message on a typical weekday. [3] These figures describe different populations and behaviors. They are starting points for a local inbox baseline, not executive service-level standards.

Methodology

This review uses first-party telemetry and peer-reviewed workplace research with disclosed samples. Microsoft published its Work Trend Index on May 9, 2023. Its email telemetry covers a rolling 28-day period ending in March 2023 and commercial Microsoft Exchange Online users; the related survey covered 31,000 workers in 31 markets from February 1 through March 14, 2023. [1] The 2016 CHI study logged 40 information workers for 12 workdays and paired activity records with biosensors and daily surveys. [2] The 2019 WSDM study combined 15 interviews with about three million recorded actions from 40,000 anonymized enterprise Outlook users between May 6 and May 19, 2018. [3] The 2018 CHIIR study used large-scale message logs plus a survey, while Microsoft's 2024 Copilot analysis covered 6,317 employees at 58 customer organizations. [4][5] None isolates executives as an occupation.

What the evidence can support

The evidence supports a workload baseline built from time in email, deferral behavior, message revisits, and local response distributions. Microsoft telemetry supplies scale, while the peer-reviewed logging studies explain behaviors that a weekly average can hide. [1][2][3][4][5] None of these sources reports a representative executive-only average or a universal response target.

The broader evidence also connects email to boundary pressure, checking frequency, interruptions, and reported strain. [6][7][8][9][10] These studies use different populations and measures. Some are surveys, some are experiments, and some analyze product activity. Together they justify measuring the local inbox. They do not justify combining their figures into a synthetic executive benchmark.

The strongest workload figure is not an executive average

In Microsoft's March 2023 telemetry, the top 25 percent of commercial users by email duration spent 8.8 hours a week reading and writing email. [1] The same report estimated that the average user spent 15 percent of measured Microsoft 365 activity in email. Meetings, chat, and document work made up the rest of the observed activity. The report does not publish an executive-only cut, an inbox message count, or the distribution behind the 8.8-hour figure.

That distinction matters. The figure describes heavy users within one product environment, not the typical chief executive. It also measures intentional application activity rather than every minute of attention or all work performed outside Microsoft 365. A team can use 8.8 hours as context, but should not present it as the average executive's weekly inbox burden.

Deferral is measurable, but it is not the same as neglect

The WSDM study defined a deferred email as one first read in one session and answered, forwarded, or replied to in a later session. Across about three million actions, 3 percent of messages met that definition. At least one deferral appeared in 12 percent of triage sessions, and 16 percent of active users deferred a message on a typical weekday. [3] All 15 interview participants also described deferring email, often because a response needed more time or information.

A deferred message can represent sound judgment. An executive or assistant may need to collect facts, consult another owner, or wait for a decision. The operational risk is an item that loses its owner or return date. The executive inbox management guide covers the working rules, while the email triage guide for executive assistants explains how to separate urgent, delegated, and deferred work.

Email time, productivity, and stress should not be collapsed into one claim

The 2016 CHI field study found that longer daily email duration was associated with lower perceived productivity and higher measured stress among 40 information workers. [2] People who relied on notifications differed from people who self-interrupted to check email. Batching was associated with higher rated productivity when email duration was longer, but the researchers found no evidence that batching reduced stress.

This was a small observational workplace study. It can support testing notification rules or scheduled processing windows, but it cannot establish that email caused the reported outcomes. It also cannot tell a leadership team how many daily messages are safe or productive.

Revisits reveal hidden inbox work

The 2018 CHIIR study found that more than one third of observed emails had a lifetime shorter than five minutes. In its accompanying survey, 73 percent of revisits were made to find information and 20 percent were made to respond. [4] A revisit is not automatically waste. Messages often hold instructions, files, or earlier decisions that people need again.

Still, repeated searching can expose a weak handoff between email and the system of record. When a message creates a task, decision, or deadline, move that state into the agreed tracker instead of expecting the inbox to preserve it. Keep the original message linked when the record matters.

Measure response time by urgency and coverage

The cited studies do not establish a universal executive reply-time benchmark. Measure local response time from receipt to a meaningful acknowledgment during the documented coverage window. Report the median and 90th percentile separately for urgent, routine, and information-only messages. An automated receipt does not count as acknowledgment.

Pair speed with outcome measures. Track the share of messages that needed a reply, the share answered within the agreed window, deferrals without a return date, reopened threads, and responses later corrected by the executive. Faster replies are not an improvement if they create more rework or encourage every sender to label a message urgent.

Build a four-week executive email baseline

Choose four representative weeks and record message counts, sender class, urgency, first meaningful response time, final resolution time, owner, and deferral status. Exclude message bodies unless a defined review requires them. Separate automated mail and newsletters from messages written by people, and note board weeks or transactions that distort normal volume.

Review the distribution rather than one average. Compare normal and peak weeks, then change one rule at a time. A rule might reroute routine scheduling, require a return date for deferred decisions, or reserve a non-email channel for genuine emergencies. Teams that need help designing the support model can contact ExecutiveSupportStaff after establishing the baseline.

Limits of executive email benchmarks

The main limitation is that product telemetry records behavior inside a platform, while surveys record what participants report. Neither explains the meaning, difficulty, confidentiality, or business value of a message. The peer-reviewed studies use enterprise or information-worker samples rather than representative samples of executives. Vendor datasets may also reflect product design and customer mix.

Microsoft's 2024 customer analysis found that the typical person read about four emails for every email sent, and it reported lower email-reading time for Copilot users at two participating companies. [5] Those intervention results came from selected customers and do not replace a neutral executive benchmark. Use all of these statistics to shape local measurement, not to score an individual or promise a response time the evidence does not support.

Key findings

  • The heaviest quartile of commercial Microsoft email users spent 8.8 hours a week reading and writing email in March 2023. [1]
  • In a 40,000-user enterprise sample, 3 percent of messages were deferred and 16 percent of active users deferred at least one message on a typical weekday. [3]
  • Among surveyed email revisits, 73 percent were for finding information and 20 percent were for responding. [4]
  • A 40-person field study associated longer email duration with lower perceived productivity and higher measured stress, but it did not establish causation. [2]
  • No cited source provides a representative executive email count or universal reply-time target.

Sources

  1. Work Trend Index Annual Report: Will AI Fix Work?, Microsoft WorkLab
  2. Email Duration, Batching and Self-interruption: Patterns of Email Use on Productivity and Stress, ACM CHI via Microsoft Research
  3. Characterizing and Predicting Email Deferral Behavior, ACM WSDM via Microsoft Research
  4. The Lifetime of Email Messages: A Large-Scale Analysis of Email Revisitation, ACM CHIIR via Microsoft Research
  5. AI Data Drop: 3 Key Insights from Real-World Research on AI Usage, Microsoft WorkLab
  6. Breaking down the infinite workday, Microsoft WorkLab
  7. Stress in America: Coping with Change, American Psychological Association
  8. Checking email less frequently reduces stress, Computers in Human Behavior
  9. Stress and productivity patterns of interrupted, synergistic, and antagonistic office activities, Scientific Data
  10. Email Overload at Work: An Analysis of Factors Associated with Email Strain, Microsoft Research

Return to the Research Content library