Time Zone Meeting Planner — Built to Survive Daylight Saving
Time zone meeting planner: add participants, propose a time, and see each person's local hour plus a 24-hour overlap strip showing where working hours line up — accurate through daylight saving transitions because it uses named IANA time zones, not fixed UTC offsets that go stale twice a year. Nothing is sent to any server.
Local times
| Participant | Time zone | Local time | Working hours |
|---|---|---|---|
| My location | Europe/Minsk | Sun, Jul 26, 10:00 | In window |
24-Hour Overlap Finder
Each block represents one hour of the day in the base participant's time zone. Green means all participants are within working hours. Amber means partial overlap. Neutral means no one is in their window.
Why the Overlap Shifts Twice a Year
Daylight saving time is the single most common reason a recurring cross-time-zone meeting suddenly feels off by an hour. The planner above always uses the correct offset for the exact date you pick — here is why that matters.
The US and EU change clocks on different dates
The United States starts daylight saving on the second Sunday of March and ends it on the first Sunday of November. The European Union starts on the last Sunday of March and ends on the last Sunday of October — roughly one to three weeks later in spring and one week earlier in autumn.
Why the gap shifts twice a year
Outside the transition window, a US–EU pair like New York and London sits at a steady 5-hour gap: both on standard time in winter, both on daylight time in summer. During the mismatch weeks — after the US has sprung forward but before the EU has — the same pair briefly sits at a 4-hour gap instead, then returns to 5 hours once the EU catches up.
Which pairs break during the mismatch weeks
Any recurring meeting between a US city and an EU or UK city is affected: New York–London, New York–Berlin, Chicago–Paris, and similar pairs all shift by an hour for those one-to-three-week windows twice a year. A meeting booked at a fixed local time in one region can land an hour earlier or later than expected for the other.
Southern-hemisphere pairs shift in the opposite direction
Australia and New Zealand observe daylight saving in their own summer, which is the northern hemisphere's winter — so their DST calendar runs roughly opposite to the US and EU. A pair like Sydney–London has its own separate set of mismatch weeks, distinct from the US–EU ones.
Want to see this in a live view for your own team instead of reading about it? Use the world clock meeting planner to compare working-hours overlap for common city pairs on standard time.
Why Use a DST-Aware Time Zone Meeting Planner?
- Named IANA time zones instead of fixed UTC offsets — no stale math after a DST change
- Recalculates the correct offset for the exact date you propose, not just "today"
- 24-hour overlap strip finds the best working-hours window for any given date
- DST transition guide on this page explains why recurring meetings drift twice a year
- Shareable link encodes all inputs (no personal data) so the whole team sees the same planner
- Copy summary exports a plain-text block ready to paste into Slack, email, or a calendar invite
- 100% private — no data is sent to any server; everything runs in your browser
- Works for any combination of cities, teams, or countries across all IANA time zones
Frequently Asked Questions
Make Every Meeting Count
MeetWave records your Zoom, Teams, and Google Meet calls locally — then generates AI summaries, action items, and meeting insights automatically. No bot joins your call. Privacy-first, works on Windows — there is no macOS or mobile version yet.