Executive Assistant Scheduling Time Audit: Test the Five-Hour Return

Run the five-hour scheduling audit in eight steps

Choose one repeatable lane such as customer steering calls, partner reviews, or operating updates. Exclude board emergencies, personnel matters, relationship-sensitive requests, and travel-heavy weeks. The test should measure routine coordination while protecting the assistant’s highest-value judgment.

1. 1

   Define the meeting lane and the finish line

   Write the lane’s purpose, owner, duration, normal date window, required roles, optional people, time zones, protected executive time, location rules, approval mode, and exception owner. Define completion as one verified invitation for the approved group or one bounded decision returned to the EA.
   • The lane repeats often enough to compare across two working periods.
   • Sensitive or ambiguous meetings stay EA-owned.
   • A poll response, drafted email, or proposed slot does not count as completion.
2. 2

   Baseline ten business days of manual touches

   For every meeting in the lane, log request cleanup, calendar checks, participant lookup, availability request, reminder, time-zone conversion, proposal, hold, approval preparation, invitation, decline handling, reschedule, and repair. Record active minutes, elapsed days, participant count, companies, providers, and final outcome.
   • Use a timer or same-day estimate rather than reconstructing the week from memory.
   • Separate active handling time from waiting on people.
   • Record abandoned and expired meetings as outcomes rather than dropping them from the sample.
3. 3

   Separate coordination from EA judgment

   Mark each touch as repetitive coordination, executive-policy application, relationship judgment, preparation, travel judgment, approval, or exception handling. The goal is to return repetitive coordination time. Do not count deciding what deserves the calendar, protecting focus, reading a stakeholder, or preparing the executive as waste.
   • The EA defines the classification, not the software vendor.
   • Mixed touches are split when a two-minute calendar check leads to a ten-minute priority decision.
   • The audit never frames the assistant as replaceable.
4. 4

   Write the delegation and privacy boundary

   Decide what the system may coordinate, which Google or Microsoft free/busy sources are approved, how an unconnected participant can provide bounded availability, who may be contacted, reminder caps, what context can be disclosed, and which slot requires review. Keep private reasons and event details with the EA.
   • Calendar connection is optional for external participants.
   • Possessing an address does not grant permission to contact it.
   • Required people, protected windows, and review-before-book cannot be silently relaxed.
5. 5

   Pilot with review-before-book

   Run the same lane with a structured brief. Let the workflow check approved free/busy, collect missing windows, normalize time zones, follow up inside policy, and prepare the best overlap. The EA reviews the exact slot, attendee set, organizer calendar, and wording before one invitation is sent.
   • The EA can pause, revise, reclaim, or stop any meeting.
   • Every handback asks for one real decision rather than forwarding the thread.
   • The assistant can see evidence freshness and the reason a slot was chosen.
6. 6

   Track completion and exception quality

   Count verified bookings, bounded exceptions, required declines, no-overlap decisions, stale evidence, expired approvals, duplicate messages, duplicate events, missing invitations, and repairs. Track whether Google, Microsoft, cross-company, or unconnected-participant cases create extra EA work.
   • A meeting marked complete has the right time, zone, organizer, required people, and invitation state.
   • Expected participant wait is not counted as assistant handling time.
   • Privacy exposure, unwanted contact, or a wrong attendee is a stop condition, not a minor metric.
7. 7

   Calculate the verified weekly return

   For the lane, subtract pilot-period coordination minutes plus pilot setup, review, exception, and repair minutes from baseline coordination minutes at comparable meeting volume. Normalize to a working week. Keep EA judgment and meeting preparation outside the savings column. Compare the result with WonderCal’s at-least-five-hour target.
   • Show the meeting count and complexity behind each period.
   • Do not hide implementation or exception time in another budget.
   • Report a shortfall honestly and name the touch categories that remain.
8. 8

   Expand, narrow, or reject the lane

   Expand only when completion stays correct, privacy holds, exception handbacks are useful, and net time returns. Narrow the lane when one participant type or meeting class creates repeated judgment. Reject the workflow when the EA spends more time correcting state, calming relationships, or checking invitations than the old method required.
   • Broader authority follows evidence, not vendor enthusiasm.
   • Sensitive lanes keep their own approval and disclosure rules.
   • Repeat the audit after workflow, calendar, executive, or team changes.

Compare scheduling approaches by net EA time returned

The audit follows the entire coordination loop. A method receives credit only when the meeting reaches a correct invitation or a useful exception without pushing hidden work back to the assistant.