Several Canadian provinces and territories recently decided to stay on daylight saving time permanently. As a result, clocks in these regions won't fall back by one hour on November 1, 2026.
This change impacts certain events in Google Calendar. As an administrator, you can help users in your organization prepare for these changes and understand how Google updates their calendars.
How calendar events are affected
Any calendar event that meets all of the following conditions will appear on the calendar grid one hour later than originally scheduled starting November 1, 2026:
- The event occurs on or after November 1, 2026.
- The event uses one of the affected Canadian time zones.
- The event was created before Google updated the time zone definitions for that region (varying by province, as shown in the table below).
For example, if a user scheduled a meeting for 9:00 AM, it might show on the calendar at 10:00 AM.
Affected time zones
The following time zones are changing to permanent daylight saving time:
| Province / Territory | Affected time zone IDs | New permanent offset | Which events are affected? |
|---|---|---|---|
| British Columbia | America/Vancouver Canada/Pacific |
Permanent UTC-07:00 | Post-November 1 events created before July 20, 2026 |
| Alberta & NWT (Yellowknife) |
America/Edmonton America/Yellowknife Canada/Mountain |
Permanent UTC-06:00 | Post-November 1 events created before September 8, 2026 |
| Northwest Territories (Inuvik) | America/Inuvik | Permanent UTC-06:00 | Post-November 1 events created before September 28, 2026 |
| Manitoba | America/Winnipeg Canada/Central America/Rainy_River |
Permanent UTC-05:00 | Post-November 1 events created before mid October, 2026 |
How Google is updating events
In October 2026, Google will automatically shift most of the 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
Google won't automatically update all affected events, including invitations from Outlook users. This protects your users from losing event information.
To help users fix these events, Google Calendar on the web will highlight affected events with a warning banner. Users can click Move one hour earlier on the banner to quickly fix the time, or click Keep current time to dismiss the warning.
What you can do
As an administrator, you can share the following best practices with your organization:
- Don't run custom scripts: Don't run your own domain-wide scripts or use third-party bulk-remediation tools to shift these events. If you run automated client-side scripts, this might corrupt calendar data.
Encourage users to use Google Calendar on the web to identify affected events: Google only shows the in-product warning banners and one-click fixes on the web version of Calendar. Users might temporarily see incorrect times on mobile devices or third-party apps until those devices update their local time zone databases. You can encourage users to update their mobile operating system (OS) or third-party software to use the latest version.
Manually update complex events: For recurring events with custom exceptions, users should manually adjust each instance. Learn more about manually adjusting recurring events.
Manage room bookings
As a result of these changes, room conflicts are likely to occur when meetings shift. For instance, if Team A booked a room in May 2026 for 9:00 AM on November 4, 2026 before time zone definitions updated, the booking currently displays 10:00 AM. If Team B then booked the same room for 9:00 AM using updated time zone definitions, moving Team A's meeting back to 9:00 AM could cause the room to decline the shifted event. Organizers will receive an email once a room declines an event and should always verify room availability after shifting meetings.