How to Schedule Meetings Across Time Zones (Without the Pain)

Published July 7, 2026 · gworldtime Guides

Every distributed team learns the same lessons the hard way: someone joins at midnight, someone converts the time wrong, and someone gets ambushed by daylight saving. Here's the playbook that prevents all three.

Step 1: Know your overlap window

Before proposing any time, work out when everyone's working hours actually intersect. Assuming a 9:00–18:00 workday, here's what common city pairs look like:

Cities	Difference*	Realistic overlap
New York ↔ London	5 h	9:00–13:00 NY / 14:00–18:00 London — comfortable
London ↔ Seoul	8–9 h	8:00–10:00 London / 17:00–19:00 Seoul — narrow
New York ↔ Seoul	13–14 h	Almost none — one side must flex (early NY morning = Seoul evening)
San Francisco ↔ Berlin	9 h	8:00–9:30 SF / 17:00–18:30 Berlin — narrow
Seoul ↔ Sydney	1–2 h	Nearly the whole day — easy

* Ranges exist because daylight saving time changes the difference during part of the year.

For two-region teams, the overlap window is usually obvious once you see it. For three regions (say US–Europe–Asia), a single humane meeting time often does not exist — see "when there is no good time" below.

Step 2: Write times so they can't be misread

Most cross-zone disasters are communication failures, not calculation failures. Three rules:

Name the city, not the abbreviation. "9:00 a.m. CST" is ambiguous — CST is used for US Central, China, and Cuba time. "9:00 a.m. Chicago time" cannot be misread.
State the date for every zone. "Friday 8 p.m. New York" is "Saturday 9 a.m. Seoul". If you write only "Friday", half the invitees will show up a day off. Write both: "Fri Jul 10, 20:00 New York / Sat Jul 11, 09:00 Seoul."
For anything precise, add UTC. A single UTC timestamp (Sat 01:00 UTC) is the unambiguous anchor everyone can verify. (Why UTC? See UTC vs GMT.)

Step 3: Let the calendar do the conversion

Calendar invitations (Google Calendar, Outlook, iCal) store events as absolute moments and render them in each attendee's local zone automatically — including future DST shifts. This makes a calendar invite strictly more reliable than any time written in an email or chat. The rule for teams: if it matters, it gets an invite. Text descriptions are a courtesy; the invite is the truth.

Step 4: Defuse the daylight saving bomb

Twice a year, recurring international meetings silently move for half the attendees, because the US, Europe, and the southern hemisphere all change their clocks on different dates — and Asia doesn't change at all. A meeting pinned to 9:00 a.m. New York moves an hour later in Seoul every November, and there are weeks in spring and autumn when New York–London is 4 hours apart instead of 5.

What works:

Anchor each recurring meeting to one explicitly named city, and make sure everyone knows which one it is.
Put the four annual change dates (US spring/fall, EU spring/fall) in the team calendar as reminders to re-check meeting times.
After every clock change, re-confirm the next occurrence in chat: "Reminder: from next week this call is 22:00 Seoul, not 23:00."

Step 5: When there is no good time, rotate the pain

For US–Europe–Asia teams, every possible time is bad for someone: what's morning in California is night in Seoul and evening in Berlin. Healthy teams handle this deliberately:

Rotate meeting times so the same region isn't always on the midnight shift. Alternate between an Asia-friendly slot and an Americas-friendly slot.
Go async by default. Reserve live meetings for discussion and decisions; move status updates into documents, recorded videos, or threads that each zone reads during its own day.
Record everything and treat the recording + notes as first-class output, so missing the live call costs little.
Respect the edges. A "quick 30 minutes" at 11:30 p.m. is not quick for the person staying up for it. Acknowledge it, and return the favor.

Step 6: Build zone-awareness into daily habits

Teams that work smoothly across zones share one habit: they always know roughly what time it is for their colleagues. The fastest way to build that intuition is to keep the other offices' clocks visible. On gworldtime you can pin up to five cities and see them side by side with live time-difference badges — and the day/night globe tells you at a glance whether your teammate is in daylight or fast asleep. Checking it for two seconds before you hit "call" is the cheapest courtesy in remote work.

Quick checklist

☑ Found the real overlap window (checked today's time difference, not a remembered one)
☑ Time written with named cities + dates for each zone (+ UTC for precision)
☑ Calendar invite sent — the invite is the source of truth
☑ Recurring meetings anchored to one named city, DST change dates in the calendar
☑ Late-night burden rotated, meeting recorded for those asleep

Open the World Clock →