Capacity benchmark

Executive support span of control benchmark in 2026

How to size executive support capacity by workload mix, decision rights, communication load, and coordination complexity.

Research desk with charts, planning matrix, and executive support capacity materials
Key takeaway: There is no universal executive-support ratio. Use public labor data to frame the role, then set capacity from the leaders, workflows, risk, and service levels actually in scope.

Key stats

MeasureValueContext
Occupation employment502,800 jobs in 2024BLS estimate for executive secretaries and executive administrative assistants; it describes the occupation, not a recommended support ratio. [2]
Median annual wage$74,260BLS median annual wage in May 2024 for executive secretaries and executive administrative assistants; it is a labor-market anchor, not an all-in service price. [2]
Communication load60% of Microsoft 365 timeMicrosoft's 2024 Work Trend Index measure for time spent in email, chats, and meetings; it is context for coordination load, not a staffing ratio. [9]
Work-volume pressure68%Microsoft reports that 68% of surveyed people struggle with the pace and volume of work in its 2024 survey. [9]

Key takeaways

  • Count workload categories and decision risk, not just the number of executives supported.
  • Separate calendar and inbox administration from research, board, project, and confidential work.
  • Define what support may decide, draft, route, or escalate before comparing ratios.
  • Pilot a capacity model against four weeks of actual work and revise it from queue and rework data.

Support model comparison

ModelCost anchorManagement
One leader, high discretionDeep context, access, and priority protectionDirect escalation and narrow decision boundaries
Several leaders, shared workflowsCommon calendar, inbox, meeting, and reporting systemsQueue rules and a named priority owner
Fractional executive operationsRecurring cadence plus project and decision supportMilestone planning and cross-functional escalation
Managed support teamCoverage, specialization, and backup capacityService levels, QA, security, and account ownership

Why a fixed ratio is misleading

Executive administrative work includes scheduling, correspondence, records, reports, research, information requests, and coordination. O*NET's task and work-context data show why two leaders with similar titles can create very different support loads. [1][2]

A useful span-of-control benchmark therefore starts with the work mix: recurring administration, preparation, stakeholder routing, project follow-through, travel, board material, and sensitive cases. The ratio is an output of that brief, not a substitute for it. [3][4][5]

Build a capacity model

For four weeks, log each request by leader, category, estimated effort, urgency, sensitivity, required judgment, and blocked-by reason. Record recurring meetings and preparation separately from exceptions so a busy calendar does not conceal research or follow-up work. [1][6][7]

Then assign the support role an explicit decision boundary. Support may prepare, route, draft, and track; the accountable executive retains consequential judgment unless a narrower delegation is documented. This keeps a capacity ratio from becoming an accidental transfer of authority. [8][5][2]

Use public data as context, not proof

BLS reports 502,800 executive secretaries and executive administrative assistants in 2024 and a $74,260 median annual wage in May 2024. Those figures help frame labor-market availability and direct-hire cost, but they do not tell a company how many leaders one person can support. [2][3]

Microsoft's 2024 Work Trend Index reports that 60% of Microsoft 365 time was spent in email, chats, and meetings and that 68% of surveyed people struggle with work volume. The findings support measuring communication and coordination load, not applying a universal staffing rule. [9][10][11]

Choose and test the support model

Use dedicated support when one leader's confidentiality, access, or context switching makes shared queues unsafe. Use shared support when workflows are standardized and a priority owner can resolve conflicts. Use fractional or managed support when the team needs coverage, specialization, or operating-rhythm ownership. [12][4][8]

Technology may reduce retrieval and drafting effort. McKinsey estimates $2.6 trillion to $4.4 trillion in potential annual value across 63 generative-AI use cases, while its estimate is not a staffing benchmark. Pilot one low-risk workflow, require human review, and compare queue age, rework, missed commitments, and executive time before changing the span of control. [13][14][7]

Sources

  1. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
  2. Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
  3. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
  4. ILOSTAT Labour Statistics, International Labour Organization.
  5. Creating helpful, reliable, people first content, Google Search Central.
  6. Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
  7. Search Engine Optimization Starter Guide, Google Search Central.
  8. World Development Indicators, World Bank DataBank.
  9. 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
  10. Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
  11. Productivity Statistics, OECD Data Explorer.
  12. Business Formation Statistics, U.S. Census Bureau.
  13. The economic potential of generative AI, McKinsey Global Institute.
  14. 2026 Work Trend Index Annual Report, Microsoft and LinkedIn.

Related research