Meeting planner
Drop in 2–6 cities and ZoneShift will lay out the next 24 hours side by side, highlighting the slots where everyone is inside their normal 09:00–17:00 working window.
Schedule
Times are shown locally for each city. Rows shaded green are inside 09:00–17:00 in every selected city — those are the safe slots for a synchronous meeting.
| UTC | London Europe/London |
Singapore Asia/Singapore |
All in business hours? |
|---|---|---|---|
| 20:00, Thu UTC | 21:00, Thu · | 04:00, Fri · | — |
| 21:00, Thu UTC | 22:00, Thu · | 05:00, Fri · | — |
| 22:00, Thu UTC | 23:00, Thu · | 06:00, Fri · | — |
| 23:00, Thu UTC | 00:00, Fri · | 07:00, Fri · | — |
| 00:00, Fri UTC | 01:00, Fri · | 08:00, Fri · | — |
| 01:00, Fri UTC | 02:00, Fri · | 09:00, Fri | — |
| 02:00, Fri UTC | 03:00, Fri · | 10:00, Fri | — |
| 03:00, Fri UTC | 04:00, Fri · | 11:00, Fri | — |
| 04:00, Fri UTC | 05:00, Fri · | 12:00, Fri | — |
| 05:00, Fri UTC | 06:00, Fri · | 13:00, Fri | — |
| 06:00, Fri UTC | 07:00, Fri · | 14:00, Fri | — |
| 07:00, Fri UTC | 08:00, Fri · | 15:00, Fri | — |
| 08:00, Fri UTC | 09:00, Fri | 16:00, Fri | ✅ Yes |
| 09:00, Fri UTC | 10:00, Fri | 17:00, Fri · | — |
| 10:00, Fri UTC | 11:00, Fri | 18:00, Fri · | — |
| 11:00, Fri UTC | 12:00, Fri | 19:00, Fri · | — |
| 12:00, Fri UTC | 13:00, Fri | 20:00, Fri · | — |
| 13:00, Fri UTC | 14:00, Fri | 21:00, Fri · | — |
| 14:00, Fri UTC | 15:00, Fri | 22:00, Fri · | — |
| 15:00, Fri UTC | 16:00, Fri | 23:00, Fri · | — |
| 16:00, Fri UTC | 17:00, Fri · | 00:00, Sat · | — |
| 17:00, Fri UTC | 18:00, Fri · | 01:00, Sat · | — |
| 18:00, Fri UTC | 19:00, Fri · | 02:00, Sat · | — |
| 19:00, Fri UTC | 20:00, Fri · | 03:00, Sat · | — |
How to run a meeting that includes more than three time zones
Once a recurring meeting spans three or more time zones, you usually cannot find a slot that is inside everybody's working day. The pragmatic answer is to accept that, and to design around it: rotate which side is "inconvenienced" each week, keep the meeting short (30 minutes is plenty when one team is calling at 21:00), and make heavy use of an asynchronous follow-up channel so people who could not attend live still feel included.
The most common mistake teams make is to optimise the meeting time for the head office and never revisit it. Within six months everyone in the field has rearranged their evenings around a meeting nobody actually questioned. Use this planner once a quarter to re-check that the slot still makes sense — especially after a daylight-saving transition has shifted the relative offsets between two of the cities.
If your meeting is genuinely critical and one team is in Asia-Pacific while another is in the Americas, it is sometimes better to split it into two shorter regional meetings with shared written notes than to insist on a single global call at 23:00 for someone. ZoneShift cannot make those judgement calls for you, but the table above will tell you, brutally honestly, whether a polite single slot exists.