Executive assistant operating workflow
Executive Assistant Scheduling Across Time Zones: A Cross-Company Runbook
A cross-company executive meeting is not ‘convert 3:00 PM to London.’ It is one principal in New York, a client CEO in London, counsel in San Francisco, an optional operating lead in Singapore, protected focus blocks, a travel day, and calendars split between Google and Microsoft. The executive assistant has to protect relationships and judgment while the coordination loop keeps moving.
The eight-step cross-company time-zone runbook
Run the method on one meeting type such as a monthly partner review, customer steering call, or operating committee. Do not start with a board emergency or a meeting whose priority is still disputed. The workflow removes repeated calculation and chasing without erasing the EA’s judgment.
- 1
Write one complete executive meeting brief
Record purpose, decision needed, organizer, required people, optional people, duration, date window, deadline, meeting format, meeting time zone, protected dates, travel constraints, approval owner, and communication owner. Add relationship context only when it changes the rule—for example, a client CEO who should receive a direct note rather than an automated reminder.- Required and optional people are listed separately.
- The deadline and duration are explicit before outreach begins.
- Protected preparation, travel, and recovery blocks remain hard constraints.
- 2
Build a zone and working-hours ledger
Store an IANA time-zone name for each participant and show every proposed slot in each person’s local time. Keep working hours, religious or regional constraints, and known travel in separate fields. Never carry a zone as ‘UTC-5’ across seasons; daylight-saving changes can make a fixed offset wrong.- Mark unknown zones as missing rather than inferred facts.
- Confirm the zone when a person replies with a vague local phrase.
- Recalculate every proposal after a zone or travel correction.
- 3
Set fairness and exception policy before finding slots
Define acceptable local hours for ordinary meetings and a narrower protected band for the executive. Decide who can approve an early or late exception and record who carried the last inconvenient slot. Fairness is a relationship decision. A scheduling system can apply the rule, but the EA owns the rule and any exception.- No slot outside policy appears as an ordinary recommendation.
- A recurring meeting rotates inconvenience when the relationship permits it.
- The proposal explains which policy created the tradeoff.
- 4
Read connected free/busy without exposing private details
Use approved Google and Microsoft free/busy for the principal and participants who have connected calendars. Record which account is authoritative and when availability was read. The coordination record needs busy intervals, not event names. If a token expires or a provider response is partial, mark the evidence incomplete rather than treating the person as free.- Keep private titles, locations, and attendee lists out of the shared record.
- Read only calendars that legitimately affect the meeting.
- Separate no conflict from no usable calendar response.
- 5
Collect missing availability in each participant’s local zone
Calendar connection is optional. Ask unconnected participants for availability inside the bounded date window, state the duration, show the organizer’s zone and the recipient’s local zone, and set a response deadline. Normalize the answer into the same availability record as connected free/busy. Cap reminders and keep relationship-sensitive outreach in the EA-owned lane.- Participants do not need to reveal event details or create an account.
- Ambiguous answers receive one narrow clarification.
- Silence from a required participant escalates; it never becomes implied consent.
- 6
Produce a two-slot decision card
Intersect all required availability first. Then score optional attendance, local-hour fairness, principal preferences, travel, buffers, and deadline. Give the EA no more than two leading slots plus the best rejected alternative. Show local times, availability freshness, missing optional people, and the exact exception attached to each choice.- Never drop a required participant to improve convenience.
- Every proposed slot shows each participant’s local date and time.
- A no-overlap result names the smallest constraints that could move.
- 7
Approve and commit one canonical invitation
Use review-before-book until the lane is proven. Re-check free/busy immediately before the commit, bind approval to the exact slot and participant list, and send one invitation from the designated organizer calendar. A repeated click or worker retry must return the same event rather than create duplicate holds or invitations.- The event time zone and every attendee are verified after creation.
- Optional attendance is visible rather than silently assumed.
- The EA can pause or reclaim the meeting before the final commit.
- 8
Close the loop and review exceptions weekly
Record the booked slot, local-hour burden, approval owner, manual touches, missing-calendar path, declines, and any post-booking repair. Review recurring causes: stale calendars, vague time-zone replies, travel changes, relationship-sensitive reminders, or rules that generate too many exceptions. Fix the policy before widening automation.- Track coordination time returned without counting preparation or relationship work as waste.
- Keep a short list of meeting types that always remain EA-owned.
- Use recovered time for priorities, preparation, and people—not more low-value meetings.
The EA keeps the decisions that make the calendar credible
An open slot is not permission. The EA knows that a technically free hour lands after an overnight flight, before an earnings call, or inside the only preparation block that protects the executive’s performance. That context becomes policy where it is repeatable and stays human judgment where it is not.
The EA also keeps relationship tone. Some participants can receive a routine availability request. A board member, sensitive candidate, regulator, investor, or strained client relationship may need a direct message. A scheduling companion should reduce coordination interruptions and surface those exceptions early. It should never pretend the relationship layer is replaceable.
Time-zone arithmetic is not scheduling execution
A time-zone converter can render 14:00 UTC in five cities. A calendar-sync utility can expose conflicts. A booking link can show host-side options. A poll can gather votes. An AI assistant can draft ‘what works for you?’ Those are useful steps, but the EA still carries required roles, missing calendars, follow-ups, fairness, approval, and the final invitation.
Scheduling execution owns the complete brief through connected or conversational availability, required overlap, exception routing, safe booking, and verified invitations. That is the boundary WonderCal is moving toward for executive assistants, with the EA retaining priorities, approvals, relationships, and unusual cases.
Privacy rules for cross-company executive meetings
Google Calendar supports a free/busy-only sharing level that hides event details. Microsoft’s delegate model lets the account owner choose the level of access. The runbook should use the minimum access that supports the meeting and keep event titles out of emails, spreadsheets, analytics, and model prompts.
Privacy also means not explaining another participant’s conflict. Say that a slot is unavailable. Do not expose the customer escalation, medical appointment, legal matter, compensation conversation, or board preparation that created the block. The shared scheduling record needs availability and policy, not private reasons.
A safe rollout toward five hours returned
Choose one repeatable cross-company lane and tag the EA’s work for a week: brief cleanup, calendar check, zone conversion, availability request, follow-up, proposal, hold, invitation, and repair. Keep preparation, travel planning, relationship work, and priority decisions outside the removal target. WonderCal’s five-hour figure is the target; the team’s own before-and-after record must prove it.
Start in review-before-book. After the lane survives daylight-saving changes, unconnected participants, a required decline, a travel update, and a reschedule, consider allowing only that lane to book inside policy. Good delegation is not maximum autonomy. It is calendar Tetris disappearing while the EA’s judgment becomes easier to apply.
Compare cross-time-zone scheduling by finished work
The right approach protects local hours, private calendars, and executive judgment while carrying the coordination to one confirmed event.
| Decision vector | Email, spreadsheet, and manual holds | Converter, poll, booking link, or sync tool | WonderCal execution direction |
|---|---|---|---|
| Coordination completion | The EA converts zones, checks calendars, chases replies, selects the slot, sends the invite, and repairs changes. | Removes one step, while required roles, follow-up, approval, and closure can remain with the EA. | Designed to carry a complete brief through availability, overlap, approval, invitation, and result. |
| Cross-company reach | Works everywhere because the EA translates every provider and participant by hand. | Works when the participant can use the surface and host-side availability is enough. | Target path combines Google and Microsoft free/busy with conversational collection for unconnected people. |
| Privacy | Depends on consistent masking across spreadsheets, copied holds, and long email threads. | Varies by product and configuration; shared surfaces can collect or expose more context than needed. | Product direction matches private free/busy and keeps event details out of participant coordination. |
| Exception handling | Strong human judgment, with every routine case also interrupting the EA. | Often stops at no overlap, incomplete votes, broken sync, or a participant who cannot use the link. | Designed to surface a bounded exception with local-time, role, freshness, and policy context for the EA. |
| Time and cost | No new software path, but the EA remains the human API for every calendar and time zone. | Fast to adopt for a narrow step; actual time return depends on how much chasing and closure remain. | The value case is the five-hour weekly target, measured against retained control and correct escalation. |
Coordination completion
Email, spreadsheet, and manual holds
The EA converts zones, checks calendars, chases replies, selects the slot, sends the invite, and repairs changes.
Converter, poll, booking link, or sync tool
Removes one step, while required roles, follow-up, approval, and closure can remain with the EA.
WonderCal execution direction
Designed to carry a complete brief through availability, overlap, approval, invitation, and result.
Cross-company reach
Email, spreadsheet, and manual holds
Works everywhere because the EA translates every provider and participant by hand.
Converter, poll, booking link, or sync tool
Works when the participant can use the surface and host-side availability is enough.
WonderCal execution direction
Target path combines Google and Microsoft free/busy with conversational collection for unconnected people.
Privacy
Email, spreadsheet, and manual holds
Depends on consistent masking across spreadsheets, copied holds, and long email threads.
Converter, poll, booking link, or sync tool
Varies by product and configuration; shared surfaces can collect or expose more context than needed.
WonderCal execution direction
Product direction matches private free/busy and keeps event details out of participant coordination.
Exception handling
Email, spreadsheet, and manual holds
Strong human judgment, with every routine case also interrupting the EA.
Converter, poll, booking link, or sync tool
Often stops at no overlap, incomplete votes, broken sync, or a participant who cannot use the link.
WonderCal execution direction
Designed to surface a bounded exception with local-time, role, freshness, and policy context for the EA.
Time and cost
Email, spreadsheet, and manual holds
No new software path, but the EA remains the human API for every calendar and time zone.
Converter, poll, booking link, or sync tool
Fast to adopt for a narrow step; actual time return depends on how much chasing and closure remain.
WonderCal execution direction
The value case is the five-hour weekly target, measured against retained control and correct escalation.
Frequently asked questions
How should an executive assistant schedule across time zones?
Should executive assistant scheduling software replace the EA’s judgment?
What if an external executive will not connect a calendar?
How do you protect privacy in cross-company executive scheduling?
Where can EAs review WonderCal’s current workflow?
Primary sources
- Google Calendar Help: Share your calendar — official sharing levels, including free/busy with hidden event details
- Google Calendar API: Freebusy query — official free/busy bounds, response time zone, intervals, and error fields
- Microsoft Support: About delegates — official delegate access and owner-controlled permission guidance
- Microsoft Graph: calendar getSchedule — official Microsoft availability request, response-zone, and working-hours model
- IANA Time Zone Database — canonical time-zone identifiers and daylight-saving rule data
Delegate the time-zone chase. Keep the executive judgment.
Start with one cross-company meeting lane, keep review-before-book visible, and measure whether WonderCal returns coordination time while the EA retains priorities, relationships, and exceptions.
See WonderCal for executive assistants