How to Schedule Meetings Across 3+ Time Zones (Without the Headache)
Three time zones is exponentially harder than two. The bigger your team's geographic spread, the smaller the overlap window — and the more important it is to do this right.
The overlap problem
With two time zones, you usually find some working overlap (NYC and London share 9 AM-1 PM Eastern / 2 PM-6 PM London). Add a third zone and the math gets brutal:
NYC + London + Bangalore: the only overlap when all three are at work is roughly 9-10 AM Eastern / 2-3 PM London / 7:30-8:30 PM Bangalore. That's a one-hour window where one team is starting their day and another is ending theirs.
Add a fourth zone like Sydney and the all-overlap window often disappears completely. You then have to make tradeoffs about who works outside normal hours.
Strategy 1: Rotate the burden
If one meeting time always works for two teams but never for the third, the third team always loses. Over time, this creates resentment.
Fix: rotate. If the team in Bangalore takes evening meetings this month, the team in NYC takes early-morning meetings next month. Make this explicit — write it down. Otherwise the default (whatever's convenient for HQ) becomes permanent.
Strategy 2: Default to async, sync only when necessary
Most meetings don't need to be meetings. Status updates, FYIs, and decisions with clear options can be a written message + comments. Reserve sync time for things that genuinely benefit from real-time conversation:
- Brainstorming new ideas (high bandwidth)
- Resolving conflict or disagreement
- Onboarding or relationship-building
- Decisions where you need to read the room
Everything else: write it down, post it where the team can see, ask for written replies within a window (24-48 hours). This is harder than scheduling a meeting but creates better documentation.
Strategy 3: Define team overlap windows
For each pair of time zones in your team, identify the 2-4 hour window where both have normal working hours. Make these "meeting windows" official.
NYC + London? 9 AM - 1 PM Eastern.
NYC + Bangalore? 7:30 AM - 10 AM Eastern (heavy lift for NYC) or 7 PM - 10 PM Bangalore.
London + Bangalore? 2 PM - 5:30 PM London / 6:30 PM - 10 PM Bangalore.
Schedule meetings inside these windows by default. Anything outside should require explicit reasoning.
Strategy 4: Record everything that's sync
If a meeting absolutely must happen at a time that excludes part of your team, record it. Post the recording and a written summary the same day. The excluded folks can watch async and add written follow-up.
This isn't a perfect substitute — they miss the live discussion — but it's far better than them learning about decisions through office gossip days later.
Tools that actually help
The category of "scheduling tools" includes a lot of bloat. The few that actually save time:
- World clock with multiple cities pinned: See all your team's local times at a glance. ClockWithUs world clock supports this for free.
- Time zone converter for one-off conversions: "What's 3 PM London in Bangalore?" Quick lookups beat mental math. The timezone converter handles this.
- When2meet or Doodle for polling: When you genuinely don't know which time works, get availability from everyone first.
- Calendar overlay in Google Calendar/Outlook: Add a "secondary time zone" to your calendar app so you see local + team time side-by-side.
The cruel twist: Daylight Saving Time
Just when you've got your meeting times memorized, DST hits. Different countries switch on different dates — or not at all.
The US/Canada switches in March/November. Europe switches the LAST Sunday of March/October, which is one week different from North America. India never switches. Brazil and most of Asia don't switch either.
So for two weeks each year, your "9 AM London / 4 PM Bangalore" meeting shifts by an hour. Your team in Bangalore wonders why London is suddenly late. Mark these transition periods on your team calendar — they cause more confusion than anything else in distributed scheduling.
Frequently asked questions
What's the best time to schedule a meeting between New York, London, and Bangalore?
The narrow overlap is roughly 9-10 AM Eastern, which is 2-3 PM London and 7:30-8:30 PM Bangalore. This means one team is starting their day, one is mid-day, and one is ending theirs. Recurring meetings at this time work but are tough on the India team — rotate the burden if you can.
How do I avoid booking meetings at impossible times for some of my team?
Add a secondary time zone to your calendar app so you see both your local time and your colleague's local time when scheduling. In Google Calendar: Settings > World Clock. In Outlook: View > Calendar > Time Zones. This catches accidental 2 AM scheduling for someone else.
Is it OK to schedule meetings outside someone's working hours?
Occasionally yes, but rotate who bears the burden. If one team always has to be online at 6 AM or 10 PM and others never do, you're creating a hidden tax on that team. Document the rotation explicitly.
How does Daylight Saving Time affect international meetings?
For 2-3 weeks each year, your recurring meeting times shift relative to teams in countries that don't observe DST (India, most of Asia) or that switch on different dates (Europe switches a week before/after the US). Mark these transition periods in your team calendar — they cause endless confusion.
What's better: rotating meeting times or always meeting at the same time?
Always meeting at the same time is easier but creates a permanent burden on whichever team has the worst local time. Rotating is fairer but adds scheduling overhead. For a small team that meets weekly, rotation works. For a large team meeting monthly, fixed time with rotation of the 'inconvenient' role works better.