Published July 2026 · 5 min read
You've been in that meeting every Tuesday at 10 AM for months. Then one week in March, half your team shows up an hour late. Or worse — an hour early. Nobody sent a memo. Nobody changed the invite. Daylight Saving Time just quietly rewrote your schedule while nobody was looking.
Recurring meetings and DST transitions are natural enemies. They collide twice a year, every year, and the damage is quietly expensive: confused attendees, missed handoffs, and the slow erosion of trust in calendar invites. According to research, DST-related productivity losses and health care costs run an estimated $411 billion annually in the United States alone. A chunk of that comes from scheduling chaos that's entirely preventable.
Here's how to make your recurring meetings DST-proof.
Why recurring meetings break during DST
The core problem is deceptively simple: DST doesn't happen on the same date everywhere. In 2026, the United States and Canada "spring forward" on March 8. Most of Europe waits until March 29 — a three-week gap. In the fall, the US "falls back" on November 1, while Europe changes on October 25 — a one-week gap in the opposite direction.
Only 71 countries observe DST at all. The rest of the world — including most of Asia, Africa, and South America — stays on standard time year-round. When your team spans DST-observing and non-observing regions, those three weeks in March create a moving target that no static calendar invite can handle.
Consider a recurring weekly meeting anchored to 3 PM Paris time. For most of the year, your New York colleague joins at 9 AM. But during that three-week window between March 8 and March 29, New York has already sprung forward while Paris hasn't — so the meeting suddenly starts at 10 AM in New York. Then on March 29, Paris springs forward too, and the meeting snaps back to 9 AM New York time. The invite never changed. The math did.
The "lead time zone" concept
Most calendar applications handle DST by anchoring recurring events to a single time zone — what Teamup calls the "lead time zone." When you create a recurring meeting in Google Calendar or Outlook, the event stores one canonical time zone. All DST adjustments for that event flow from that anchor.
This means the choice of lead time zone determines whose local time stays fixed and whose shifts. If you anchor to Paris, Paris always sees 3 PM, and New York bounces between 9 AM and 10 AM. If you anchor to New York, New York always sees 9 AM, and Paris bounces between 2 PM and 3 PM. There's no right answer — but there is a wrong one: not picking one deliberately, and letting the calendar software guess.
Concrete strategies that work
1. Anchor to the organizer's time zone
The simplest rule: whoever runs the meeting picks the lead time zone. If you're the host and you're in London, the meeting anchors to London time. Everyone else adjusts. This is predictable, transparent, and avoids the confusion of a floating anchor nobody can name.
2. Audit recurring meetings one week before each DST transition
Set a recurring calendar reminder (ironic, but effective) for the first week of March and the last week of October. Review every recurring meeting on your calendar and confirm: who is the anchor? Will any attendees see a time shift? Send a one-line note to affected participants. Doodle's help center recommends exactly this: "review your recurring meetings in advance of any upcoming DST changes."
3. Use UTC as the universal anchor for fully distributed teams
If your team spans five or more time zones with no clear geographic center, consider anchoring recurring meetings to UTC. UTC never observes DST. Everyone's local time may shift twice a year, but the UTC anchor never moves. The downside: you need a team that's comfortable thinking in UTC, and someone has to do the local-time math each season.
4. Communicate the shift — don't assume the calendar handles it
Calendar software is better than it used to be. Google Calendar, Outlook, and Apple Calendar all handle single-timezone DST correctly when configured properly. But the moment attendees cross DST boundaries with mismatched transition dates, the invite alone isn't enough. A five-word Slack message — "Meeting shifted an hour for you" — prevents more confusion than any software feature.
5. Use a visual time zone planner for the transition weeks
For the two or three weeks surrounding each DST transition, don't trust the calendar invite alone. Drop your team's cities into a visual time zone meeting planner and verify that the overlap window still works. You might discover that your carefully-negotiated 9 AM San Francisco / 5 PM London slot disappears for three weeks in March because one side jumped and the other didn't.
The tools that make this easier
Not all calendar tools handle DST equally well. Here's what to look for:
- Manual lead time zone selection — the ability to explicitly set which time zone anchors a recurring event, rather than letting the software infer it from your current location.
- Automatic DST-aware time conversion — tools like Doodle and AddEvent automatically detect each participant's time zone and apply DST rules, so everyone sees their correct local time even across transition dates.
- Visual overlap checking — a time zone meeting planner that shows working hours as visual bars makes it obvious when DST shifts eat into your overlap window.
- DST transition warnings — some planners proactively flag upcoming DST changes within a 30-day window, so you see the problem before it becomes a missed meeting.
The bottom line
DST transitions aren't going away — at least not soon. The EU has debated abolishing DST since 2018. The US passed the Sunshine Protection Act in the Senate in 2022, but it stalled. For the foreseeable future, your recurring meetings will face two scheduling earthquakes per year.
The fix isn't complex. Pick a lead time zone deliberately. Audit your calendar before each transition. Send a quick heads-up to anyone whose meeting time shifts. And when in doubt, use a visual planner to verify overlap windows during the transition weeks. A few minutes of checking twice a year beats the slow grind of scheduling confusion and the quiet productivity tax it imposes on every distributed team.
Planning a meeting across time zones? Don't let DST catch you off guard. Try the Time Zone Meeting Planner →