Most international meeting schedules have a fairness problem. The same timezone ends up with the 7 AM or 9 PM slot every week while everyone else meets during normal hours. This guide covers the rotation method, the 4-hour overlap rule, and async-first patterns that distributed teams actually use to fix this.
The Problem with "Let's Find a Time That Works"
When a team spans New York, London, and Singapore, there is no single time that's comfortable for everyone. The typical response is to pick a time that's "OK" for most people — which in practice means the team in the least powerful timezone (usually APAC) gets the worst slot.
A quick example: a "compromise" meeting at 9 AM New York / 2 PM London / 10 PM Singapore is fine for two of three offices and miserable for the third. If that meeting happens weekly for a year, Singapore has attended 52 late-night meetings while everyone else was comfortable. That's not a scheduling problem — it's a retention problem.
The Rotation Method
The simplest fair solution: rotate the meeting time so the inconvenience is shared. Three common patterns:
Weekly rotation (3-timezone teams)
| Week | Time (UTC) | NY (ET) | London (GMT) | Singapore (SGT) | Who stretches |
|---|---|---|---|---|---|
| Week 1 | 14:00 | 9 AM | 2 PM | 10 PM | Singapore (late) |
| Week 2 | 08:00 | 3 AM | 8 AM | 4 PM | New York (early) |
| Week 3 | 22:00 | 5 PM | 10 PM | 6 AM | London (late) |
Each timezone gets an uncomfortable slot once every 3 weeks instead of one timezone absorbing it permanently. This works best for recurring meetings like all-hands or team retrospectives.
Two-slot rotation (simpler)
If a 3-slot rotation feels chaotic, use two alternating times. For US-Europe-APAC teams:
- Slot A: Friendly for US + Europe (e.g., 9 AM ET / 2 PM GMT / 10 PM SGT)
- Slot B: Friendly for Europe + APAC (e.g., 4 PM GMT / 12 AM SGT+1 / 11 AM ET)
Alternate weekly. APAC attends Slot B in person and watches the Slot A recording, and vice versa for the US.
The 4-Hour Overlap Rule
Before scheduling anything, check how many hours of business-hours overlap your team actually has. The rule of thumb: you need at least 4 hours of overlap for synchronous collaboration to work. Below that, you should shift to async-first.
| Corridor | Overlap | Recommended approach |
|---|---|---|
| US East ↔ UK | ~3.5h | Mostly sync, with async for non-urgent |
| US East ↔ Central Europe | ~3h | Protect the overlap for decisions only |
| UK ↔ India | ~4.5h | Comfortable sync window |
| US West ↔ UK | ~1h | Async-first, 1 sync per week max |
| US ↔ Australia | ~0-2h | Fully async or rotation |
| US ↔ Japan | ~0-1h | Fully async or rotation |
Use the global meeting planner to see your exact overlap. Add all your team's cities and the green zones show when everyone is in business hours.
When to Go Async-First
If your overlap is under 3 hours, don't fight it with more meetings. Instead:
- Replace status updates with written async updates. A daily Slack post or Notion page takes 5 minutes to write and can be read by any timezone at any time.
- Use recorded video for context-heavy communication. A 5-minute Loom explaining a PR is worth more than a 30-minute meeting to discuss it.
- Reserve synchronous time for decisions. If something needs real-time back-and-forth, that's worth the calendar gymnastics. If it doesn't, write it down.
- Set "response windows" instead of "response times." Instead of "respond within 2 hours," agree on "respond within your next business day." This prevents the expectation that people are available 24/7.
Setting Up Your Tools
Calendar setup
Every calendar app supports multiple timezones. Turn it on:
- Google Calendar: Settings → Time zone → check "Display secondary time zone"
- Outlook: File → Options → Calendar → check "Show a second time zone"
- Apple Calendar: Preferences → check "Turn on time zone support"
Always create events in one specific timezone and let the calendar app convert. Never write both times in the invite body — they'll drift when DST changes.
Meeting planner tools
Before proposing a time, check the visual overlap:
- Global Meeting Planner — Add all your team's cities and drag the timeline to find working hours overlap. Free, no account required.
- Conference Call Planner — Designed specifically for scheduling international conference calls.
Meeting Hygiene for Global Teams
- Start on time, every time. When someone is attending at 10 PM their local time, every minute of waiting feels like an insult.
- Share the agenda 24 hours before. This lets people in early timezones prepare before the overlap window.
- Record everything. Someone will miss the meeting. Make it painless for them to catch up.
- End 5 minutes early. Back-to-back meetings across timezones mean no buffer. Build it in.
- Acknowledge the stretch. If someone is joining at 6 AM or 10 PM, say thank you. It matters.
Specific Advice for Common Corridors
US East Coast ↔ UK
The New York-London corridor has about 3.5 hours of overlap. Best slot: 2 PM London / 9 AM New York. Watch out for the 2-3 week DST gap in March and October when the time difference shifts from 5 to 4 hours.
US ↔ India
The US-India corridor is brutal: 9.5 to 13 hours depending on which US coast. The only real overlap is morning IST / evening ET. Most teams use 8-9 AM IST / 9:30-10:30 PM ET, or accept that this corridor is async-first.
Europe ↔ APAC
UK to Singapore has a workable 4.5-hour overlap. UK to Australia is tougher at 1-2 hours (and 0 during parts of DST). For EU-APAC teams, the sweet spot is 8-9 AM London / 4-5 PM Singapore.
Find Your Team's Overlap
Add all your cities and see exactly when everyone is in business hours.
Open Global Meeting Planner
