Key Takeaways
- O*NET identifies schedule management, travel, correspondence, report preparation, and office coordination as core EA tasks.
- O*NET respondents report daily email use for 97%, daily telephone conversations for 99%, and constant contact with others for 80%.
- The O*NET occupation had 502,800 employed workers in 2024 and 50,000 projected openings from 2024 through 2034.
- There is no authoritative universal executive-to-EA ratio or weekly task-hour benchmark for every organization.
Executive assistant capacity is often discussed as a simple coverage ratio. In practice, one EA can support a senior leader with a dense, well-structured calendar or struggle with a smaller group whose priorities, travel, and communications change by the hour. The useful unit is not a universal ratio. It is the workload created by the work system.
This research page uses public occupational and executive time-use sources to identify measurable workload signals. It does not claim a standard number of executives, meetings, or weekly hours that every EA should support.
What the occupation includes
The O*NET profile for Executive Secretaries and Executive Administrative Assistants defines the occupation as high-level administrative support. Its core tasks include managing executive schedules, arranging travel, preparing invoices and reports, coordinating office services, preparing routine correspondence, and handling information requests.
That task list matters because an EA role combines planned work with interruption-prone coordination. A calendar change may trigger a travel update, a meeting brief, participant communication, and a document revision. Counting only meetings or only inbox messages misses the linked work around each event.
| O*NET task | Capacity implication |
|---|---|
| Manage and maintain executive schedules | Measures calendar complexity, not only meeting count |
| Make travel arrangements | Often bundles booking, policy, changes, and expense follow-up |
| Prepare reports and correspondence | Requires accuracy, context, and review standards |
| Coordinate office services | Can create cross-functional dependencies and urgent exceptions |
| Compile research and materials | Needs a clear definition of source quality and decision use |
Communication intensity is a real workload signal
The O*NET work-context summary reports that 99% of respondents have telephone conversations every day and 97% use email every day. It also reports that 80% have constant contact with others, while 45% experience time pressure at least weekly.
These are occupational survey descriptors, not a live benchmark for one team. O*NET notes that task and work-context data can have different collection years, so the figures should be treated as a structured description of the role rather than a current real-time census. The O*NET update record provides those field dates.
Still, the pattern is useful: EA capacity is vulnerable to unplanned coordination because the role is communication-heavy by design. If several executives make late changes and all routing decisions return to one person, the calendar can look manageable while the unseen follow-up queue grows.
Labor-market context
O*NET reports 502,800 people employed in this occupation in 2024, with projected employment decline of 1% or lower over 2024 to 2034 and 50,000 projected openings. These figures draw on Bureau of Labor Statistics wage and employment projections.
The projection does not establish that demand for high-trust executive support is disappearing. It is an occupation-wide estimate that can reflect technology, organizational design, and replacement needs. It also does not show how many executives a particular EA can support.
Executive time creates the demand side
The demand for EA support also depends on how leaders spend time. The NBER review of CEO time-use research describes diary data from 1,114 CEOs in six countries, covering 42,233 activities and an average of 50 working hours per CEO. At the median, meetings accounted for more than half of working time.
This is CEO evidence, not EA workload evidence. It is nevertheless relevant because meeting-heavy executive work creates scheduling, preparation, participant, and follow-up work. The appropriate inference is that executive calendar design affects EA demand. It is not evidence that every EA works a given number of hours or that a specific support model will increase productivity.
Measure load with a service model
An EA team can create a more reliable capacity view by tracking workload in categories that match its operating model. Start with a four-week baseline and review it with the person doing the work.
| Metric | How to track it | What to look for |
|---|---|---|
| Calendar complexity | Meetings, external participants, time zones, changes within 24 hours | Change volume and exception load |
| Request intake | New requests by channel and priority | Work arriving outside the agreed queue |
| Preparation work | Briefs, agendas, travel plans, and materials completed | Hidden work attached to each event |
| Rework and escalations | Corrections, missed handoffs, and manager intervention | Quality risk from overload or unclear rules |
| Protected work | Blocks for proactive planning and project work | Whether urgent coordination consumes all capacity |
Use service levels that fit the team. A board-meeting change should receive a different response time from a routine calendar request. Document the decision owner for each type of request, especially where confidentiality or executive judgment is involved.
Capacity levers to test
The first lever is usually not hiring. It is reducing preventable variation: one intake channel, calendar rules, standard travel preferences, reusable meeting-brief templates, and a clear delegate for routine approvals. A second lever is defined support for repeatable work, including a virtual assistant or coordinator operating within approved access and review boundaries.
Any support model needs a quality and privacy check. A task that is repetitive is not automatically suitable for delegation. Sensitive personnel, legal, financial, or board work needs the correct authorization and escalation route.
Caveats
- There is no authoritative universal executive-to-EA ratio. Team structure, executive behavior, time zones, and confidentiality needs change the answer.
- O*NET describes the occupation and includes fields collected at different times. It is not a live workload audit.
- CEO diary research informs the demand created by executive time use, but it does not measure EA output or establish an ideal staffing model.
- Count quality and rework alongside volume. A faster queue that creates missed commitments is not added capacity.
Related reading
- Administrative turnover reduction statistics with VA support
- How CEOs delegate effectively
- Executive assistant services
Sources
Tags
Ready to put this into practice?
Book a free 15-min match call
Tell us what role you're filling. We'll match you with a pre-vetted virtual assistant - or tell you honestly if we're not the right fit.
Book a free call →