Daylight Saving Time & Meetings 2026: Survive Clock Changes Without Confusion

DST 2026 Dates by Region

The DST Gap Problem

The US shifts to DST 3 weeks before the EU does. For those 3 weeks (March 8-29 in 2026), the time difference between US and EU is one hour smaller than normal.

Practical impact: a recurring meeting set for "3pm ET / 8pm London" the rest of the year becomes "3pm ET / 7pm London" during the gap. If calendar invites use named timezones (which they should), the local time displays auto-adjust. If invites use fixed offsets, the meeting time displayed in one location is off by an hour.

The APAC Asymmetry Problem

Australia and New Zealand observe DST in opposite season because they're in the southern hemisphere. Their DST starts in October and ends in April.

Meanwhile, US-Australia time difference changes 4 times per year:

• March 8: US gains DST. US-Sydney offset shifts by 1 hour.
• April 4-5: Australia ends DST. US-Sydney offset shifts by 1 hour again.
• October 4: Australia gains DST. Another 1-hour shift.
• November 1: US ends DST. Final 1-hour shift.

Between these, the offset cycles through 14, 15, 16, and 17 hours. Recurring US-Australia meetings become a different relative time at different points in the year, not just by an hour in March, but by hours over different periods.

India ignores DST entirely. So a US-Bangalore meeting at "9am ET" becomes "6:30pm IST" most of the year but "7:30pm IST" during US DST gap periods. The India side feels the shifts even though India itself doesn't change clocks.

Named Timezones vs Fixed Offsets

The single most important technical detail: use named timezones (IANA database identifiers) rather than fixed UTC offsets.

In Google Calendar, when you create an event and click the timezone, you see "New York" or "London" or "Tokyo"; those are city-based names tied to the IANA database. Use those, not the UTC offset display.

Scheduling Around the DST Shift

For one-off meetings near the transition

• Re-confirm meeting time 2 days before the shift. "Reminder: meeting tomorrow at 10am ET, which is X in your timezone post-shift."
• Be explicit about which side of the shift in invite descriptions. "Note: US clocks shift on March 8. Meeting is on March 10 (post-shift). 10am ET = 2pm UTC."
• Watch for invites created before but happening after the shift. Modern calendars handle this, but older or migrated invites sometimes don't.

For recurring meetings spanning DST shifts

• Pick one anchor timezone for the recurring meeting (typically where the meeting "owner" lives). All other zones derive from it.
• Other participants accept that their local time shifts when the anchor shifts (and back).
• Send a heads-up 1 week before each DST change. "Meeting time changes next week from 4pm London to 3pm London because US doesn't shift to BST."
• Document the anchor in the calendar event description. "Anchored to NYC ET; other zones shift during local DST changes."

For new global teams setting expectations

• Pick an anchor with care. If most senior people are in the US, US anchor works. If APAC is largest population, anchor there.
• Document the DST behavior upfront. New hires should know that "their" meeting time shifts at certain dates and why.
• Schedule a couple of DST-around-the-shift simulations during the first month so the team learns to expect them.

Common DST Mistakes

• Sending recurring invites with fixed UTC offsets. The recurring instances on the other side of a DST shift display at the wrong local time.
• Saying "EST" or "PST" year-round. Those specifically mean standard time. During DST it's EDT/PDT. Better: "ET" or "PT" (which covers both) or "America/New_York" (unambiguous).
• Assuming everyone shifts together. India, China, most of Asia don't shift at all. Australia shifts in the opposite season.
• Updating only the meeting owner's invite. If you correct a DST error in your calendar but the other party still has the old invite, you'll show up at different times.
• Forgetting Mexico no longer observes DST. As of 2022, most of Mexico ended DST. Long-time US-Mexico schedulers may still operate on the old assumption.
• Trusting auto-conversion blindly during the DST gap. Calendars usually get it right, but in the 3-week US-EU gap, double-check by visualizing in a Meeting Planner.
• Booking flights for "post-shift" times without checking. A flight at "10pm" the night before DST falls back has an extra hour... or doesn't, depending on how the airline interprets it. Always check airline-published local time.

Planning a Year With DST in Mind

Key DST-related dates to put on your team calendar in advance:

Communicating DST Changes to Your Team

One week before a DST transition, send a Slack/email reminder:

Heads up: US DST starts this Sunday, March 8.

What changes:
· US clocks move forward 1 hour at 2am Sunday
· For 3 weeks (until March 29), US-EU time gap is 1 hour smaller than usual
· Our Tuesday 10am ET sync = 2pm London (instead of usual 3pm)

What stays the same:
· The meeting time itself (Tuesday 10am ET) doesn't change
· Calendar invites with named timezones auto-display correct local time
· If you see a weird-looking time on your calendar, refresh it

Need help: ping #team-ops

One sentence per important point. Visual contrast between what changes and what doesn't. Routine and predictable so people learn to expect these.

Tools That Handle DST Automatically

• Google Calendar: uses IANA timezones natively. DST transitions are seamless for events with proper timezone tags.
• Outlook (Microsoft 365): same story, named timezones handle DST automatically. Older Outlook clients sometimes lag on DST rule updates; keep clients updated.
• Apple Calendar: uses macOS / iOS timezone database; DST handling is automatic.
• Our Meeting Planner: shows DST-aware times based on the meeting date you select.
• Calendly / SavvyCal: auto-adjust availability windows for DST in both your timezone and the booker's.
• Server-side cron jobs: use UTC for cron schedules to avoid DST shifts. Display in local time for humans.

Will DST Be Abolished?

Several proposals exist:

• US Sunshine Protection Act: would make DST permanent (year-round summer time). Passed Senate 2022; stalled in House. Status unchanged in 2026.
• EU Directive on Seasonal Time Changes: EU Parliament voted in 2019 to end DST changes from 2021. Implementation stalled due to disagreement between countries about whether to settle on standard or daylight time. Status unchanged in 2026.
• Mexico ended DST in 2022. Most of country no longer shifts.
• Brazil ended DST in 2019.
• Various US state-level efforts: some states have passed laws making DST permanent contingent on federal approval (which hasn't come).

Until the laws actually change, plan as if DST will continue. The reform conversation has been happening for years without action.

Frequently Asked Questions