Why DST Breaks Your Recurring Meetings and How to Fix It
DST breaks recurring meetings because the calendar can stay the same while the real overlap moves underneath it. The fix is operational review, not blind trust in the old invite.
Recurring meetings break around DST because cities switch on different dates or not at all. The invite may still exist, but the practical overlap has changed, which is why the meeting suddenly feels wrong.
Direct Answer
Most recurring meetings do not fail because the calendar software is broken. They fail because the team never re-checks the pair after the offset moves.
The Repair Process
- Identify the city pair that matters.
- Check whether the cities switched together, separately, or not at all.
- Confirm the live overlap again.
- Republish the slot in UTC and local city time.
The Common Failure Modes
| Failure mode | What it looks like | Fix |
|---|---|---|
| One side moved first | Someone is now an hour early | Reapprove the slot during the gap |
| One side never moves | The recurring band feels permanently worse | Reset the invite and document the pair |
| Nobody reviewed the window | Attendance drops quietly | Review before every transition season |
Where To Check The Pair
Frequently Asked Questions
Why does the invite still look correct when the meeting feels wrong?
Because the invite can remain intact while the real local times drift.
Should every recurring cross-region meeting be reviewed before DST season?
Yes. If the meeting matters enough to recur, it matters enough to review.
What should teams publish after the fix?
Publish the final slot in UTC and the local city times people actually follow.