Executive Assistant Scheduling Approval Workflow: Keep Every Decision Current

Build a current executive scheduling approval queue in eight steps

Use one executive, one EA, a chief of staff who owns board exceptions, eight open meetings, Google and Microsoft calendars, three external people without connected calendars, protected preparation blocks, and two proposals that expire while the executive is traveling.

1. 1

   Start with one executable meeting brief

   Record meeting ID, purpose class, duration, bounded date range, deadline, IANA zones, required and optional people, approved substitutes, protected time, buffers, relationship owner, outreach policy, approval mode, organizer calendar, and terminal proof. Keep sensitive rationale in a restricted field separate from the decision card.
   • Every request has one current revision and one accountable owner.
   • Required attendance cannot be weakened inside a rushed approval reply.
   • A draft, hold, poll winner, or suggested slot is not marked booked.
2. 2

   Write the authority matrix before the queue fills

   Name who may read free/busy, contact each participant, release protected time, shorten duration, approve a substitute, approve the final slot, write the event, reschedule, cancel, and disclose a reason. Calendar permission and executive judgment are different. Route board, personnel, legal, and relationship exceptions to their named owners.
   • The EA keeps priorities, context, relationships, approvals, and exceptions.
   • The executive sees only decisions that require the executive.
   • A delegate token or mailbox permission cannot expand business authority.
3. 3

   Collect current evidence before asking for a decision

   Read approved Google and Microsoft free/busy for connected required people. Ask unconnected participants for bounded windows through approved channels with purpose, local time, deadline, correction, reminder cap, and opt-out. Normalize source, retrieval or reply time, IANA zone, consent, freshness, expiry, and provider errors.
   • Calendar connection is optional and helpful.
   • Private event titles and unrelated attendees stay outside the queue.
   • Missing access, silence, and stale evidence are unknown rather than free time.
4. 4

   Separate routine completion from true approval work

   Let already-delegated, low-risk meetings proceed under settled rules. Open an approval item only for a choice the named owner must make: release a block, accept a relationship tradeoff, approve a substitute, choose among equivalent current slots, widen dates, shorten duration, change wording, or reclaim the meeting.
   • The queue does not turn every free/busy read into an interruption.
   • Each item asks for one decision and names the consequence.
   • No-overlap becomes a bounded exception, not another inbox dump.
5. 5

   Build privacy-safe decision cards with expiry

   Show meeting purpose, decision owner, exact question, participant roles, candidate local times, current evidence timestamp, protected constraint, deadline, options, consequences, revision, and expiry. Omit private event names, another participant’s reply, internal relationship notes, and medical or personnel detail unless the approver truly needs it.
   • Every option already clears all current required-participant evidence unless the card says otherwise.
   • An expired card cannot authorize a write.
   • The approver can decline, change, delegate, or reclaim instead of choosing a false binary.
6. 6

   Order the queue by deadline and decision ownership

   Group cards by owner and decision type, then rank deadline risk, participant wait, relationship policy, and evidence expiry under explicit rules. Batch only decisions that remain independent. One urgent customer meeting cannot silently consume protected time reserved for a board obligation.
   • Priority is declared policy, not persuasive wording in a request.
   • The same collision cannot appear in three owners’ queues.
   • Waiting items show what resumes them and when they expire.
7. 7

   Bind approval to the current revision and re-check

   Capture actor, authority, meeting revision, exact slot, required and optional people, organizer calendar, disclosure, evidence versions, and expiry. Before booking, refresh required availability and confirm the approval still applies. If anything material changed, revoke the old card and issue one concise updated decision only when judgment is still needed.
   • A yes to Tuesday cannot authorize Wednesday after a provider change.
   • Repeated clicks or worker deliveries cannot create a second event.
   • The EA can see why approval expired without rereading the entire thread.
8. 8

   Verify invitations and audit time returned to the EA

   Issue one idempotent booking operation, reconcile an uncertain provider response, then read back time, zone, organizer, every required attendee, optional decision, and invitation state. Close reminders and proposals. Measure queue decisions, coordination touches avoided, exception burden, false escalations, duplicate writes, and verified completion without inventing a savings result.
   • Completion is one verified invitation set or one bounded unresolved exception.
   • The weekly five-hour target is tested locally against measured EA work.
   • The audit preserves decision evidence while redacting private calendar and message content.

Compare executive approvals by what the decision contains

The useful companion delivers one current, scoped decision while the EA keeps priorities, relationships, privacy, and exceptions.