Review the next 12 meetings

Set the anchor instruction

Choose the anchor city, a starting date, the weekly weekday, local start time, and duration. The first occurrence is on the chosen weekday on or after the starting date. The preview contains twelve weekly occurrences, each resolved in the anchor’s named zone.

Read every city’s row

The anchor’s local weekday and time remain the instruction. Other cities can change their local hour or date when their offset relationship changes. The preview identifies changes so you can inspect them, but you should also compare each occurrence’s end time and availability.

Try the New York Tuesday example

Use New York at 09:00 on Tuesdays, starting 27 October 2026. London reads 13:00 on the first date and 14:00 on 3 November. Berlin moves from 14:00 to 15:00. The New York clock stays at 09:00; a later offset change creates the different local displays elsewhere.

Resolve or skip exceptional rows

A repeated local time needs an earlier-or-later instance. A missing local time needs a valid replacement or an explicit skip. You can apply the selected policy and inspect per-occurrence choices. A corrected row may no longer match the usual clock time, so review it as an intentional exception.

Check the end of the supported range

All preview dates must be within 2026–2035. A starting date near the end of 2035 can leave later occurrences out of range. Those rows are not silently extrapolated or exported. Choose a supported starting period for a complete twelve-week review.

Export the reviewed set

The file contains separate events for resolved, unskipped rows. It does not create an indefinite calendar recurrence rule. Confirm the ready and skipped counts, download the file, and check the import on both sides of a clock change. Keep a project JSON backup for later edits; existing calendar imports are not updated automatically.