Executive Document Approval Cycle Statistics 2026: Volume, Delay, and Delegation Data

Executive document approval cycle statistics are often presented as if every contract, policy, purchase request, and board paper moves through the same process. It does not. Public research usually measures management decisions, executive calendars, or a specific regulated workflow. Software vendors publish faster turnaround claims, but those figures may come from customer samples or commissioned studies.

The most defensible 2026 view is therefore a set of related measures, not one universal approval time. McKinsey's 2018 global survey measured decision workload across 1,259 business leaders. Porter and Nohria tracked how 27 CEOs used nearly 60,000 hours. A peer-reviewed university study measured thousands of research-protocol approvals. Each source answers a different part of the approval question.

This article labels measured cycle time, survey responses, modeled costs, and vendor benchmarks separately. That distinction matters when an organization sets a service-level target or estimates how much review work can be delegated.

Executive approval statistics at a glance

Sources: McKinsey's decision-making survey, Porter and Nohria's CEO time study, and the UC San Diego approval-workflow study.

The table should not be averaged into a synthetic approval cycle. A survey response about organizational speed is different from a timestamp recorded in a workflow system. A protocol that must pass regulatory review is also different from a routine expense approval.

How much decision work reaches senior leaders?

McKinsey surveyed 1,259 members of its Online Executive Panel in 91 countries in February 2018. One-third of respondents were C-level executives and 35% were senior managers. Respondents spent 37% of their working time making decisions on average. More than half spent over 30% of their time on decisions, and 14% of C-suite respondents said decision making consumed more than 70% of their time.

Those are decision-volume measures, not document counts. The survey covered infrequent, high-stakes decisions, cross-cutting decisions, and smaller routine decisions that could be delegated. It did not report how many files each executive signed or how long a single approval sat in a queue.

The study still provides a useful workload boundary. Approval work competes with every other decision an executive must make. If a dashboard counts only documents, it can miss the meetings, research, consultation, and conflict resolution behind each approval.

McKinsey also found that 57% of C-level respondents said most of their decision-making time was ineffective. Across all respondents, the figure was 61%. Only 20% said their organizations excelled at decision making. These results are perceptions from business leaders, not stopwatch observations, but they show that volume alone is an incomplete performance measure.

Why approval delays need a clear clock

“Approval time” can refer to at least four different clocks:

1. total elapsed time from submission to final disposition
2. active review time while an approver reads or edits
3. queue time while the document waits for an owner
4. rework time after a rejection or request for changes

A system that reports only active review time may hide days in a queue. A system that reports only elapsed time may blame the approver for time spent correcting an incomplete submission. Good reporting stores both timestamps and reason codes.

The UC San Diego study shows why that separation matters. Researchers analyzed 3,389 new human-research protocols submitted in 2013 and 2014 and followed later operational measures. As new applications per full-time staff member increased from 69 in 2013 to 72 in 2016, median administrative time rose from 13 days to 25 days. Median overall approval time rose from 75 days to 86 days.

The authors also compared committees handling similar phase III multisite commercial studies. One committee had a median review and approval time of 53 days, significantly longer than its peers. Workflow analysis identified duplicate scientific review. After training and performance feedback, its median time matched the other committees.

This is measured cycle-time evidence, but it belongs to a regulated university research setting. It should not become a target for contracts, policies, invoices, or marketing documents. Its practical lesson is narrower: workload per reviewer and duplicate review can be measured, and both can affect elapsed time.

Reporting layers and decision speed

The 2018 McKinsey survey found a clear association between organizational layers and reported speed. Among respondents at organizations with one to three reporting layers, 61% agreed that decisions were made quickly. The share fell to 47% at organizations with four to six layers and 38% at organizations with seven or more.

The corresponding figures for high-quality decisions were 70%, 53%, and 45%. Fewer layers were associated with both speed and reported quality in this survey. The result does not prove that deleting an approval step will improve outcomes. Industry, company size, decision type, and organizational health may influence both structure and performance.

Before removing a review, identify the risk it controls. A legal review, segregation-of-duties check, or board authorization may be mandatory. Duplicate status checks, undefined “FYI” reviewers, and approvals that add no decision are better candidates for redesign.

Executive calendars constrain document review

Michael Porter and Nitin Nohria asked 27 CEOs to track their time for 13 weeks. The resulting dataset covered nearly 60,000 hours. The CEOs spent 72% of their work time in meetings and 28% alone. About 75% of their scheduled time was planned in advance, while 25% was spontaneous.

The study did not isolate document approvals, and it did not label meetings as wasted time. It does show why an approval request can wait even when its active reading time is short. Review must fit into limited solo time or enter a scheduled meeting.

