Productivity · Specialized agent role

Executive Assistant

The Executive Assistant supports preparing executive priorities, correspondence, schedules, meetings, decisions, and delegated follow-through. It works from approved inboxes, calendars, briefing documents, meeting records, priority lists, contacts, and delegation rules, applies explicit operating rules, and makes incomplete or uncertain work visible instead of silently guessing.

Get StartedReview the workflow

Best for

  • Teams that repeatedly handle preparing executive priorities, correspondence, schedules, meetings, decisions, and delegated follow-through and can describe a dependable operating path
  • executives and authorized human assistants who need consistent preparation, explicit ownership, and visible exception handling

Typical inputs

  • Authoritative inputs such as approved inboxes, calendars, briefing documents, meeting records, priority lists, contacts, and delegation rules, with access restricted to what the role needs
  • Definitions, required fields, service expectations, approval thresholds, and checks for authority, confidentiality, relationship sensitivity, timing, recipient, commitment, priority, and conflicting instructions

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Confirm the request, responsible owner, permitted sources, and definition of completion for preparing executive priorities, correspondence, schedules, meetings, decisions, and delegated follow-through

2

Gather context

Collect approved inboxes, calendars, briefing documents, meeting records, priority lists, contacts, and delegation rules and retain enough context to trace material facts and decisions

3

Prepare the work

Apply the configured rules, validate authority, confidentiality, relationship sensitivity, timing, recipient, commitment, priority, and conflicting instructions, and prepare executive briefs, decision queues, schedule options, correspondence drafts, and delegated action trackers

4

Review and hand off

Send the result to executives and authorized human assistants, pausing exceptions or consequential actions for an accountable person

Actions it can perform

  • Organize and prepare preparing executive priorities, correspondence, schedules, meetings, decisions, and delegated follow-through using the permitted sources and documented operating rules
  • Validate authority, confidentiality, relationship sensitivity, timing, recipient, commitment, priority, and conflicting instructions, preserve source context, and route exceptions before consequential action

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • A reviewable package of executive briefs, decision queues, schedule options, correspondence drafts, and delegated action trackers with ownership, status, sources, and unresolved questions
  • An exception queue explaining which rule, field, source, or approval prevented safe completion

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • executive-assistant
  • assistant-supports
  • supports-preparing
  • preparing-executive
  • executive-priorities
  • priorities-correspondence
  • correspondence-schedules
  • schedules-meetings
  • meetings-decisions
  • delegated-follow
  • follow-through
  • inboxes-calendars
  • calendars-briefing
  • briefing-documents
  • documents-meeting
  • meeting-records
  • records-priority
  • priority-lists
  • lists-contacts
  • delegation-rules
  • rules-applies
  • applies-explicit
  • explicit-operating
  • operating-rules
  • makes-incomplete
  • visible-instead
  • silently-guessing
  • guessing-produce
  • produce-executive
  • executive-briefs
  • briefs-decision
  • decision-queues
  • queues-schedule
  • schedule-options
  • options-correspondence
  • correspondence-drafts
  • delegated-action
  • action-trackers
  • trace-back
  • authoritative-inputs
  • inputs-such
  • access-restricted
  • needs-definitions
  • definitions-required
  • required-fields
  • fields-service
  • service-expectations
  • authority-confidentiality
  • confidentiality-relationship
  • relationship-sensitivity
  • sensitivity-timing
  • timing-recipient
  • recipient-commitment
  • commitment-priority
  • conflicting-instructions
  • instructions-confirm

Human approval and escalation

Approval boundary

executives and authorized human assistants approve consequential external actions, policy exceptions, irreversible record changes, and any output that represents a business commitment.

Escalation rule

Confidential matters, board or investor communication, legal commitments, personal issues, and ambiguous delegated authority are routed with the source context, work completed, uncertainty, and requested decision intact.

What remains under human control

  • People define the source authority, permissions, quality rules, review gates, and acceptable boundaries for preparing executive priorities, correspondence, schedules, meetings, decisions, and delegated follow-through
  • executives and authorized human assistants resolve ambiguity, approve consequential actions, and remain accountable for the final business outcome

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

Microsoft 365Review integration scopeGoogle WorkspaceReview integration scopeSlackReview integration scopeNotionReview integration scope

Example workflow

A recurring request involving preparing executive priorities, correspondence, schedules, meetings, decisions, and delegated follow-through is checked against authority, confidentiality, relationship sensitivity, timing, recipient, commitment, priority, and conflicting instructions; routine preparation is completed, while exceptions are sent to executives and authorized human assistants with the evidence needed to decide.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

Email Assistant

See the responsibilities, controls, and handoffs for this related specialist role.

Explore Email Assistant

Calendar Manager

See the responsibilities, controls, and handoffs for this related specialist role.

Explore Calendar Manager

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible Executive Assistant workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started