Check weekly meetings across time zones and daylight saving
Choose a real start in the planner, then inspect the weekly preview. Its anchor is the first city’s IANA zone and local weekday and time, not a fixed UTC offset.
From one selected start to 4, 8 or 12 meetings
Enter 2–8 cities, their same-day local work windows, a date and a 15–90 minute meeting length. Find windows and select the start you intend to use.
The weekly count includes the initial week. Four meetings means four rows, seven calendar days apart in the first city. The planner resolves each local date again using this browser’s time zone data. Duration stays real elapsed minutes.
New York and London: a recurring meeting time example
With America/New_York first, choose Monday 2026-10-19 at 09:00. Europe/London sees 14:00, 13:00, 14:00 and 14:00 over four weeks because the two places change clocks in different weeks.
Set London’s work window to 14:00–16:00 and the meeting length to 90 minutes. The second week fails the complete-window check even though New York keeps 09:00. Read every participant’s local dates, both interval ends and offset change relative to the first meeting.
Missing or repeated local times stay visible
New York Sundays at 02:30, starting 2026-03-01: the 2026-03-08 time does not exist. Sundays at 01:30, starting 2026-10-25: 2026-11-01 happens twice. Those rows say adjustment is needed and contain no determined meeting time or passing work-window result.
The preview never shifts a missing time, chooses the earlier or later repeated time, or skips a bad week to add another one. Later weeks still compute; a four-meeting preview always keeps four rows. Dates beyond years 0001–9999 are reported rather than rolled into another year.
A work-window check covers the entire meeting
Every elapsed minute is checked against each person’s local work window. Checking only the start can hide an overrun; checking just the two ends can miss a fall-back interval that briefly leaves a window.
These are daily hours you enter, not personal calendar free/busy, holidays or weekend rules. Overnight or split work windows are not supported. Quarter-hour offsets such as Kathmandu and half-hour clock changes such as Lord Howe are handled at minute precision.
Share a reusable team; ICS remains one meeting
The new fragment link restores the team, an eligible chosen start and the preview count. An invalid or stale selection returns to an unselected state with a visible warning. Changing planner inputs clears the old selection and preview, so choose again before exporting.
Copy weekly preview gives a text report. Download .ics exports only the selected single meeting in UTC; it does not generate RRULE, recurring invitations or calendar updates. Imported events and participants’ calendar recurrence settings are your responsibility.
Recheck when time zone rules change
Governments and software updates can change time zone rules. Results use the data available to this browser; confirm with participants before each meeting. This tool does not promise permanently correct future rules or automatic updates to another calendar.
Technical background: W3C’s Working with Time Zones explains wall time and changing rules; its distributed-meeting guidance discusses scheduling across time zones. Links below are references, not a guarantee of calendar-app behavior.