How to Schedule Meetings Across Time Zones

Scheduling across time zones goes wrong in a few predictable ways: someone mixes up the direction of the offset, forgets that daylight saving shifted overnight, or writes "3pm" without saying where. Here is a method that removes the guesswork every time.

1. Anchor to one reference zone

Pick a single zone as your anchor — usually the organizer's, or the zone most attendees share — and work out the proposed time there first. Everything else becomes a conversion from that anchor. Trying to juggle three local times at once in your head is how mistakes creep in; converting from one fixed anchor keeps it straight.

2. Find the working-hours overlap

The real constraint is not "what time is it there" but "when are we all awake and working at the same moment." Sketch each person's working window — say 9:00 to 17:00 — and look for where the windows overlap. Sometimes the overlap is generous; sometimes it is a single uncomfortable hour; occasionally there is none, and someone has to take an early or late call.

A quick rule: the wider apart the zones, the earlier you should search. San Francisco and London overlap in San Francisco's morning; San Francisco and Sydney barely overlap at all except very early or very late.

3. Watch the date, not just the clock

When zones are far apart, a meeting can fall on a different calendar day for different people. A Friday afternoon call in New York is already Saturday morning in Tokyo. Always confirm the date in each person's zone, not only the time — "Friday 4pm New York = Saturday 6am Tokyo." This single habit prevents a surprising share of missed meetings.

4. Name the zone the way humans do

Never send an invite that just says "3pm." And be careful with abbreviations — "CST" can mean Central Standard Time in North America or China Standard Time, which are worlds apart. The clearest format names a city and the UTC offset:

• Good: "10:00 London (UTC+1) / 11:00 Berlin / 05:00 New York"
• Risky: "10:00 BST" or "3pm CST"

Listing two or three local times explicitly leaves nothing to interpretation, and it is a courtesy that signals you have done the math so they don't have to.

5. Let calendar software own recurring events

For one-off meetings, a clearly written invite is enough. For anything recurring, create it in calendar software with an explicit time zone attached, and let the software handle daylight-saving shifts. A weekly call set to "09:00 America/New_York" stays correct through DST changes; a call remembered as "always 14:00 UTC" will drift out of everyone's mornings twice a year.

Make the overlap visual

The fastest way to do all of this is to see it. Our meeting planner lays each city's hours side by side and highlights the window where everyone is inside working hours, so you can pick a slot in seconds and read off each person's exact local time and date.