The week the gap changes
Suppose your team meets every Tuesday at 09:00 in New York. On 27 October 2026, that is 13:00 in London and 14:00 in Berlin. One week later, New York still reads 09:00, but London reads 14:00 and Berlin reads 15:00.
The meeting has not moved on the New York clock. The clocks in these places changed on different dates. The UK returned to standard time on 25 October; New York follows on 1 November. During the intervening week, the gap between New York and London is four hours. After the US change, it returns to five hours.
| Meeting date | New York · anchor | London | Berlin |
|---|---|---|---|
| 27 October 2026 | 09:00 | 13:00 | 14:00 |
| 3 November 2026 | 09:00 | 14:00 | 15:00 |
Tuesday, October 27, 2026
- New York
- 09:00
- London
- 13:00
- Berlin
- 14:00
Tuesday, November 3, 2026
- New York
- 09:00
- London
- 14:00
- Berlin
- 15:00
All times in a row describe the same moment. The rows are separate weekly meetings.
Choose a city to anchor
Before creating a recurring meeting, decide which place should keep the same weekday and clock time. That is the anchor city. In this example, the instruction is “Tuesday at 09:00 in New York.” The named city supplies the date-specific rules each week.
An anchor is a planning choice. It does not make that city’s working day more important than everyone else’s. If London needs the stable slot, choose London and review what happens to New York. Tell the group which city controls the recurring time so that an expected change does not look like a mistake.
Review the next meetings
Look through all twelve dates in the recurring preview. Compare each city’s local date as well as its hour. A meeting close to midnight may land on the next day elsewhere. A slot that suited everyone last week may also move outside someone’s working hours after a clock change.
Check the full duration. A meeting that starts inside a shared window is still unsuitable if it ends after someone’s availability. Decide whether to shorten it, change the start, or discuss an exception. The planner shows the constraint; the people involved decide what is fair.
Handle unusual local times
A clock change can make a local time occur twice or not at all. For example, 01:30 in New York occurs twice on 1 November 2026, once at UTC−04:00 and again at UTC−05:00. These are different moments, one hour apart.
Choose the earlier or later instance explicitly when a time repeats. If the time does not exist, pick a valid time or explicitly skip that occurrence. Keep the offset beside the choice so that the consequence remains visible.
Check the calendar import
HourBraid’s recurring export contains the reviewed meetings as individual calendar events. It does not connect to your calendar account or send invitations. Check the event count and compare one event before and one after the clock change in the calendar application you use.
If the schedule changes, review a new preview before importing again. Removing or replacing earlier imports depends on your calendar application. Keep a JSON copy of the plan if you want to return to its settings later.
Sources
Follow the original references for the rules and formats used in this guide.