ELD Requirements for New Carriers: Who Needs One and What FMCSA Will Check

If you are a new carrier hauling general freight interstate, your ELD setup is going to be one of the first things FMCSA looks at. A non-registered device, a missing instruction sheet, or logs that do not match supporting documents can each generate audit findings. This guide explains who needs an ELD, what FMCSA expects, and the small details that catch carriers off-guard.

Who needs an ELD

Under 49 CFR Part 395 Subpart B, almost every driver required to keep records of duty status (RODS) must use an ELD. That includes drivers operating commercial motor vehicles in interstate commerce who must keep logs. The narrow exceptions are:

• Short-haul drivers who qualify under 49 CFR 395.1(e)(1) and stay within 150 air miles of their normal work location, returning within 14 hours
• Drivers who use paper logs no more than 8 days in any 30-day rolling period
• Drivers of vehicles older than model year 2000
• Drivers conducting drive-away/tow-away operations where the vehicle being driven is the cargo

Registered device list

Your ELD must appear on the FMCSA's registered devices list at fmcsa.dot.gov. The list is public and searchable by manufacturer. If your device was removed from the list -- this has happened to several brands -- you must replace it within an FMCSA-defined timeline. An unregistered or revoked ELD generates an automatic critical violation regardless of how clean the logs are.

What must be in every vehicle

FMCSA expects the following in every CMV equipped with an ELD:

• ELD user manual or quick-start guide for the driver
• Instruction sheet describing how to transfer logs to an authorized safety official
• Instruction sheet describing ELD malfunction reporting procedures
• A supply of blank graph-grid paper logs sufficient to cover at least 8 days of operation in case the ELD malfunctions

These materials are inexpensive but easy to forget. Missing them is a routine finding even when the ELD itself is fine.

Records retention

Carriers must retain six months of ELD records (49 CFR 395.22(i)) plus the supporting documents that corroborate the logs. Supporting documents include fuel receipts, bills of lading, toll receipts, and dispatch records. FMCSA expects at least eight supporting documents per driver per 24-hour period, up to a maximum, organized so an auditor can match them to specific log entries.

What auditors verify

1. ELD make and model is on the registered list

   Searched directly during the audit.

2. In-cab documentation is present

   Instruction sheet, malfunction procedures, blank paper logs.

3. Six months of logs are retrievable

   Either uploaded to the New Entrant Audit System or available on demand.

4. Logs are consistent with supporting documents

   Fuel receipts and BOLs cross-checked against duty status.

5. Unassigned driving time is accounted for

   Patterns of unassigned driving suggest log falsification.

Common ELD audit findings

• ELD removed from registered list -- carrier never noticed
• No in-cab instruction sheet or malfunction procedures
• Driver logging on-duty time as off-duty
• Personal conveyance used to extend the 14-hour window
• Unassigned driving time accumulating with no resolution

Selecting an ELD as a new carrier

1. Pick from the registered devices list

   Do not select on price alone. Check that the manufacturer is current on FMCSA's list.

2. Confirm the device manufacturer is established

   Brands that have been on the list for years are safer choices than brands recently added.

3. Make sure the device supports both wireless web service and email transfer

   Auditors can request either.

4. Print the instruction sheet and put it in the cab the day the ELD is installed

   Do not wait.

How ClearToHaul helps with ELD compliance

The New Carrier Startup Package includes verifying your ELD is on the registered devices list and ensures the in-cab documentation is correct so your audit binder reflects the setup. Done-For-You Compliance adds the supporting-document organization and weekly log review workflow.