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

Treat clock shifts like an incident: forecast them, warn loudly, and move the invite before someone rage-quits.

Need the background story first? Read DST: Why It Breaks Meetings and come back here for the playbook.

Build a DST calendar for every recurring invite

Dump every attendee’s city into the DST Planner and screenshot the upcoming transitions. Those dates tell you exactly which weeks stretch or shrink overlap. Paste the critical ones into the invite description with blunt notes (“Week of 24 Mar: UK jumps ahead, call hits 07:00 ET”). Add a Timezone grid if you want to show before/after times in one image.

Example: Product ops between Austin, London, Cape Town

Austin (Central) springs forward before London, while Cape Town ignores DST. The planner shows a messy two-week span where Austin shifts a week earlier. Your 10:00 Austin call turns into 16:00 London / 18:00 Cape Town for a single week, then settles at 15:00 London once the UK changes. Log that awkward week in the invite and pre-authorize an async alternative so no one wakes up cranky.

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

Brazil ditched DST, Chicago still flips, and Madrid jumps ahead before both. DST Planner shows October weeks where Chicago is briefly one hour behind São Paulo instead of two, plus March weeks where Madrid races ahead. Flag both spans now, rotate who takes the late slot, and when Chicago springs forward, slide the invite 30 minutes earlier locally so Brazil doesn’t drift into midnight territory.

Playbook: keep recurring calls intact

  1. Copy every relevant transition from the DST Planner into your meeting runbook or doc.
  2. Update the invite description with plain “local time” notes (“Week of 24 Mar: London +1h, US unchanged”).
  3. One week out, send a reminder with a Timezone screenshot so people see the new rows.
  4. Rotate who eats the painful slot during transition weeks and note the rotation so it stays fair.
  5. When clocks settle, confirm the normal time and delete any temporary placeholder invites.

Try the tools

Related guides

FAQ

How far ahead should I warn people?
Two weeks gives folks time to rearrange childcare. Update the invite right away, then drop a chat ping a few days before.
What if nobody on the call changes clocks?
Check anyway. Vendors, exec drop-ins, or future teammates might, and you’ll look careless if they join at the wrong hour.
Can I lock meetings to one region’s time?
You can, but it just pushes pain elsewhere. Use the DST Planner to rotate who gets the bad shift so resentment doesn’t pile up in one timezone.

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