CVSA Enforcement Bulletin 2026-02 and Canadian Hours of Service
Finally in 2026 a regulator put something in writing.
An interpretation of ELD violations found roadside and how they are dealt with. The CVSA just released Enforcement Bulletin 2026-02 and I cannot stress how important this is for carriers facing ELD penalties or punitive audit enforcement for ELD internal carrier monitoring.
Up until last week if a carrier had an ELD violation and wanted to plead not guilty and go to court there was no public-facing information explaining what an ELD violation actually was. There has never been an interpretation guide for ELD violations published for industry. Most carriers simply pay the ticket.
How are you supposed to defend yourself when there is no public information explaining what ELD data actually constitutes a violation? Now carriers finally have something to build a case on.
Most ELD violations are dealt with in traffic court. That means it is the driver or the carrier explaining the validity of the violation to a judge who likely has no commercial vehicle training and little familiarity with ELD systems.
The majority of people in the industry do not understand the minutia of ELD data and how it relates to regulation. They know they cannot easily explain why a violation is not a violation to a judge.
The enforcement officer, meanwhile, carries built-in credibility. Judges reasonably assume that if an officer issued a ticket, it must be correct.
Now with Enforcement Bulletin 2026-02 industry finally has something tangible from a regulatory body.
Enforcement Guidance from 2026-02
Inspectors should rely on the driver interview and make every effort to support the OOS violation through motor carrier contacts and the collection of supporting documentation. The goal is to only place drivers OOS who pose an imminent hazard.
For standard false RODS, where it is possible for the inspector to determine when the falsification occurred, and the driver is not over hours at the time of inspection, these false RODS should be cited under § 395.8(e)(1): No driver or motor carrier may make a false report in connection with a duty status., and the driver should be allowed to proceed.
In Canada the comparative violation is:
SOR 2005-313 86(2): No motor carrier shall request, require or allow any person to enter, and no person shall enter, inaccurate information in a record of duty status or falsify, mutilate, obscure, alter, delete, destroy or deface the records or supporting documents.
If the driver is over the HOS limits at the time of inspection, the driver should be cited under § 395.8(e)(1) and placed OOS until such time as eligibility to drive is re-established.
For drivers whose RODS have been reengineered, reprogrammed or tampered with and the ELD does not accurately record or retain required data, and it is not possible for the inspector to determine when driving occurred, the inspector should cite a § 395.8(e)(2): No driver or motor carrier may disable, deactivate, disengage, jam, or otherwise block or degrade a signal transmission or reception, or reengineer, reprogram, or otherwise tamper with an ELD so that the device does not accurately record and retain required data. violation and place the driver OOS for 10 consecutive hours.
In Canada the comparative violation:
SOR 2005-313 86(3): No motor carrier shall request, require or allow any person to, and no person shall, disable, deactivate, disengage, jam or otherwise block or degrade a signal transmission or reception, or re-engineer, reprogram or otherwise tamper with an ELD so that the device does not accurately record and retain the data that is required to be recorded and retained.
False RODS where the driver still has available hours should result in a ticket, but the driver is allowed to continue. If the RODS are false and the driver is over their hours, the driver should receive a ticket and be placed out of service until sufficient hours are available to drive again. If the RODS have been tampered with or reprogrammed so the ELD cannot accurately determine driving time, the driver should receive a ticket and be placed out of service for 10 consecutive hours.
Why This Matters in Canada
Finally, after many years, there is an opinion of what constitutes an ELD violation and what to do about it.
There is still no opinion regarding historical violations discovered during a NSC Standard 15 audit or compliance review, but because NSC Standard 15 is currently under review this issue should eventually be addressed.
Here is the problem.
It has taken regulators years to reach this point — just in time for technology to already be moving ahead again. Full telematics systems including ELDs, in-cab cameras and exterior cameras are becoming standard across the industry.
Insurance companies are increasingly demanding this level of data. Recent information from the insurance industry (HUB Insurance 2026 report) stated that adoption and optimization of emerging technology are non-negotiable. Underwriters now expect the use of critical transportation technology systems when negotiating policy terms.
Which raises a reasonable question.
Why are regulators spending years writing interpretations for technology the industry is already moving beyond?
ELDs rely on driver input. A driver must log in, change duty status and make manual entries. Regulators already recognize the weakness of this system — the technical standard itself includes diagnostics and tampering provisions because the data can be manipulated.
Meanwhile the next generation of safety technology already exists. Driver-facing AI cameras, telematics and engine data can identify exactly who is driving and when the vehicle is moving. Systems like DriveWyze already transmit vehicle and carrier information to enforcement agencies for weigh station preclearance.
If autonomous trucks are still years away, the alternative is obvious: automate the driver monitoring systems instead.
So why are regulators spending years writing interpretations for technology that the industry is already preparing to replace?
Regulators had years to educate stakeholders and failed to do so. Instead, enforcement issued thousands of tickets that carriers had little ability to challenge because regulators either did not understand the technology themselves or did not publicly release the limited information they had.
The Canadian Hours of Service Problem
So what is the real problem?
SOR 2005-313 91(1) Out-Of-Service Declaration.
In Canada we do not have an ELD interpretation guide or enforcement direction from regulators. The only reference available is the federal Hours of Service regulation itself.
If we compare SOR 2005-313 to 49 CFR Part 395, we see that SOR 2005-313 section 91(1) (e) addresses false records and (f) addresses tampering, while SOR 2005-313 91(3)(a-e) outlines the out-of-service conditions. The U.S. equivalent is 49 CFR 395.13 Drivers ordered out-of-service.
SOR 2005-313 91(3) An out-of-service declaration applies
(a) for 10 consecutive hours, if the driver contravenes paragraph 4(b) – driving would be likely to jeopardize the safety or health of the public, the driver or the employees of the motor carrier;
(b) for 10 consecutive hours, if the driver contravenes section 12 – 13 and 14 hours in a day
(c) for 8 consecutive hours, if the driver contravenes sections 13 – off-duty time or 39 – north of 60 off duty time;
(d) for 72 consecutive hours, if the driver contravenes section 86 – 86(1) duplicate, 86(2) false and 86(3) tampered;
(e) for the number of hours needed to correct the failure, if the driver fails to comply with the off-duty time requirements of any of sections 14 to 29 and 41 to 54 or of a term or condition of a permit or with the requirements of section 98.
(4) The out-of-service declaration in respect of a driver who contravenes section 86 continues to apply beyond the 72 hours until the driver rectifies the record of duty status, if applicable, and provides it to the director or inspector so that the director or inspector is able to determine whether the driver has complied with these Regulations.
Basically, how it works is the driver receives a ticket for 86(2) or 86(3) and is then placed out-of-service according to 91(1) and 91(3).
The Big Question
Carriers and stakeholders now need to understand how CVSA Enforcement Bulletin 2026-02 will impact enforcement in Canada.
Is Transport Canada, the CCMTA and each provincial and territorial jurisdiction planning to adopt the principle that “The goal is to only place drivers OOS who pose an imminent hazard”?
We do not have this language written into Canadian Hours of Service regulations.
However, CVSA represents enforcement agencies from Canada, the United States and Mexico. Canadian regulators and enforcement agencies sit on CVSA committees and participate in the development of these enforcement policies. It is therefore reasonable to assume Canadian regulators were involved in approving this guidance.
This matters because an ELD error is not the same thing as an imminent safety risk.
ELDs are not error-proof. We cannot engineer away poor decision making, inconsistent network connectivity or temporary data transmission failures.
A driver who makes a mistake and is placed out-of-service for 72 hours faces a very different outcome than a driver placed out-of-service for 10 hours.
A Real-World Example
Consider a driver operating in northern Ontario between Wawa → White River → Marathon → Terrace Bay → Nipigon.
There are long stretches of highway in this corridor with weak or no cellular connectivity.
When the driver enters an area with good signal again, the ELD recalculates and updates duty status information. During these periods of low connectivity, the driver must manually keep track workshift time.
Sometimes the math simply does not math and the driver exceeds a duty status limit even if it’s only 10 minutes.
If the driver cannot explain that connectivity gap — where the ELD did not accurately record and retain the required data — will that driver be sitting roadside for 10 hours or 72 hours?
The Bottom Line
Carriers and drivers should carefully review any ELD violation they receive.
For years there has been no publicly available interpretation explaining how ELD data should be enforced.
Now with CVSA Enforcement Bulletin 2026-02, there is finally something tangible that can be used when challenging an ELD penalty.
If you receive an ELD violation roadside, during a compliance review, or through a NSC Standard 15 audit, it may be worth examining whether the enforcement action actually aligns with this guidance.
If you have received an ELD penalty and want a second opinion before deciding whether to challenge it in court, send it to me and I will let you know if it may be worth fighting.
