Meeting Planner
Find overlapping work hours across multiple time zones for global team scheduling.
Date
Add Timezone
No full overlap — best partial: 2/3 zones overlap simultaneously
Darker green columns show maximum overlap. Consider early/late start times for some participants.
Related Tools
How the Meeting Planner Works
The planner uses the browser''s built-in Intl.DateTimeFormat API backed by the IANA Time Zone Database — the same standard used by every major calendar app, operating system, and programming platform. All 24 columns represent UTC hours on the selected date. Each cell converts that UTC instant to the local time in the respective timezone, accounting for the exact UTC offset on that specific date, including all DST rules.
- 1
Select a date
Pick the date you want to meet. The planner automatically adjusts UTC offsets and DST for every timezone on that specific date.
- 2
Add your time zones
Add every location where participants are based. The grid supports unlimited zones — from two to a full distributed team across five continents.
- 3
Read the overlap grid
Each row is a timezone, each column is a UTC hour. Green cells are local business hours (9 AM–6 PM). Columns where all rows are green are your optimal meeting windows.
- 4
Book the meeting
The banner above the grid surfaces the UTC window where all zones overlap in business hours, or the best partial overlap if none exists.
DST Accuracy & Methodology
Daylight saving time transitions vary by country and year. The United States typically switches in mid-March and early November; most of Europe follows two weeks later. Some regions — Arizona, Iceland, most of Africa, Japan — observe no DST at all. This planner uses IANA timezone identifiers (e.g., America/New_York, Europe/London) rather than raw UTC offset strings, so it correctly reflects the precise offset on any date you select — including the two-week transition window when US and EU clocks are offset by one extra hour.
Best Meeting Times for Common Timezone Combinations
Reference guide for the most common global team pairings (standard time, non-DST period unless noted).
| Location Pair | Best Window |
|---|---|
| New York + London | 2 PM–5 PM ET / 7 PM–10 PM London |
| New York + Paris / Berlin | 3 PM–5 PM ET / 9 PM–11 PM CET |
| London + Dubai | 9 AM–5 PM London / 12 PM–8 PM Dubai |
| London + Singapore | 9 AM–1 PM London / 5 PM–9 PM SGT |
| New York + Mumbai | No natural overlap |
| New York + Tokyo | No natural overlap |
| London + Sydney | 9 AM–11 AM London (summer) / 6 PM–8 PM AEDT |
| Los Angeles + Tokyo | 4 PM–5 PM PT / 9 AM–10 AM JST (+1 day) |
Windows shift ±1 hour near DST transitions. Use the interactive planner above for exact dates.
Tips for Scheduling Global Team Meetings
- →Rotate inconvenient slots fairly. When there''s no overlap, take turns holding the off-hours slot so the same team member isn''t always on a late-night call.
- →Always share times in UTC. Calendar invites should specify UTC (or include it alongside local times). This avoids confusion during DST transitions when one party''s offset has already changed.
- →Check DST dates twice a year. Build a recurring reminder in March and November (or April/October for the Southern Hemisphere) to verify that recurring meeting slots haven''t drifted by an hour.
- →Prefer mid-week slots. Tuesday, Wednesday, and Thursday tend to have better attendance rates for cross-timezone meetings than Monday mornings or Friday afternoons.
- →Record and async-follow-up. For teams where overlap is less than 1 hour, record the meeting and share it with team members in difficult time zones so they can catch up asynchronously.