May 22, 2026
When FMCSA investigators conduct a compliance review, they do not start with roadside inspection records. They start by requesting specific back-office reports from the carrier's ELD system. According to industry compliance consultants who have observed the review process directly, investigators request a consistent set of data: unassigned driving miles, log edit histories, odometer jump reports, and violation summaries. These are not obscure system outputs that require special access to generate. They are standard reports available in every FMCSA-compliant ELD back-office platform. They are also the reports that most fleet managers never look at until a compliance review forces the issue.
The practical argument for reading them weekly is straightforward. An investigator who arrives and requests these reports is looking at the last six months of data at once, searching for patterns. A fleet manager who reviews the same reports weekly catches individual events before they become patterns. The 10% threshold that determines whether a pattern exists under 49 CFR Part 385 Appendix B, meaning violations in more than 10% of reviewed records, is crossed by three violations in 30 records. A weekly review that catches and corrects two of those three events before they solidify into the record changes the outcome of a potential compliance review without requiring any change to driver behaviour or operating procedures.
The HOS violation report is the most obvious report in any ELD system and the one most fleet managers do look at occasionally. What most do not do is read it at the right frequency or with the right pattern recognition.
The report shows every instance where a driver 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. In a well-managed fleet, this report should be reviewed every morning for the previous day. Not weekly. Not at month end. Daily, because the 7-day window within which log annotations and driver notifications should be documented closes faster than most safety coordinators expect.
The pattern to look for is not just which drivers are generating violations. It is when and where violations are occurring. A driver who generates HOS violations consistently at the end of routes that originate from the same terminal is telling you something about route planning, not driver behaviour. A driver who generates violations on the same day of the week repeatedly is telling you something about scheduling. The violation report that surfaces individual events is useful. The violation report read across four weeks as a dataset is the tool that identifies the systemic cause.
The AI ELD compliance reports generate exportable HOS violation summaries across all drivers and vehicles. For a fleet of any size, filtering by driver, by route, and by time period within the same report set is the workflow that converts a daily violation check into a pattern identification exercise rather than a record-keeping task.
The unassigned driving report shows every instance of vehicle movement that was not attributed to an authenticated driver. This happens when a driver moves a truck without logging in, when a handoff between drivers leaves a gap in authentication, or when a vehicle is moved in a yard by someone who is not assigned to that vehicle in the ELD system.
FMCSA investigators treat this report as a primary falsification indicator. A carrier whose vehicles consistently generate unassigned driving events, particularly events that occur at the same time as other drivers' logged records, has a documentary pattern that suggests either systematic non-compliance with authentication requirements or deliberate log manipulation. Even when unassigned events have innocent explanations, the carrier has an obligation to annotate and resolve them. A compliance review that finds accumulated unassigned events with no resolution documentation treats that accumulation as evidence of inadequate compliance management regardless of the underlying cause.
The operational standard for unassigned driving events is daily resolution. Not because the regulation specifies a daily deadline, but because unresolved events that accumulate across multiple days are harder to annotate accurately. A driver who is asked three weeks after the fact whether they moved a specific vehicle on a specific afternoon at a specific terminal will not remember with the precision the annotation requires. A driver asked the next morning will.
The fleet manager's weekly check on the unassigned report should verify that all events from the previous week have been annotated or assigned, and that no new clusters of unassigned events have appeared on the same vehicle or from the same location. A vehicle that generates unassigned driving events repeatedly is a hardware or authentication workflow problem. Identifying it weekly rather than at month end means the problem gets resolved before it generates six weeks of unexplained events.
The log edit report is the one that generates the most investigator attention during a compliance review and the one that most fleet managers review least frequently. It shows every change made to a driver's log after the initial recording: who made the edit, when it was made, what changed, and what annotation was provided.
FMCSA investigators are specifically trained to read this report for the pattern that indicates falsification: edits that change on-duty time to off-duty time, that occur within hours of an approaching HOS limit, that affect the same driver repeatedly, or that correlate with specific events such as crashes or roadside inspections. In compliance reviews, investigators specifically look deeper at edit reports to see if there are ways drivers are manipulating the electronic record. An edit that happens two hours after a driver's 14-hour window would have closed is not automatically a violation, but it is an edit that requires a credible and documented explanation.
The fleet manager's role with the log edit report is not to prevent all edits. Legitimate corrections happen constantly: a driver who forgot to switch from on-duty not driving to sleeper berth at a rest stop, a co-driver handoff that was logged at the wrong time, a yard move that was accidentally recorded as personal conveyance. These corrections are expected and appropriate. What the edit report reveals over time is whether the pattern of edits at a carrier looks like normal operational corrections or like a systematic effort to manage hours that were already exceeded.
Reviewing the edit report weekly with the question "does this edit pattern look like normal operations?" is a different exercise from reviewing individual edits for correctness. The pattern question is what an investigator asks. Building that habit internally means a fleet manager arrives at any compliance review with an already-completed understanding of their own edit history rather than reading it for the first time alongside an investigator.
The odometer jump report is the least well-known of the standard ELD back-office outputs, and it is the one that surfaces a specific compliance problem that does not appear in any other report type.
An odometer jump occurs when the mileage recorded in the ELD shows a significant unexplained gap between consecutive log entries. The ELD records vehicle position and mileage at regular intervals and whenever a duty status change occurs. When the recorded mileage at a status change is significantly higher than the mileage at the previous entry in a way that is inconsistent with the time elapsed, the system flags the discrepancy as an odometer jump.
The legitimate causes of odometer jumps include cellular connectivity gaps in rural areas where the ELD's periodic position recording was interrupted, firmware edge cases during device reboots, and in some cases hardware connectivity issues between the ELD and the vehicle's ECM. The problematic cause is vehicle movement that was not recorded in the ELD, which can indicate either a device malfunction that needs to be documented and repaired under the 8-day malfunction protocol, or a deliberate disconnection of the device during a driving segment.
Investigators treat unexplained odometer jumps the same way they treat unassigned driving events: as a pattern that requires explanation. A carrier whose odometer jump report is clean has a simple answer when the question is raised. A carrier who has never looked at the report may be looking at months of unexplained gaps for the first time during a review.
The weekly check on the odometer jump report takes five minutes. Confirming that every flagged jump has either a connectivity or firmware explanation, or that it has been documented as a malfunction under the appropriate regulatory framework, is the kind of preventive documentation that changes the outcome of a compliance review without changing any operational practice.
If you want to see what the odometer jump, edit history, and unassigned driving reports look like for your specific fleet before committing to a compliance review preparation workflow, the AI ELD platform surfaces all four report types in a single back-office interface. A 14-day trial gives full access to the reporting suite across your actual drivers and vehicles.
The driver availability report is the one that prevents violations at the assignment stage rather than documenting them afterward. It shows each driver's current HOS status: remaining driving hours in the current cycle, remaining time in the current 14-hour window, time until the next required off-duty period, and projected availability after a reset.
This is the report that dispatchers need but most ELD systems bury in a compliance module that dispatchers rarely access. A dispatcher assigning a 400-mile run to a driver who has three hours of remaining window time is not making a malicious decision. They are making a decision with incomplete information. When that driver calls from the road at hour two to say they cannot complete the run, the dispatcher has a load problem, the customer has a service problem, and the driver has an HOS pressure situation.
The fleet manager's role with the driver availability report is architectural rather than operational: ensuring that dispatch has access to this data in the same workflow where load assignments happen, not in a separate compliance system that requires a separate login. The carriers that prevent the most HOS violations are not the ones whose drivers know the rules better. They are the ones whose dispatchers have the same visibility into remaining hours that the drivers have.
For fleet safety coordinators who review this report in the morning before dispatch begins assigning loads for the day, the practical check is confirming that every driver scheduled for a run that day has enough remaining hours to complete it, including realistic allowances for terminal time, fuel stops, and delivery windows. For the specific calculation of how terminal dwell time and detention time affect available driving hours on multi-stop or time-critical routes, the ELD for LTL carriers guide and the ELD for expedited carriers guide cover the operational planning adjustments that matter most.
The five reports above are not independent tools to be checked on five separate schedules. They work as a system when reviewed together on a consistent cadence.
A practical weekly reporting workflow for a fleet of 5 to 50 trucks runs as follows. Every morning, the HOS violation report and the unassigned driving events from the previous day are reviewed and any new items are either annotated or escalated to the relevant driver for explanation. Once per week, the log edit report is reviewed for the previous seven days to confirm that the edit pattern across all drivers reflects legitimate corrections rather than a concerning trend. Once per week, the odometer jump report is checked to confirm all flagged discrepancies have explanations on file. The driver availability report is checked before the daily dispatch cycle begins to ensure load assignments are made against current remaining hours rather than theoretical shift start availability.
This workflow takes approximately 30 to 45 minutes per day for a safety coordinator managing a 20-truck fleet. It scales downward for smaller fleets and upward for larger ones, but the core habit is the same regardless of fleet size. The fleet manager who arrives at a compliance review having run this workflow consistently for six months has already done the investigator's work. They know their edit patterns, their unassigned event history, their odometer jump explanations, and their violation trends. That preparation changes the dynamic of the review.
The fleet manager logbook audit checklist covers the monthly comprehensive review that complements this daily and weekly routine. The weekly workflow keeps the record clean between formal audits. The monthly audit confirms the workflow is working and surfaces any patterns that the daily checks missed.
Compliance reviews do not announce themselves far enough in advance for a fleet to prepare from scratch. The carriers that manage compliance reviews without significant findings are the ones whose safety coordinators have been reading the same reports an investigator will request, every week, for months before any review takes place.
If you want to set up this reporting workflow on your current fleet and see what each report type shows for your drivers specifically, start a free 14-day trial of AI ELD. The full back-office reporting suite is available from day one with no contract requirement. The five reports covered in this article are standard outputs of the platform, accessible in a single compliance dashboard rather than requiring separate logins or export requests.
Heavy Duty Trucking. "What Happens When FMCSA Comes to Audit Your Driver Logs." January 30, 2026. Primary source for the specific back-office ELD reports FMCSA investigators request during compliance reviews: unassigned driving miles, edit reports, odometer jump reports, and violation reports. Source for the investigator interview process and the cross-referencing of ELD data against accounts receivable, payroll, and dispatch records. https://www.truckinginfo.com/articles/what-happens-when-fmcsa-comes-to-audit-your-driver-logs
eCFR. "49 CFR Part 385, Appendix B: Explanation of Safety Rating Process." Primary regulatory source for the 10% pattern threshold: when more than 10% of reviewed records contain a critical violation, a pattern of noncompliance is established. Source for the two-point scoring for HOS-specific critical violations. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-385/appendix-Appendix%20B%20to%20Part%20385
Geotab. "ELD FAQs: Unassigned Driving Time." May 2025. Source for the FMCSA obligation that all unassigned drive time records must be either annotated or reassigned to a driver, that both drivers and carriers are accountable for unassigned drive time, and that carriers are responsible for checking unassigned logs at least once per day. https://www.geotab.com/blog/unassigned-driving-time/
Motive Help Center. "Compliance Reports and Alerts." April 9, 2026. Source for the standard report types available in ELD back-office systems: HOS violations reports, log audit and logs detail reports, ELD output file and violation error summary, personal conveyance and yard move usage reports. Source for the log audit report structure showing who made edits, when changes were made, and what was modified. https://helpcenter.gomotive.com/hc/en-us/articles/30866843579549-Compliance-Reports-and-Alerts
AI ELD. "Fleet Manager Logbook Audit Checklist: The 8-Step Process FMCSA Investigators Use." April 2026. Source for the monthly comprehensive audit sequence including HOS violation report review, unassigned driving event resolution, and log edit report examination as steps in the investigator-mirroring audit process. https://ai-eld.com/insights/fleet-manager-logbook-audit-checklist
AI ELD. "FMCSA Compliance Review: What the HOS Investigation Actually Looks Like." May 2026. Source for the off-site compliance review format, the 48-72 hour document upload requirement, and the confirmation that investigators cross-reference supporting documents against ELD data when reviewing back-office records. https://ai-eld.com/insights/fmcsa-compliance-review-eld-hos
FMCSA. "ELD Malfunctions and Data Diagnostic Events." Source for the malfunction documentation framework under 49 CFR Part 395 Subpart B Appendix A, the 8-day repair obligation, and the requirement to document malfunction events when odometer discrepancies result from device failure rather than deliberate disconnection. https://www.fmcsa.dot.gov/hours-service/elds/eld-malfunctions-and-data-diagnostic-events
J.J. Keller Encompass. "3 Electronic Log Audits Every Fleet Should Do." 2024 update. Source for the daily unassigned driving review recommendation, the next-day violation notification standard, and the on-duty to off-duty edit auditing workflow as the three primary ongoing compliance management tasks. Referenced via: ai-eld.com/insights/fleet-manager-logbook-audit-checklist