ELD Mandate Explained: Who Has to Use One, Who's Exempt, and How to Stay Compliant

The ELD mandate is the federal requirement that most drivers of commercial motor vehicles record their hours of service electronically instead of on paper logs. It has been fully in effect since December 16, 2019, when the last grandfathered AOBRD devices were phased out, and it remains one of the most misunderstood rules in trucking. Carriers still get placed out of service for running unregistered devices, drivers still get cited for editing logs incorrectly, and safety departments still struggle to document exemptions correctly when a roadside inspector asks for proof.

This guide covers exactly who has to run an ELD, who is legally exempt, how ELDs differ from the AOBRDs they replaced, what has to be in the cab alongside the device, how the hours-of-service limits the ELD is enforcing actually work, what happens when a device malfunctions, and how ELD data gets used against — or for — a carrier during a DOT audit.

The mandate: history and legal basis

Congress ordered the FMCSA to require electronic logging in the Moving Ahead for Progress in the 21st Century Act (MAP-21) of 2012, largely in response to widespread falsification of paper logs. The FMCSA published the final ELD rule in December 2015, codified at 49 CFR Part 395, Subpart B (395.20 through 395.38), plus the technical specifications in Appendix A to Subpart B.

The rule rolled out in three phases. Phase 1 (February 2016–December 2017) was voluntary. Phase 2 began December 18, 2017, when carriers not already running a compliant AOBRD had to switch to a registered ELD. Phase 3, the true deadline that most people mean when they say "the ELD mandate," hit December 16, 2019 — the date every AOBRD grandfather clause expired and every covered driver had to be on a registered, compliant ELD.

Who has to use an ELD

The baseline rule under 395.8(a) is simple: any driver required to keep records of duty status (RODS) under Part 395 must use an ELD unless a specific exception applies. In practice this covers essentially every CDL and non-CDL driver operating a commercial motor vehicle over 10,001 lbs GVWR/GCWR in interstate commerce who does not qualify for the 100 air-mile or 150 air-mile short-haul logging exception, plus many intrastate drivers whose states have adopted the same rule.

It does not matter whether the driver is a company employee or an owner-operator, whether the truck is owned or leased, or whether the carrier is a one-truck operation or a thousand-truck fleet. If the driver has to prepare a paper log on more than 8 days out of the prior 30, the ELD requirement applies.

The five ELD exemptions

FMCSA built five narrow carve-outs into 395.8(a) and 395.1. Each has to be independently proven if a roadside officer or auditor asks — none is automatic just because a driver believes it applies.

1. The 8-days-in-30 short-haul/paper-log exception

A driver who is required to keep RODS on no more than 8 days within any 30-day rolling period may use paper logs for those days instead of an ELD (395.8(a)(1)(iii)). This typically covers drivers who mostly qualify for the short-haul exception under 395.1(e) but occasionally exceed the air-mile radius or the 14-hour window and have to log on paper a handful of days a month.

2. Drive-away tow-away operations

Drivers who deliver a vehicle that is itself part of the shipment — driveaway/towaway operations where the truck being driven is the commodity, such as moving a new motorhome or semi-tractor from a factory to a dealer — are exempt because installing an ELD would be impractical (395.8(a)(1)(i)). This does not apply to the tow vehicle in a wrecker/tow-truck business hauling disabled vehicles.

3. Pre-2000 engine model years

A CMV with an engine model year older than 2000 is exempt from the ELD requirement, even if the truck itself is newer (395.8(a)(1)(ii)). The engine model year controls, not the chassis year — a 2005 truck with a rebuilt 1998 engine still qualifies. These drivers must still keep paper RODS unless another exception applies.

4. Short-haul drivers who never need RODS at all

Drivers operating within a 150 air-mile radius of their work reporting location and released within 14 hours (395.1(e)(1) for CDL holders) or the 100 air-mile / 12-hour version for non-CDL short-haul drivers never have to prepare RODS in the first place, so there is nothing to log electronically. The carrier must still keep time records under 395.8(j) showing on-duty time, start and end time, and total hours for each day.

5. Agricultural and other HOS-exempt operations

