Executive Assistant Scheduling Workflow: Coordinate Two Executive Offices

Coordinate two executive offices in eight steps

Use one forty-five-minute strategy meeting with Executive A, Executive B, both EAs, one outside board adviser, counsel, and one optional finance observer. The group spans Google and Microsoft. Counsel shares bounded windows without connecting a calendar. Each EA controls separate priority, privacy, and approval rules.

1. 1

   Open one shared meeting brief

   Record meeting ID, purpose, duration, bounded date range, deadline, meeting time zone, location, required and optional people, approved substitutes, organizer calendar, disclosure class, outreach policy, and terminal proof. Keep office-private context outside the shared fields. Success is one verified invitation or one bounded decision returned to the authorized assistants.
   • Both offices agree on the same attendee geometry and meeting revision.
   • A forwarded email never becomes the operating brief by accident.
   • A proposal, poll result, or drafted message is not completion.
2. 2

   Build an authority matrix for each office

   For Executive A and Executive B, name who may share free/busy, approve outreach, protect or release time, accept a substitute, approve a slot, write or update an event, reschedule, cancel, and disclose a reason. Keep calendar permission separate from business authority. An EA may be able to edit an event without being authorized to move a protected commitment.
   • Priority and relationship judgment stay with the responsible EA.
   • Booking, rescheduling, and cancellation have explicit owners.
   • The narrower office rule wins when shared disclosure would expose private context.
3. 3

   Name one coordinator of record

   Choose the person or system responsible for revision numbers, participant state, response deadlines, proposal status, and the final handback. This does not make that coordinator the executive calendar owner. It prevents two assistants from sending duplicate availability requests, approving different slots, or creating competing events.
   • Every reply and approval resolves to one meeting ID and revision.
   • Duplicate messages are suppressed before another participant chase begins.
   • Either EA can pause, reclaim, or escalate work within their authority.
4. 4

   Set privacy and outreach rules participant by participant

   For the board adviser, counsel, and observer, record approved channel, disclosed purpose, local-time send window, response deadline, reminder cap, opt-out path, and wording owner. Share ‘an executive conflict exists’ when needed, not the private customer, personnel, legal, or travel reason behind it.
   • Possessing contact information does not grant outreach authority.
   • Private event titles and unrelated attendees never enter the external request.
   • Relationship-sensitive wording remains reviewable by the responsible EA.
5. 5

   Collect current availability without requiring every connection

   Read approved Google and Microsoft free/busy for connected required people. Ask counsel for bounded windows in local time through the approved response path. Normalize identity, source, IANA zone, retrieval or reply time, consent, freshness, and error state. Keep one office’s private calendar details out of the other office’s view.
   • Missing provider access, silence, or expired evidence is not open time.
   • A correction invalidates proposals based on the old window.
   • Calendar connection is helpful and optional, not the product category.
6. 6

   Apply both executive policies before ranking preferences

   Intersect every required person, then apply protected blocks, preparation time, travel, working hours, meeting load, required buffers, and any office-specific deadline. Rank optional attendance and preferences only after both executive policies pass. If no slot survives, return the smallest date, duration, substitute, observer, or protected-time decision to the assistant who owns it.
   • One office cannot relax the other office’s hard rule.
   • Optional finance attendance can improve a proposal without blocking it.
   • The exception card names one owner and one decision, not the whole email chain.
7. 7

   Bind both approvals to one proposal revision

   Show exact slot, local times, required people, optional decision, organizer calendar, disclosure, evidence freshness, and any approved tradeoff. Capture the approvals required by the authority matrix. Re-check current required availability, then run one idempotent booking command. Reconcile an uncertain provider timeout before repeating the event write.
   • An approval for one slot cannot authorize a revised attendee set or different time.
   • Repeated approval or queue delivery does not create another event.
   • A changed required calendar returns the proposal for repair rather than booking stale evidence.
8. 8

   Verify the invitation and close the shared ledger

   Read back the canonical event and verify time, zone, organizer, every required participant, optional-attendee decision, approved wording, and invitation state. Return one concise result to both offices while keeping each office’s private rationale private. Record declines, stale evidence, human reclaims, retries, and the owner of any unresolved exception.
   • Both EAs see the same current meeting state.
   • No private office field appears in the shared event or completion message.
   • The workflow ends with verified invitations or a bounded exception.

Compare cross-office scheduling by who joins the state

The useful companion preserves two sets of executive judgment while carrying one shared meeting from brief to current invitations.