During an inspection, follow the safety official’s request and the installed ELD’s documented display or transfer workflow. When a malfunction prevents accurate HOS recording or presentation, notify the carrier within 24 hours. Reconstruct the current day and previous seven days when required, use paper or another permitted method, and have the carrier repair, replace, or service the ELD within eight days unless FMCSA grants an extension.
Identify what the officer found
| Finding | Immediate response | After the stop |
|---|---|---|
| HOS/RODS violation | Follow the officer’s direction; do not alter the record at roadside | Preserve inspection report, ELD file, supporting records; review correction or challenge path with qualified compliance counsel |
| Missing/unavailable required record | Produce the supported display/transfer or permitted fallback | Determine account, retention, transfer, or training root cause |
| ELD malfunction/diagnostic | Preserve code and use the malfunction procedure when functions are affected | Match notice, reconstructed records, repair deadline, service record, extension if applicable |
| Device/list or information-packet issue | Provide current evidence available; follow official direction | Verify exact registration and current 49 CFR 395.22 in-vehicle items |
A carrier should not promise that an ELD prevents citations or that every finding can be “fixed” by editing a log.
What to check
| Check | How to verify |
|---|---|
| 1. Inventory the required in-cab ELD materials | Keep the user manual, instruction sheet, data-transfer instructions, malfunction sheet, required blank grids, exact device/version, vehicle, and inspection date. |
| 2. Display or transfer the requested record range | Retain the driver and vehicle, requested dates, selected method, routing entry, displayed result or receipt, time, and any missing-day exception. |
| 3. Verify the original records edits and annotations | Save the requested original records, edit history, annotations, unidentified-driving disposition, certifications, supporting context, and reviewer notes. |
| 4. Rehearse malfunction and paper-log fallback | Keep the simulated code or failure, driver notice, carrier response, reconstructed records, blank-grid use, repair or support route, and return-to-service decision. |
| 5. Run a failed-transfer branch and retain the result | Record the exact failed method and error, alternate display or transfer, inspector instruction, receipt or displayed result, support case, corrective action, and retest. |
Limits of this page
Roadside ELD Violations: Response and Review Checklist explains the federal or cross-border decision path but does not replace an operation-specific determination by the carrier's qualified reviewer or applicable authority.
Sources and review date
Reviewed August 10, 2026. The notes beside each source explain what it supports. Recheck current rules, registry status, product documentation, and commercial terms at the time of the decision.
- Federal Motor Carrier Safety Administration — ELD malfunction and data-diagnostic responsibilities.
- Federal Motor Carrier Safety Administration — Official ELD technical FAQ covering engine synchronization, VIN, odometer, position, data transfer, events, and device behavior.
- Federal Motor Carrier Safety Administration — Roadside and safety-official ELD data-transfer methods.
Rehearse the roadside workflow
Bring the installed device, current instructions, sample records, transfer method, malfunction packet, and a named reviewer.