Executive Assistant Scheduling Intake Template: Write a Brief AI Can Execute

Build the executive scheduling brief in eight steps

Start with one repeatable cross-company meeting type: a customer steering call, partner review, or operating update. Do not begin with a board emergency, personnel matter, travel-heavy week, or relationship the executive has marked as EA-owned.

1. 1

   Name the purpose and the decision owner

   Write one sentence for why the meeting exists, the decision or outcome expected, the requesting person, the executive sponsor, and the person who can change the brief. A vague courtesy request may still deserve the calendar, but the EA needs enough context to rank it against preparation, travel, focus, and other commitments.
   • The meeting has a named owner rather than a forwarded chain.
   • The purpose is safe to share at the approved level.
   • An unclear priority remains in EA review rather than automatic coordination.
2. 2

   Set the date window, deadline, and duration

   Record the earliest date, latest date, scheduling deadline, meeting duration, minimum notice, and whether the deadline is hard or preferred. Add the executive’s meeting time zone and each known participant zone. Keep travel, preparation, recovery, and focus blocks as policy rather than treating every visible gap as available.
   • Use calendar dates and IANA time zones rather than ‘sometime next week.’
   • Duration includes any required preparation or transition buffer.
   • The request names who can extend the window or shorten the meeting.
3. 3

   Separate required roles from optional people

   List required participants, optional participants, required roles, approved substitutes, and people who need the result but not the invitation. ‘Customer team’ is not a participant rule. A meeting can proceed without an optional observer; it cannot quietly drop the decision-maker because Wednesday looks convenient.
   • Required and optional attendance are visible before availability collection.
   • Substitutes are approved by role and named authority.
   • Recipients of notes are not added to the scheduling quorum by accident.
4. 4

   Write the executive’s calendar policy for this meeting

   Apply preferred days, working hours, protected blocks, meeting density, buffers, travel limits, location rules, focus windows, and any participant-specific treatment that the EA is authorized to record. Mark each constraint as hard, preferred, or explain-before-overriding. Keep private reasons out of shared fields.
   • A technically free slot can still be prohibited by policy.
   • Sensitive relationship context remains in the EA-owned record.
   • Only the executive or named delegate can change a hard constraint.
5. 5

   Define the privacy and availability boundary

   Choose whether approved connected calendars may provide free/busy, who can see availability, and what the system may ask unconnected participants. Calendar connection should reduce work, not become mandatory. Request bounded windows from external people without asking them to expose personal event details or a full calendar.
   • Event titles, descriptions, attendee lists, and private reasons stay out of routine coordination.
   • The brief records authoritative calendars and the freshness expected before booking.
   • An external participant can decline or correct availability without creating an account.
6. 6

   Assign outreach, reminder, and tone authority

   Name who the system may contact, through which channel, in whose voice, with what meeting description, and how many reminders are permitted. Define escalation for silence, decline, ambiguous response, sensitive reply, and deadline risk. The EA keeps relationship tone; software follows the approved communication lane.
   • Possessing an address is not the same as permission to contact it.
   • Reminder caps and do-not-contact state are explicit.
   • VIP, board, personnel, and disputed-priority requests stay human-owned where required.
7. 7

   Choose coordinate, review, or EA-owned booking

   Use coordinate only for a settled lane the software may carry through one invitation. Use review when the system may collect evidence and prepare choices but the EA approves the exact slot and people. Use EA-owned when priority, relationship, travel, confidentiality, or exception risk requires the assistant to lead every move.
   • Approval is bound to the current brief, people, slot, and organizer calendar.
   • The EA can pause, revise, reclaim, or cancel the workflow.
   • Booking, rescheduling, cancellation, and outreach can have different authority.
8. 8

   Define completion and the exception handback

   The brief is complete when one canonical invitation is verified for the approved attendees, or when a bounded exception returns to the named owner. List stop reasons such as no required overlap, required decline, deadline risk, stale calendar evidence, expired approval, changed brief, or provider write uncertainty. Each handback asks for one decision.
   • The EA receives a result, not a pile of status notifications.
   • A no-overlap handback names the smallest authorized change that could help.
   • The final event, attendee list, local times, and any unresolved exception are visible.

Compare scheduling intake by what happens after submission

A good intake method protects the executive’s policy and then reduces coordination work. Capturing a request without carrying it to a result only creates a cleaner queue.