11 mins to read

ELD mandate compliance guide

By Jennifer Coreno Strouth April 28, 2026

The electronic logging device (ELD) mandate has been in place for years, but it still requires close attention from fleets. Just because you are utilizing a functioning device doesn’t mean you’re automatically compliant.

The Federal Motor Carrier Safety Administration (FMCSA) takes ELD mandate compliance seriously for good reason: safety. FMCSA estimates the ELD mandate helps avoid 1,844 crashes annually, prevents 562 injuries and saves 26 lives each year by reducing fatigued driving.¹

Most drivers who are required to keep records of duty status (RODS) must use a compliant ELD to track hours of service (HOS).² That basic rule has not changed, but portions of it evolve.

For fleets, the key is knowing where compliance pressure is showing up now — and where small oversights can create bigger problems during DOT inspections or audits.

Who does the ELD mandate apply to?

The ELD mandate generally applies to interstate commercial drivers who are required to keep records of duty status (RODS) under 49 CFR Part 395. That usually means most interstate commercial motor vehicle (CMV) drivers — particularly those operating vehicles over 10,001 lbs — those carrying hazardous materials or transporting 9 to 15+ passengers. These drivers are subject to federal hours of service (HOS) rules unless they qualify for an exemption.

What’s new in the 2026 regulatory landscape?

There is no brand-new 2026 ELD mandate law taking effect this year. What has changed is the enforcement environment around those ELD mandate requirements.

The "clean registry" push is real

One of the biggest developments is FMCSA’s ongoing cleanup of its Registered ELDs list. Over the past year, the agency has removed dozens of devices in multiple waves after determining they no longer met the minimum technical requirements in Appendix A to Subpart B of Part 395.³

They will continue to determine whether devices meet technical standards, even if they were compliant at the time of registration.

For fleets, that means compliance is no longer a one-time decision. Carriers should periodically confirm that their device is still on the registered list and has not been moved to the FMCSA Revoked ELD device list.

If a device is revoked, fleets generally have 60 days to replace it. After that, continued use may be treated the same as operating without ELD devices installed.² Fleets risk potential out-of-service (OOS) orders, hours-of-service citations and significant fines.

The in-cab paper manual requirement may be going away

Another notable update is FMCSA’s proposal to remove the requirement for drivers to carry a physical ELD operator’s manual in the cab, recognizing that instructions are often available digitally through the device or online.⁴ Even so, fleets still need to ensure drivers know how to use inspection mode, transfer logs and annotate records correctly during roadside stops.

The truck ELD mandate is only one part of staying compliant. This eBook breaks down the tools that can help simplify fleet compliance, from HOS and DVIRs to IFTA and FMCSA requirements.

Core technical requirements for ELD hardware

FMCSA's push to remove non-compliant ELDs puts more focus on what a compliant device is. Under 49 CFR Part 395, it must automatically record and retain specific data in a standardized, inspectable format that supports HOS enforcement and reduces opportunities for manual error.²

At a minimum, a compliant device must capture key operating data such as:

Engine power status
Vehicle motion
Miles driven
Engine hours
Date and time
Location information

Much of that depends on engine synchronization — the ELD’s ability to connect to the engine control module (ECM) or vehicle data bus and pull information directly from the vehicle rather than relying only on driver input.

"Tamper-proof" does not mean "unchangeable"

ELDs must be tamper-proof to prevent altering driving data, according to the mandate. Drivers and authorized carrier personnel can make certain corrections or propose edits to a log, but the system must preserve the original record. If a carrier proposes a change, the driver must review and certify it before the exchange becomes part of the final record.

That same principle applies to ELD annotations. Devices must allow drivers to explain certain events and status changes, which is especially important when documenting exceptions such as yard moves or personal conveyance.

ELD driver inspection mode and roadside data transfer

A compliant device also has to be able to produce records in a format inspectors can review. That means displaying logs on screen or producing a printout when required, and supporting approved data transfer methods such as wireless web services or email during a roadside inspection.

Navigating ELD exemptions

Several exemptions can affect whether a driver is required to use an ELD. But being exempt from the ELD mandate rules does not always mean a driver is exempt from keeping records of duty status (RODS). In some cases, it simply means paper logs are allowed instead. Here are some common exemptions:

