How to Schedule Meetings Across Three Time Zones
Short answer: Three-zone meetings rarely have a window where everyone is in standard working hours. Pick a fair rotation, default to the narrowest natural overlap (often 30–60 minutes), and use async writeups for anything that does not need a live discussion.
A team that spans New York, London, and Bangalore covers a 14-hour spread. Even if every member stretches their day, the live overlap is short. The question is not which hour works for everyone — it is which compromise the team is willing to accept and how to keep one region from absorbing all the inconvenience.
Step 1 — Map the working hours
Write down each region's normal working day in its own local time, then convert each to a common reference (UTC works well). Where the three windows overlap is the only time everyone is inside ordinary hours. For most Americas–Europe–Asia teams, that overlap is 30–90 minutes wide, not several hours.
Step 2 — Decide the meeting's purpose
- Decisions or unblockers: Schedule live, inside the natural overlap.
- Status updates and FYIs: Replace with async written updates.
- Working sessions: Shorter sessions, more often, inside the overlap window.
Step 3 — Anchor and rotate
Pick one region as the anchor for each recurring meeting and book in that region's local time. Rotate the anchor over time so each region absorbs the inconvenience in turn. Document the rotation so people know when their out-of-hours week is coming.
Step 4 — Buffer the DST weeks
US, UK, and EU DST transitions do not align. India does not observe DST. The practical effect is that recurring three-zone meetings can shift by an hour for a week or two in March and October. Reconfirm the meeting time around those transitions so nobody shows up at the wrong hour.
Step 5 — Make async the default
The honest version of three-zone scheduling is that most meetings should not be meetings. Standardise written updates, recorded video walkthroughs, and clear comment windows in shared docs. Keep live time for the things that actually need live time.
Frequently asked
What is the typical overlap for the Americas, Europe, and India?
Roughly 30–90 minutes around 09:30–10:30 New York / 14:30–15:30 London / 19:00–20:00 Bangalore. The exact window shifts by an hour during DST gaps in March and October.
Should one region always host the meeting?
No. A rotation is more sustainable. Anchor each meeting to one region's working hours and rotate the anchor week to week or month to month so the same team is not always working late or early.
What if no overlap exists at all?
Replace the meeting with a structured async update: written status, recorded video, or a shared document with a 24-hour comment window. Save synchronous time for decisions that genuinely need a live conversation.
How does this change with daylight saving time?
The overlap can move by an hour for two short windows each year when one region switches and others have not. Re-confirm the recurring meeting time around mid-March and late October.