Executive inbox triage benchmarks: volume, latency, and response expectations

An executive inbox does not need a universal quota. It needs an agreed operating rule for what gets seen, by whom, and how quickly. This research brief separates the measurable parts of that problem: message volume, triage latency, response latency, and the risk of treating every urgent-looking message as urgent.

TL;DR

The public evidence does not establish a single healthy number of emails per day or a universal promise such as "reply within an hour." Research uses different populations and denominators. A global survey can describe interruptions across knowledge work, while a small qualitative study can describe the experience of email-heavy workers. Neither is an executive inbox benchmark.

For an executive support team, use published research to choose what to measure locally. Start with a two-to-four-week baseline. Track arrival volume, the time until an item is classified, the time until the executive has a decision-ready brief, age by category, and the share of items escalated as urgent that were later reclassified. Set response targets by category, not by inbox-wide average.

Contents

• Methodology
• Limitations
• Key statistics
• Key takeaways
• A responsive evidence table
• Analysis
• FAQ
• Sources

Methodology

This review was retrieved on August 1, 2026. It prioritizes peer-reviewed papers, government data, and primary institutional reports. Vendor research is included only when the publisher states the sample and method. The source set covers work-email behavior, interruption, response expectations, workplace communication, and business-email compromise.

For each source, the review records the publication or update date, geography, sample, unit of analysis, and denominator where the source makes those details available. "Volume" means messages received or sent. "Triage latency" means time from arrival to classification or routing. "Response latency" means time from arrival to a reply. "Decision latency" means time from arrival to a decision or a decision-ready packet. Most published sources report volume or perceived expectations, not triage latency. That gap is why teams need a local measurement plan.

Limitations

The evidence is not executive-specific in most cases. Executives vary by role, industry, time zone, regulatory exposure, and assistant coverage. Survey results are not the same as telemetry, and a small interview sample is not a population estimate. Complaint data captures reported incidents, not all incidents. Historical email studies may not transfer cleanly to current collaboration tools.

The figures below are therefore comparison points, not service promises. They should not be averaged, added together, or used to grade an assistant without context. The most defensible benchmark is the one a team defines in advance and checks against its own work.

Key statistics

• Microsoft reported that its 2025 Work Trend Index combined global survey and observational work, with survey data from 31,000 workers in 31 countries. Its executive summary reported 275 interruptions per day by a meeting, email, or chat during work hours. The denominator is workers in the study, not executives and not email alone.
• A 2025 qualitative study interviewed 30 knowledge workers, with 28 usable responses. Those respondents reported an average of 64 work emails received and 48 sent on a typical workday. The sample came from public-sector education and a private insurance firm. It is a description of interviewees, not a global benchmark.
• Russell and colleagues' 2024 systematic review synthesized 62 empirical papers. Its framework identifies regular triage and communicated access boundaries as practices linked to effective work-email activity. This is a literature synthesis, not a new response-time survey.
• Giurge and Bohns' paper reports eight preregistered studies with N = 4,004. In one archival analysis of 1,515 U.S. employees, 51.1% had sent or responded to email outside normative work hours. The studies also found that receivers overestimated how quickly senders expected replies to non-urgent off-hours email.
• A 2016 CHI field study logged 40 information workers for 12 workdays. Longer daily email time was associated with lower perceived productivity and higher measured stress. The study tested patterns of email use, not executive performance.
• A 2022 quasi-experimental study in a Dutch financial-services organization found that batching reduced email interruptions. The effect on emotional exhaustion was strongest for people with high email volume and organizations that did not expect instant replies, and it wore off after two weeks.
• A 2022 analysis of digital communication patterns reported a 48.5-minute increase in average workday span after lockdowns, defined as the interval between the first and last email or meeting. This measures span, not time spent reading email.
• The FBI's 2025 Internet Crime Complaint Center report recorded 24,768 business-email-compromise complaints in 2025 and 21,442 in 2024. Its complaint-loss table reports $2,770,151,146 in BEC losses for 2024. Complaint counts and reported losses are not prevalence estimates.

Key takeaways

1. Treat volume as a workload signal, not a quality score. A short message that requires a wire-transfer check can carry more operational risk than a long scheduling thread.
2. Separate classification from response. An assistant may acknowledge, route, draft, or prepare a decision without sending the final answer.
3. Publish response expectations. The research on email urgency bias suggests that silence invites recipients to assume a faster deadline than the sender intended.
4. Batch routine work only where the role allows it. Batching can reduce interruptions, but it is a poor fit for live incident coverage or clearly defined time-sensitive work.
5. Build security into triage. A request to change payment details, share credentials, or bypass a normal process is a verification event, not a fast-reply event.

A responsive evidence table

Analysis

Volume is not triage latency

