The operating problem
Executive support breaks down when every invitation looks equally urgent and each reply depends on context held only in the executive’s head. The result is a busy inbox, avoidable calendar collisions, incomplete meeting preparation, and follow up that disappears after a conversation.
Delegation also creates risk when an assistant is expected to accept commitments, infer confidential priorities, book nonrefundable travel, or answer sensitive messages without explicit rules. The goal is not maximum inbox access. It is a reliable coordination lane with clear points where the executive decides.
Who this role is for
This lane serves executives and leadership teams whose calendars, inboxes, meetings, and travel create a steady coordination load. This service fits when calendar and communication work recurs often enough to document, the team can name calendar rules, priority contacts, and approved message context, and a executive is available to review exceptions. It is not a substitute for an undefined role or an absent decision maker. The strongest starting point is one bounded queue that can be observed, practiced with safe information, and measured against a finished example.
How the work should be organized
Begin with written scheduling rules: working windows, buffers, recurring priorities, travel time, protected focus periods, and meeting types that always require review. Add examples of invitations that were accepted, declined, delegated, or escalated and explain why.
For inbox work, define priority people, message categories, expected response windows, approved draft patterns, and private topics that the assistant must leave untouched. Drafting and triage can be delegated while the executive retains the choice to make a promise or disclose sensitive information.
Use a morning brief and an end of day handoff. The brief shows conflicts, preparation needs, decisions, and follow ups. The handoff records what changed, what remains blocked, and which commitments need executive confirmation.
Inputs required before access
An assistant cannot produce reliable work from missing context. Assemble these inputs, remove obsolete versions, and identify the owner who can clarify each source.
- Calendar availability rules, buffers, focus periods, and no book conditions
- Priority contact list plus examples of urgent and nonurgent messages
- Travel preferences, budget approval limits, loyalty details, and booking authority
- Meeting brief template, note format, and action owner conventions
- Confidentiality categories, delegated access method, and escalation contacts
Work included
Calendar coordination
Review requests against written rules, prepare options for conflicts, confirm logistics after approval, and keep attendee details current without inventing executive availability.
Inbox preparation
Apply approved categories, surface priority messages, draft routine replies, and preserve private or sensitive messages for direct executive review.
Meeting readiness
Assemble agendas, prior decisions, participant context, open actions, and source documents into a concise brief before the meeting.
Travel research
Compare realistic itinerary options, cancellation terms, ground connections, and total costs for executive approval before any purchase.
Follow through
Record decisions and action owners, send approved reminders, and flag overdue items without changing a commitment or deadline independently.
Concrete deliverables
Deliverables should be reviewable without a manager reconstructing the assistant’s activity. Each item needs a current state, source, owner, and visible exception where applicable.
- Daily schedule and conflict brief with decisions needed
- Categorized inbox queue and clearly marked reply drafts
- Meeting packet with agenda, context, documents, and open actions
- Approval ready itinerary comparison showing terms and total cost
- Decision and follow up register linked to the source conversation
Quality controls
Quality review should inspect evidence and decisions, not screen presence or raw activity counts. Use a consistent sample, discuss corrections, and update the operating guide when a missing rule causes repeat errors.
- Sample calendar changes and sent messages against the approved rules each week
- Require explicit approval for commitments, purchases, sensitive replies, and unusual attendees
- Use delegated access and named accounts rather than the executive’s primary credentials
- Keep a correction log so recurring scheduling or tone errors update the written guidance
Human decision boundaries
- The assistant does not make strategic commitments, negotiate terms, or speak as the executive on sensitive matters.
- Travel purchases, gifts, expense commitments, and nonstandard cancellation exposure require named approval.
- Private personnel, legal, medical, board, and account recovery messages remain under executive control.
A realistic example
A client request conflicts with a protected planning block
Context: A priority client asks for an urgent meeting during a protected focus period. The request gives no agenda, and accepting it would compress travel time before another commitment.
Assistant response: The assistant checks the priority rules, requests the missing agenda using approved language, and prepares two viable meeting options. The executive chooses whether the protected block moves. The assistant then confirms attendees and updates the brief.
Manager review: The weekly review checks whether the escalation was timely, the alternatives respected buffers, no commitment was made early, and the final calendar record matches the executive’s choice.
Launch this role
Launch is a controlled transfer of one queue, not a single account handoff. Keep early scope small enough that a reviewer can see every material result and correct the system before volume grows.
Map the first queue
Choose one recurring executive assistant workflow. Record its trigger, calendar rules, priority contacts, and approved message context, expected finish, normal due time, and the executive who resolves an exception. Remove obsolete instructions before a candidate sees them.
Run safe representative work
Build a paid sample that resembles a daily schedule brief, prepared replies, meeting records, and travel comparisons but uses invented, redacted, or otherwise approved information. Include a normal item, a missing input, and a conflict between two important commitments. Score accuracy, completeness, communication, and whether the candidate stops at the right boundary.
Open minimum access
Create a named account and grant only the systems and records needed for the opening queue. Keep administrator rights, account recovery, exports, and commitment, spending, and confidential judgment with authorized owners. Record the access owner and removal path before live work begins.
Review before expanding
Inspect every early output or use a risk appropriate sample. Compare the work with source evidence, discuss exceptions, and correct the written process. Add volume, tools, or task ownership only when the evidence is stable and the executive agrees.
Frequently asked questions
Can an assistant accept meetings without review?
Yes, but only for meeting types, attendees, windows, and buffers explicitly covered by the written rules. New commitments, unusual guests, conflicts, and exceptions return to the executive.
Should the assistant use the executive password?
No. Use named or delegated access, appropriate authentication, limited permissions, and a documented removal process. Keep account recovery with an authorized owner.
Can this role manage personal tasks?
A clearly agreed personal administration lane may be possible, but privacy, payment, household, and family information need separate boundaries and should never be assumed from a business scope.
How is performance reviewed?
Review calendar accuracy, conflicts caught, brief completeness, follow through, tone, and escalation choices. Online status or message volume does not prove executive support quality.
What should the first week include?
Start with observation, redacted examples, calendar practice, draft replies, and one conflict rehearsal. Open live work only after the assistant can explain the approval rules.