AI ELD
Apr 2, 2026
Most fleets discover their compliance problems when someone else forces them to. The FMCSA investigator requests records. The roadside officer reviews seven days of logs. The insurance auditor pulls the six-month history. By that point, the options narrow quickly.
A monthly internal log review using the same sequence an investigator follows changes the timeline. Problems caught internally in week two of a 30-day cycle can be corrected, documented, and addressed through driver coaching before they accumulate into the kind of pattern that attracts enforcement attention. Problems discovered during a compliance review cannot.
This article builds a monthly audit process from the same methodology compliance investigators use, explains what they are specifically looking for at each step, and adds the one piece most fleet managers do not know about: exactly how many violations in a sample will cross the legal threshold that triggers a rating consequence.
When FMCSA conducts a compliance review, investigators use ERODS software to scan ELD records automatically, flagging potential violations without having to work through individual logs manually. This means investigators can review more records faster than was possible with paper logs, and it means patterns that would have gone unnoticed in a manual paper review are now detected systematically.
Investigators approach ELD audits in two phases. The first is a basic review for HOS violations: did drivers exceed the 11-hour, 14-hour, or 60/70-hour limits? Did anyone miss the 30-minute break? The second phase is a review for falsification: are there signs that electronic records were manipulated to conceal violations? These are not separate investigations. If something flags in the basic review, the investigator moves immediately into the deeper check.
The eight steps below follow that sequence. Running them monthly puts your fleet in the same position an investigator starts from, with enough time to actually fix what is found.
This is the regulatory mechanic that most fleet managers have not read. Under 49 CFR Part 385, Appendix B, a single violation of a critical regulation does not automatically affect a carrier's safety rating. What creates a rating finding is a pattern of noncompliance. Under the FMCSA's rating methodology, a pattern is defined as more than one violation, and when a number of records are being reviewed, the number of violations required to establish a pattern equals at least 10% of those examined.
For HOS and ELD violations specifically, there is an additional consequence that does not apply to other categories: each pattern of noncompliance with a critical regulation under Part 395 is assessed two points against the carrier's rating, compared to one point for other critical violation patterns. Three or more points in any single factor results in a finding of inadequate safety management controls in that factor.
The practical meaning for monthly audits: if an investigator reviews 30 records per driver, as required by FMCSA's compliance review formula, finding violations in just three of those records, which is 10%, establishes a critical violation pattern. In a fleet with multiple drivers, violations do not need to be concentrated in one driver's logs to cross the threshold. Three violations across 30 reviewed records trigger the same outcome whether those violations belong to one driver or three.
Running a monthly audit against this threshold is the only way to know whether a fleet's current violation rate would produce a critical finding if investigators requested records today.
The first check is the most direct. Run the HOS violation report from the ELD back-office system for the period being reviewed. This surfaces any driver who exceeded the 11-hour driving limit, hit the 14-hour window, missed the required 30-minute break, or approached the 60 or 70-hour cycle limit.
For each violation that appears, the review requires two actions. First, confirm the violation is real rather than a system error or status logging issue. Second, verify that the driver was notified. If a fleet is not notifying drivers the next day when violations occur, drivers may come to believe the company is not watching, which tends to increase the frequency of violations over time. The notification and any coaching conversation should be documented, because a compliance review that finds repeated violations with no corresponding corrective action treats that pattern as a carrier management failure.
A driver who does not certify their daily log creates a compliance gap that is immediately visible to investigators. Uncertified logs are one of the clearest signals that a fleet is not actively managing its ELD data, and even when the underlying driving time is lawful, an uncertified log invites deeper scrutiny and can extend an inspection or audit.
The monthly review should identify every driver with uncertified log days in the review period and document follow-up. Chronic certification failures across multiple drivers indicate a training issue rather than an individual driver problem, and that is how investigators read them: repeated missing certifications across a fleet are treated as evidence of systemic supervision failure, not isolated oversight.
Certification should be the last action a driver takes before logging off at the end of each shift. Fleets that build this into driver habit through brief daily confirmation reduce their uncertified log count to near zero without additional monitoring effort.
Unassigned driving occurs when the vehicle moves but no driver account is logged in. Every motor carrier is required to either assign unassigned driving time to the appropriate driver or attach an explanation for why it could not be assigned. Unassigned events without any explanation attached are cited as violations during audits and can also trigger expanded scrutiny of drivers who were not part of the original sample.
Investigators look closely at unassigned driving because it is one of the most common mechanisms through which drivers attempt to conceal driving time. A vehicle showing movement while the assigned driver is logged as off-duty or in the sleeper berth is a red flag, particularly when the on-duty and off-duty location records do not match. The fleet compliance dashboard makes unassigned events visible in real time so they can be resolved before accumulating.
The most effective approach is to assign someone within the fleet to review and resolve unassigned driving events daily rather than at month-end. For the monthly audit, the check is to confirm that all events have been assigned or annotated and to flag any patterns, such as the same driver consistently generating unassigned events or events clustering around specific vehicles.
Every ELD system maintains a complete record of edits made to driver logs, including what changed, when the change was made, and by whom. Investigators review this report specifically because on-duty to off-duty edits are the primary mechanism through which drivers attempt to falsify electronic records.
Pull the edits report and examine any instances where on-duty time was changed to off-duty. For each such edit, confirm there is a legitimate annotation explaining the change. Edits that coincide with approaching HOS limits, that follow a crash or roadside inspection, or that appear repeatedly for the same driver warrant closer review and documented follow-up. Unlike paper logs, electronic records cannot be rewritten, but they can be edited, and every edit creates a traceable record that investigators are trained to read.
The ELD logbook tools maintain full edit histories for exactly this reason: the carrier needs a complete record of every change, not just what the final log shows.
Personal conveyance is the most common source of false log violations identified during compliance reviews, according to former DOT safety investigator Dave Osiecki of Scopelitis Transportation Consulting. Investigators check the beginning and ending odometer values during PC periods and compare them to route context. Excessive distance during a personal conveyance period, or a route that aligns with the direction of the next dispatch, raises the question of whether the movement was truly personal or was advancing a commercial purpose.
The personal conveyance rules for what qualifies as legitimate use are specific. The monthly review should pull all PC events for the period and check associated odometer records. Any instance with unusually high mileage, or where the direction of travel appears inconsistent with genuinely personal movement, should be discussed with the driver and documented. For fleets with a written PC policy, the review should also confirm that actual usage stays within what the policy permits.
Investigators compare the odometer reading at the start of a logged 30-minute break against the reading at the end. If the vehicle moved during the break period, the break does not satisfy the regulatory requirement even if the log shows a compliant rest period. This check is straightforward and takes only a few minutes against any driver who logged a 30-minute break during the review period.
The monthly audit should flag any break where odometer values indicate vehicle movement and document the follow-up conversation with the driver. This is one of the most common compliance issues investigators find precisely because drivers and fleet managers rarely run this check themselves.
Investigators look at the list of login IDs used across the fleet and the associated login activity. A driver using multiple login credentials, logging in inconsistently, or not logging in before driving is a pattern associated with log falsification. The monthly review should confirm that each driver in the fleet has a single consistent login account and that there are no unexplained instances of the same driver appearing under multiple credentials.
The review should also confirm that the ELD system is communicating correctly with the back-office portal and can produce records for electronic transfer to law enforcement. An ELD that cannot produce records electronically during a roadside inspection creates an immediate compliance problem, and a fleet that cannot demonstrate this capability during a compliance review faces additional scrutiny. This is part of what investigators check when they verify that the devices communicate with the web portal for transferring data to enforcement.
The final step in the investigator sequence is comparing ELD records against supporting documents. Investigators pull fuel receipts, bills of lading, toll records, and payroll records and compare the timeline and location information against what the driver logged. A fuel receipt placing a driver in one state while their log shows them off-duty in another state at the same time is exactly the kind of discrepancy that moves an investigation from a basic hours review into a falsification inquiry.
The monthly audit does not need to cross-reference every supporting document for every driver. For any driver who triggered concerns in steps one through seven, running a spot-check against fuel receipts and bills of lading for the same period is the most realistic test of whether those records will hold up under investigator review. This is the step most fleet internal reviews skip, and it is the one that would catch the most serious problems.
Investigators do not select drivers at random. The formula targets drivers with red-flag violations, those with the highest percentiles in the HOS BASIC, drivers involved in crashes, those with the highest overall violation rates, and recently hired drivers. That last group is worth noting specifically. Recently hired drivers appear on the selection list regardless of their individual violation history, because carriers are expected to have verified and supervised new hires from day one.
For a fleet of 100 drivers in an on-site compliance review, the investigator reviews at least 11 drivers with a minimum of 30 records of duty status per driver. For an off-site review, as few as three drivers are selected. Given the 10% pattern threshold, 30 records means three violations establish a critical finding. Running the monthly audit against your most recently hired drivers and your highest-violation drivers first mirrors the logic investigators use, and it is where the review effort pays off most.
An internal audit that is not documented may as well not have happened. If a compliance review takes place and the fleet has no evidence of an internal oversight process, the investigator has no basis for concluding that problems are being actively managed. A basic record of each monthly review, covering the date, which reports were pulled, what was found, and what corrective action was taken, creates documentation that demonstrates the carrier is meeting its compliance management obligations.
The AI ELD reports generate the violation summaries, uncertified log counts, unassigned driving totals, and edit histories this process requires. Fleets using AI ELD average a 4% FMCSA safety score, which reflects consistent compliance management across all drivers rather than compliance that only surfaces when enforcement forces the issue.
For context on what a compliance review actually looks like from the outside, the ELD roadside inspection guide covers the driver-facing side. The HOS rules reference covers the specific limits being checked in step one of this sequence.
For questions about setting up monthly review workflows or how the AI ELD dashboard surfaces the data needed for each step, the support team can walk through the setup, or you can start a free 14-day trial to explore the reporting tools directly.
eCFR. "49 CFR Part 385, Appendix B: Explanation of Safety Rating Process" — 10% pattern threshold for critical violations; two-point scoring for HOS-specific critical violations under Part 395. https://www.law.cornell.edu/cfr/text/49/appendix-B_to_part_385
FMCSA. "Safety Measurement System (SMS) Methodology" — intervention threshold structure, BASIC scores, and how investigation findings feed carrier prioritization. https://csa.fmcsa.dot.gov/documents/smsmethodology.pdf
J.J. Keller Compliance Network. "Motor Carrier Fitness Rating Factors" — two-point HOS scoring rule; three-point threshold for inadequate safety management controls. https://jjkellercompliancenetwork.com/regsense/motor-carrier-fitness-rating-factors
Heavy Duty Trucking / TruckingInfo. "What Happens When FMCSA Comes to Audit Your Driver Logs?" September 2020 — investigator audit sequence, 30-record minimum, driver selection formula, ERODS software, supporting document cross-reference, PC as top false log source. Source: Dave Osiecki, Scopelitis Transportation Consulting, former DOT safety investigator. https://www.truckinginfo.com/10125729/what-happens-when-fmcsa-comes-to-audit-your-driver-logs
J.J. Keller Encompass. "3 Electronic Log Audits Every Fleet Should Do." Updated 2024 — daily unassigned driving review, next-day violation notification, on-duty to off-duty edit auditing. https://eld.kellerencompass.com/resources/blog/2018-blogs/3-electronic-audits-every-fleet-should-do
J.J. Keller. "4 Things Every Fleet Should Know About ELD Data" — carrier violation risk from unresolved unassigned events; ELD compliance requires active auditing, not just device installation. https://www.jjkeller.com/learn/4-things-fleets-should-know-ELD-data
J.J. Keller. "FMCSA Interventions for BASIC Scores Above the Threshold" — intervention escalation: warning letter through comprehensive on-site investigation. https://www.jjkeller.com/learn/csa-interventions
ELDT Nation. "ELD Logbook Mistakes That Trigger Violations." February 2026 — uncertified logs, unassigned driving, and end-of-shift certification as compliance discipline. https://www.eldtnation.com/blog/eld-logbook-mistakes-that-trigger-violations-fixes-inside
TruckStop.com. "CSA Scores." August 2025 — 65% intervention threshold for HOS Compliance, Unsafe Driving, and Crash Indicator BASICs. https://truckstop.com/blog/csa-scores/
US Compliance Services. "Why Paying Attention to Your CSA Score Is More Important Than Ever." July 2025 — focused investigations at five-year highs; average six violations per investigation; average settlement $7,155 per closed case. https://uscomplianceservices.org/why-paying-attention-to-your-csa-score-is-more-important-than-ever/