How to Create an SOP for Your Executive Assistant
How to create an SOP for an executive assistant
A standard operating procedure for an executive assistant is a written reference document that captures how recurring tasks should be handled, what decisions the EA is authorized to make, and where to find the context they need to work independently.
Without one, every new process has to be explained from scratch. With one, the EA can act without waiting for direction and the executive can step away without things falling apart.
Why the SOP matters more than most executives expect
Most executives believe they can explain how they work during the first few conversations. They can cover the basics. But the real detail, the preferences, the exceptions, and the judgment calls, only becomes visible over months.
An SOP codifies that detail deliberately rather than waiting for it to emerge through trial and error. It compresses the time it takes the EA to reach independent, reliable operation.
The SOP also removes you as the bottleneck. When the EA has a written reference for a process, they do not need to interrupt the executive every time a question comes up. That reduction in interruptions is where a significant share of executive time comes back.
The core sections every EA SOP covers
The most useful EA SOPs cover five areas. They do not have to be long, but they do have to be specific.
The first is communication preferences. How the executive prefers to receive messages (voice note, text, email, chat), response time expectations by message type, and which channels are for what. An EA who knows that operational questions go to Slack and urgent items get a call avoids the wrong-channel interruption.
The second is calendar management rules. What meetings go on the calendar, what should be declined or pushed, how much buffer the executive prefers between calls, what travel days look like, and who has priority when there is a scheduling conflict. These rules let the EA manage the calendar without a daily back-and-forth.
The third is inbox management. Which emails the EA handles entirely, which require a draft for the executive to send, which go to the executive's full attention, and the standard labels or folders the EA uses to sort and flag. Good inbox SOPs also include the tone the executive prefers for different categories of correspondence.
The fourth is recurring tasks and deadlines. The weekly and monthly items the EA owns: board prep schedules, expense report submissions, stakeholder follow-up cadences, meeting notes distribution. Recurring tasks are where gaps are most costly and where a written process pays for itself immediately.
The fifth is decision authority. What the EA is authorized to confirm or commit to on the executive's behalf, and what always requires the executive's sign-off. This section prevents both under-delegation, where the EA asks for approval on things they could handle, and over-reach, where they make commitments the executive did not intend.
How to write each section without overcomplicating it
The SOP does not need to be polished. It needs to be accurate and usable. A two-sentence description of a process is more useful than a dense workflow diagram that takes 20 minutes to read.
For each process, write three things: what the task is, what the EA does when it comes up, and any exceptions or edge cases the EA should know about. That structure covers most recurring situations and gives the EA a reference that takes 30 seconds to consult.
Capture processes as they come up rather than waiting until you have a complete document. When the EA asks a question, that question is a signal that a process needs writing. Answer the question and write down the answer. Over a few weeks, the SOP builds itself from real workflow moments.
Use the EA's own language where possible. If the EA is the one who will use the document, write it in a way they would write it. Formal or overly technical language slows consultation.
For a structured approach to the first 30 days of building this working relationship, the EA onboarding framework covers the phased process of setting up communication systems, tool access, and decision authority incrementally. For a list of the specific task categories most executives delegate, tasks to delegate to your EA maps the common areas.
Keeping the SOP current
A SOP written once and never revisited becomes inaccurate quickly. Preferences change, tools change, the executive's priorities shift, and the EA's role expands as they demonstrate capability.
A monthly check-in where the EA flags anything in the SOP that no longer reflects how things actually work takes about ten minutes and prevents the document from drifting into fiction. Annual overhauls are slower and more disruptive than frequent small updates.
When a process changes, update the SOP promptly. An out-of-date SOP is worse than none because it gives the EA false confidence in a wrong answer.
The International Association of Administrative Professionals provides professional standards and resources for executive and administrative support roles, including frameworks for process documentation that EAs can adapt to their specific environments.
When to hand the SOP writing to the EA
Many executives find that once the initial structure is in place, the EA is better positioned to maintain and expand the SOP than the executive is. The EA is closer to the daily process. They notice gaps and edge cases that the executive does not see.
Assign the EA ownership of the SOP document after the first 60 days. Have them flag updates for executive review. This shifts the maintenance burden to the person with the most complete view of how the work actually runs.
Frequently asked questions
How long should an executive assistant SOP be?
Length depends on the role complexity. A focused EA SOP covering communication, calendar, inbox, recurring tasks, and decision authority can run five to ten pages. Longer is not better. A SOP that gets read is more valuable than one that is comprehensive and avoided.
Should the SOP be in a document or a project management tool?
Either works, but accessibility matters more than format. The SOP should be somewhere the EA can consult in under 30 seconds. A shared document with a clear table of contents is usually more practical than one buried in a project management platform.
What is the difference between an SOP and a preferences document?
A preferences document captures what the executive likes: how they take their coffee, how they prefer to be introduced, whether they like pre-reads or prefer live briefings. An SOP captures how recurring work gets done. Both are useful. A full EA operating system includes both.
Do you need an SOP for a part-time executive assistant?
Yes, and the case is stronger for part-time support than full-time. A part-time EA has less context-building time and more cognitive reset between sessions. A clear written process reduces the startup overhead at the beginning of each work block.
How do you create an SOP when you do not yet know what you want to delegate?
Start with the tasks that already cross your desk daily: email, calendar, and meeting prep. Document those first. Over the first 30 days, the pattern of what you are actually handing off becomes visible, and the SOP grows from there.