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.
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.
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.
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.
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.
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.
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.
A ELD (electronic logging device) is a device that automatically records information using the CMV (commercial motor vehicle) ECM (Electronic Control Module), truck sensors and GPS trilateration to automatically record driving time. Fun fact, February is Black History Month and we need to acknowledge GPS was invented by mathematician Gladys West who was the second black woman to be hired to work as a programmer for the US Navy. As a CMV is moving the ELD is receiving information from the ECM and comparing that information to GPS position to monitor compliance to the Federal Hours of Service HOS (SOR/2005-313) and the Technical Standard.
A driver’s day in ELD sequence.
The ELD records all the required information from the Federal Hours of Service HOS (SOR/2005-313) and additional device compliance health monitoring in the Technical Standard. The data collected is related to: carrier identification, driver identification, vehicle identification, driver location information at prescribed intervals and each change of duty status, a running and cumulative odometer and engine hours total, duty status totals and ELD identification information.
The drivers’ daily, workshift, cycle and off-duty requirements are continuously monitored, and a driver is alerted within 30 minutes of reaching a duty status limit.
The ELD continuously monitors the device functionality and alerts the driver if any data is missing or there is a connectivity issue. Drivers are prompted to provide missing information if data is not automatically recorded. Drivers are alerted to uncertified RODS and missing data elements. Unidentified driving records must be accepted or rejected by the driver and no other information can be entered until unidentified driving time is resolved, Technical Standard 4.1.5 3).
The data from the ELD is shared between the drivers in-truck device and a dashboard or portal for the motor carrier to monitor the entire fleet. All the data is stored on the cloud for 6 months and can be retrieved by the carrier for inspection. The motor carrier is expected to monitor the drivers continuously using the information generated from the ELD. A driver should never be in a out of service condition for HOS because as soon as the driver is alerted to a problem the driver is supposed to immediately stop and alert the carrier. The driver and carrier are supposed to work together to resolve the issue and if the issue cannot be resolved follow the OOS criteria. The data doesn’t lie and the data doesn’t go away.