Drivers who are fully exempt from hours-of-service rules — such as certain agricultural operations within a 150 air-mile radius of the source farm during planting and harvest, or utility service vehicles responding to an electrical, gas or water emergency under state-declared emergencies — have nothing for an ELD to record, since Part 395 does not apply to them for those trips.

ELD vs. AOBRD: why the difference still matters

Automatic On-Board Recording Devices (AOBRDs) were the pre-2017 electronic logging technology, governed by the older 395.15. AOBRDs simply recorded engine on/off, movement, miles and time — they did not enforce the HOS rules or restrict edits the way ELDs do. As of December 16, 2019, AOBRDs are no longer legal for any driver required to log electronically, full stop. If your fleet is still running AOBRD firmware, or a used truck comes with an AOBRD-only telematics unit, you are out of compliance the moment a covered driver operates it.

Registered devices and the revoked-device problem

FMCSA does not "approve" ELDs the way it certifies medical examiners. Manufacturers self-certify that their device meets the technical specifications in Appendix A, then register it on FMCSA's public list at the agency's ELD website. As of any given day there are several thousand device model listings on that list — and a rotating handful get revoked every year for failing to meet the specification, most often around data transfer or malfunction detection.

When FMCSA revokes a device, carriers using it get a compliance window — historically 60 days — to migrate to a registered device before the revoked unit is treated as no ELD at all. Running a revoked device past that window means every driver on it is legally in the same position as a driver with no ELD: an inspector can place the driver out of service and the carrier can be cited for each driver operating without a compliant device. Check the registered list before buying hardware, and check it again periodically — a device that was compliant at purchase can be revoked later without the vendor necessarily telling you.

Required documents in the cab

An ELD replaces the paper logbook, but it does not replace the rest of the required cab paperwork. Roadside inspectors expect to find all of the following, and a missing item is cited separately from any ELD violation.

Hours-of-service limits the ELD enforces

An ELD does not create new hours-of-service rules; it enforces the same limits that have existed under 49 CFR 395.3 for property-carrying drivers, now automatically calculated instead of hand-written. Understanding the numbers is essential because the ELD will hard-stop a driver's ability to log on-duty driving once a limit is reached.

The sleeper-berth provision is the one drivers and dispatchers get wrong most often on an ELD. Under the current rule, a driver can split the required 10 hours off duty into a period of at least 7 consecutive hours in the sleeper berth plus a separate period of at least 2 consecutive hours (either off duty or also in the berth), or the older 8/2 split. Neither period by itself counts against the 14-hour driving window, but the two periods together must add up to at least 10 hours, and the ELD software has to correctly exclude both qualifying periods from the 14-hour calculation — older ELD firmware sometimes gets this wrong, which is worth checking against a manual calculation before trusting the app's countdown.

Edits, unassigned driving time, and driver certification

ELDs are built to make falsification harder, not impossible, so FMCSA layered specific edit rules on top of the raw data. A driver can annotate or request a correction to their own record, but the device must retain the original entry alongside the edited one — nothing is truly deleted. A carrier's back-office staff (safety manager, dispatcher) can propose edits too, but the driver must review and accept or reject every proposed change; a carrier cannot unilaterally alter a driver's certified record.

Unassigned driving time is the single most common ELD-related audit finding. It shows up when a vehicle moves while no driver is logged in — often a yard hostler moving a truck, a mechanic road-testing a repair, or a driver forgetting to log in before pulling out. Every unassigned segment has to be reviewed and either assigned to the correct driver or annotated with an explanation; unreviewed unassigned time sitting in the ELD account is treated by auditors as evidence of undocumented driving and can be cited on its own.

Personal conveyance and yard moves

Personal conveyance (PC) lets a driver move the CMV for personal reasons off duty — commuting to a hotel after being relieved from a load, or moving the truck to get a meal — without that time counting as driving. FMCSA guidance does not set a fixed mileage or time cap, but it does require the movement to be genuinely personal, not in furtherance of the load, and most carrier policies cap PC at a reasonable distance to avoid abuse (many use 75 to 250 miles as an internal guardrail, but that is company policy, not federal law). A loaded trailer being moved for the carrier's benefit — even a short distance — is not personal conveyance.

