Let me save you the hour you were about to spend dragging a slider across a time zone tool. For how to schedule a meeting across 4 time zones, the answer is not a clever time. There is no good time for New York, London, Singapore, and Sydney together. The spread is fifteen hours. Every slot on the clock is someone's midnight. Once you accept that, the problem gets simpler: there are three bad times, and fairness means nobody owns the worst one permanently.
The worked example: New York, London, Singapore, Sydney
Using October offsets (New York UTC-4, London UTC+1, Singapore UTC+8, Sydney UTC+11), three slots cover every region's worst case evenly:
| Slot | UTC | New York | London | Singapore | Sydney | Who stretches |
|---|---|---|---|---|---|---|
| A | 13:00 | 9:00 AM | 2:00 PM | 9:00 PM | 12:00 AM | Sydney |
| B | 22:00 | 6:00 PM | 11:00 PM | 6:00 AM | 9:00 AM | London, Singapore |
| C | 06:00 | 2:00 AM | 7:00 AM | 2:00 PM | 5:00 PM | New York |
Rotate A, B, C weekly. Over three weeks every region takes the bad slot exactly once.
How to schedule a meeting across 4 time zones: the implementation
The rotation only works if it is explicit and enforced, which is where most teams fail. Create three separate recurring calendar events, one per slot, each repeating every three weeks and staggered so exactly one fires each week. Put the full rotation table in the meeting description so nobody has to ask when their bad week is. Then hold to it, especially when the current slot is inconvenient for whoever has the most calendar power. The classic failure mode: the rotation exists in theory, but the manager quietly moves every session to their own comfortable slot, and Sydney ends up back on permanent midnight duty. If you have ever been the Sydney in this arrangement, you know exactly how this ends: the person burns out, dreads the meeting, and eventually leaves.
When to give up on live meetings entirely
Rotation is the answer for meetings that genuinely need four regions live. Most recurring meetings do not. Status updates cross fifteen hours perfectly in writing and cost nobody their evening. My default for a 4-zone team: move everything to a shared document, and keep one live slot a month for decisions that actually need all four voices. You are reading this because someone asked you to find a time. The better answer might be that the time does not need to exist.
Check the overlap for your own four cities.
Interactive overlap indicator, computed from the real tz database.
Open the Timezone Overlap PlannerFrequently asked questions
How do you schedule a meeting across 4 time zones?
Accept that no good time exists, then rotate three inconvenient slots so the same region never owns the bad one. Create three recurring events, one per slot, each repeating every three weeks, and document the rotation in the meeting description.
Is there working-hours overlap across New York, London, Singapore, and Sydney?
No. The fifteen-hour spread means every slot falls outside normal hours for at least one region. The best you can do is mildly inconvenient for one side per week.
How do you implement a rotating meeting schedule?
One recurring calendar event per slot, each repeating every three weeks and staggered to fire weekly. Enforce it even when the current slot is bad for whoever controls the calendar, or the rotation quietly dies.
When should a 4-zone team stop meeting live?
When the meeting is mostly status sharing, or when one region keeps absorbing the bad slot. Move updates to writing and keep live time for real decisions.
Related guides: The Best Meeting Time Across the US, Europe, and Asia · Daylight Saving and Recurring International Meetings · Scheduling Across Time Zones in Google Calendar
Remote-work scheduling notes, roughly monthly: subscribe to the newsletter.