The short version. A calendar event is tied to a time zone, usually the organizer’s. What happens on Nov 1 depends on that time zone, not on where you are.
- Organized in BC, Alberta, Manitoba or the NWT using the old time zone: these will be an hour off from Nov 1 until the organizer updates them. Google fixes most of them automatically. Outlook doesn’t.
- Organized anywhere else (Toronto, Seattle, New York): nothing breaks. The meeting stays put in the organizer’s time, but it will land an hour later for people in BC, Alberta and Manitoba from November to March. That’s correct.
- If you were invited: you can’t fix it. Only the organizer can.
Why some meetings show an hour late and others don’t
When you book a meeting, your calendar saves it as “10:00 AM in this time zone”. It doesn’t save “10:00 AM in Vancouver forever”. The time zone is whatever the organizer’s calendar was set to when they booked it.
Until this year, Vancouver, Seattle and Los Angeles all shared one time zone in most calendars: Pacific Time. On Nov 1, 2026 that stops being true. Seattle and LA fall back to UTC−8. BC stays at UTC−7. So a meeting saved in the old “Pacific Time (US & Canada)” time zone will follow Seattle back an hour, and land an hour late for anyone actually in BC. The same goes for Alberta with Mountain Time and Manitoba with Central Time.
The fix is to change the meeting to the new time zone for that province, which Microsoft, Google and Apple have added this fall.
Who has to do what
| The meeting was organized… | What happens from Nov 1 | What to do |
|---|---|---|
| In BC, Alberta, Manitoba or the NWT, before the calendar knew about the change | Lands an hour later than intended, for everyone. In that province it shows an hour late; elsewhere it stays where it was before Nov 1, when it should have moved. | The organizer changes the meeting’s time zone to the new one and sends the update. |
| In BC, Alberta, Manitoba or the NWT, after updating to the new time zone | Correct. | Nothing. |
| In a place that still changes clocks (Ontario, Quebec, the US…) | Correct. It stays at the same time for the organizer and moves an hour later for people in BC, Alberta and Manitoba. | Nothing, unless the time no longer suits. Then the organizer moves it. |
| In Saskatchewan or Yukon | Correct. Nothing changes. | Nothing. |
An example: a weekly Vancouver–Toronto call
Say there’s a weekly call at 10:00 AM Vancouver time, which has been 1:00 PM in Toronto all summer.
| Who organized it | Vancouver, from Nov 1 | Toronto, from Nov 1 |
|---|---|---|
| Vancouver organizer, old Pacific time zone, not updated | 11:00 AM (wrong) | 1:00 PM |
| Vancouver organizer, updated to the new BC time zone | 10:00 AM | 12:00 PM |
| Toronto organizer, booked at 1:00 PM Eastern | 11:00 AM (correct) | 1:00 PM |
Notice that fixing the Vancouver organizer’s meeting moves it in Toronto. That’s the point: BC and Ontario are now 2 hours apart in winter instead of 3. Someone’s meeting has to move. Which one depends on who booked it. You can check any pair with the Vancouver to Toronto converter or find a new slot with the meeting planner.
Fixing BC and Alberta meetings in Outlook and Microsoft 365
The new Outlook time zones: Pacific Time (British Columbia), Mountain Time (Alberta) and Manitoba
Microsoft has added three new time zones: (UTC-07:00) Pacific Time (British Columbia), (UTC-06:00) Mountain Time (Alberta) and (UTC-05:00) Manitoba. Windows got them in the September preview update and the October 13, 2026 security update. If you’re in BC’s East Kootenay (Cranbrook, Fernie), pick Mountain Time (Alberta).
How to fix recurring meetings in Outlook
Existing meetings do not switch over automatically. Microsoft’s instructions, in short:
- Install Windows updates and restart, then set your calendar time zone to the new one. In Outlook on the web and new Outlook it’s under Settings › Calendar › View › Time zones. Classic Outlook for Windows follows the Windows time zone.
- For each meeting you organized on or after Nov 1, open it (choose Edit series for a recurring one), click the time zone globe, pick the new time zone and send the update.
- Check the series afterwards. Changing a series’ time zone resets any instances you’d moved or edited, so you’ll need to redo them.
Outlook meetings still showing an hour late?
Things to watch for:
- Only the organizer can make the change. Attendees get the updated invitation automatically.
- New Outlook for Mac and Outlook for iOS. Users have reported these showing BC and Alberta meetings an hour late after Nov 1, even when other Outlook apps show them correctly. Microsoft hadn’t posted a fix at the time of writing. Several BC universities are telling staff to make their changes in Outlook on the web.
- Room bookings. When a meeting moves an hour, the room may already be booked, and the room can decline it. Check after updating.
- Don’t change your computer’s time zone by hand to make one meeting look right. It throws off everything else.
Google Calendar and the BC time zone change
Google is doing most of the work itself. It says that in October 2026 it will “automatically shift most of the affected events back by one hour”. An event counts as affected if it’s on or after Nov 1, uses an affected Canadian time zone, and was created before Google updated that zone:
| Region | Affected if created before |
|---|---|
| British Columbia | July 20, 2026 |
| Alberta and the NWT (Yellowknife) | September 8, 2026 |
| NWT (Inuvik) | September 28, 2026 |
| Manitoba (and Rainy River, Ontario) | mid-October 2026 |
What Google won’t fix automatically:
- Recurring events with edited instances, such as one week moved, a different room or a custom description. Those have to be fixed instance by instance.
- Invitations that came from Outlook users.
Google Calendar on the web shows a banner on affected events with two buttons: Move one hour earlier or Keep current time. The phone apps don’t show it, so do this on a computer. Google also asks Workspace admins not to run bulk-fix scripts, which it says can corrupt calendar data.
Apple Calendar on iPhone and Mac
We couldn’t find a public Apple support article about meetings and this change. Apple ships time zone updates with iOS and macOS, and sometimes over the air, so devices can differ until they’ve all been updated. UBC’s IT team reports that current macOS and iOS already use the new BC rules and show the time zone by city, Vancouver for example.
What that means in practice:
- Update iOS and macOS, and make sure the time zone is set automatically or set to your city. Check your device here.
- Apple Calendar shows whatever your calendar service sends it. If the meeting lives in Outlook or Google, fix it there and Apple Calendar will follow.
- For iCloud calendar events you created yourself before the update, open a few repeating events after Nov 1 and check the time.
A checklist for the week before Nov 1
- Update your phone and computer, and restart.
- Set your calendar to the new time zone for your province.
- List the recurring meetings you organize that continue past Nov 1, starting with any that include people outside your province.
- Update each one’s time zone and send the update, or end the series on Oct 31 and start a new one.
- Check room bookings and any instances you’d edited.
- On Monday, Nov 2, check your first few meetings against the time zone converter. If one is off and you didn’t organize it, tell the organizer.
Questions
Do I need to update meetings I was invited to?
No. Only the organizer can change a meeting’s time zone. If a meeting you were invited to looks wrong after Nov 1, tell the organizer. Don’t move it on your own calendar.
Will Google Calendar fix my meetings automatically?
Mostly. Google says it is automatically moving most affected events in October 2026, including recurring events with no edited instances. Recurring events with edited instances, and invitations that came from Outlook, have to be fixed by hand.
Why are my Outlook meetings showing an hour late after Nov 1?
The meeting is probably still saved in the old “Pacific Time (US & Canada)” or “Mountain Time (US & Canada)” time zone, which falls back on Nov 1 while BC and Alberta don’t. The organizer needs to change it to Pacific Time (British Columbia) or Mountain Time (Alberta). If it’s already been changed and still looks wrong, you may be using new Outlook for Mac or Outlook for iOS, which some people report showing these meetings an hour late. Check in Outlook on the web.
Will Outlook fix my meetings automatically?
No. Microsoft’s instructions are for the organizer to open each meeting or series, change its time zone to the new one (for example “(UTC-07:00) Pacific Time (British Columbia)”) and send the update.
My weekly call with Seattle moved an hour. Is that a bug?
No. From November to March, Seattle is on UTC−8 and Vancouver stays on UTC−7, so a 10 AM Seattle meeting is now 11 AM in Vancouver. If you want it at 10 AM Vancouver time, the organizer needs to move it to 9 AM Seattle time.
Should I end my recurring series and start a new one?
It’s the cleanest option if the series has lots of edited or cancelled instances. Changing a series’ time zone resets those edits. UBC’s IT team suggests ending the series on Oct 31 and starting a fresh one on Nov 1.
Does this affect meetings in Saskatchewan or Yukon?
No. They already stayed on one time all year, so nothing changes for meetings set in those time zones.
Sources
- Microsoft Support: Outlook time zone changes for Alberta and British Columbia
- Microsoft Tech Community: British Columbia 2026 time zone update available now
- Microsoft 365 message center MC1479468: Interim time zone guidance for Alberta and British Columbia
- Microsoft Q&A: New Outlook and Outlook Mobile incorrectly display British Columbia meetings
- Google Workspace Admin Help: Manage Canadian daylight saving time changes for Calendar
- UBC IT: BC time zone change, what it means for your calendar and devices
- University of Victoria: BC time zone change may affect calendar meetings
- University of the Fraser Valley IT: BC time-zone change may affect Outlook calendar meetings
Something out of date? Email [email protected] and we’ll fix it. See our corrections log.