The ELD mandate has been in effect long enough that most drivers know they need a device, but the actual rules around which device, what it has to do, who's exempt, and what happens when the device fails are still genuinely confusing. The compliance framework is in 49 CFR Part 395, and the parts that bite carriers in the field are the ones that don't get covered in ELD vendor marketing — data transfer at roadside, the malfunction rules, the editing procedure, the supporting documents requirement. Knowing where the regulation actually draws the lines is what keeps an inspection from turning into a violation list.
Who has to use an ELD
The rule applies to most drivers required to keep records of duty status (RODS) under federal hours of service rules. That means commercial motor vehicle drivers operating in interstate commerce. The basic test:
- You're required to keep an HOS record of duty status, AND
- You're not covered by one of the explicit exemptions
The exemptions matter:
Short-haul exemption. Drivers operating within a 150 air-mile radius of their work reporting location, returning to that location within 14 hours, and not required to take a 30-minute break can use timesheet records instead of an ELD. This covers a lot of regional and local operations.
Pre-2000 model year exemption. Drivers operating vehicles manufactured before model year 2000 are exempt from the ELD requirement. The exemption applies based on the engine model year (some interpretations) or the truck model year (most common interpretation). This exemption is being narrowed in interpretation over time, but it's still operative.
Driveaway-towaway operations. When the vehicle being driven is itself the commodity (being delivered to the buyer), ELD isn't required.
8-day exemption. Drivers who keep RODS for 8 or fewer days in any 30-day period can use paper logs.
For most OTR carriers and most new authority operations, none of the exemptions apply and the ELD is mandatory.
What counts as a compliant ELD
FMCSA maintains a registered ELD list at eld.fmcsa.dot.gov. To be compliant, a device has to be self-certified by the manufacturer and registered with FMCSA. The list is the definitive source — if a device isn't on the list, it isn't compliant, regardless of what the vendor's marketing says.
A few requirements the device must meet:
- Automatic recording of duty status changes
- Engine connection to capture engine power events, vehicle motion, miles driven, and engine hours
- Display of HOS data to the driver
- Data transfer capability to enforcement (one of the FMCSA-specified methods)
- Tamper resistance and edit/annotation rules per the regulation
Devices that were previously AOBRD (Automatic On-Board Recording Devices, the predecessor technology) had to be replaced or upgraded to true ELD compliance by December 2019. AOBRDs are no longer acceptable.
When choosing a device, the FMCSA-registered list is the floor. Above that, features and price vary widely between vendors.
How data transfer at roadside actually works
When an inspector requests your logs at roadside, you have to be able to transfer the data using one of two FMCSA-approved methods:
Telematic method: Web services or email transfer initiated by the device.
Local method: USB or Bluetooth transfer from the device to the inspector's reader.
Most modern ELDs support both. The inspector specifies which one they want; you initiate the transfer through the device.
A backup method is also required: if the primary transfer fails, you have to show the inspector the logs on the device display (or a printout) covering the current 24-hour period and the previous 7 days. The display has to show duty status, location, and miles for each segment.
If the device is malfunctioning or you don't know how to operate the transfer, the inspector can move forward with the inspection treating you as a non-compliant ELD operation, which is a violation on its own. Knowing how to do the data transfer on your specific device — practicing it before you need it — is part of the readiness work.
The malfunction rules
If your ELD malfunctions, the regulation requires you to:
- Notify the carrier in writing within 24 hours.
- Reconstruct the RODS for the current 24-hour period and the previous 7 days using paper logs.
- Continue using paper logs until the ELD is repaired or replaced.
- Get the ELD back in service within 8 days, OR request an extension from FMCSA.
If the device is just intermittently glitchy (drops connection briefly, syncs slowly), that's not a malfunction in the regulatory sense — the device is still recording, just imperfectly. A true malfunction is the device failing to record duty status, failing to record vehicle data, or failing to display required information.
The 8-day repair window is rarely a problem in practice — most ELD vendors can ship a replacement device within a few days. The carrier-side documentation of the malfunction (the written notification within 24 hours) is what often gets missed.
Edits and annotations
ELDs allow drivers and authorized carrier personnel to edit logs, with limits:
- Driver edits: A driver can correct mistakes in their own log entries (a duty status change that was logged wrong, for example). All edits are annotated with the reason and timestamped.
- Carrier edits: Authorized carrier staff can propose edits to a driver's log. The driver has to certify and accept the edit before it takes effect.
- What can't be edited: Engine-recorded data — vehicle motion, miles, engine hours — can't be edited. Those are the immutable record. Duty status interpretations layered on top of that data can be edited.
Edits that try to retroactively change the time the truck was moving are not just non-compliant; they're falsification, which is a high-weight HOS violation under CSA scoring.
Supporting documents
Even with an ELD, you're required to keep supporting documents that corroborate the log entries. The regulation specifies what counts:
- Bills of lading and dispatch records
- Toll receipts
- Fuel receipts
- Receipts for purchases (food, supplies) that show date, time, and location
- Phone records to the extent they show location
Up to 8 supporting documents per 24-hour duty cycle have to be retained for 6 months. The auditor at a compliance review compares the ELD record against the supporting documents looking for inconsistencies — a fuel receipt timestamped during a "sleeper berth" period, for example, is a discrepancy that suggests log falsification.
Carriers who let supporting documents pile up unsorted are vulnerable in an audit. The discipline is sorting them weekly into the driver's file.
Personal conveyance and yard moves
ELDs have two special duty statuses that need understanding:
Personal conveyance (PC): Off-duty driving for personal reasons, not under dispatch. Time and miles don't count against HOS limits, but the use is bounded — PC has to be authentic personal time, not a way to extend the work day.
Yard moves (YM): On-duty driving on private property at low speed without affecting the HOS clock the same way driving time does. YM is bounded to actual yard maneuvers — not a workaround for closer customer runs.
Both statuses are scrutinized by enforcement and auditors. Improper use of PC or YM is one of the higher-weight HOS findings.
Honest caveat: ELD vendors vary widely in how they handle edge cases
Two FMCSA-registered ELDs that both technically comply with the regulation can have very different real-world behaviors around things like: how connection drops are handled when the truck briefly loses cell signal, what happens when the engine cycles off during a load, how supporting document attachment works, how the device handles co-driver swaps, and how easy it is to demonstrate roadside data transfer. Carriers who picked the cheapest registered device sometimes spend extra hours at scales because the data transfer is awkward, or they have to call vendor support to walk through a malfunction documentation question. The registered list ensures the device meets the regulatory minimum; the operational experience can vary by an order of magnitude between vendors. New carriers who switch ELDs after the first six months often cite this — they discovered the operational shortcomings of their first choice after they were already invested in the platform.
The ELD rule is now mature enough that compliance is a settled question for most carriers. What's still moving is how individual devices handle the regulation's edge cases and how comfortable drivers are with the routine operations — data transfer, edits, malfunctions, the supporting documents requirement. Treating the ELD as a serious piece of compliance infrastructure rather than a black box that runs in the background is what keeps small problems from becoming inspection findings.
Where this fits in your compliance footprint
The ELD program is one slice of the larger compliance footprint that any operating authority has to maintain — alongside the drug and alcohol program, BOC-3, UCR, MCS-150, and the ongoing FMCSA filings. The decisions about which ELD you run sit inside that broader picture. If you'd rather hand the broader authority and compliance footprint to a partner who keeps it current for you, have us handle your authority.