Short-haul exception: Drivers who qualify for the ELD short-haul exception do not need to keep RODS, which means they also do not need to use an ELD. They must meet the conditions of that exception, including limits around work reporting location and duty window.
8 days in 30 rule: Drivers who are required to keep RODS no more than 8 days in any rolling 30-day period are not required to use an ELD.
Pre-2000 vehicles: Vehicles manufactured before model year 2000 are generally exempt because many do not support the engine synchronization required for compliant ELD operation. Though this is generally considered the "ELD model year exemption," it’s really about the engine manufacture date. While any vehicle with a pre-2000 VIN is exempt, newer models with an engine manufactured before 2000 are also exempt. This occurs most commonly when a vehicle is rebuilt using a "glider kit" or when an engine is swapped from one vehicle to another.⁵
Driveaway-towaway operations: If the vehicle being driven is itself the commodity being delivered, an ELD is generally not required. This often applies when trucks or other commercial vehicles are being transported rather than used to haul freight.
150 air-mile agricultural rule: Certain agricultural commodity operations may be exempt from HOS and ELD requirements within a 150 air-mile radius of the source of the commodity during applicable planting and harvesting periods. Once a driver moves beyond that exempt area, normal logging requirements may apply again.

There are also more limited ELD exemptions and waivers for certain operations, including some government and industry-specific use cases.

The fleet manager’s audit checklist

Installing an approved device is only part of ELD mandate compliance. The bigger test is whether a fleet can produce clean, defensible records when an inspector or auditor starts asking questions.

Supporting documents are essential

FMCSA requires carriers to retain up to eight supporting documents for each 24-hour period a driver is on duty, and drivers must submit their RODS and supporting documents within 13 days. Carriers must then retain those records for six months.⁶ Supporting documents can include:

Dispatch or trip records
Fuel or expense receipts
Electronic mobile communication records
Payroll or settlement records

If the ELD shows one thing and the paperwork shows another, that can create extra scrutiny during an audit.

Keep unidentified miles from piling up

One of the most common trouble spots for managers is unassigned driving time, sometimes called unidentified driving records. This happens when a vehicle moves but no driver is logged in.

While unidentified miles do not automatically mean a violation occurred, it is the kind of issue that can suggest weak controls or poor log management if it keeps showing up.⁷

Fleets should have a consistent process for reviewing those records, assigning them when appropriate and documenting why a change was made. Verizon Connect’s Reveal ELD Logbook software places all these unidentified miles in a single queue for easy review. A clean queue shows that the fleet is actively managing its HOS data instead of letting questionable records accumulate.

Fleet technology can help you support compliance — but it can also do so much more. This eBook shows how connected fleet data can help improve productivity, efficiency and your fleet’s overall performance and ROI.

Know the malfunction protocol

When an ELD fails, there is a defined process for what happens next. FMCSA says drivers must notify the carrier within 24 hours if the device malfunctions. If the malfunction prevents the ELD from accurately recording or displaying HOS data, the driver must reconstruct the current day and previous seven days of logs and switch to compliant paper RODS or another approved backup method.⁸

From there, the carrier generally has eight days to repair, replace or service the device, or request an extension.⁸

The business case for compliance with ELDs

For many fleets, the biggest value of ELDs is not simply checking a compliance box. It is reducing the small recordkeeping problems that can turn into larger operational or enforcement headaches.

Fewer "form and manner" issues

Before ELDs became standard, many hours-of-service violations came from form and manner violations⁹ — missing locations, unsigned records, incomplete vehicle information or other clerical mistakes. By pulling data directly from the vehicle and standardizing how logs are created, ELDs can help reduce many of those avoidable errors.

That matters to fleets because ELD-related HOS violations still feed into FMCSA’s HOS Compliance BASIC, where repeated issues can affect a carrier’s CSA scores.

Cleaner records can support insurance conversations

Clean HOS records, demonstrating a commitment to ensuring drivers are rested and managers adhere to regulations, can support conversations with insurers about premium discounts.

Drivers notice the difference, too

Modern ELD systems are easier to use than older hardware or paper RODS, especially when they automate status changes, simplify log certification and give drivers clearer visibility into their available time.

For Mike Narvaez, safety and compliance director at R&M Trucking, ELDs — and Logbook specifically — have made life easier for his drivers.

"They don’t have to struggle with filling in lines on a log book form from the seat of their truck," he says. "You’re always current, your form and manner is perfect — you’ve got nothing to worry about. It’s one less thing on the driver’s mind when he’s got a million things already going on."

Read about R&M’s experience using Verizon Connect Reveal ELD Logbook to improve the trucking company’s safety scores.

Managing the ELD mandate moving forward

The ELD mandate law may be well established, but ELD mandate compliance still requires attention to detail. That means more than installing a device and moving on. Fleets need to understand the technical requirements behind compliant hardware, know which exemptions still apply, keep supporting records organized and stay ready for audits, inspections and malfunctions.

Want a simpler way to manage ELD compliance, driver logs and HOS records? Book a demo and see.