Teams can reduce avoidable delay by packaging the decision before it reaches the executive. A complete approval packet states the requested decision, deadline, owner, options, recommendation, material risks, and prior reviewers. That is an operating practice, not a claim from the CEO time study.

For related evidence on calendar pressure, see executive time management statistics and executive interruption recovery cost statistics.

What delegation evidence supports

McKinsey reported that respondents who said decisions were made at the right organizational level were 6.8 times more likely to work at a company the researchers classified as a winner. “Right level” often meant moving routine decisions lower in the organization. This is an association within the survey, not proof that delegation created superior financial performance.

Gallup provides another executive-specific data point. Its study of 143 CEOs on the 2014 Inc. 500 list compared leaders with high Delegator talent against those with lower scores. Companies in the high-delegator group had average 2013 revenue of $8 million, versus $6 million in the comparison group. They also reported a three-year average growth rate 112 percentage points higher.

The Gallup sample is small and unusual. Inc. 500 companies are fast-growing private businesses, and the observational design cannot show that delegation caused the revenue difference. The result supports measuring delegation, but it does not justify a promised return on handing off approval work.

An executive assistant can prepare a document register, check required fields, collect prior reviews, flag deadlines, compile questions, and route routine decisions under written authority. The executive retains decisions that require personal, fiduciary, legal, or board-level authority. Organizations considering that model can compare an executive assistant service with support for a busy executive.

Measured cycle time versus vendor benchmarks

Vendor research can help a buyer understand a product category, but it needs a separate label. Forrester's 2021 systems-of-agreement report, for example, was commissioned by DocuSign. A commissioned study is not automatically invalid. Its sponsor, sample, definitions, and method must stay visible when results are used.

Do not combine a vendor's customer turnaround figure with an internal approval clock unless both measures start and stop at the same events. “Sent to signed” may exclude drafting and internal review. “Request to approval” may exclude implementation. A median can also look much faster than a mean when a small number of documents remain stuck for weeks.

For a defensible internal benchmark, publish:

• document type and risk tier
• number of completed items and measurement period
• start and stop events
• median, 75th percentile, and 90th percentile elapsed time
• active review time and queue time
• number of review rounds and rejection reasons
• percentage completed within the stated service level

The baseline should come from the organization's own timestamped records. External figures provide context, not a substitute for that baseline.

A practical approval-cycle scorecard

Measure volume as the number of approval requests received, completed, rejected, withdrawn, and still open. Split the count by document type and risk tier so ten routine expense approvals do not look equivalent to ten acquisitions.

Measure delay with median and percentile cycle times. The median describes the typical item. The 90th percentile exposes the long tail. Also report current aging buckets, such as zero to two days, three to five days, and more than five days.

Measure delegation as the share completed under delegated authority, the share prepared by support staff but decided by the executive, and the share escalated. Record the escalation reason. A low escalation rate is not automatically good if staff are approving work outside their authority.

Finally, measure quality. Track rework, reversals, policy exceptions, missed deadlines, and audit findings. Faster approval is useful only when required controls and decision quality remain intact.

Frequently asked questions

What is the average executive document approval time?

No authoritative source in this review establishes one cross-industry average. Cycle time depends on document type, risk, required reviewers, and how the clock is defined. Use timestamped internal data and report the definition with the result.

How much time do executives spend making decisions?

In McKinsey's 2018 survey of 1,259 business leaders, respondents spent 37% of working time making decisions on average. The survey did not say that all of this time involved documents.

Do more approval layers cause longer delays?

McKinsey found that reported decision speed was lower in organizations with more reporting layers. The survey shows an association, not proof of causation. Some reviews are required controls, while others may be redundant.

Should an executive delegate document approvals?

Routine, low-risk decisions can be delegated when written authority permits it. Support staff can also prepare and route higher-risk requests without making the final decision. Legal, fiduciary, personnel, and board matters need authority-specific rules.

Which approval metric is most useful?

No single metric is sufficient. Use volume, median cycle time, a tail percentile, queue time, review rounds, delegated share, and quality outcomes together.

Sources

1. McKinsey, Decision making in the age of urgency, 2019, reporting a February 2018 online survey of 1,259 participants in 91 countries.
2. Porter and Nohria, What Do CEOs Actually Do?, 2018, time-use study of 27 CEOs for 13 weeks each, covering nearly 60,000 hours.
3. Hall et al., Systems approach to assessing and improving local human research Institutional Review Board performance, 2019, workflow analysis including 3,389 new protocols submitted in 2013 and 2014 and later operational data.
4. Gallup, Delegating: A Huge Management Challenge for Entrepreneurs, 2015, study of 143 CEOs on the 2014 Inc. 500 list.
5. Forrester Consulting, State of Systems of Agreement, 2021, a study commissioned by DocuSign and included here to explain vendor-benchmark disclosure.