Executive Assistant PTO Coverage: Hand Off Scheduling Without Duplicating Outreach

Hand off executive scheduling coverage in eight steps

Use one executive, a primary EA leaving for five business days, a backup EA, seven open meetings, Google and Microsoft calendars, three external people who will not connect calendars, one confidential hold, and one meeting that requires principal approval before booking.

1. 1

   Build one open-meeting ledger before PTO starts

   For every active request, record meeting ID, purpose class, duration, bounded date range, deadline, IANA zone, required and optional people, approved substitutes, connected and conversational availability, outreach status, proposal revision, approval state, organizer calendar, next action, next owner, and terminal proof. Keep private rationale in a separate restricted field.
   • A forwarded thread is supporting history, not the operating ledger.
   • Every meeting has one current revision and one accountable next action.
   • A draft, poll result, or tentative hold is not marked booked.
2. 2

   Write the coverage authority matrix

   Name who may read free/busy, contact each participant, release protected time, change duration, approve a substitute, approve a slot, write an event, reschedule, cancel, and disclose a reason during coverage. Separate calendar permission from executive judgment. Record what remains with the primary EA, the executive, chief of staff, or another relationship owner.
   • Backup access does not grant authority to relax priorities or relationship rules.
   • Sensitive, legal, board, and personnel meetings can follow narrower coverage rules.
   • The primary EA remains able to reclaim a meeting under the declared emergency path.
3. 3

   Classify each meeting as continue, hold, or escalate

   Continue settled coordination when authority, people, privacy, and next steps are clear. Hold work that depends on the primary EA’s unavailable judgment. Escalate a bounded decision when the meeting deadline cannot wait. Record the classification, reason, expiry, owner, and exact condition that reopens the workflow.
   • Coverage does not create fake urgency for every executive request.
   • A hold pauses reminders and proposals rather than leaving workers active.
   • An escalation asks for one decision, not a transcript review.
4. 4

   Transfer participant context without leaking private rationale

   Give the backup the approved channel, disclosed purpose, local-time wording, relationship owner, response deadline, reminder cap, opt-out path, and latest message state for each participant. Keep private event titles, internal priority disputes, personnel notes, and unrelated attendee details outside the coverage packet.
   • Possessing an email address does not grant new outreach authority.
   • The backup can see whether a reply is missing without seeing unnecessary calendar detail.
   • Relationship-sensitive wording remains reviewable by its owner.
5. 5

   Continue availability collection from current evidence

   Read approved Google and Microsoft free/busy for connected required people. Preserve still-valid bounded windows from unconnected participants with identity, source, IANA zone, consent, reply time, correction, and expiry. Ask only for missing or stale availability. Calendar connection is helpful and optional.
   • The backup does not restart the thread because the original message is unfamiliar.
   • Missing access, silence, and expired evidence are unknown rather than open time.
   • Optional people can improve a slot without blocking every proposal.
6. 6

   Return exceptions to the person who owns the judgment

   Intersect every required person, then apply protected time, travel, preparation, working hours, buffers, meeting load, deadline, and approved substitute policy. If no slot survives, create one exception card for the right owner: release this block, shorten duration, approve this substitute, widen these dates, change wording, or wait for the primary EA.
   • The backup never invents a priority tradeoff to make the calendar fit.
   • The executive sees the smallest required decision with local times and consequences.
   • Unrelated meetings and private reasons stay out of the exception card.
7. 7

   Book under the current authority and verify the result

   Bind approval to exact meeting revision, slot, required and optional people, organizer calendar, and disclosure. Re-check current required availability, issue one idempotent booking command, reconcile an uncertain provider response, then read back time, zone, organizer, attendees, and invitations. Record who acted under coverage authority.
   • Repeated approval or worker delivery cannot create a second event.
   • A changed required calendar invalidates the proposal before booking.
   • Completion is one verified invitation set or one bounded unresolved exception.
8. 8

   Hand control back without another reset

   At PTO end, return a concise ledger: booked and verified, waiting on participant, waiting on executive decision, held by policy, failed with recovery owner, or reclaimed. Revoke temporary access where appropriate, transfer open-operation ownership, preserve message and event identifiers, and stop the backup’s reminders before the primary EA resumes.
   • No meeting has two active coordinators after the handback.
   • The primary EA can inspect changes without rereading every thread.
   • Temporary permissions and copied files do not remain open by accident.

Compare PTO coverage by what the backup inherits

The useful companion transfers current coordination state while the EAs keep executive judgment, relationships, and exceptions.