The clocks aren't falling back this year. Your computers might anyway.

If you live in BC, Alberta, or Manitoba, November 1 is about to be a pretty boring Sunday. No fumbling with the microwave clock, no arguing about whether you gained or lost an hour. Your province has decided the time change is done.

Your computers haven't heard the news yet. That's where we come in.

What actually changed

BC's transition to a single year-round time began after the province sprang forward on March 8, 2026. That was the final time change, and clocks that would normally have turned back on November 1 will stay put. The province calls the new zone "Pacific time," fixed at UTC-7, matching the offset it already uses during daylight saving. One wrinkle: Cranbrook and other East Kootenay communities that follow Mountain time will keep switching between standard and daylight time, so if you have staff there, they're an exception.

Alberta followed in the spring. Under the new legislation, the province stays on UTC-6 year-round, branded "Alberta Time." The Northwest Territories announced it would also end seasonal clock changes and align with Alberta.

Manitoba is the newest arrival. Premier Kinew told 680 CJOB on September 17 that clocks will not revert to Standard Time on November 1, meaning Manitoba will stay on UTC-5 permanently. We're still waiting on the formal paperwork behind that announcement, and we'll update this post as it lands.

Saskatchewan and Yukon made the switch years ago. Ontario and everyone east of it still change clocks, at least for now.

Why this is an IT problem and not just a calendar problem

Your devices don't know what time it is because they're told. They know because they're given a set of rules: this region is UTC-8, except between the second Sunday in March and the first Sunday in November, when it's UTC-7. Those rules live in time zone databases baked into Windows, macOS, iOS, Android, Linux, your phone system, your cameras, your door controllers, and about half the applications you use every day.

On November 1 at 2:00 a.m., every one of those databases that hasn't been updated will do exactly what it was told to do: fall back an hour. The device's underlying clock (which runs on UTC) will still be perfectly correct. The display, the scheduling, and the "what time is it here" logic will be one hour behind everyone in the room.

The good news is that the time zone rules those devices are running today are still correct until November 1. There's nothing to fix yet. There's a lot to prepare.

Where the fixes stand

The master reference for the world's time zones is the IANA tz database, and it has been racing to keep up with Western Canada. The 2026b release in April was driven by BC's decision, and the maintainers noted it would likely cause downstream problems because the CLDR locale data couldn't handle the change as specified. Release 2026c in July added Alberta's permanent UTC-6, and 2026d covered the Northwest Territories. Manitoba is in none of them. Given the September 17 announcement, expect a 2026e, but it will take time to ripple into operating systems and applications, and November 1 is six weeks away.

On the Microsoft side, a Windows update introduces two new time zones: "(UTC-07:00) Pacific Time (British Columbia)" and "(UTC-06:00) Mountain Time (Alberta)", the latter covering Alberta and the affected Northwest Territories communities, including Yellowknife and Inuvik. Microsoft is shipping these as non-security updates, starting in September 2026 for Windows 11 and in October for other Windows versions. The update needs to be installed before the change takes effect on November 1. For devices that can't get patched in time, Microsoft's interim advice for Alberta is to temporarily switch to "(UTC-06:00) Saskatchewan" after the transition. Microsoft has no guidance for Manitoba yet.

Apple pushes time zone data through regular macOS and iOS updates, so current Apple devices will follow suit as Apple picks up the IANA releases. Linux servers get it through the tzdata package. Applications with their own embedded time zone tables (Java, some databases, ERP and payroll systems, VoIP platforms) each need their vendor to ship an update.

What can go wrong on November 1 if nothing is done

Calendars are the obvious one. Meetings will appear to shift by an hour for anyone whose device fell back, and recurring meetings with US colleagues will look right to one side and wrong to the other. Beyond that, we're watching for:

•       Backup jobs, patch windows, and maintenance schedules running an hour off from what you expect

•       Phone system auto-attendants opening and closing an hour late, sending daytime callers to the after-hours greeting

•       Door access schedules, alarm arming times, and thermostat programs drifting

•       Security camera footage timestamped an hour behind the wall clock, which matters if you ever need it as evidence

•       Time-clock and payroll systems recording the wrong hour

•       Log files that no longer line up across servers in different provinces, which makes troubleshooting slower

None of these are catastrophic. All of them are annoying, and several quietly cost you money for weeks before anyone notices.

What Campfire is doing for managed clients

We're treating this as a project, not a patch. Between now and November 1 we're:

1.     Tagging every managed device by province so we know exactly what's affected

2.     Confirming the September and October Windows updates land on every Windows 11 and Windows 10 device, and moving BC and Alberta devices to the new named time zones before the transition

3.     Preparing a fixed UTC-5 fallback for Manitoba devices in case an official Windows zone doesn't arrive in time

4.     Validating that servers, including domain controllers and hypervisor hosts, are on current time zone data, since virtual machines often inherit time from their host

5.     Reviewing every scheduled job in our management tools, plus backup schedules, to confirm they behave correctly after the change

6.     Auditing Microsoft 365 and Google Workspace settings that carry their own time zone: Teams and Google Voice business hours, Bookings, Outlook mailbox time zones, and shared calendars

7.     Building a list of line-of-business applications and network devices with embedded time zone data, and chasing each vendor for their fix or recommended fixed-offset workaround

A note on neighbours

The map looks different in winter now. Alberta lines up with Saskatchewan and Chicago all year. BC sits an hour ahead of Seattle from November to March. Manitoba matches Ontario and New York in winter, and stays an hour ahead of Saskatchewan year-round. If you have staff or clients across those borders, expect a few weeks of "wait, what time is it there?" and be patient with your scheduling links.

The bottom line

Your province gave you the gift of never touching a clock again. Your IT stack needs a little help accepting it. If you're a Campfire client, your Managed Services Advisor will share the specifics for your environment. If you're not, and you're reading this while looking nervously at a server rack, get in touch. We'd rather help you get ahead of November 1 than help you clean up after it.