Alberta isn’t falling back—but your software might

Some of us are old enough to remember the ancient times during the birth of the internet. In 1999 the whole world was waiting for the end when computers that could not read 00 as a year would shut everything down. That never happened and we are now watching the development of AI which as we all know from the Terminator movies will be the end of us as a species. In the meantime, the Province of Alberta has decided to eliminate time change which unlike 1999 will not be the end of the world but, it may cause some ELD troubles.

On Sunday, November 1, 2026, Alberta will remain on permanent Alberta Time (ABT), UTC−6. No more falling back or springing forward. Before assuming your ELD has developed a problem, check the other devices and software it works with.

Do not assume your provider has completed every necessary update—or that a downloaded update has finished installing. Check for pending updates and required restarts before November 1.

Check these five things:

1  The phone or tablet

Does the device show the correct Alberta time and date? Check the time-zone setting as well as the displayed clock. Install pending operating-system updates and restart when required.

2  The ELD application

Check for pending ELD app and firmware updates, where applicable. Read your provider’s instructions for Alberta’s time change and confirm whether a restart is required. If the provider has issued no guidance, ask how its system will handle Alberta remaining at UTC−6.

3  The carrier portal and home terminal

The provider fix should ensure that an Alberta home-terminal setting will use the correct time. However just to make sure compare the same event in the driver’s app, the carrier portal and a downloaded report. Establish which time zone each view uses before treating a difference as an error.

4  Other software that uses time

Check dispatch and appointment systems, Google Calendar, Outlook, payroll and time clocks. Review existing bookings and recurring meetings after November 1. Google and Microsoft have published guidance about affected calendar events: updating the computer clock does not necessarily correct appointments already saved. Also check scheduled reports, backups, building access and other automated tasks.

5  Supporting records and timestamps

Compare a known vehicle movement or duty-status event with supporting records such as GPS tracking, dashcam footage, fuel transactions and dispatch records. Identify the time zone and UTC offset each system uses. Save examples of unexplained differences and contact the relevant provider. Document any confirmed time-zone discrepancy so a later reviewer can understand it.

Keep the explanation with the records

During an audit or compliance review, unexplained differences between RODS and supporting documents can raise questions about the accuracy of the records. If a time-zone issue caused the discrepancy, retain the provider’s notice or support response, examples of affected records, and a clear explanation of what happened and when it was corrected.

A one-hour difference does not, by itself, prove falsification or an ELD malfunction but you better have receipts! Preserve the original records and use the provider’s approved process for any necessary correction.

Alberta’s clocks may be staying put. Make sure your software knows that too.

crossmenu