ELD Compliance Rules Every U.S. Trucking Company Must Follow

If you're trying to understand what are the ELD requirements for trucking companies in the US, start here: running a truck without a compliant electronic logging device can result in an out-of-service order and fines potentially reaching four figures. The FMCSA ELD mandate has been fully enforced since 2019, yet violations still account for thousands of citations every year. The reason isn't usually defiance, it's confusion. Carriers aren't sure which drivers are covered, what the device must actually do, or whether their operation qualifies for one of the existing exemptions.

This guide cuts through that confusion. You'll find the exact coverage criteria, the technical specs your device must meet, every exemption that actually applies, and what happens during a roadside ELD inspection if something goes wrong. You'll also see what non-compliance costs in real numbers, and how to build a rollout that holds up under scrutiny.

One operational note worth flagging upfront: managing ELD compliance alongside HOS tracking, driver dispatch, and settlements in separate tools creates the exact kind of operational gaps that generate violations. Integrated platforms like Spotter.ai centralize all of this in one dashboard, which we'll cover at the end. First, the rules.

ELD requirements for trucking companies in the US: who must comply

The anchor rule comes from 49 CFR 395.8(a): if a driver is currently required to maintain Records of Duty Status (RODS), they almost certainly need an ELD. That requirement applies to all commercial motor vehicle (CMV) drivers operating in interstate commerce who keep HOS logs. It covers U.S.-domiciled carriers and extends to Canada- and Mexico-domiciled drivers whenever they prepare HOS records while operating in the United States.

The vehicle threshold matters here. The mandate applies to CMVs manufactured in model year 2000 or newer, even if the truck lacks a factory engine control module (ECM). If a pre-2000 engine was later swapped into a newer chassis, the engine model year controls the determination, so document any engine replacements carefully. When a driver is required to keep RODS, the ELD requirement follows automatically unless a specific exemption applies.

Drivers and vehicles that don't trigger the requirement

The flip side is equally important for fleet managers running mixed operations. If a driver qualifies for an exemption from RODS entirely, the ELD requirement doesn't apply to them. Short-haul drivers using timecards instead of logs, drivers of pre-2000 vehicles, and operators in driveaway-towaway situations all have built-in outs under the rule. The next section details each exemption and its exact qualification threshold, because the criteria are specific enough that misreading them creates its own compliance risk.

What the FMCSA ELD rule requires a compliant device to actually do

Passing a roadside inspection isn't just about having a screen mounted in the cab. The device must meet the technical performance standards in 49 CFR Part 395, Subpart B, and those standards specify both what data gets recorded and how the device connects to the vehicle. Knowing these requirements is what separates a compliant ELD from a GPS tracker a vendor mislabeled as compliant.

Mandatory data elements and automatic recording

A compliant ELD must automatically record seven core data elements: date, time, CMV geographic location, engine hours, vehicle miles, driver identification data, and vehicle identification data. Beyond those seven, the device must pull five specific data points directly from the truck's systems: VIN, wheel speed, RPM, engine hours, and odometer. If the device loses the connection needed to capture any of those five, it must generate a "missing required data elements" diagnostic alert. That alert isn't optional, an uninvestigated alert at a roadside stop is a citation waiting to happen.

Drivers also have manual entry responsibilities. They must input or verify the CMV power unit number, trailer number, shipping document number, and location descriptions when prompted. Annotations must be added when applicable, and output file comments must be entered when an authorized safety officer requests them. The device captures the automatic data; the driver completes the record.

Certification and the FMCSA registered device list

ELD manufacturers self-certify their devices against FMCSA's technical specifications and register them at eld.fmcsa.dot.gov. The device must appear on that registry to be legally compliant. This is a hard line: a GPS tracker, a standalone logging app, or any device absent from the FMCSA registered ELD list does not satisfy the mandate, regardless of what vendor marketing materials claim. Before purchasing any device, search the registry by ELD name, model number, or provider and confirm the exact model is active with no flags for revocation or investigation. For official FMCSA guidance for providers and manufacturers, see the FMCSA provider training resources.

ELD exemptions that may apply to your operation

For carriers managing mixed fleets or short-haul routes, the exemptions are worth understanding in detail. The criteria are specific, and applying the wrong exemption to the wrong driver is treated the same as having no exemption at all.

Short-haul drivers and the 8-day rule

CDL drivers who operate within a 100 air-mile radius of their home terminal, return to that terminal at the end of each shift, and don't exceed HOS driving limits qualify for the short-haul timecard exception. They use timecards instead of RODS and are fully exempt from ELDs. Non-CDL drivers get a slightly wider window: 150 air miles. Both categories must return to their starting location daily to maintain the exemption.

The 8-day rule catches many carriers off guard. Drivers who need RODS for 8 days or fewer in any rolling 30-day period are exempt from ELDs for those days, though they must still use paper logs. On the 9th day within that 30-day window, an ELD is required for the remainder of that stretch. If a driver who usually qualifies for short-haul makes one too many exceptions in a month, they cross into ELD territory without necessarily realizing it. Track this threshold actively.

Pre-2000 vehicles, driveaway-towaway, and agricultural operations

Vehicles with engines manufactured before model year 2000 lack the ECM integration ELDs require, so those vehicles are exempt. The determination is based on engine model year, not VIN, which means engine swaps must be documented. Driveaway-towaway operators are also exempt when the vehicle being driven is the commodity delivered, specifically unladen motor vehicles with wheels on the roadway, motorhomes, or recreational vehicle trailers.

