Time Zone Meeting Planner Guide: Scheduling Across Global Teams
Quick Answer
- *Convert each participant's work hours to UTC, then find the overlap window.
- *US ↔ Europe typically overlaps 3–5 hours; US ↔ Asia overlaps only 1–2 hours.
- *There are 38 distinct UTC offsets in use (not 24), including half-hour and 45-minute zones.
- *DST transitions create 1–2 week windows where your usual overlap shifts by an hour.
The Remote Work Time Zone Challenge
Remote work is no longer niche. According to Buffer's 2025 State of Remote Work report, 69% of remote workers collaborate with at least one colleague in a different time zone. For fully distributed companies, that number hits 91%. Scheduling a single meeting that works for New York, London, and Tokyo is genuinely hard math.
A 2024 study by Owl Labs found that time zone coordination was the #2 challenge for remote teams (behind communication clarity). The average distributed team spans 3.2 time zones, and teams with members across 5+ zones report spending 4.3 hours per week on scheduling logistics alone.
How to Calculate Overlap Hours
The method is simple: convert everyone's working hours to UTC, then find the intersection.
| City | UTC Offset | Local Hours (9–5) | In UTC |
|---|---|---|---|
| New York | UTC−5 | 9:00 AM–5:00 PM | 14:00–22:00 |
| London | UTC+0 | 9:00 AM–5:00 PM | 09:00–17:00 |
| Berlin | UTC+1 | 9:00 AM–5:00 PM | 08:00–16:00 |
| Dubai | UTC+4 | 9:00 AM–5:00 PM | 05:00–13:00 |
| Mumbai | UTC+5:30 | 9:00 AM–5:00 PM | 03:30–11:30 |
| Tokyo | UTC+9 | 9:00 AM–5:00 PM | 00:00–08:00 |
| Sydney | UTC+11 | 9:00 AM–5:00 PM | 22:00–06:00 |
New York and London overlap from 14:00–17:00 UTC (9 AM–12 PM ET / 2–5 PM GMT). That gives you 3 hours. Add Berlin and it shrinks to 14:00–16:00 UTC (2 hours). Add Tokyo and there is zero overlap during standard business hours.
Common Route Overlaps
| Route | Offset Difference | Overlap Window | Duration |
|---|---|---|---|
| US East ↔ UK | 5 hours | 2–5 PM UK / 9 AM–12 PM ET | 3 hours |
| US East ↔ Central Europe | 6 hours | 3–5 PM CET / 9–11 AM ET | 2 hours |
| US West ↔ UK | 8 hours | 5 PM UK / 9 AM PT | 1 hour |
| UK ↔ India | 5.5 hours | 9–12:30 PM UK / 2:30–6 PM IST | 3.5 hours |
| US East ↔ Japan | 14 hours | 8–9 AM JST / 6–7 PM ET | 1 hour |
| Europe ↔ Australia | 10–11 hours | 8–9 AM CET / 6–7 PM AEDT | 1 hour |
The Daylight Saving Trap
DST transitions are a scheduling landmine. The US switches in March and November. The EU switches on different dates. Japan, China, and India don't observe DST at all. This creates 4–6 weeks per year where your normal overlap window silently shifts by an hour.
In 2023, the EU seriously debated abolishing DST entirely. As of 2026, it remains in effect but individual member states can opt out. According to the IANA time zone database, there are over 400 named time zones tracking these rules, which is why hardcoding offsets in code or calendars is a recipe for bugs.
Practical tip: always schedule recurring meetings using the city name, not the UTC offset. "9 AM New York time" automatically adjusts for DST. "14:00 UTC" does not — it stays fixed, meaning it becomes 10 AM ET in summer instead of 9 AM.
Strategies for Impossible Time Zones
Rotating Meeting Times
If one group always takes the 7 AM or 10 PM meeting, resentment builds. GitLab's remote work handbook (based on 2,000+ employees in 65+ countries) recommends rotating inconvenient times so no single timezone bears the burden permanently.
Async-First Communication
Companies like Basecamp and Doist have documented that reducing mandatory meetings by 50% while increasing async documentation actually improved project velocity by 15–20%. Not everything needs a meeting. Status updates, code reviews, and most decisions can happen asynchronously.
The Follow-the-Sun Model
Some support and operations teams hand off work at the end of each timezone's day to the next zone. This creates continuous coverage without anyone working overnight. According to a 2023 Gartner report, 34% of enterprise support teams now use some form of follow-the-sun scheduling.
Find the best meeting time across time zones
Use our free Time Zone Meeting Planner →Frequently Asked Questions
How do I find overlapping work hours between time zones?
List each participant's working hours in UTC, then find the intersection. For example, New York (UTC−5, working 9am–5pm = 14:00–22:00 UTC) and London (UTC+0, working 9am–5pm = 09:00–17:00 UTC) overlap from 14:00–17:00 UTC, which is 9am–12pm in New York and 2pm–5pm in London.
What is the hardest time zone combination to schedule?
US West Coast (UTC−8) to East Asia (UTC+8/+9) is among the hardest with a 16–17 hour offset. Standard work hours barely overlap — typically only 5–6pm Pacific lines up with 9–10am in Tokyo. Teams spanning these zones often rely on asynchronous communication or rotate meeting times.
How many time zones are there?
There are 38 distinct UTC offsets in use, not the commonly assumed 24. Some zones use 30-minute offsets (India at UTC+5:30, Iran at UTC+3:30) and a few use 45-minute offsets (Nepal at UTC+5:45, Chatham Islands at UTC+12:45). The IANA time zone database tracks over 400 named zones.
When does daylight saving time change in different countries?
The US and Canada switch in March and November. The EU switches in March and October. Australia switches in April and October (reversed seasons). Many countries including Japan, China, India, and most of Africa and Asia do not observe DST at all. During transition weeks, your usual overlap hours may shift by an hour.
What is the best time to schedule a meeting with Europe and Asia?
For Western Europe (UTC+0/+1) and East Asia (UTC+8/+9), the best window is typically 8–10am European time, which is 4–6pm in East Asia. This gives European participants a morning meeting and Asian participants a late-afternoon slot before end of business.