Datatruck Raises $12M Series A to Accelerate AI-Native TMS for Carriers
8/5/26, 3:04 PM
ELD Compliance for Carriers What the Mandate Requires
One missed ELD log or a device that drops connection can turn a routine roadside inspection into an out-of-service order. ELD compliance is not optional for most carriers, and the rules around exemptions, malfunctions, and record transfers trip up fleets every day. This guide covers what the ELD mandate requires, who is exempt, and how to stay audit-ready.
Key takeaways
|
What the ELD mandate requires
The ELD mandate, in full effect since December 2019 after the AOBRD phase-out, requires drivers who must keep records of duty status to use an electronic logging device registered with the FMCSA. The device connects to the engine and automatically records driving time, which removes the guesswork and edits that paper logs allowed.
An ELD is not just a clock. It must capture and transmit a specific data set on demand at a roadside inspection.
Date, time, and location at each duty-status change
Engine hours, vehicle miles, and driver identification
Carrier and vehicle information tied to the record
A standardized output the officer can view or transfer
Who has to comply, and who is exempt
Most commercial drivers who currently keep RODS must run an ELD, but several operations are carved out. Knowing where you fall keeps you from buying compliance you do not need or skipping compliance you do.
Operation | ELD required? |
Interstate CMV driver keeping RODS | Yes |
Short-haul within 150 air miles, back in 14 hours | No, if the exception holds every day |
Vehicle with an engine older than model year 2000 | No |
Driveaway-towaway, vehicle is the commodity | No |
Driver using paper logs 8 or fewer days in 30 | No |
The short-haul exception is the one carriers lean on most, and it is also the easiest to break. Cross the 150 air-mile line by a mile or run past the 14-hour window even once, and that day requires a full record.
ELD compliance and hours of service
An ELD enforces the hours of service limits automatically, which is the point of the mandate. The device tracks the clocks so a driver and dispatcher can see remaining hours before a violation happens, not after.
The core limits the ELD watches are the 11-hour driving cap, the 14-hour on-duty window, the 30-minute break, and the 60 or 70-hour weekly limit. Review the full hours of service rules so your dispatchers plan loads inside them.
Compliance failures here feed directly into your CSA score, which is why HOS sits alongside the other items on a trucking compliance checklist for fleets over 10 trucks.
Malfunctions, edits, and record retention
An ELD failing does not excuse a missing log, so the mandate has strict rules for what happens next. Every driver needs to know the procedure before the device ever fails.
Note the malfunction and switch to paper logs immediately
Reconstruct RODS for the current and prior 7 days if needed
Notify the carrier in writing within 24 hours
Repair or replace the device within 8 days
Records must be retained for 6 months, and any edits must keep the original entry visible with an annotation. Unassigned driving time also has to be reviewed and assigned, which is a common audit finding when it piles up.
Common ELD compliance mistakes
Most violations are not from ignoring the mandate, they come from small process gaps. These are the ones inspectors and auditors catch most.
Drivers not logging in, so miles land as unassigned driving time
No malfunction procedure, so a failed device becomes a violation
Personal conveyance used incorrectly to stretch driving time
Form and manner errors, like a missing shipping document number
These slip through when compliance data lives apart from operations. When your ELD integrates with your fleet data, unassigned time and HOS risk surface on the same board your dispatchers already watch.
How Datatruck keeps ELD data connected to operations
Datatruck is a TMS for carriers that pulls ELD and telematics data into the same database as dispatch and settlements, so hours of service, location, and load status live in one place. That connection is what turns compliance from a separate chore into part of how you already dispatch.
Instead of checking a standalone ELD portal, dispatchers see remaining hours next to the load board and assign work that stays inside the limits. Explore the available ELD and device integrations, and see the full picture in a Datatruck demo.
FAQs
What does the ELD mandate require?
The ELD mandate requires most drivers who keep records of duty status to log hours of service on an FMCSA-registered electronic logging device connected to the engine. The device must record driving time automatically and transmit a standardized record at roadside inspections.
Who is exempt from the ELD mandate?
Drivers using the 150 air-mile short-haul exception, vehicles with engines older than model year 2000, driveaway-towaway operations, and drivers who keep paper logs 8 or fewer days in any 30-day period are exempt. The short-haul exception only holds on days when every condition is met.
What happens if an ELD malfunctions?
If an ELD malfunctions, the driver switches to paper logs, reconstructs the current and prior 7 days of records if needed, and the carrier must be notified in writing within 24 hours. The device has to be repaired or replaced within 8 days.
How long must ELD records be kept?
Carriers must retain ELD records for 6 months, and any edits must preserve the original entry with an annotation. Unassigned driving time also needs to be reviewed and assigned, since it is a frequent audit finding.