BC Clocks Won't Fall Back Nov 1: Check Your AI Bookings

If you've been planning a Sunday morning on November 1 to set the clocks back and fix your booking bot, here's the twist: in British Columbia, the clocks aren't falling back this year. Your software might still try to. That gap is what this 20-minute check is about.

What actually changes on November 1

On March 2, 2026, the province announced it was adopting permanent daylight saving time. The March 8 spring forward was the last change. Pacific time in BC now sits at UTC-7 all year, and the release says that on Nov. 1, 2026, when clocks would usually go back an hour, they stay put.

Across the border, things are different. According to NIST, US daylight saving time in 2026 runs until November 1 at 2 a.m. local time. So from that morning, a Burnaby shop is one hour ahead of Seattle, where customers used to be on the same clock.

For a front desk, nothing changes. Open at 9 still means 9. The risk lives in the software. Calendars, booking pages, phone systems and AI agents all lean on a shared time zone database, and the people who maintain it had to rush.

Why your tools might get it wrong

The IANA Time Zone Database release 2026b, published April 22, 2026, records that BC moved to permanent UTC-7. There's a catch, though: to work around a bug in Unicode CLDR, the database temporarily models the change as happening on November 1, 2026 at 02:00. It also starts labelling BC times as "MST". The tz NEWS file shows similar changes for Alberta (2026c), the Northwest Territories (2026d) and Manitoba (2026e, released September 29).

What that means in practice:

• Any phone, server or app still running older time zone data will think BC falls back on November 1 and show times an hour off.
• Your AI booking agent might tell a customer their 2 p.m. appointment is at "2 p.m. MST". That's technically right and very confusing for someone who has never heard Vancouver called Mountain time.
• If you run your own server, IANA notes that older versions of its zic compiler (2023d through 2026a) could build a file that makes readers ignore the November 1 transition entirely.

The big vendors have published guidance. Google's Workspace page says events on or after November 1 in an affected Canadian time zone, created before Google updated its definitions, will show one hour later than scheduled. Google says it will shift most of these back automatically in October 2026, but not invitations from Outlook users or recurring events with custom exceptions. Microsoft's Outlook guidance asks users to switch events to the new "(UTC-07:00) Pacific Time (British Columbia)" zone, and it warns that changing the zone on a recurring series resets any exceptions, so you have to recreate them.

The 20-minute check

Grab a coffee and a phone that isn't yours. Here's the order we'd use.

Minutes 0 to 5: book a test appointment. Open your website as a customer and book something for the week of November 2. Then check that it lands at the same clock time in your staff calendar, your confirmation email and your text reminder. If any of the three shows a different hour, write it down. That's your problem spot.

Minutes 5 to 10: ask the AI agent. If you have a chat or voice bot taking bookings, ask it plainly: "What time is it right now?" and "Can I book 10 a.m. on November 3?" Read the reply closely. Does it say PST, PDT or MST? Does the confirmation match the calendar? Large language models don't know the time on their own. A well built agent pulls the current time and time zone from your booking system, so if that system's data is stale, the bot will confidently repeat the wrong hour.

Minutes 10 to 15: check recurring events and reminders. Look at your weekly staff meetings, standing client appointments and any scheduled automations, like "send the reminder 24 hours before" or "post the daily specials at 11". Recurring series with moved instances are exactly the ones Google and Microsoft say may need a manual fix. If your team mixes Outlook and Google Calendar, check the cross invites by hand.

Minutes 15 to 20: review your Google Business Profile and public hours. Your regular hours stay the same, so don't touch them. While you're in there, though, Remembrance Day falls on November 11, and Google's Business Profile help suggests confirming holiday hours even when they match your usual ones. You can set special hours for short changes without editing your regular schedule. If you serve US customers, add a line to your site or booking page noting that you're on Pacific time (UTC-7), which is now an hour ahead of Seattle and Portland through the winter.

A simple example

Here's an illustrative case, not a real client. A New Westminster physio clinic uses an online booking page that syncs to Google Calendar, plus an AI assistant on its website that answers "do you have anything Tuesday?" A patient books a 9 a.m. slot for November 3 back in September. If the booking tool's time zone data predates the change, the clinic's calendar could show 10 a.m. while the patient's email still says 9. The clinic opens at 9, nobody's expecting the patient, and the AI assistant, reading the same calendar, tells the next caller that 9 a.m. is free. One booking gets doubled. That's the whole failure: not dramatic, just annoying, and avoidable with a test booking.

Where this doesn't apply

Be honest with yourself about how much of this you need.

If you take bookings by phone and keep a paper or whiteboard schedule, there's nothing to check beyond your posted holiday hours. Adding an AI tool now, in October, just to "be ready" would add risk, not remove it.

If your whole stack is one mainstream calendar on updated devices, the vendors are doing most of the work. Google's guidance specifically tells admins not to run custom scripts or third party bulk tools to move events, so resist the urge to "fix" things that aren't broken.

There's also real uncertainty. The tz database itself calls its November 1 modelling a temporary hack, to be removed once CLDR is fixed, and four provinces and territories have changed rules in a single year. Smaller booking apps and older phone systems may lag. We can't tell you which vendors are fully updated, and you shouldn't trust anyone who says they can without testing. Test results beat vendor promises.

Finally, if a bot already gives customers wrong answers at a normal rate, this weekend won't be your biggest problem. Fix the basics first.

The takeaway

November 1 is the first year BC businesses don't change their clocks, and that's good news for most teams around Burnaby and Metro Vancouver. Just spend 20 minutes making sure your software agrees with your wall clock. Book a test appointment, question your AI agent, check recurring events, and confirm Remembrance Day hours.

Sources

• Government of British Columbia, BC Gov News, "Adopting permanent daylight saving time," March 2, 2026. https://news.gov.bc.ca/releases/2026AG0013-000209
• Internet Assigned Numbers Authority (IANA), "Time Zone Database Release 2026b," April 22, 2026. https://www.iana.org/time-zones/releases/2026b
• IANA, tz database NEWS file (releases 2026b to 2026e), 2026. https://ftp.iana.org/tz/data/NEWS
• National Institute of Standards and Technology (NIST), "Daylight Saving Time (DST)," accessed October 2026. https://www.nist.gov/pml/time-and-frequency-division/popular-links/daylight-saving-time-dst
• Google Workspace Knowledge Center, "Manage Canadian daylight saving time changes for Calendar," 2026. https://knowledge.workspace.google.com/admin/calendar/manage-canadian-daylight-saving-time-changes
• Microsoft Support, "Outlook Time Zone Changes for Alberta and British Columbia," 2026. https://support.microsoft.com/en-us/outlook/calendar/timezone-changes-for-canada-provinces
• Google Business Profile Help, "How to set Special hours," accessed October 2026. https://support.google.com/business/answer/6303076

Not sure your booking bot or automations will get November 1 right? Book a free call with Autana. We'll run the test booking with you, check your AI agent's time handling, and tell you straight if nothing needs changing.