Agricultural exemptions exist under 49 CFR 395.1(k) for drivers transporting agricultural commodities from their source to a destination within 150 air miles, and for drivers hauling farm supplies from wholesale or retail distribution points to farms within 150 air miles, during state-determined planting and harvesting seasons. The exemption does not cover processed foods or hauls beyond the radius. Because state-specific seasonal windows define when it applies, verify current criteria directly with FMCSA rather than relying on prior-year assumptions.

How data transfer and roadside ELD inspections work

Many compliance failures at roadside inspections stem not from a missing device, but from drivers and carriers being unfamiliar with the data transfer process. An officer who can't receive your ELD data treats the situation the same way as no ELD at all.

Telematics vs. local transfer methods

FMCSA accepts two categories of data transfer, and a compliant ELD must support both methods within its chosen category. Telematics ELDs must support both wireless web services using SOAP protocol and encrypted email to FMCSA's designated address using S/MIME encryption. Local transfer ELDs must support both USB 2.0 and Bluetooth. A device that supports only one local method, USB but not Bluetooth, for example, fails the requirement. The inspector selects the method; the driver executes the transfer on request.

What the inspector checks at the roadside stop

The officer reviews transferred HOS records, verifies the device appears on the FMCSA registered list, and checks for active malfunction or diagnostic indicators. An unresolved diagnostic event on the screen is a citation. If the device can't transfer data at all, expect an out-of-service order. Drivers should also have reconstructed paper RODS available if an ELD malfunction occurred during the trip. Under 49 CFR 395.34, a driver whose ELD malfunctions must notify the carrier in writing within 24 hours and manually reconstruct RODS on paper logs for up to 8 days until the device is repaired or replaced.

What non-compliance actually costs you

The penalty structure under the FMCSA ELD rule is tiered by violation type and escalates sharply for repeat offenses. A single inspection can generate multiple citations simultaneously. Here's how the fine ranges break down:

Ongoing recordkeeping violations can reach $1,584 per day with a total cap near $15,846 per violation. For small carriers, those figures can represent a significant portion of monthly operating margin when combined with the revenue lost during any resulting downtime.

CSA score damage and the operational fallout

Beyond fines, ELD violations carry weighted severity scores inside FMCSA's Safety Measurement System. Most non-OOS ELD violations are expected to carry a weight of 1, while out-of-service ELD failures step up to a weight of 2. A pattern of violations raises your CSA percentile, which increases inspection frequency and creates real exposure on insurance renewals. Out-of-service orders bench a driver for a minimum of 10 hours, and for a small fleet running a time-sensitive load, that downtime often costs more than the fine attached to it.

How to select and deploy a compliant ELD solution

What to look for when evaluating an ELD

Start with the FMCSA registered list. If a device isn't on it, the evaluation stops there. Once you've confirmed registration, verify the following before committing to a device:

• Automatic diagnostic alerts when required data elements are missing
• Support for both transfer methods within the device's category: telematics devices must support both SOAP web services and encrypted email; local transfer devices must support both USB 2.0 and Bluetooth
• Real-time HOS monitoring with violation alerts before hours are exhausted
• Disconnect notifications so you know immediately when the ELD loses its ECM connection
• Malfunction documentation workflows so drivers know exactly what to do when something fails on the road

Also confirm that the vendor has a process for notifying customers when device registration status changes. An ELD that was compliant when you bought it can be removed from the FMCSA list if the manufacturer falls out of compliance, and that becomes your problem during the next inspection.

Why growing carriers are consolidating ELD compliance into their TMS

Separate ELD devices, standalone HOS dashboards, and manual compliance tracking create the kind of fragmentation that makes violations harder to catch before they happen. When a disconnect alert lives in one system, the driver's load assignment lives in another, and settlements run through a spreadsheet, things fall through the cracks. The visibility often isn't there to catch a malfunction before it becomes a citation.

Spotter.ai is designed to address that problem by building ELD compliance directly into the TMS. Disconnect alerts and load assignments share the same dashboard, and HOS status sits alongside driver performance metrics and payroll, without logging into a second or third system. For a fleet manager trying to stay DOT compliant without building a dedicated back-office team, that kind of consolidation is aimed at preventing the operational gaps that create violations in the first place.

Your ELD compliance checklist

Before your next dispatch cycle, work through this decision tree:

• Determine RODS requirement. Confirm whether each driver is required to maintain Records of Duty Status. If yes, an ELD is required unless a specific exemption applies.
• Check exemption criteria. Evaluate your fleet against short-haul radius limits, the 8-day rolling count, vehicle model year, and operation type.
• Verify device registration. Confirm every device in use appears on the FMCSA registered ELD list as currently active.
• Confirm transfer method support. Verify each device supports both transfer methods within its category, not just one.
• Brief drivers on malfunction protocol. Make sure drivers know the procedure: written carrier notification within 24 hours and immediate paper RODS reconstruction.

Understanding what are the ELD requirements for trucking companies in the US is the foundation, but the bigger operational risk isn't picking the wrong device, it's managing ELD compliance in isolation from the rest of your fleet operations. When your electronic logging data, HOS status, and disconnect alerts all live in separate tools, small issues compound into inspection failures.

Spotter.ai brings ELD compliance into the same operational view as dispatch, driver hours, and settlements, giving you the visibility to act before a malfunction becomes a citation or a missed threshold becomes an out-of-service order. If you're evaluating how to consolidate your compliance and operations into one platform, request a demo and see what integrated fleet management looks like in practice.