Yard moves are a separate ELD special duty status for moving a vehicle on private property, such as repositioning a trailer within a yard for the purposes of a road test or spotting a dock door. Yard move status is optional for the carrier to enable, and it is limited to on-property movement only; a driver who exits onto a public road under yard-move status has misused the classification.

Malfunction procedures and the 8-day rule

Section 395.34 sets out exactly what happens when an ELD malfunctions. The driver must notify the motor carrier within 24 hours of discovering the malfunction, and must reconstruct the current 24-hour period's record of duty status on paper (using the blank log forms required to be in the cab) starting from the moment the malfunction occurred, continuing on paper until the device is repaired, replaced, or serviced.

The carrier then has 8 days from the date the malfunction was discovered to correct, repair, replace, or service the malfunctioning ELD. If the carrier needs more time, it must request an extension from the FMCSA Division Administrator in the driver's home state before the 8 days expire; extensions are not automatic. A carrier that ignores a known malfunction past the 8-day window, or lets drivers keep running with a broken device and no paper backup, is exposed to a false-log or no-ELD violation for every day that follows.

Roadside data transfer

During a roadside inspection, the officer will ask the driver to transfer ELD data using one of two FMCSA-approved methods: telematics (wireless transfer via web services or email, common on devices with cellular data plans) or local transfer (USB or Bluetooth, used when the truck has no signal or the device lacks telematics). Every registered ELD must support at least one local method as a backup. A driver who cannot produce the data on request — dead battery, unfamiliarity with the device, forgotten login — can be cited for failing to provide RODS, which carries the same severity weight as having no logs at all.

ELD violations and CSA severity weights

ELD and HOS violations post directly to the Hours-of-Service Compliance BASIC in the FMCSA Safety Measurement System, and several carry among the highest severity weights of any violation category — enough on their own to push a carrier over an intervention threshold.

A false-log violation (severity 7) is treated by FMCSA as more serious than most single equipment defects, and it is one of the few HOS-related violations that can independently support an Unsatisfactory safety rating. This is why coaching drivers on correct edit and annotation procedure is worth as much attention as the mechanical act of logging in each shift.

How ELD data gets used in a DOT audit

During a compliance review or new-entrant audit, the investigator will typically pull 6 months of ELD records for every driver and cross-reference them against supporting documents — fuel receipts, toll records, dispatch logs, bills of lading, and even GPS breadcrumb data if the telematics system logs it. The goal is to catch mismatches: a fuel purchase 400 miles from where the ELD says the truck was, a delivery timestamp that contradicts an off-duty status, or a pattern of edits that always shaves a few minutes off the 14-hour window on the same days each week.

Auditors also specifically check the carrier's unassigned-driving-time queue, because an unreviewed queue is an easy, objective finding that requires no interpretation. A carrier that reviews and resolves unassigned segments weekly, keeps a written HOS/ELD policy, and retains malfunction and edit records for the required 6 months will move through this part of an audit far faster than one that has never looked at the back end of its ELD account.

Building an ELD compliance program

A durable ELD program has four working parts: a registered, non-revoked device on every applicable truck; a written company policy covering personal conveyance, yard moves, and edit procedures that every driver signs; a weekly review of unassigned driving time and pending edits by a named person, not "whoever has time"; and a malfunction protocol that drivers actually know how to execute, including where the paper log forms and instruction sheets are kept in the cab. Carriers that treat the ELD as a one-time hardware purchase, rather than an ongoing data-management process, are the ones who show up in the CSA HOS BASIC with elevated scores and eventually draw a focused investigation.

It's also worth budgeting for driver turnover. Every new hire needs to be trained on the specific ELD brand your fleet runs — login procedure, status changes, personal conveyance and yard move activation, and how to pull up the malfunction instruction sheet — before their first loaded mile, not after the first roadside inspection exposes a gap.

Keeping an ELD program audit-ready — registered devices, clean edit trails, a resolved unassigned-driving queue, and documented exemptions — is exactly the kind of ongoing work Long Haul Compliance handles for carriers of every size. Call (865) 992-8089 to have our team review your ELD setup before an inspector or auditor finds the gaps first.