Published October 15, 2026. A current BLS and O*NET evidence review for scoping executive-assistant work, screening candidates, and separating coordination from retained authority.
Decision this research supports
A buyer deciding whether to hire an executive assistant needs a role definition before comparing candidates or providers. The useful question is not whether a person can “do admin.” It is which recurring outputs, information boundaries, decisions, systems, and response windows belong in the role. This review translates current federal occupational evidence into a scoping tool. It does not claim that every assistant performs every listed duty, that occupational data predicts an individual’s performance, or that a national employee profile establishes a remote contractor’s price. Those distinctions matter because a vague role creates false comparisons: one proposal may cover calendar coordination and correspondence while another quietly assumes research, financial-document preparation, external representation, and supervisory work.
What the occupational sources actually say
The Bureau of Labor Statistics describes secretaries and administrative assistants as workers who perform routine clerical and organizational tasks. Its current Occupational Outlook Handbook also notes that some administrative assistants work from home as virtual assistants. O*NET’s executive-assistant profile is narrower and more demanding: it includes high-level administrative support, research, statistical reports, information requests, correspondence, conference calls, and scheduling. O*NET lists managing executive schedules, arranging travel, and preparing invoices, reports, memos, letters, financial statements, and other documents among reported tasks. These are descriptive occupation-level observations, not a ready-made job description. A buyer should select only the outputs that match the actual business need and name the review or approval attached to each one.
The strongest signal is coordination complexity
The O*NET work-activity profile emphasizes organizing, planning, prioritizing, gathering information, communicating inside and outside the organization, documenting information, and coordinating activities. Its work-context results also show frequent email, telephone contact, teamwork, external contact, accuracy requirements, and some decision freedom. Together, those findings support an inference: executive-assistant value often depends less on isolated clerical speed than on reliable coordination across people, systems, and deadlines. That inference is useful for role design but should not be converted into a universal personality test. A work sample should instead reveal whether a candidate can reconstruct context, identify conflicts, prepare options, preserve source facts, and escalate a decision at the right boundary.
Experience and training should change the screening plan
The 2025 BLS Occupational Requirements Survey reports that prior work experience was required for 87.2 percent of executive secretaries and executive administrative assistants, and on-the-job training was required for 74.0 percent. More than basic people skills were required for 95.9 percent. These figures describe jobs in the surveyed U.S. economy; they do not mean every opening must impose the same credential threshold. They do show why a buyer should test for practiced judgment and communication rather than treating software familiarity as sufficient. For a lower-complexity role, the employer can narrow the scope and provide a controlled ramp. For a high-context role, evidence from comparable coordination work, reference questions tied to actual duties, and a realistic work sample become more probative.
Build a role map before a task list
Start with five columns: output, source of truth, allowed action, retained decision, and service window. “Manage calendar” becomes a set of outputs such as conflict detection, option preparation, invite updates, attendee confirmation, and exception escalation. The source of truth might be a named calendar plus a travel file. Allowed actions could include moving internal holds inside written limits. Retained decisions could include declining a customer meeting, accepting a financial commitment, or changing an executive priority. The service window states what needs same-day handling and what belongs in a weekly review. This map is more useful than a long list of verbs because it exposes missing authority and lets providers estimate real effort.
Use tools as evidence of workflow fit, not as a proxy for judgment
O*NET identifies office suites, spreadsheets, scheduling tools, cloud collaboration, conferencing, project management, accounting, and other software categories associated with the occupation. Product names and demand signals change, so a buyer should avoid screening for a frozen tool inventory unless a system is genuinely essential on day one. Ask candidates to demonstrate transferable actions: reconcile two conflicting sources, construct a reviewable schedule, preserve version history, or prepare a decision brief. Then separately document the organization’s access model, training owner, and time allowed for system learning. Tool fluency can shorten ramp time; it cannot replace authorization rules, quality checks, or domain review.
A practical evidence-based scorecard
A defensible scorecard can cover source fidelity, prioritization, written clarity, exception recognition, confidentiality behavior, and handoff completeness. Define observable anchors before reviewing candidates. For example, a strong source-fidelity response distinguishes confirmed facts from assumptions and links each material claim to the supplied record. A strong prioritization response names dependencies and explains tradeoffs instead of simply sorting by urgency labels. Reviewers should score independently before discussion, record the work-sample version, and avoid adding criteria after seeing a favored candidate. The score is decision support, not a mechanical hiring command; references, availability, role-specific knowledge, and lawful employment review still require accountable human judgment.
Limitations and local validation
BLS and O*NET describe U.S. occupations, not AssistantStaffing customers, a particular provider, or a guaranteed remote-work outcome. Occupational categories aggregate jobs with different industries, tools, risk levels, and organizational designs. Some O*NET task data is older than the page’s latest update, while software and labor-market fields may be newer. The sources therefore support a disciplined starting point, not a claim that the role has one universal shape. Validate the draft role against two weeks of real requests, count exception types, interview the current decision owner, and remove duties that cannot be given a clear source, permission boundary, or acceptance test.
Niche conclusion for assistant buyers
The evidence favors a scoped coordination role over a generic “do everything” brief. Buyers should treat calendar, travel, correspondence, research, reporting, and external communication as separate workstreams, each with its own authority and information exposure. Where the work requires frequent judgment or representation, the selection process should place more weight on comparable experience and scenario evidence. Where work is repeatable and bounded, a narrower role with explicit training may be appropriate. The purchasing decision is therefore not simply assistant versus no assistant. It is whether the organization can define a coherent bundle of outputs and retain the decisions that should not be delegated.
How to apply the findings
Pilot the framework on one representative workflow. Name the owner, freeze the current instructions, and collect ordinary cases plus exceptions for a defined period. Record inputs, decisions, outputs, elapsed time, missing information, and corrections. Review the evidence with the people who request, perform, approve, and receive the work. Change one control at a time where possible, version the instruction, and set a reassessment date. This approach does not prove causation, but it creates a traceable basis for deciding whether the role or control is ready to expand.
Source discipline
Each source below was checked on October 15, 2026. Source titles and publishers are recorded so readers can evaluate authority and revisit changeable guidance. Facts attributed to public agencies are separated from this article’s operational analysis. Inferences are framed as recommendations for a buyer rather than claims about a person, vendor, or guaranteed outcome. Where a question turns on law, security architecture, payroll, or another professional judgment, the assistant may assemble records and coordinate follow-up while the qualified owner retains the decision.
Sources
- Secretaries and Administrative Assistants - U.S. Bureau of Labor Statistics. Checked October 15, 2026.
- Executive Secretaries and Executive Administrative Assistants - U.S. Bureau of Labor Statistics. Checked October 15, 2026.
- Executive Secretaries and Executive Administrative Assistants (43-6011.00) - O*NET OnLine, U.S. Department of Labor. Checked October 15, 2026.
