On Sunday, November 1, 2026, a night shift in Seattle can gain an extra hour while the same shift in Vancouver stays eight hours long. A standing meeting between the two cities can move by an hour, even though nobody edits the invitation. For employers, this year’s daylight saving time changes reach well beyond resetting a clock.

Several Canadian jurisdictions are ending seasonal clock changes, while U.S. locations that observe daylight saving time will still fall back. That creates two different jobs for payroll and scheduling teams: account for the repeated hour where it happens, and prevent an unwanted clock adjustment where it does not.

RULES CHECKED OCTOBER 29, 2026 · U.S. AND CANADIAN EMPLOYER GUIDE

Who changes clocks on November 1, 2026?

The familiar “fall back” reminder is no longer enough for a business operating across Canada and the United States. Use the following summary to identify which locations need attention, then verify the specific community and its current local rule.

Sources: B.C.’s Pacific Time announcement, the October 15 Golden-area update, Alberta’s official guidance, the NWT announcement, Manitoba’s announcement, Ontario Regulation 333/26, and NIST’s 2026 U.S. rules.

Two details deserve extra care. Older B.C. announcements can predate the subsequent East Kootenay and Golden decisions. Meanwhile, Nunavik’s planned change is not taking effect this year: Makivvik’s October 14 clarification says the region will fall back on November 1, 2026, with an end to seasonal changes targeted for November 2027.

Some places, including Yukon and much of Saskatchewan, already use fixed time. A location with no clock change can still have a new time difference from a customer, supplier, or colleague whose clock changes.

The hidden scheduling issue: your neighbours may move

When one location keeps its time and another falls back, the relationship between them changes. This affects dispatch windows, customer support coverage, shift handoffs, and meetings booked across borders.

These examples are calculated from the applicable offsets on each date. For a recurring event, decide what should stay fixed: the start time at the workplace, or the same shared instant for everyone. A Vancouver opening shift may need to remain at 9:00 a.m. Vancouver time. A cross-border handoff may need a different local start time to preserve continuous coverage.

Review recurring invitations and the roster for the first full week after November 1. Show both cities and dates in important handoff instructions; a label such as “Pacific” by itself is now too vague for a Vancouver–Seattle team.

Eight hours or nine? Pay for the time actually worked

A posted start and finish time does not always tell you how much time elapsed. Consider employees working continuously from 10:00 p.m. Saturday, October 31 to 6:00 a.m. Sunday, November 1, with no unpaid breaks:

• Seattle: The clock falls back during the shift. The employee works nine elapsed hours.
• Vancouver: The clock stays unchanged. The employee works eight elapsed hours.

An hourly rate of $25 would produce $225 for nine straight-time hours and $200 for eight, before any applicable overtime, premiums, or deductions. These are illustrations, not a substitute for the pay rules that apply to the employee.

The extra hour can also affect overtime

For a covered, nonexempt U.S. employee, federal overtime generally applies after 40 hours in a workweek. Suppose the employee has already worked 32 hours in the same established workweek and then works the full nine-hour Seattle shift. That produces 41 hours, assuming all nine belong to that workweek.

If $25 is also the employee’s regular rate and no other payments affect it, the calculation is 40 × $25 + 1 × $37.50 = $1,037.50. Recording the shift as eight hours would leave the employee at 40 recorded hours and miss $37.50 in this example. The U.S. Department of Labor’s overtime guidance explains the federal threshold; applicable state rules can provide additional protections.

For Canadian employees, check the applicable provincial, territorial, or federal employment standards and any agreement. Daily overtime, weekly thresholds, shift premiums, and break treatment can differ. The clock change itself is not a universal rule that every additional hour must receive the same premium.

For the wider process of handling midnight, workday boundaries, and overnight approvals, see TimeTrex’s overnight shift time tracking guide.

What to check in your timekeeping systems

A clock can show the right time today while still carrying an outdated rule for Sunday. Check the full path from the device employees use to the payroll report a manager approves.

1. Verify the location’s time zone and available updates

Review time clocks, kiosks, phones, computers, servers, scheduling applications, and payroll integrations. Install supported updates and follow the relevant vendor’s instructions. Alberta’s guidance specifically warns that older devices may not update automatically.

Use the location-based time zone supported by your system and current rules. Avoid choosing a different city simply because its clock matches today. Confirm both the displayed time and a future-dated test after November 1.

2. Distinguish the repeated hour

At a fall-back location, “1:30 a.m.” can refer to two different moments. Your review record should distinguish them using the time-zone offset or an equivalent unambiguous timestamp. For example, in Seattle, 1:30 a.m. at UTC−07:00 occurs an hour before 1:30 a.m. at UTC−08:00.

Check that the system preserves the sequence of punches, pairs clock-ins and clock-outs correctly, and calculates the elapsed duration. Two matching clock labels alone do not prove a duplicate entry.

3. Test both kinds of location

Run a test shift spanning November 1 for a location that falls back and one that keeps its time. Check the schedule, punch display, worked duration, breaks, overtime allocation, and payroll export. Include a repeated-hour punch pair if your business operates then.

Use approved test records or a test environment. Keep a note of expected results, actual results, and the person who reviewed them. If a discrepancy appears, preserve the original punches and resolve it through your normal correction process.

4. Bring scheduling and payroll into the same review

TimeTrex brings employee scheduling, time and attendance, and payroll into a connected workforce workflow. Use that relationship to compare the planned shift, the recorded work, and the hours prepared for payment.

Confirm the configuration and updates for your own deployment before approving the affected payroll. Treat a successful sample reconciliation as evidence for that configuration; do not assume every device or integration has updated because one screen looks correct.

Your November 1 employer checklist

Assign one owner to coordinate these checks and one payroll reviewer to sign off. Use the checkboxes as a temporary review aid; they reset when the page reloads.

• Confirm the rule for every workplace. Record the city, current time zone, November 1 action, and source.
• Check system readiness. Review device and software updates, location settings, and future-dated test results.
• Review overnight coverage. Identify who works across the transition and whether each shift lasts the intended number of hours.
• Confirm cross-border handoffs. Check recurring meetings, dispatch times, and customer-facing hours for the week of November 2.
• Give employees clear instructions. State whether their workplace changes time, which local time governs the shift, and who handles questions.
• Reconcile before payroll approval. Check elapsed hours, breaks, premiums, overtime, and exports against the original punch records.

Frequently asked questions

Editorial note: Regional rules were checked on October 29, 2026. This guide covers selected U.S. and Canadian locations; it is not an exhaustive time-zone map. Verify current local rules and the employment standards that apply to each employee before processing payroll.