Google Calendar has a new Help article, "Fix Calendar events for Canadian daylight saving time": https://support.google.com/calendar/answer/18712272
It documents a feature rolling out that will help users adjust events in timezones affected by this year's changes: In October 2026, Google Calendar will automatically shift most affected > events back by one hour to their original scheduled local times. This > automatic fix applies to: > > - Single events > - Recurring events that don’t have future exceptions, such as a single > rescheduled instance, a different room, or a custom description > > After the events move to their original times, your guests will need to > RSVP to your event again. Today I received an email about the update with the subject "[Action Advised] Review Google Calendar events scheduled after Nov 1, 2026", likely due to some test events using Canadian zones on my calendars. According to the email, the rollout began 7 October and the auto-corrections will occur "within the next few weeks". Affected events will receive an exclamation mark "warning badge", similar to when all attendees decline a shared meeting. Clicking into the details will present guidance text "Because of a change in how time zones are tracked, you may need to move this event one hour earlier and check its details" alongside "one-click fix" buttons to either shift the event (recommended) or leave it alone. For example, the Manitoba changes just made it into Google Calendar in the last day or so. If I make a new recurring event for 12:00 Winnipeg time now that the new rules have been ingested, it shows up (for me) at 13:00 EDT for the rest of October and 12:00 EST thereafter through the winter, consistent with Manitoba's adoption of year-round UTC−5. However, an older version of the event that I made before the new rules were ingested currently still shows at 13:00 ET on both sides of the change. The upcoming prompt will ask me whether to move the winter ones an hour earlier in order for them to keep the original 12:00 Winnipeg intent. As far as I'm aware, this is the only major web calendar vendor that has proactively reached out to affected accountholders and is taking an actual "notify, repair, verify" approach. Some list members may remember I've discussed before that user prompting is basically the only correct approach in cases like this, so it's good to see such a positive example here. -- Tim Parenti
