ELD Guide

Who This Applies To

• Commercial motor vehicle drivers required to maintain Records of Duty Status under FMCSA regulations who must use a compliant ELD.
• Motor carriers responsible for ensuring all qualifying vehicles have FMCSA-registered ELDs installed, drivers are trained, and a written malfunction response procedure is in place.
• Operations teams checking whether a specific vehicle, driver category, or operation type qualifies for an ELD exemption before assuming one applies.
• Carriers transitioning drivers or vehicles from paper logs to ELD and managing the documentation that FMCSA requires be retained alongside ELD data.

What To Verify

• That the ELD installed in each vehicle appears on FMCSA's registered compliant device list at eld.fmcsa.dot.gov. A vendor's claim of compliance is not the same as appearing on the list.
• Which drivers and vehicles qualify for exemptions. The short-haul exception, the driveaway-towaway exemption, and the pre-2000 vehicle exemption each have specific conditions in eCFR Part 395 that must be met — partial qualification doesn't count.
• That the carrier has a written ELD malfunction response policy, that drivers know the 8-day paper log requirement during a malfunction period, and that drivers carry blank paper log sheets in the vehicle.
• That ELD data transfer capability is working — FMCSA requires the ability to transmit records to enforcement during a roadside inspection via telematics or local transfer.

Step-by-Step Overview

1. Verify each installed device against the FMCSA registered ELD list before drivers use it for RODS. The list is searchable by provider name and device model.
2. Train drivers on: how to review and certify daily logs, how to handle unassigned driving segments, how to annotate the log when the ELD shows conditions that differ from actual duty status, and what to do if the device malfunctions.
3. Establish a data retention practice. FMCSA requires ELD records to be retained for a minimum period — verify the current requirement in eCFR Part 395 and confirm the ELD provider stores records accessibly for that period.
4. Test data transfer capability periodically, not just at installation. A device that can't transfer records during a roadside inspection is treated the same as a missing ELD.
5. Put a written malfunction procedure in place before any malfunction happens. It should specify: what the driver does immediately (note the code, switch to paper), when the carrier is notified (within 24 hours), and what the repair timeline is (8 days).

Common Mistakes

• Installing an ELD that the vendor says is compliant but that is not on the FMCSA registered device list. Unregistered devices do not satisfy the ELD mandate regardless of the vendor's claims.
• Assuming an exemption applies without checking all its conditions. The short-haul exception requires specific radius limits, return-to-location conditions, and daily on-duty time caps — missing any one condition removes the exemption for that day.
• Not having paper logs in the vehicle. Every driver subject to ELD requirements must carry enough blank paper log sheets for at least 8 days of RODS in case of malfunction.
• Treating data diagnostic events as minor annoyances. Persistent unresolved diagnostic events — especially unassigned driving — suggest records may not accurately reflect duty status, which draws enforcement attention.
• Certifying logs without reviewing them. Drivers who certify without checking for unassigned segments or location gaps are signing off on records that may be inaccurate, which becomes a much larger issue during an inspection.