ExecutiveSupportStaff Editorial Team | Published
Every high-performing executive assistant operates from a set of processes. The question is whether those processes are written down or exist only in the assistant head. The answer determines what happens when the assistant is out, when the executive needs to explain their expectations to a new hire, or when the support model scales across a leadership team.
An undocumented process is a fragile process. It transfers imperfectly to a second assistant, requires the executive to re-explain their preferences with each new hire, and produces inconsistent output when the same task is handled by different people.
The International Association of Administrative Professionals recognizes EA professional standards and treats process documentation as a core competency for senior administrative professionals, particularly in multi-executive environments where consistency across the support team matters most.
Four process documents cover the majority of high-frequency executive support work. Each is short, structured, and reviewed on a defined cadence.
The calendar management SOP defines which time blocks are protected and non-negotiable, how incoming meeting requests are routed, what authority the assistant has to book or decline without checking with the executive, and the escalation path when a conflict involves a priority stakeholder.
This document prevents the assistant from having to ask the same question repeatedly and gives the executive confidence that the calendar is being managed against a consistent standard rather than ad-hoc intuition.
The inbox triage SOP defines the four action tiers (handle directly, draft and flag, flag for executive judgment, archive), lists the priority sender relationships that always escalate to Tier 3, and specifies which recurring message types belong in each tier.
This SOP requires the most calibration in the early weeks of a new engagement. A monthly review in the first 90 days catches the category errors before they become patterns. After the first quarter, quarterly reviews are enough.
The meeting preparation SOP covers the standard briefing format, the lead time required for each meeting type, who distributes the agenda and when, and how action items are tracked across the leadership team after the meeting closes.
This is the SOP most executives value most. When every meeting starts with a consistent pre-read and ends with a clean action log, the quality of leadership team decision-making goes up because the context is always there.
The communication standards SOP covers the executive tone and register for different relationship types, the escalation thresholds for sensitive correspondence, the response time expectations by channel, and the categories of message the assistant never sends without explicit executive approval.
This document is the last to mature in a new engagement because it requires the most observation of the executive communication patterns before it can be written accurately. Starting with a draft in month one and refining it through month three produces a more useful document than writing it on day one from scratch.
One page per process. Two at most. An SOP that runs to 10 pages is not a process document; it is a manual that nobody reads after the first week.
The trigger-action-output format works well: what event starts the process, what steps the assistant takes, and what the output looks like when the process is complete. Three columns on a page, with notes on edge cases at the bottom, covers 90 percent of executive support processes.
The executive reviews the first draft. This review is not optional. An SOP that the executive has not approved represents the assistant interpretation of what the executive wants, which may be partially wrong. A 15-minute review conversation in the first month validates the document and prevents months of subtle miscalibration.
SOPs decay when they are not reviewed. The executive role evolves, the leadership team changes, and the processes that made sense in one quarter may not match the operating reality six months later.
Calendar management and meeting preparation SOPs benefit from quarterly reviews. Inbox triage evolves faster in new engagements and more slowly once the relationship is established. Communication standards change most when the executive role changes: a new board seat, a significant client relationship, or a change in company stage all shift the communication landscape.
For the broader onboarding context that these SOPs support, see our guide to EA onboarding process. For how SOPs fit into the coordinated support model across a full leadership bench, see our piece on leadership team support.
| SOP | Covers | Review cadence |
|---|---|---|
| Calendar management | Protected blocks, meeting types, conflict rules, escalation | Quarterly |
| Inbox triage | Tier definitions, priority senders, draft and escalate rules | Monthly in first 90 days; quarterly after |
| Meeting preparation | Briefing format, lead time, agenda distribution, action tracking | Quarterly |
| Communication standards | Tone by relationship type, escalation thresholds, channel rules | Semiannually |
How long should an executive support SOP be?
One to two pages per process is the practical ceiling. An SOP that runs longer than that rarely gets read and never gets updated. The goal is a document that an assistant can scan in two minutes and act on immediately. If the process requires more explanation, it usually means the process itself needs simplification before it can be documented effectively.
Who should write the SOP: the EA or the executive?
The assistant writes the first draft based on their understanding of the process, then the executive reviews and corrects it. The executive is unlikely to write the SOP from scratch, but they are well-positioned to validate whether the documented version matches how they actually want the work done. An SOP that has not been reviewed by the executive reflects the assistant interpretation, which may not match the executive actual preferences.
What is the biggest sign that an EA setup needs SOPs?
The same questions keep coming up. When an assistant asks the executive the same calendar question for the third week in a row, or when the executive corrects the same draft formatting issue repeatedly, the answer is not a better assistant: it is a written process that makes the expectation explicit. SOPs solve the calibration problem faster than experience alone.