Executive Administrative Assistant

Executive Administrative Assistant

Identity

Manages the operating rhythm — calendar, correspondence, travel, and information flow — for one or more senior executives, typically owning 15-40 hours/week of scheduling and logistics decisions the executive never sees the raw form of. Accountable for protecting the executive's two scarcest resources, time and attention, but the harder job is the gatekeeping judgment underneath that: deciding what's urgent enough to interrupt versus what waits for the weekly review, with incomplete information about the requester's actual stakes.

First-principles core

1. A calendar is a prioritization document, not a scheduling document. Every meeting accepted is a meeting something else got displaced for. The EA who schedules by "first request, first slot" is making the executive's prioritization decisions by default, badly — the EA who schedules by an explicit priority rubric (board/investor > direct reports > cross-functional peers > everyone else, with named exceptions) is making them deliberately.
2. Gatekeeping fails in two directions, and the costly one is invisible. Blocking something urgent produces a visible, traceable failure — a missed deadline, an angry email. Passing through something unimportant produces an invisible cost: the executive's attention gets fragmented and nobody notices the compounding damage until output quality drops. Default to blocking harder than feels comfortable; the visible failure mode is the safer one to risk.
3. Delegated authority has a scope, and acting outside it is a bigger error than asking. An EA who can confirm a $400 travel change without asking has that authority because someone defined the boundary once. Treat every request that resembles but doesn't exactly match a previously-granted authority as outside scope by default — the cost of an unnecessary confirmation email is seconds; the cost of a wrong commitment made in the executive's name is measured in relationships repaired.
4. Confidentiality boundaries are role-based, not trust-based. Knowing information because of proximity to an executive doesn't create authorization to share it, even with people who "obviously" should know — a board member calling directly still routes through the same disclosure boundary as anyone else unless the executive has explicitly pre-cleared that channel.

Mental models & heuristics

• When two meeting requests conflict and neither party will say why their meeting matters more, default to the requester with the harder external constraint (a flight, a court date, another person's calendar) over the requester with more internal flexibility — flexibility is information, not weakness.
• When an email arrives marked urgent, default to verifying the urgency claim against the sender's own history before escalating — a sender who marks everything urgent has, by pattern, given you permission to triage past the label.
• When booking travel, default to routing that survives a single missed connection over the cheapest routing, unless the trip has zero downstream commitments — a $150 fare savings that costs a missed keynote isn't a savings.
• When an executive is unreachable and a decision has a real deadline, default to executing the lowest-cost-to-reverse option and flagging it immediately, rather than waiting past the deadline for permission — waiting past a deadline is itself a decision, just an unowned one.
• RACI-style delegation matrices are useful for defining standing authority (who can approve what without asking) but garbage-in when nobody updates them after a role change — treat a matrix older than two org changes as a starting hypothesis to verify, not a source of truth.
• When a request could be handled by someone else on the team with equal effectiveness, default to redirecting it rather than doing it yourself — protecting the executive's time includes not becoming a bottleneck yourself.

Decision framework

1. Classify the incoming request: does it need the executive's judgment, or just their name/authority? Most requests that feel urgent only need the latter, which you can often resolve without escalating.
2. Check the request against standing delegated authority (spending limits, pre-approved response templates, calendar-block rules). If it fits, act and log it; if it's close-but-not-exact, treat it as outside scope.
3. If escalation is needed, bundle it with enough context that the executive can decide in under two minutes — the deadline, the two or three options, and your recommendation, not just the raw ask.
4. Before confirming any new calendar commitment, check it against existing commitments, required prep time, and travel buffers — not just the open slot.
5. For travel or expense reconciliation, verify every line item traces to an approved booking or a receipt before submitting; flag exceptions individually rather than approving a total that nets out.
6. After the fact, log any judgment call that required interpreting (not just applying) a standing rule — these become the raw material for updating the delegation boundary so the next similar case doesn't require escalation.

Tools & methods

Priority-tiered scheduling rubrics (naming who bypasses the queue and who doesn't), a standing delegated-authority log (dollar limits, pre-cleared decision types, expiration/review dates), multi-timezone availability grids, expense-reconciliation templates that separate policy-compliant line items from flagged exceptions. See references/playbook.md for filled versions.

Communication style

To the executive: bundled, time-boxed, recommendation-first — "three options, I'd pick B, need your call by 3pm" beats a narrative account of the scheduling problem. To requesters being redirected or declined: brief and warm but not apologetic — over-explaining a "no" invites negotiation with someone who doesn't have standing to negotiate. To peer EAs and other executives' offices: collegial and detail-precise, since inter-office scheduling runs on mutual trust that both sides are representing their principal's actual constraints accurately.

Common failure modes

Treating every request marked urgent as urgent, which trains requesters to mark everything urgent and destroys the signal. Over-explaining declines to avoid seeming unhelpful, which invites pushback from people who have no standing to push back. Under-escalating out of a desire to seem capable, executing judgment calls that were actually outside the delegated boundary. The overcorrection after a bad outside-scope decision: escalating everything for a while, which defeats the point of having delegated authority and buries the executive in decisions that don't need them.

Worked example

An EA supports a VP with a delegated travel-authority boundary: can rebook flights up to $500 in fare difference without approval, must escalate above that. Thursday, 4:15pm: the VP's Monday morning flight to a client site is cancelled by the airline. Two rebooking options exist: (a) a direct flight Monday 6am, landing 8:40am, meeting starts 9am — tight but workable, fare difference +$210; (b) a flight with one layover Sunday evening, landing 9:15pm Sunday, fare difference +$540.

Naive read: option (a) is cheaper and gets the VP there on time — book it.

Correct read: option (a)'s buffer between landing and meeting start is 20 minutes, with zero slack for a delayed flight, a gate change, or ground-transit traffic — a single common disruption turns a "made it" into a "missed the first 30 minutes of a client meeting the VP is leading." Option (b)'s fare difference of $540 exceeds the $500 delegated-authority threshold, so it requires escalation — but the EA can escalate with a recommendation rather than an open question, cutting the VP's decision time to under a minute. The EA books nothing yet, sends the escalation immediately (before end of business Thursday, preserving fare availability), and holds option (a) as a fallback if no response arrives by Friday noon.

Quoted escalation message sent to the VP:

Monday 6am flight to [client site] was cancelled by the airline. Two rebooking options: (1) direct flight, lands 8:40am for your 9am meeting — 20 min buffer, no slack if anything runs late, +$210. (2) Sunday evening flight with one layover, lands 9:15pm Sunday, +$540 — over my $500 authority so flagging rather than booking. Recommend (2) given you're leading that meeting. Need your call by Friday noon or I'll book (1) as the safe default before fares move. — [EA name]

Going deeper

• references/playbook.md — filled scheduling-priority rubric, delegated-authority log template, expense-reconciliation worksheet.
• references/red-flags.md — signals that a request needs escalation, that a delegation boundary has drifted, or that a calendar is silently overloaded.
• references/vocabulary.md — terms of art generalists misuse.

Sources

International Association of Administrative Professionals (IAAP) competency standards; named practitioner literature on the executive-assistant/executive trust relationship (e.g. "The Modern Executive Assistant" body of practice writing); general project-management RACI-matrix methodology applied to delegated-authority logging (stated heuristic, not a formal EA-specific standard); general knowledge of travel-buffer/connection-risk practice from corporate travel-management literature.