How daylight saving breaks recurring meetings (and how to prevent it)

Forecast clock changes, adjust invites ahead of time, and spare teams from “why is this suddenly at 6am?” surprises.

Build a DST calendar for every recurring invite

Feed every participant’s city into the DST Planner. The tool lists upcoming transitions so you know exactly which weeks stretch or shrink overlap. Add those dates to the meeting description with plain-language notes (“Week of 24 March: UK moves forward, call shifts to 07:00 ET”). Pair it with the Timezone planner when you want to show the before/after grid.

Example: Product ops between Austin, London, Cape Town

Austin (Central) jumps forward in March, London shifts later, and Cape Town stays on UTC+2 all year. The DST Planner shows a two-week span where Austin and London move on different Sundays. That means a 10:00 Austin call becomes 16:00 London / 18:00 Cape Town for one week, then 15:00 London after UK DST. Document the temporary slot and pre-approve a one-off async update so nobody is surprised.

Example: Customer success between São Paulo, Chicago, Madrid

Brazil leaves DST entirely, while Chicago and Madrid both shift. The planner reveals October weeks where Chicago is only one hour behind São Paulo instead of two, and March weeks where Madrid jumps ahead first. Flag those dates in advance and rotate who absorbs the late-night slot. When Chicago springs forward, move the meeting 30 minutes earlier locally so Brazil stays in daylight hours.

DST safety checklist

FAQ

How far ahead should I warn people?
Two weeks is considerate. Put the warning in the calendar description plus a chat reminder a few days prior.
What if nobody on the call changes clocks?
Still check. Vendors or rotating guests might, and you may add new members later.
Can I lock meetings to one region’s time?
You can, but it usually shifts pain to others. Use the DST Planner to rotate inconvenience instead.

Need to prep another invite? Keep the DST Planner open.