Time Zones and Daylight Saving in Canadian Booking

For a salon where every customer walks through the same door, time zones never come up. For a coach in Regina with clients in Halifax, a clinic group with locations in two provinces or a consultant who books calls across the country, time zones decide whether people show up at the right hour. This guide explains the Canadian quirks a booking site has to handle and the habits that keep times correct.

Who changes clocks in Canada, as of November 2026

2026 was the year western Canada stopped changing its clocks. Several provinces made their last spring change on March 8, 2026 and did not fall back on November 1. The rules below were checked against government sources in November 2026. Treat them as a snapshot and check again before building anything that depends on them.

Yukon

The Government of Yukon says the territory is permanently seven hours behind Coordinated Universal Time (UTC-7)¹. It stopped changing clocks in 2020.

British Columbia

B.C.'s last seasonal change was on March 8, 2026. Clocks stayed the same on November 1, 2026, and the province now keeps Pacific time, seven hours behind UTC, all year². The north-east (the Peace River region and the northern Rockies) already used UTC-7 all year and now matches the rest of the province. South-eastern B.C., including Cranbrook, Fernie, Golden and Invermere, stays aligned with Alberta at UTC-6 all year². A business with locations in Vancouver and Cranbrook therefore needs two zones.

Alberta

Alberta has adopted permanent Alberta Time, equal to UTC-6, and from November 2026 its clocks no longer go back to Mountain Standard Time³. Saskatchewan's April 2026 release confirmed that Alberta's 2026 spring change would be its last⁴. In clock terms, Alberta and Saskatchewan now show the same time all year.

Northwest Territories

In April 2026 the territory's premier announced an end to seasonal time changes, acting alongside Alberta⁵. The IANA time zone database records that the Northwest Territories moved to permanent UTC-6 on August 21, 2026 and did not fall back on November 1. Most of the territory follows the same rules as Alberta in the database, and the change separately affects the zone used for Inuvik⁶.

Saskatchewan

The province's Time Act, 2026 took effect on October 30, 2026 and sets year-round Central Standard Time across the province⁷. Under the old law, the Saskatchewan side of Lloydminster switched to Mountain Standard Time in winter to match Alberta. With both provinces now on the same clock, Lloydminster stays on one time all year⁷. The new Act also lets border areas follow a neighbour's time by regulation, so check local rules if you serve communities near a provincial boundary⁷.

Manitoba

Manitoba did not turn its clocks back on November 1, 2026, and will not spring forward in March 2027. Its new year-round time, Manitoba Standard Time, is five hours behind UTC⁸. The province specifically asks businesses to review booking, scheduling and payroll systems, check future recurring appointments and not assume the time difference with partners elsewhere stays the same all year⁸.

Nunavut, northwestern Ontario and the rest of the east

Release notes for the IANA time zone database say a provincial regulation now lets the parts of northwestern Ontario that kept Winnipeg's clock follow Manitoba's year-round UTC-5⁹. The 2026 database releases record no change for Nunavut, the rest of Ontario, Quebec or the Atlantic provinces¹⁰, so those areas still change clocks in spring and autumn. Nunavut's communities sit in three different zones, so a business serving the territory should check each community's local time. In winter, Winnipeg and Toronto now show the same time. In summer, Toronto is an hour ahead.

Your booking system needs current time zone data

Software does not learn about these changes by itself. Operating systems, programming languages, databases and phones get their rules from the IANA time zone database. British Columbia's change arrived in release 2026b (April 22, 2026), Alberta's in 2026c (July 8), the Northwest Territories' in 2026d (September 11) and Manitoba's in 2026e (September 29)¹⁰. A server, plugin or app still running older data will show winter appointments in those places an hour off. Ask your booking platform which time zone data release it uses, keep servers and libraries updated, and check a few future winter bookings in each zone you serve.

Store a named zone, not an offset

A frequent mistake is storing appointment times as a fixed offset, such as UTC minus 5. An offset is correct on the day it is calculated and wrong for any date on the other side of a clock change. A named time zone identifier, such as America/Toronto, America/Edmonton or America/Vancouver, carries the rules for every date, including rule changes like the ones in 2026, once the system has updated time zone data.

The calendar standards support this. iCalendar, defined in RFC 5545, allows a time to be written in Coordinated Universal Time with a trailing "Z", or as a local time tied to a time zone definition through a TZID reference such as America/New_York¹¹. The Google Calendar API specifies time zones using IANA identifiers and requires a single time zone for recurring events so the recurrences can be expanded correctly¹².

Recurring appointments need local intent

A weekly class at 6 p.m. should stay at 6 p.m. local time after the clocks change, which means its UTC time shifts by an hour. If the system stored only a UTC time, the class would jump to 5 p.m. or 7 p.m. That is why recurring events need a named zone, and why the Google Calendar API insists on one for recurrences¹².

Show times in the customer's zone, and say so

For in-person services, show times in the location's zone and name it if customers might be elsewhere, for example "All times in Saskatchewan time (CST)". For calls and online sessions, detect the visitor's zone, show times in it and name it next to the times, with a way to change it. A small label such as "Times shown in Atlantic Time" removes the guesswork.

Confirmations should carry the zone

The confirmation email, the reminder and the calendar file a customer saves should all carry the same time and zone. A calendar file that includes a proper time zone reference lets the customer's own calendar show the appointment correctly wherever they are. We test this by saving a confirmation to calendars set to different zones.

The awkward hours where clocks still change

In places that still change clocks, on the night clocks go forward, one local hour does not exist; on the night they go back, one local hour happens twice. Few businesses book appointments at 2 a.m., but systems that run overnight jobs, such as reminder sends, can misfire. When we set reminder timings, we check what happens on both nights.

A testing routine

1. Book an appointment for a winter date in each zone you serve, including B.C., Alberta, the Northwest Territories or Manitoba if relevant, and check it in the staff calendar.
2. Create a weekly series that spans a clock change in a zone that still has one, such as Toronto, and check several weeks.
3. Book from a browser set to Saskatchewan time and another set to Atlantic time, and compare.
4. Confirm which IANA time zone data release the server and booking platform use.
5. Save the confirmation's calendar file to a calendar in a different zone.
6. Check the reminder send time in the week after each change.

Multi-location businesses

A business with locations in different provinces should store each location's zone with the location, not with the business as a whole. Staff who work at more than one location should have their availability tied to the location's zone for each shift. Customers should choose a location before seeing times, so the times they see are in the right zone from the start.

What we do on every booking site

We store times with named zones, show the zone next to times wherever a customer could be elsewhere, include proper time zone data in calendar files and run the test routine above before launch. Where your clients book across provinces, we repeat the display checks after each clock change and each time zone rule change as part of our booking site care plans.