How to Set Expectations With a New Executive Assistant
How to set expectations with executive assistant
Most new executive assistant relationships struggle not because of skill gaps but because of unspoken assumptions. The executive expects one thing; the EA interprets the situation differently. Neither is wrong. Expectation-setting is the step that closes that gap before misalignment has time to compound.
Done deliberately at the start, it takes a few focused conversations and one or two reference documents. Left undone, it generates months of corrections, friction, and guesswork that erode the relationship.
Define the scope before the first task
The most common mistake is assigning tasks before scope is established.
A scope document answers three questions: what is this EA responsible for, what requires sign-off before action, and what is off-limits at this stage. It does not have to be exhaustive. A one-page document covering the main task categories is enough to start.
Calendar management, correspondence, travel planning, and document preparation each need a few sentences explaining the expected depth. For calendar access, note whether the EA can schedule and decline independently or only propose options. That one boundary prevents a significant share of early missteps.
Communicate your preferences in writing
Preferences are harder to document than responsibilities because they feel informal. But preference mismatches cause more friction than capability gaps, and they are easy to address when they are written down.
Note how you prefer to receive information: brief async updates, a structured daily summary, or a longer weekly wrap. Specify whether you want decisions proposed with a recommendation or just the options laid out. State whether communication outside business hours is acceptable for urgent matters or whether everything waits.
Cover tone preferences for correspondence the EA handles on your behalf. The language appropriate for a board member differs from what works with a vendor. A few example emails you have already written give the EA a reference point rather than a guess.
Set work product standards with examples
Abstract standards like "high quality" are not actionable on their own.
Show examples of what good looks like. Pull two or three meeting briefs, travel summaries, or email drafts you found well-executed, and point to what made them work: structure, brevity, level of detail. The EA now has a benchmark rather than an undefined target to aim at.
For new deliverable types, build in an early review loop. The EA submits a draft, you mark it up briefly, and the next version reflects that feedback. After a few rounds, patterns become clear and the need for explicit review drops naturally.
Establish a feedback cadence from the start
Many executives avoid giving feedback until frustration builds. By that point, the EA has been repeating the same pattern for weeks because no one said it was wrong.
Brief check-ins in the third and sixth week of the engagement work better than waiting for a formal quarterly review. Keep each session short and specific: what worked well, what missed the mark, and one thing to adjust going forward. That structure prevents vague conversations that produce anxiety without producing improvement.
Real-time feedback on specific tasks is also useful. A brief note after a task is completed, rather than batching everything into a periodic review, connects the feedback to the context the EA still remembers clearly.
Agree on how to handle ambiguity
No scope document covers every situation that comes up. Agree in advance on a default behavior for uncertain cases.
The most practical approach is a simple rule: if the EA is uncertain whether a decision falls within their authority, they pause and ask rather than act on an assumption. Establish a preferred channel for those questions, whether that is a direct message, a flagged item in a shared inbox, or a standing check-in slot.
Over time, good judgment develops and the frequency of those questions drops. But in the opening period, a bias toward asking produces better outcomes than a bias toward acting and correcting after the fact.
What happens when expectations are left implicit
When expectations are not set, the EA operates on inference.
They make reasonable guesses based on past experience and signals from early interactions. Some guesses align with what the executive actually wants. Others do not, and corrections follow. Because those corrections are not tied to a stated standard, the EA may not recognize the underlying principle the executive was applying.
The result is a pattern of reactive corrections rather than a working system. The EA learns to respond to feedback rather than develop sound judgment about what the executive actually needs.
The Society for Human Resource Management notes that clear role definitions and documented expectations are among the highest-leverage investments in a new placement. For executive assistants, where so much of the work involves exercising judgment on behalf of the executive, that point is especially true.
A strong virtual EA onboarding process builds the operational foundation. Clear expectations are what make that foundation load-bearing. Starting with an explicit conversation about scope, preferences, and standards means the working relationship begins from clarity rather than trial and error.
Executives working with a provider that selects from the top 1 percent of candidates, with roughly 1 in 1,000 applicants reaching final placement, find that a well-chosen EA absorbs stated expectations quickly. Explore placement options through executive support services.
Frequently asked questions
What is the most important expectation to set with a new executive assistant?
Decision authority generates the most friction when left undefined. Specify which decisions the EA handles independently, which require a brief check-in, and which stay with the executive. That boundary prevents both over-caution and overreach, and it gives the EA a clear framework for every judgment call they make.
Should expectations be communicated in writing or verbally?
Written is better. Verbal agreements drift over time as the memory of the original conversation fades. A short written document is something the EA can reference when uncertain, reducing the need to ask the same question twice and reducing the risk of acting on a misremembered instruction.
How detailed should a scope document be?
Specific enough to answer the most common judgment calls, but not so exhaustive it becomes a reference document no one reads. A practical scope document covers the main task categories, decision boundaries, and work product standards. A page or two is enough to start; it grows over time as edge cases get documented.
What if expectations need to change after the engagement starts?
Update them explicitly rather than signaling the change through feedback alone. A brief written note that explains what is shifting and why is more useful than a pattern of corrections the EA has to interpret. Changes happen; the key is making them visible rather than implicit.
How do I handle an EA who keeps missing stated expectations?
First, verify the expectation was communicated clearly and accompanied by an example. Then check whether the feedback has been specific and timely. If both are true and the pattern continues, the issue may be a fit problem rather than a communication gap. A quality placement provider should offer a path to reassignment in that case.