An inbox can receive 80 items and still be under control if 70 are newsletters, receipts, or threads with a clear owner. It can receive 20 items and be overloaded if six require judgment from the executive and arrive without context. Count arrivals, but add a classification field: delete, archive, delegate, draft, schedule, executive decision, or security review.

The assistant's first service level is often classification. A useful target might be that all new items are classified by the next agreed triage window, with exceptions for defined incident categories. That target is locally chosen. It should not be inferred from a vendor's average response claim.

Response time needs a category and an owner

"Respond within one hour" hides several different actions. It might mean acknowledge receipt, provide a substantive answer, send a draft for approval, or decide whether the message belongs on the executive's radar. These actions have different costs and different owners.

Create a small matrix. Routine scheduling can have a same-business-day target. A live customer or board issue may need a defined escalation channel. A sensitive finance or access request needs verification before speed. The executive's assistant can maintain the matrix and report misses without turning every miss into a performance judgment.

The inbox is also an access-control surface

IC3's BEC reporting makes the security point concrete. An executive inbox is attractive because a convincing message can appear to authorize money movement, credential sharing, or a change in a trusted relationship. CISA recommends phishing-resistant multifactor authentication where possible. The FTC recommends checking a request through a known phone number or other independent channel.

Triage rules should therefore include a stop condition. If a message requests a payment-detail change, password, one-time code, sensitive file, or unusual urgency, pause the workflow and verify. A fast reply is not a successful triage outcome if the request itself is fraudulent.

A practical local benchmark

For two to four weeks, record only low-risk operational metadata:

• arrival time and category;
• time classified and routed;
• time a draft or decision-ready brief reached the executive;
• time of final response, if one was required;
• whether the item was reclassified as urgent;
• whether the item needed an out-of-band security check.

Review medians and the oldest open items, not just averages. Compare like with like: investor requests with investor requests, scheduling with scheduling, and incident messages with incidents. After the baseline, change one rule, such as a twice-daily routine triage window or a standard acknowledgment template. Review it after two weeks and keep it only if it improves the agreed outcome without pushing work into unhealthy hours.

For a practical operating guide, see executive email triage and how to prioritize an executive inbox. For the security side of the workflow, see executive inbox phishing risk.

FAQ

What is a reasonable executive email response time?

There is no universal number supported by the evidence. Set a target by message category, urgency, sender group, and the executive's working hours. State whether the target means acknowledgment, routing, a draft, or a final answer.

How many emails does an executive receive per day?

Published studies do not provide a reliable executive-wide average. One 2025 qualitative study found 64 work emails received per typical workday among 28 usable interview responses, but its sample was not executive-specific.

What is triage latency?

Triage latency is the time between an item's arrival and its classification or routing. It is different from response latency, which ends when someone replies, and decision latency, which ends when the executive has decided or received a decision-ready brief.

Should executives use inbox zero?

Inbox zero is a workflow choice, not a research-backed requirement. A categorized queue with clear owners and aging rules can work just as well. Measure whether important work is found, prepared, and closed rather than whether the inbox count reaches zero.

How can an assistant triage safely?

Use defined authority boundaries, least-privilege access, phishing-resistant MFA where available, and an independent verification step for payment, credential, and access-change requests. Keep a short audit trail for escalations.

Sources

• Microsoft Work Trend Index 2025, published April 23, 2025; global survey and observational research, including 31,000 workers in 31 countries.
• Microsoft Work Trend Index 2025 executive summary, retrieved August 1, 2026; interruption statistic and denominator context.
• Russell et al., Getting on top of work-email, 2024, systematic review of 62 empirical papers.
• You’ve got mail: an emic investigation into email management, 2025, qualitative interviews with 30 knowledge workers, 28 usable responses.
• Giurge and Bohns, email urgency bias, 2021, eight preregistered studies, N = 4,004.
• Email duration, batching and self-interruption, CHI 2016, logged field study of 40 information workers over 12 workdays.
• For whom and under what circumstances does email message batching work?, 2022, quasi-experimental Dutch financial-services intervention.
• The impact of COVID-19 on digital communication patterns, 2022, analysis of email and meeting span.
• 2025 IC3 Annual Report, published 2026; U.S. complaint counts and reported losses.
• CISA: Require multifactor authentication, retrieved August 1, 2026; business account protection guidance.
• FTC: Cybersecurity for small business, retrieved August 1, 2026; independent verification guidance.
• NIST: Phishing guidance for small business, retrieved August 1, 2026; email authentication and phishing-resistant authentication guidance.

The source set was last verified on August 1, 2026. Vendor or publisher claims are labeled with their own sample and denominator and are not treated as universal benchmarks.

Related research

Read executive inbox phishing risk for the threat model behind verification rules. The operating guides on executive email triage and how to prioritize an executive inbox turn the measurement ideas here into a daily workflow.

If your inbox is consuming decision time, book a free consultation call to discuss an executive support workflow with explicit authority and response rules.