Alberta Time: What the November 1 Change Means for Your Calendar

Open your calendar and scroll ahead to December. If one of your recurring meetings is sitting an hour later than you know it was booked for, nothing is broken on your end. You are looking at the first visible symptom of Alberta's move to permanent Alberta Time.

On November 1, 2026, Alberta stops falling back. The clock change is over. That is good news for anyone who has spent twenty years resetting the microwave twice a year, and it is a genuinely welcome simplification for businesses that work across provincial lines. But a change this fundamental has to ripple through every operating system, cloud platform, and scheduling tool your business touches, and those systems are not all updating on the same day.

For a few weeks, that gap between updated and not-yet-updated systems is going to make some meetings look wrong. We would rather you understand what you are seeing now than discover it when you miss a client call in December. Here is what changed, why your calendar is showing what it is showing, and what to check before November.

What Alberta actually changed

Alberta has adopted permanent Alberta Time, officially abbreviated ABT. It is the same offset the province has been on all summer, previously called Mountain Daylight Time. The Government of Alberta confirms that beginning in November 2026, clocks no longer reset to Mountain Standard Time and the province stays on Alberta Time year-round, which is equivalent to UTC-6.

Alberta is not doing this alone. British Columbia locked in permanent daylight time when residents moved their clocks forward in March 2026, and the Northwest Territories has moved to align with Alberta. What used to be a tidy line of Mountain Time provinces is now a patchwork, and the mental shortcut most of us carry around about who is an hour ahead of whom is about to stop working.

💡  The practical shorthand: after November 1, Alberta is on the same time as Saskatchewan all year, and one hour ahead of British Columbia all year. Neither of those relationships changes again.

Why your calendar is showing the wrong time

Every device and cloud service carries its own internal rulebook of the world's time zones. When a government changes the rules, each vendor has to publish an updated rulebook, and they do not all publish on the same day.

Think of it like two people holding two editions of the same recipe book. As long as the recipe hasn't changed, both produce the same cake. The moment one edition gets revised, the two cooks quietly diverge, and neither of them knows it.

That is what is happening to your meetings. A calendar entry is not really stored as "3:30 on a Wednesday." It is stored as a precise moment in universal time, with a time zone attached, and each device does the arithmetic to display it in local terms. If the system that filed the meeting is still using the old rulebook, and the phone or laptop displaying it has the new one, the two calculations land an hour apart. The meeting itself is fine. The translation of it is not.

📋  The updated rules reached the internet's master time zone database in July 2026, and Microsoft is rolling the change into Windows through the September and October 2026 updates. Anything that has received both is correct. Anything that has received one is where the trouble lives.

The tell: everything looks fine until November 1

This is the single most useful thing to know, because it turns a confusing symptom into an obvious diagnosis.

Scroll back to a week in October. If those meetings look correct, and then everything from November 1 onward is exactly one hour late, you have found it. Before November 1 the old rulebook and the new one produce the same answer, so nothing looks wrong. The cutover date is where they part company, and the error appears the instant you cross it.

A second confirmation takes about thirty seconds. Open the same meeting in two places, for example on your laptop and in Outlook on the web. If the two disagree by an hour, you have a mismatch between an updated system and one that is still waiting.

✅  Check this now rather than in late October. Finding it in September gives you seven weeks to sort it out quietly. Finding it on November 2 means sorting it out while meetings are already going sideways.

Where Alberta sits after November 1

Worth printing and sticking on a wall if your team books across borders. The column that surprises people most is the last row, because Alberta and Denver have always moved in lockstep and no longer will.

What to check, and roughly when

Not everything on this list carries the same weight. The top two rows affect whether your team shows up to meetings. The bottom rows affect whether systems you never think about keep running on schedule.

⚠  If a device cannot be updated before November, a fixed offset can be set as a short-term patch. Microsoft is clear that these are temporary only, because they carry different names, geography, and history behind the scenes. Treat it as a bridge to the real update, never as the fix.

The one thing not to do

When a meeting displays an hour late, the instinct is to drag it back an hour so it looks right. Please don't.

The underlying appointment is correct and consistent for everyone attending. Moving it fixes your screen and breaks everyone else's, and it does so invisibly, because the other attendees have no reason to re-check a meeting that was already on their calendar. A display problem you can explain is far better than a data problem nobody notices until the room is empty.

🚨  Manually shifting a shared meeting rewrites it for every attendee. If something looks wrong, report it and let it be diagnosed properly. Do not correct it by hand.

Calendars are the visible part, not the whole of it

Meetings are where you notice a time zone problem. They are rarely where it costs you the most. Anything in your business that runs on a wall-clock time depends on the same rulebook, and those systems fail silently.

• Overnight backups. A job set for 11:00 p.m. that drifts to midnight can collide with maintenance windows or run into business hours.
• After-hours phone routing. Calls route to the on-call path an hour early, or keep ringing the front desk an hour after everyone has left.
• Door access and alarm schedules. Doors unlock or arm an hour off, which is a safety and insurance question, not just an inconvenience.
• Payroll cutoffs and time tracking. Shift boundaries land in the wrong hour, and the error only surfaces at the next pay run.
• Automated reports and data feeds. Daily numbers quietly cover the wrong window, which is difficult to unwind after the fact.

None of these announce themselves. The first week of November is worth a deliberate look at anything scheduled, rather than waiting for someone to notice the numbers are off in December.

Common questions

Do I need to do anything on November 1 itself?

No. There is no clock to change, which is the whole point. Your devices will simply carry on at the same offset. The work is in making sure they have the updated rules before that date, not in doing anything on the day.

Will this affect meetings I have with people outside Alberta?

Those are exactly the ones to watch. A meeting between two Alberta colleagues on two updated laptops will be fine. A meeting between you and a supplier in Denver or Toronto involves more systems, and only one of them has to be behind for the time to land wrong for one side. For anything important in November and December, a short note confirming the time is cheap insurance.

Why does my calendar say MST, MDT, CST, or ABT depending on where I look?

Three-letter abbreviations are labels, not reliable identifiers. Different systems have picked different labels for the same offset, and some will show CST because Alberta now matches Saskatchewan. The offset is what matters. If it says UTC-6, it is correct regardless of the letters next to it.

My software vendor hasn't mentioned this. Should I be concerned?

Ask them. Large platforms generally handle time zone updates well and quietly. Smaller and older applications, especially anything that schedules work or stamps records with a local time, are the ones that tend to be caught out. A direct question in writing now is much easier than troubleshooting in November.

Is this related to the American push to end clock changes?

Separate things. Alberta's decision is provincial and is already law. Proposals in the United States are still moving through their own process and would not change what happens here. Plan around the Alberta date.

Not sure whether your systems are ready for November 1? Always Beyond audits device and server patch levels, verifies scheduled jobs and after-hours routing against the new Alberta Time rules, and works through the vendor list with you so nothing is left assuming. Reach out to start the conversation.