Recurring meetings
Anchor one local time. Review every other city.
Choose the city that controls the schedule
A weekly plan starts with an anchor city and its local weekday and clock time. “Tuesday at 09:00 in New York” follows the New York rule set. It does not mean a fixed UTC time, nor does it promise that every other city will keep the same local hour.
Inspect all twelve occurrences
The preview resolves the anchor instruction separately for each week. Compare every city’s local date, start, end, and availability. For the example beginning on 27 October 2026, New York remains at 09:00 on Tuesdays while London changes from 13:00 to 14:00 in the second row.
Handle an unusual occurrence explicitly
If a local time repeats, choose the earlier or later instance and review the resulting offset. If it does not exist, correct the time or explicitly skip that occurrence. An unresolved row prevents a calendar export; the planner does not silently move the meeting to a different wall time.
Export the dates you reviewed
The calendar download contains separate events for the resolved preview dates. It is not an unlimited recurring series. A skipped occurrence reduces the event count. Check that count and an event on each side of a clock change after importing the file into your calendar.
Revisit the plan when circumstances change
Keep a JSON project backup to preserve the editable settings. New availability, a different anchor, or updated time-zone rules calls for a new preview. The site does not update earlier calendar imports or send notices to participants.