What Virtual Executive Assistants Should Document
The first things a virtual executive assistant should document early in an executive partnership are the executive’s priorities and goals, professional context, communication preferences, calendar preferences, meeting standards, decision rules, stakeholder and VIP information, recurring tasks, inbox and information flow, SOPs, digital access and tools, and any travel, personal, or financial information that is relevant to the support scope.
A strong executive partnership doesn’t begin with a perfectly color-coded inbox or a complete overhaul of the board deck. It begins much quieter than that. With notes, observations, questions. Tiny details that seem almost too small to matter until they prevent a double-booked investor call, a tense client exchange, or the executive skipping lunch because the day was scheduled too tightly.
For virtual executive assistants, this documentation matters even more. When you’re not sitting outside the executive’s office or catching context in the hallway, you need a shared system for how work actually gets done. Not just what needs to happen, but how the executive prefers it handled.
Documentation is the operating system for building trust.
Article Contents:
Why Should Virtual Executive Assistants Document Early?
What Should a Virtual Executive Assistant Document First?
Executive Priorities and Business Goals
Professional Information
Communication Preferences
Calendar Preferences
Meeting Standards
Decision Rules
Stakeholder and VIP Information
Recurring Tasks and Support Areas
SOPs for Repeatable Processes
Inbox and Information Flow
Digital Access and Tools
Travel Information
Personal Information
Financial Information
Red Flags and Stress Signals
Boundaries and Working Agreements
How to Keep the Executive Support Playbook Useful
Common Mistakes to Avoid
How Executive Assistants Can Ask Better Questions
Why Executives Should Share Feedback Early
Key Takeaway
Why Should Virtual Executive Assistants Document Early?
Early documentation helps a virtual executive assistant create consistency, reduce guesswork, and build a working rhythm with the executive faster. It gives both people a shared reference point for priorities, preferences, responsibilities, and expectations.
It keeps the partnership from becoming a game of “Didn’t we talk about this already?”
At the beginning of an executive assistant and executive relationship, everything is new. The executive may say they’re “flexible,” but they probably are not flexible about everything. They may claim they “don’t care” where meetings go on the calendar, until a strategy session appears at 4:30 p.m. on a Friday and suddenly they care deeply.
The executive assistant is learning dozens of invisible rules such as which meetings can move, who gets immediate access to the executive, how decisions are made when time is tight, and what the executive means when they say “handle it.”
Documenting early turns all of that into usable intelligence.
The best virtual executive assistants don’t just record information. They interpret patterns. They notice that the executive is sharper in the morning, avoids conflict by delaying responses, always underestimates travel buffer time, or says yes when they should say “not this quarter.” Those small patterns often become the difference between reactive support and true executive leverage.
What Should a Virtual Executive Assistant Document First?
A virtual executive assistant does not need to capture every detail in the first 30 days. In fact, trying to document everything too quickly can lead to assumptions, unnecessary detail, or documentation that looks complete but is not actually useful.
The priority early on is to capture the information that helps the executive assistant support the executive safely, confidently, and with less back-and-forth.
Start with the essentials:
Executive priorities and goals: What the executive is focused on, what they want the executive assistant to take off their plate first, and what success should look like in the first 30, 60, and 90 days.
Communication and response preferences: Which channels to use, what counts as urgent, how often updates should be sent, and how much detail to include.
Calendar and meeting preferences: When the executive does their best work, which meetings can move, how much buffer time is needed, what should be protected, and what makes a meeting useful.
Decision rules and escalation points: What the executive assistant can decide independently, what needs approval, and what should always be escalated.
Recurring responsibilities and access needs: What the executive assistant owns or supports, which tools or systems they need, and where sensitive information should be stored securely.
The documentation should be customized to the executive, the scope of support, and the level of access the executive assistant actually needs.
Once those essentials are documented, the executive assistant can continue building out a playbook as patterns become clearer. Over time, the playbook may also include SOPs for repeatable processes, travel preferences, personal logistics, financial information, professional context, and red flags that signal stress or overload.
The goal is not to document everything as quickly as possible. The goal is to make documentation useful early, then refine it as the partnership develops.
Free Download: Executive Support Playbook
To make this easier to put into practice, we created a free Executive Support Playbook you can use to document priorities, communication preferences, calendar rules, decision authority, recurring tasks, access needs, travel preferences, and more. Use it as a starting point, then remove or customize sections based on the scope of support.
Executive Priorities and Business Goals
Start with what matters most.
A virtual executive assistant cannot protect an executive’s time if they don’t know what the executive is trying to accomplish.
Useful things to capture:
Top 3 to 5 business priorities and why each matters
Where executive assistant support can create leverage
The top 3 things the executive wants to remove from their plate first
Current pain points tied to those tasks or areas
Desired outcomes for the support relationship
What success should look like in the first 30, 60, and 90 days
What should feel easier for the executive over time
Ask: “What should feel easier for you 90 days from now because you have executive assistant support?” That question alone can reveal a lot.
Professional Information
A virtual executive assistant should also document the basic professional information that shapes how the executive works day to day.
This section of the playbook helps the executive assistant understand the executive’s operating environment, not just their personal preferences.
Useful details to capture include:
Executive title, email, and phone number
Department, business unit, or area of ownership
Executive time zone and typical work schedule
Executive bio or professional background link
Company name, size, website, phone number, and mailing address
This is especially helpful for virtual executive assistant support because the assistant may not absorb company context naturally through office conversations or informal meetings. Documenting the professional landscape gives the executive assistant a clearer view of what matters, who is involved, and where their support fits.
Communication Preferences
Communication preferences are where many virtual executive assistant partnerships run into friction early.
Document:
Preferred communication channels
What belongs in Slack, Teams, email, text, or phone
What qualifies as urgent
Response-time expectations
Daily or weekly update preferences
Whether the executive prefers short summaries or full context
How to communicate when the executive is in meetings, focused, offline, after hours, or unavailable
Also document what not to do. That’s often more useful.
For example:
Don’t call unless the issue is time-sensitive
Don’t send long email threads without a summary
Don’t schedule decision-heavy conversations after 3 p.m.
Don’t use Slack for sensitive topics that belong in email or a secure system
A good virtual executive assistant learns the executive’s signal from their noise. Then they help the rest of the organization hear it too.
Calendar Preferences
Virtual executive assistants should document calendar preferences.
Document the executive’s calendar standards early, including:
Best times for deep work, internal/external meetings
Days to avoid for heavy scheduling
Minimum buffer between meetings
Maximum number of meetings per day or week
Preferred meeting lengths
Whether back-to-back meetings are acceptable
Protected commitments
Meetings that can be moved and should not be moved
Naming conventions for calendar events
Notification preferences
Travel or commute buffers
Standing meetings or business rhythms to plan around
Also capture what is technically available versus what is actually useful.
An executive may technically be available at 7:30 a.m., but if they arrive at that meeting foggy and rushed it may not be a good slot. The goal is not just to fill open space. It’s to create a calendar the executive can actually use well.
A simple calendar detail can create more friction than people expect. In one executive partnership, the executive disliked how calendar events were being named but never told the executive assistant directly or explained what she preferred instead. The executive assistant kept doing it the same way, while the executive quietly grew frustrated. Once the preference was documented, the issue became easy to fix. The problem was never the calendar itself. It was the missing expectation.
For a virtual executive assistant, the calendar is often the clearest window into the executive’s working life. You may not see them walking quickly between conference rooms or looking drained after a tense call. But you can spot the pattern: four video meetings in a row, no prep time, no decision space, no lunch. That is not just a busy calendar. It is an early signal that the executive’s operating rhythm may be under strain.
Meeting Standards
Virtual executive assistants should document the executive’s meeting standards because meetings are one of the fastest places for time, attention, and decision quality to erode. A clear standard helps the executive assistant know which meetings are worth protecting, which ones need more context, and which ones should be shortened, declined, or handled asynchronously.
Early on, document what a “good meeting” looks like for this executive.
Include:
Pre-read timing
When a meeting should be declined or converted to an asynchronous update
When prep time should be added
What every meeting invite should include
When to use video, phone, or async communication
Preferred conferencing tools
Rules for recording or transcribing meetings
Backup plans for tech issues
Who takes notes
Follow-up format and timing
Where action items should live
This is especially important in remote and hybrid environments. Without standards, everything becomes a meeting. Then everyone wonders why no work is getting done.
Decision Rules
A virtual executive assistant should document what decisions they can make independently, what needs approval, what can be escalated, and what criteria the executive uses to make tradeoffs.
This is one of the most important early documentation categories because it determines how much leverage the executive assistant can create.
Without decision rules, the executive assistant becomes a messenger. With decision rules, the executive assistant becomes an extension of the executive’s judgment.
Examples of decision rules:
Accept all investor meetings only after confirming priority with the executive
Protect two focus blocks per week, no exceptions unless urgent
Schedule prep time before board, client, or media meetings
Use text only when a same-day decision is required
Hold non-urgent requests for the next daily summary
This kind of documentation saves everyone from constant approval loops. It also gives the executive assistant confidence because they know what they can handle independently and what needs to be escalated. That clarity matters. It’s hard to do strategic support well when every decision feels like a potential misstep.
In a virtual or fractional executive assistant partnership, decision rules are especially important because the executive assistant and executive may not share the same working hours every day. The executive might be in a board meeting, on a flight, or heads-down on a major deal. When the executive assistant knows the rules, work does not stall every time the executive is unreachable.
Stakeholder and VIP Information
Virtual executive assistants should document the executive’s key stakeholders and VIPs.
This helps the executive assistant understand who needs access to the executive, how often, and with how much context.
A stakeholder or VIP map should include:
Name, title, and organization
Relationship to the executive and priority level
Contact information, when appropriate
Preferred communication channel and time zone
Assistant or coordinator contact
Handling notes, such as relevant history, sensitivities, gifting preferences, or relationship context
This prevents awkward little issues from building into larger ones. For example, rescheduling a “routine” check-in may not be routine at all if the relationship is politically delicate. A client who asks detailed, winding questions may need extra prep. A board member may expect a more formal tone than a longtime advisor.
For virtual executive assistants, the stakeholder map also helps replace the context they might otherwise overhear in an office. Who gets fast access? Who tends to reschedule? Who needs a warmer tone? Who should never be left waiting without an update?
Every executive has a network of people around them, and not every relationship carries the same weight. The executive assistant needs to know who gets quick access, who needs extra context, and which conversations require a more careful touch.
Recurring Tasks and Support Areas
Virtual executive assistants should document the recurring tasks and support areas they own or support.
This is different from documenting preferences. Preferences explain how the executive likes things done. Recurring responsibility documentation explains what the executive assistant is responsible for keeping in motion.
Useful details to capture include:
The task or support area
How often it happens
Who is involved and what tools or systems are needed
What information the executive assistant needs to complete it
Any deadlines, review steps, or approval requirements
Any notes that help the executive assistant complete the work consistently
Examples might include:
Weekly leadership meeting prep
Monthly expense reports
Board packet coordination
This section becomes especially useful when the executive assistant is fractional, when backup support is needed, or when responsibilities expand over time. It keeps recurring work from living only in someone’s memory.
SOPs for Repeatable Processes
When a process happens more than once, it should usually have a simple SOP, or standard operating procedure. That does not mean a long, formal document. It can be a short checklist, a few notes, a link to the right workflow, or even a screen recording of someone completing the task.
For many virtual executive assistant partnerships, screen recordings are especially helpful. If the executive has a specific way they like something done, such as pulling a report, submitting an expense, updating a CRM field, or preparing meeting materials, recording the process once can save several rounds of clarification later. The recording does not need to be polished. It just needs to show the steps clearly enough that the executive assistant can repeat the process with confidence.
A virtual executive assistant should document SOPs for repeatable work such as:
Booking travel
Preparing meeting materials
Processing expenses
Coordinating board materials
Managing recurring reports
Updating CRM or project management systems
A useful SOP should answer:
What triggers this process?
Who is involved?
What tools or links are needed?
What steps need to happen?
What approvals are required?
What common mistakes should be avoided?
Is there a checklist, template, or screen recording that shows how it should be done?
The goal is not to turn every task into a manual. The goal is to make repeatable work easier to execute consistently, especially when timing matters or another support partner needs to step in.
Inbox and Information Flow
Virtual executive assistants should document inbox access, sorting rules, drafting expectations, response priorities, sensitive topics, filing systems, and how the executive wants information summarized.
The inbox is often where priorities, requests, decisions, and distractions all compete for attention.
Document:
Whether the executive assistant has full inbox access
What emails the executive assistant can respond to directly
What should be flagged, archived or filed
Preferred labels or folders
Drafting style and signature rules
Confidentiality expectations
How often the inbox should be reviewed
What topics require executive eyes only
What should be summarized in a daily digest
What requires an immediate ping
How attachments, contracts, and sensitive files should be handled
What the EA should never open, move, archive, or respond to
Also document the executive’s voice. Do they write warmly? Briefly? Formally? Do they use “Thanks” or “Many thanks”? Do they like context, or do they prefer a clean answer?
A virtual executive assistant who can draft in the executive’s voice becomes incredibly valuable. Not because they impersonate the executive, but because they reduce friction while preserving authenticity.
And that matters. A lot of executive communication happens in tiny moments: the quick reply to a client, the polished follow-up after a meeting, the gentle nudge to a direct report who owes a decision by Friday. When those moments are handled well, the executive feels more present than they actually had time to be.
Digital Access and Tools
Virtual executive assistants should document the tools, systems, permissions, and workflows they need to support the executive securely and effectively.
This is one area where virtual support can get clunky if no one names the details early. Everyone assumes access is “basically set up,” and then the executive assistant tries to book travel, pull a document, update a project board, or review a meeting note and hits a wall. Password request. Permission denied.
Document access needs for:
Workspace or email suite
Email and calendar
Communication tools
Video conferencing
Scheduling tools
Project management tools
File storage and document management
Password management
Travel booking platforms
Expense management tools
CRM or client information systems, if relevant
Meeting note or transcription tools
AI tools
Finance, HR, contract, customer support, or automation tools, if relevant
Key dashboards, reports, folders, or shared workspaces
AI Tool Use and Data Boundaries
Virtual executive assistants should also document whether AI tools are approved, which tools may be used, and what information should never be entered into them. This is especially important for executives working in regulated industries, handling confidential client information, or dealing with sensitive financial, legal, HR, healthcare, or board-related materials.
Clarify:
Which AI tools, if any, are approved by the company
Whether the executive assistant can use AI for drafting, summarizing, research, meeting prep, or SOP creation
What types of information should never be entered into an AI tool
Whether meeting transcripts or recordings can be summarized using AI
Whether client, employee, financial, legal, or board materials require special handling
Who to ask when the executive assistant is unsure whether AI use is appropriate
It should clearly point to the company’s approved AI policy, tools, and boundaries. The executive assistant should never have to guess whether it is acceptable to paste meeting notes, email threads, contracts, client details, or internal strategy documents into an AI platform.
Also capture rules around security:
Where sensitive files should live
What should never be sent over chat
Which approvals are required before sharing documents
How to handle confidential board, HR, legal, or financial information
What to do if access changes or something looks off
This is not glamorous work. But when a virtual executive assistant has the right access and clear rules, they can move quickly without creating risk.
Travel Information
Travel preferences deserve their own section because executive travel often involves more than flights and hotels. Done well, travel support protects time, reduces friction, and helps the executive arrive prepared instead of depleted.
Document:
Legal name as it appears on travel documents
Passport, visa, Global Entry, TSA PreCheck, or vaccination requirements, stored securely
Airline preferences and loyalty numbers
Seat preferences
Hotel preferences and loyalty numbers
Ground transportation preferences
Meal preferences or restrictions while traveling
Preferred travel times
How the executive likes itineraries formatted and delivered
Buffer preferences before and after travel
Differences between business and personal travel preferences
Also document what the executive needs around the trip, not just during the trip. Some executives want printed materials. Some want a single mobile itinerary. Some need quiet prep time before a client dinner. Some prefer not to take early flights after late events.
The details and nuance matter. A strong executive assistant spots the small sources of friction before they become bigger distractions.
Personal Information
Virtual executive assistants should document personal information that directly affects scheduling, travel, logistics, wellbeing, and executive performance, while respecting privacy and boundaries.
The goal is not to collect personal information for the sake of it. The goal is to document what the executive assistant needs to provide thoughtful, accurate support.
If personal support is part of the relationship, useful categories may include:
Identity and contact information: full legal name, preferred name, address, mobile number, personal email, and emergency contact details
Family and household context: family members, important dates, school schedules, household contacts, or personal commitments that affect scheduling
Health and wellness information, if applicable: allergies, health considerations the executive chooses to share, wellness schedules, or contacts the EA needs in order to coordinate approved support
Food and dining preferences: dietary restrictions, favorite foods, food dislikes, preferred restaurants, catering preferences, and delivery app preferences
Favorites and gifting preferences: favorite flowers, stores, colors, brands, hobbies, or gift dislikes
Home office or remote-work logistics: preferred delivery addresses, office setup needs, or local time zone considerations
Not every executive will want or need to share all of this. The executive assistant should only document what is relevant to the support relationship and store sensitive information securely.
The value is in knowing which details actually affect the executive’s time, energy, or experience, and leaving out what does not. Sensitive personal numbers, detailed medical information, passwords, credentials, or financial information should always be stored in a secure location.
Financial Information
Financial information should be documented carefully, securely, and only when it is directly relevant to the executive assistant’s responsibilities. Not every executive assistant partnership requires access to financial details, and the playbook should never collect sensitive information simply because it might be useful someday.
For some partnerships, the executive assistant may only need access to business expense tools. In others, the executive assistant may help with vendor payments, recurring subscriptions, reimbursements, travel cards, invoice tracking, or personal administrative support.
It is helpful to separate professional and personal financial information.
Professional financial information may include:
Expense platform access
Reimbursement processes
Vendor payment workflows
Invoice submission instructions
Budget codes or approval requirements
Recurring business payments or subscriptions
Receipt submission preferences
Business credit card access notes, stored securely outside the playbook
Approval thresholds for purchases or payments
Who must approve expenses, invoices, transfers, or reimbursements
Personal financial information, when appropriate, may include:
Household vendor payment details
Recurring personal payments
Personal reimbursement preferences
Personal credit card access notes, stored securely outside the playbook
Banking or account contacts, where relevant and authorized
Approval rules for personal purchases or payments
This information should never be stored casually in an unprotected document, spreadsheet, or shared folder. The playbook should not include full credit card numbers, bank account numbers, passwords, security questions, PINs, or other sensitive credentials. If financial details are needed, the executive assistant should document where the information lives, who has access, what the approval process is, and what tool or secure system should be used.
The safest approach is to keep the playbook as a guide to the process, not the vault for the information itself. Sensitive numbers and credentials should live only in approved, permission-controlled systems such as a secure password manager, expense platform, banking portal, or other company-approved tool.
Red Flags and Stress Signals
A strong virtual executive assistant does not just document what the executive prefers when things are calm. They also document what tends to happen when the executive is overloaded, rushed, or under pressure.
This does not mean diagnosing the executive or making assumptions. It means noticing practical signals that help the executive assistant adjust support before small issues compound.
Red flags might include:
The executive starts cancelling prep time
Messages become shorter or less clear than usual
The calendar fills with back-to-back meetings and no recovery time
Decisions begin to stall
Documenting these patterns helps the executive assistant respond with better judgment. For example, they may protect a focus block, bundle non-urgent questions, move a lower-priority meeting, or flag that the week is becoming unsustainable.
This kind of support is subtle, but it matters. Often, the executive assistant is the first person who can see that the executive’s operating rhythm is starting to strain.
Boundaries and Working Agreements
Virtual executive assistants should document boundaries around availability, after-hours communication, confidentiality, approval authority, personal tasks, and what support does or does not include.
Boundaries are not unfriendly. They are what make the partnership durable, especially when support is remote, fractional, or spread across different time zones.
Early working agreements should clarify:
Standard working hours and after-hours exceptions
Weekend communication norms
Emergency definitions
Confidentiality expectations
Delegation boundaries
Personal support boundaries
Response times
Backup support plans
Vacation coverage
Time zone differences
Expectations for fractional or part-time availability
What happens when the executive assistant is offline
How urgent issues should be routed
This is especially important for remote or fractional executive assistant partnerships. When people are not sitting near each other, small misunderstandings can grow quickly. Documenting boundaries keeps the relationship from drifting into either underuse or overreach.
And here’s the slightly uncomfortable truth: some executives do not know how to use executive assistant support well. They may under-delegate, over-explain, forget to share context, or treat everything as urgent because their own day already feels overloaded.
Good documentation helps coach the partnership without making it awkward.
How to Keep the Executive Support Documentation Useful
A virtual executive assistant’s playbook should be simple enough to use during a busy week. It should not become another project to manage.
The most useful playbooks are easy to scan, easy to update, and clear about what still needs to be confirmed. Instead of trying to complete everything at once, start with the areas creating the most friction right now: communication, calendar rules, decision authority, stakeholder access, and sensitive information.
Keep a “still learning” section for preferences that are not fully clear yet. Early partnerships are full of half-known patterns. Maybe the executive says they dislike morning meetings, except they happily take customer calls at 8 a.m. Maybe they want fewer updates, then later ask why they were not looped in. The goal is to document the pattern, not just the first answer.
A simple playbook that gets updated regularly is more valuable than a polished document that no longer reflects how the partnership actually works.
Free Download: Start With the Executive Support Playbook
If you are building this documentation from scratch, the free Executive Support Playbook gives you a structured place to capture the details that matter most without starting from a blank page. Fill out what applies, skip what does not, and refine it as the partnership develops.
Common Mistakes to Avoid
Even strong documentation can create problems if it is incomplete, outdated, or stored carelessly. A virtual executive assistant playbook often contains sensitive business context and personal details about the executive, so it needs to be practical, secure, and easy to maintain.
The goal is not to create a perfect document. It is to create a reliable source of truth the executive assistant can use to support the executive with better judgment, fewer delays, and less guesswork.
Storing sensitive information in the wrong place
An executive support playbook often includes business context, stakeholder notes, travel preferences, access-related information, and, when applicable, personal or financial details. That means it should not live in an unprotected document, spreadsheet, or shared folder anyone can open.
Passwords should never be typed directly into the document. Instead, link to the appropriate record in a secure password manager, such as LastPass, 1Password, or whatever tool the organization uses. Access should be limited to the people who genuinely need it, and the document itself should be password protected or stored in a secure, permission-controlled system.
The goal is to make the information useful without making it vulnerable.
Using AI tools without clear approval
AI can be helpful for drafting, summarizing, organizing notes, and creating first-pass SOPs, but it should only be used within the company’s approved guidelines. A virtual executive assistant should know which tools are allowed, what data is restricted, and when human review is required.
The playbook should not assume AI use is acceptable by default. For some executives or industries, AI tools may be limited or prohibited for certain types of information. When in doubt, the executive assistant should ask before using AI with anything confidential, personal, regulated, or business-sensitive.
Creating the documentation and then never updating it
Early documentation is not a one-time setup task. It should evolve as the executive partnership evolves.
Priorities change. Stakeholders shift. Communication preferences become clearer. A meeting that mattered six months ago may no longer need to exist. If the documentation is not updated, people stop trusting it, and once that happens, it loses its purpose.
A simple monthly or quarterly review can keep it current without turning it into a major project.
Trying to make it perfect before using it
The documentation does not need to be fancy, fully complete, or beautifully formatted to be effective. In fact, simple is usually better because simple is easier to maintain.
An executive support playbook with the right information is more valuable than a polished template that takes weeks to finish. Start with what you know, mark what still needs to be clarified, and update the playbook as patterns emerge. The first version should be useful, not perfect.
Documenting preferences without documenting decision authority
It is helpful to know how an executive likes their calendar organized or which communication channel they prefer. But the executive assistant also needs to know what they are allowed to decide independently.
Without clear decision rights, the executive assistant may still need approval for every small move. That slows the partnership down and keeps the executive involved in work they were trying to delegate in the first place.
Document what the executive assistant can handle alone, what needs a quick check-in, and what should always be escalated.
Making the document too detailed to maintain
Good documentation captures what matters. It should not become a transcript of every preference, conversation, or one-off situation.
Too much detail can make the playbook harder to use. The best version is organized, practical, and easy to scan. It gives the executive assistant enough context to act with judgment without burying the important information under clutter.
The best documentation reflects good judgment. It protects sensitive information, stays current, and captures the details that help the executive assistant support the executive with more confidence and less guesswork. It does not need to be perfect. It just needs to be clear, secure, and useful.
How Executive Assistants Can Ask Better Questions
Virtual executive assistants can make documentation feel natural by asking practical, situation-based questions during normal work rather than turning every preference into a formal interview.
Try asking questions like:
“Do you want me to protect mornings for focused work?”
“When this person reaches out, should I prioritize them?”
“Would you rather see a daily summary or only exceptions?”
“What kinds of decisions would you like me to make without checking?”
“Are there meetings on your calendar that no longer earn their keep?”
“When your week gets overloaded, what should I move first?”
“Should I send urgent items by text, Slack, or email?”
“What should I do if you’re offline and something needs a same-day answer?”
“Are there recurring tasks I should own every week or month?”
“Are there signs I should watch for that tell me your week is getting overloaded?”
“What are the first three things you would like me to take off your plate?”
“What would make this partnership feel successful in the first 90 days?”
These questions are simple. They invite useful answers. They also position the executive assistant as a strategic partner.
In a virtual partnership, the best questions often clarify what is otherwise invisible. How fast should the executive assistant respond? How much autonomy is comfortable? What should be handled asynchronously? What needs a live conversation? It seems small, but these answers become the bones of the partnership.
Why Executives Should Share Feedback Early
Executives who have not worked with an executive assistant before may hesitate to say when they dislike something or want it handled differently. They may not want to seem particular, demanding, or hard to work with. But staying quiet about preferences is one of the fastest ways to create friction in the partnership.
A strong virtual executive assistant wants that feedback. They are not expecting the executive to have every preference perfectly defined on day one, but they do need honest input as patterns emerge. If a calendar invite is named in a way that feels unclear, say so. If Slack updates feel too frequent, clarify the right rhythm. If a meeting was scheduled at a technically available but mentally terrible time, explain why that slot does not work well.
Those details are not nitpicking. They are part of how the executive assistant learns to support the executive with more accuracy and confidence.
Early feedback helps document preferences such as:
How calendar events should be titled
Which updates should be sent immediately versus bundled
What tone to use in drafted emails
How much context the executive wants before a meeting
Which meetings should not be moved without approval
What “urgent” actually means in practice
The mistake is not having preferences. Everyone has preferences. The mistake is assuming the executive assistant should somehow discover them without guidance.
In a healthy executive partnership, feedback is not a correction after something has gone wrong. It is useful context that helps the executive assistant refine the playbook, reduce guesswork, and provide better support over time. The earlier those preferences are named, the faster the partnership becomes smoother, more strategic, and less dependent on trial and error.
Key Takeaway
Virtual executive assistants should document early because the first few weeks of an executive partnership shape how trust, delegation, communication, and decision-making will work long term. The most useful documentation captures not only tasks and preferences, but also patterns, priorities, context, and judgment.
Done well, documentation becomes the partnership’s quiet engine. It helps the executive assistant act with confidence, helps the executive let go of unnecessary decisions, and helps both people move faster.
Before building the next checklist or cleaning up the next calendar, create a shared source of truth. Ask what matters, capture what repeats, notice what drains time, then keep refining it as the partnership grows.
Because the best virtual executive assistant partnerships are not built on mind reading. They are built on clear expectations, honest feedback, and the small details that help support become truly strategic.
Free Download: Executive Support Playbook
You do not have to build this documentation from scratch. Our free Executive Support Playbook gives you a practical starting point for capturing priorities, communication preferences, calendar rules, decision authority, recurring work, access needs, and support boundaries. Use what applies, remove what does not, and adapt it to the scope of your executive support partnership.
