Checking calendar imports

Know which export you downloaded

A single-meeting ICS contains one reviewed event. A recurring export contains the resolved occurrences in the twelve-date preview as separate events. Explicitly skipped occurrences reduce that count. The file does not create an unlimited series, connect to an account, or invite attendees.

Use a small, concrete check

Start with the expected number of events and a known example. For 27 October 2026, the New York 09:00–10:30 meeting corresponds to 13:00–14:30 UTC, 13:00–14:30 London, and 14:00–15:30 Berlin. All of these rows describe the same ninety-minute event.

Open the imported event and compare its date, duration, and display zone. A calendar configured for Sydney will show 00:00–01:30 on 28 October for that example. A different local hour or date can therefore be correct. Check the instant and zone context before changing the imported time.

Inspect both sides of a clock change

For the New York-anchored Tuesday series, compare 27 October and 3 November 2026. New York stays at 09:00; London changes from 13:00 to 14:00. If both imported London events show the same hour, investigate the selected anchor and the file you imported.

If a repeated local time was involved, compare the chosen numeric offset. New York’s earlier 01:30 on 1 November corresponds to 05:30 UTC, while the later one corresponds to 06:30 UTC. The wall-clock text alone cannot distinguish the two imports.

Be careful with a second import

Calendar applications differ in how they handle an event that appears again. Some may recognize an identifier, while others may create a duplicate or offer a choice. Inspect the destination calendar before importing an updated file. Remove or replace old entries using that application’s own controls; HourBraid does not reach into earlier imports.

Keep the file and the editable plan

An ICS file is useful evidence of what was exported. A project JSON file preserves the planner settings that produced it. Keep both when a schedule matters. If an import fails, retain the original error message, calendar application name, selected cities, date, and data version, while leaving private meeting notes out of any report.