How to Build an Executive Assistant Playbook That Runs on Its Own
Byline: RemoteExecutiveSupport Editorial Team
Executive assistant playbook: what it is and why it matters
An executive assistant playbook is a living document that captures everything an EA needs to operate without asking the executive for guidance. It includes the executive's preferences, recurring process steps, communication protocols, key contacts, and decision rules for common situations.
A playbook is not a list of tasks. It is a system for reducing the executive's cognitive load from EA management to near zero. When the playbook is complete and current, the EA can handle the vast majority of routine and recurring work without interrupting the executive at all.
Building a playbook requires an initial time investment, but it pays back quickly. The executive answers the same question once, in the playbook, rather than fielding it repeatedly in ad hoc moments spread across the year.
What belongs in the executive assistant playbook
Preferences section. This covers how the executive likes to work: preferred meeting times, blocked focus periods, communication channel norms, response time expectations, and how the executive wants to receive status updates. These are the rules the EA applies to every decision without asking.
Recurring process documentation. Every repeating task should have a documented process in the playbook. Board meeting prep, monthly expense reporting, weekly calendar review, quarterly planning coordination, and recurring stakeholder communications all benefit from a written process that the EA can follow consistently and improve over time.
Contact and relationship context. The playbook should include the executive's key contacts with relationship context: who they are, what the relationship is, any communication preferences the executive has for them, and recent relevant context. When a message arrives from a key contact, the EA can respond appropriately without needing to brief the executive on who they are.
Decision authority. The EA needs to know which decisions they can make independently and which require the executive's input. Documenting this in the playbook prevents both over-escalation ("should I accept this lunch invite?") and under-escalation ("I already committed you to that keynote") failure modes.
How to build the playbook without disrupting the executive
The most practical approach is to build the playbook incrementally during the first 30 to 60 days. The EA notes every time they need to ask the executive a clarifying question and adds the answer to the playbook before asking again. After 60 days, most routine decisions are documented and the question frequency drops significantly.
A structured onboarding intake form at the start of the relationship accelerates this process. The EA asks the executive to spend 45 minutes filling out a preferences and context document, which becomes the playbook's foundation. Supplementing that initial input with real decisions as they arise builds the rest.
For guidance on how to structure the first weeks of an EA relationship, working with an executive assistant covers the onboarding process and what makes the early calibration phase effective.
Keeping the playbook current
A playbook that is not maintained becomes a liability. Stale preferences create EA decisions that no longer match what the executive wants, and neither party may realize the gap until something goes wrong.
The EA should treat the playbook as a living document, updating it whenever a preference changes, a new process is established, or a correction is made. A brief quarterly review, where the EA and executive walk through the playbook together to confirm what is current, catches any drift before it causes problems.
Many EAs keep the playbook in a shared Google Doc or Notion page so both the EA and executive can see and update it. The executive can add context whenever they think of something useful; the EA updates it whenever a decision reveals new information about how the executive wants to work.
The executive assistant SOP guide covers how to document recurring processes in a format that is practical to follow and easy to hand off, which complements the playbook's preference and context sections.
The Society for Human Resource Management's documentation best practices outline how living documents remain accurate: assign clear ownership, review on a fixed schedule, and update on event rather than waiting for the review cycle. These principles apply directly to EA playbook maintenance.
Frequently asked questions
What is an executive assistant playbook?
An EA playbook is a living document that captures the executive's preferences, recurring process steps, key contacts and context, and decision rules. It is designed to let the EA operate independently on routine and recurring work without interrupting the executive for guidance.
How is an EA playbook different from an SOP?
An SOP documents how to execute a specific process step by step. A playbook is broader: it includes preferences, context, communication norms, and decision authority alongside the process documentation. The SOP is one component of the playbook, not a synonym for it.
How long does it take to build a complete EA playbook?
Most of the functional content is in place after 30 to 60 days. The initial intake captures preferences and context. Real decisions and corrections during the first weeks fill in the rest. A truly complete playbook, one that covers nearly every recurring situation, typically takes three to four months of consistent updates.
Who owns the EA playbook?
The EA owns the maintenance and currency of the playbook. The executive owns the information in it. Both parties should be able to access and update it. The EA is responsible for keeping it current and for prompting the executive when preferences need to be revisited.
What format works best for an executive assistant playbook?
A shared digital document works better than a physical one because it is accessible from anywhere and can be updated in real time. Google Docs and Notion are both commonly used. The format matters less than the accessibility: the EA needs to be able to reference and update the playbook quickly, not navigate a complex filing system to find what they need.