Executive Assistants · Fundamentals
Propose meeting times across time zones and constraints
Six people, five time zones, four continents, one hour. New York is four hours behind London this week instead of five, Sydney is about to change its clocks in the other direction, and one person has protected focus time every morning. This guide works through the arithmetic so you can spend your attention on the part that is actually hard: deciding who gets the inconvenient slot.
What AI is for here, and what it isn't
Scheduling across time zones is two problems wearing one coat. The first is arithmetic: what time is 11:30 UTC in São Paulo, Singapore and Sydney, this week, given who has changed their clocks? The second is politics: when no slot works for everyone, who stays up late?
AI is very good at the first problem when you give it the facts. It converts consistently, checks every candidate slot against every person's hours, and ranks the options by how many people they inconvenience and by how much. Calendar scheduling assistants find free time; this step adds the rules they don't know about.
The second problem is yours. The AI doesn't know that the regional head in Sydney took the late slot for the last three meetings, or that your executive wants to be seen taking the early call this time. It can tell you who is inconvenienced. It can't tell you who should be.
Collect the constraints
For each participant, write down:
- City and time zone, as a city name (for example "Sydney", not "AEST"). Abbreviations are ambiguous and don't change with daylight saving; city names do.
- Normal hours, in their local time.
- Stretch hours: what they'll accept if asked, and how often.
- Protected time: focus blocks, school runs, prayer times, standing commitments that never move.
- Free/busy for the dates you're considering.
Then the meeting itself: length, the window of dates, and whether everyone must attend all of it.
The unwritten rules are the most valuable part of this list, and the part only you have. Ask other assistants; they usually know.
Generate and rank candidate slots
Find candidate meeting slots for the participants below. Show your
working.
DATES: [range] LENGTH: [minutes] START TIMES: on the hour or half hour
PARTICIPANTS (city; normal hours; stretch hours; protected time; busy):
1. [name or role] — [city]; [hours]; [stretch]; [protected]; [busy]
2. ...
STEP 1: For each date in the range, give each city's UTC offset.
Flag any date where a city changes its clocks.
STEP 2: For each candidate start time (in UTC), give every participant's
local start and end time, and mark each person:
OK (whole meeting inside normal hours), STRETCH (inside stretch
hours) or OUT (outside, or overlapping protected time or busy).
The whole meeting must fit, not just the start.
STEP 3: List the five best slots, ranked first by fewest OUT, then
fewest STRETCH. Show the table for each.
RULES: Don't move anyone's hours. Don't decide who should be
inconvenienced. If no slot has zero OUT, say so plainly.
"The whole meeting must fit, not just the start" matters. A 21:30 start looks fine for someone who works until 22:00, until you add the hour.
Check the offsets yourself
Daylight saving is where these calculations go wrong. North America, Europe and the southern hemisphere change their clocks on different dates, so for a few weeks each spring and autumn the gaps between cities shift by an hour. Some places don't change at all.
Check each city's offset for the meeting date in a world clock or your calendar app's time zone view. If even one is wrong, every slot in the table is wrong for that person. Correct it in the prompt and run it again.
Make the call, openly
If a slot works for everyone, you're done: send it. If not, the choice is about fairness, and it's better made openly than by default. Common approaches:
- Rotate. Alternate the inconvenient slot between regions across a series of meetings, and keep a note of who took it last.
- Split. Two shorter meetings, or one meeting with a written contribution from the person who can't make it.
- Wait. If a clock change is coming, the following week may work for everyone.
- Ask. "Would you take 22:30 this once?" is a reasonable question. Assuming the answer is not.
Put the options to your executive with one line each. Then send the invitation from the organizer's calendar, so each person sees it in their own local time.
Worked example: six people, four continents
Fictional example. Elena needs a one-hour regional leadership meeting the week of Tuesday 16 March 2027. The participants:
| Person | City | Normal hours | Stretch | Protected |
|---|---|---|---|---|
| Elena | New York | 07:30–18:00 | 07:00–18:30 | |
| Rafael | São Paulo | 08:00–19:00 | 07:30–20:00 | |
| Priya | London | 08:00–18:00 | to 20:00 | |
| Jonas | Frankfurt | 08:00–19:00 | to 20:00 | 09:00–11:00 daily |
| Wei Ling | Singapore | 08:00–21:00 | to 22:00 | |
| Tom | Sydney | 07:00–21:00 | to 22:00 | Never before 07:00 |
The offsets step flags the trap first: the United States moved its clocks on 14 March, but the United Kingdom and Germany won't until 28 March, and Sydney leaves daylight saving on 4 April. This week, New York is UTC−4, London UTC+0, Frankfurt UTC+1, Singapore UTC+8 and Sydney UTC+11.
No slot works for all six. The best two each leave out one person:
| Slot (UTC) | Elena | Rafael | Priya | Jonas | Wei Ling | Tom |
|---|---|---|---|---|---|---|
| 11:30 | 07:30 | 08:30 | 11:30 | 12:30 | 19:30 | 22:30 (out) |
| 12:00 | 08:00 | 09:00 | 12:00 | 13:00 | 20:00 | 23:00 (out) |
Every reasonable option this week costs Tom a late night. Sam asks the AI to run the same check for the week of 6 April, after Sydney's change. At 11:00 UTC that week, Elena is at 07:00 and Tom at 21:00: both within stretch hours, and nobody out.
Sam's note to Elena gives three options: this week at 11:30 UTC with Tom sending a written update; this week with Tom asked to join late; or 6 April at 11:00 UTC, with Elena taking the 07:00 start herself. Elena picks the third. It's not urgent, and she'd rather take the early call than ask Tom to take another late one.
Record the schedule
Meeting: [name], [length], week of [date] Organizer: [name]
OFFSETS FOR THE DATE (checked by hand)
[City]: UTC[±n] Clock change this week? [yes/no]
PARTICIPANTS
Name | City | Normal | Stretch | Protected
SLOTS CONSIDERED (UTC → local)
Slot | OK | Stretch | Out (who)
DECISION: [slot], because [one line]
Who took the inconvenient time: [name] (last time: [name])
Invitation sent from: [calendar] on [date]
What stays with you: the politics. Who gets the inconvenient slot, how often, and how you ask them.