How to Schedule Meetings Across Time Zones (Without the Chaos)
A practical playbook for picking meeting times that don't burn out your distributed team — with overlap math, async fallbacks and the tools that make it painless.
Scheduling a single recurring meeting across three time zones is the most common — and most quietly demoralising — ritual in remote work. Get it wrong and someone is always dialling in at 5am or eating dinner at the keyboard.
1. Pick a fairness rule before you pick a time
Agree explicitly on what fair means: rotate the painful slot, minimise the worst hour for anyone, or accept that the largest subteam gets the convenient slot. Decide once, write it down, stop re-arguing it every quarter.
2. Find the real overlap window
Everyone's "working hours" in their calendar is the honest starting point. The overlap of those windows — not 9 to 5 in HQ's time zone — is your true meeting surface.
- Map each person's real start/end hours in UTC.
- Intersect them. The result is often 60–120 minutes.
- Reserve that window for live work; default everything else to async.
3. Default to async, escalate to live
Status updates, design reviews, and even most decisions can happen in a thread with a 24-hour SLA. Reserve synchronous time for the two things async actually fails at: shaping ambiguous problems and repairing trust.
4. Use a converter, not a mental model
The fastest way to lose an hour to DST is to think you know what time it is in Sydney. Use the time zone converter for every external invite and paste the result into the meeting description.
Further reading
- IANA Time Zone Database — the authoritative source every operating system relies on.
- Harvard Business Review: How to do hybrid right — research-backed defaults for distributed work.
- GitLab's all-remote handbook — the most detailed public playbook on async-first scheduling.
Frequently asked
- What's the best time of day for a global all-hands?
- Around 14:00–16:00 UTC tends to hit acceptable hours for the Americas, Europe and most of Asia-Pacific simultaneously. Confirm against your specific team's locations with the converter.
- How do I avoid the same person always taking the bad slot?
- Rotate on a published schedule (e.g. by month) and put the rotation in the calendar invite itself so it's visible to everyone.
- Should I send invites in the recipient's local time?
- No — send in UTC or your own local time and let calendar apps handle the conversion. Manually converting introduces errors, especially around DST.