Best time to schedule global meetings

For a meeting that genuinely covers the Americas, Europe, India and the Asia-Pacific, there is no time slot at which everyone is on the clock at their normal hours. The trick is to pick the slot that's the least bad for the most people — and to rotate the pain fairly when you can. This is a practical guide to doing that well.

Why "everybody at 09:00 to 17:00" doesn't exist globally

A 24-hour day fits a maximum of two non-overlapping eight-hour shifts. When your team includes US West Coast (UTC−7/8), Western Europe (UTC+0/+1) and East Asia (UTC+8/+9), you span 16 to 17 hours of offset. There is no single hour that lands inside the 09:00–17:00 window for all three. Someone is always either starting their day a bit early or finishing a bit late.

The follow-the-sun formula

Most successful global teams use a simple rule: anchor the meeting against UTC and pick the slot that minimises the worst-case discomfort. The slot that works for the largest number of teams looks like this:

This is the default "everyone-on-call" slot for most truly global teams. East Asia and the Antipodes pay a price (late evening / midnight); the Americas and Europe get reasonable hours. Whether that trade-off is acceptable depends on how often you're asking the same teams to take the bad slot.

Smaller-scope sweet spots

If your meeting only crosses three of the four big regions, you have more room. Some classic windows:

• Americas + Europe — 13:00–15:00 UTC. NY morning, UK / EU afternoon. Good for everyone.
• Europe + Asia — 09:00–11:00 UTC. UK morning, India afternoon, Singapore early evening, Tokyo late evening.
• Asia-Pacific + US West — 23:00–01:00 UTC. US West Coast late afternoon, Sydney mid-morning, Singapore late evening.
• Americas + Asia-Pacific — 22:00–00:00 UTC. US afternoon to evening, Sydney morning, Tokyo morning. The classic "Sydney 9 AM" window.

Be fair, not just convenient

The most common mistake in global meeting design is to anchor every recurring meeting on the host's local 09:00. The host gets the best slot every time, and one or two teams take the late-night cost forever. Better patterns:

1. Rotate the inconvenient slot. Every quarter, move the recurring meeting by 4–6 hours so a different team takes the late or early slot.
2. Split the meeting. If you can't find a slot that works for all regions, run the same meeting twice with a written summary in between. More work, but better attendance and morale.
3. Make some meetings async. Most "all-hands" content can be recorded and consumed asynchronously, with a short live Q&A in each regional slot.

Time-of-day effects to consider

• Avoid lunch hours. 12:00–13:00 in the host's zone knocks attendance down by 20–30%.
• Avoid the Monday 09:00 slot. Many teams reserve that for internal planning, and energy is lower than mid-week.
• Use the 25-minute meeting. Booking 30-minute meetings as 25 minutes gives attendees a buffer, which dramatically improves the on-time rate when calls are stacked.

Calendar hygiene

Anchor every recurring meeting to a single named time zone (e.g. America/New_York or Europe/Berlin). Avoid pinning to a fixed UTC offset, which will drift relative to local working hours twice a year. When in doubt, send the invite from the time zone of the smallest regional team — that team will see a stable time, and the bigger teams can absorb the seasonal one-hour shift.

FAQ

Related guides

• How to plan a multi-zone meeting
• Australia and USA meetings
• USA and Europe meetings
• Daylight saving and meetings