Key takeaways:
- FMCSA ELD compliance generally applies when a driver must prepare records of duty status (RODS) under 49 CFR 395.8. It does not apply to every commercial driver or every commercial vehicle.
- Short-haul drivers who meet every condition of the time-record exception do not prepare RODS and do not need an ELD while operating under that exception.
- Limited exceptions allow manual RODS for drivers who need RODS on no more than 8 days in any rolling 30-day period, qualifying driveaway-towaway operations, and qualifying pre-2000 vehicles or engines.
- Drivers and carriers share responsibility for accurate records. Carrier-proposed edits require driver confirmation or rejection, and the original ELD record must remain available.
- Roadside inspections, carrier investigations, and new-entrant safety audits are different processes. A violation does not automatically produce a fixed fine, safety-rating downgrade, or out-of-service order.
What FMCSA ELD Compliance Means
An electronic logging device records driving time and supports the hours-of-service recordkeeping required by 49 CFR part 395. The ELD rule did not replace the HOS limits or make ELDs mandatory for every CMV. Instead, the rule generally requires an ELD when a driver must prepare RODS under 49 CFR 395.8, unless a specific exception permits another method.
Compliance therefore starts with the operation, not the device. A carrier should determine whether part 395 applies, whether the driver must prepare RODS, and whether an ELD exception or other HOS provision applies to the trip. An ELD can improve record accuracy, but it does not decide applicability or guarantee compliance.
Who Must Use an ELD?
A motor carrier subject to 49 CFR part 395 generally must require a driver who prepares RODS to use an ELD that meets subpart B. Vehicle weight, passenger capacity, and placarded hazardous-material status can help determine whether a vehicle is a CMV, but those facts alone do not resolve the ELD question. RODS duties and applicable exceptions must also be evaluated.
When an ELD is required, the carrier must use a device on FMCSA’s registered ELD list. Providers self-certify their devices. “FMCSA-registered” is accurate; FMCSA does not certify, approve, or endorse an individual product.
For a focused applicability checklist, see when ELDs are mandatory in the United States.
ELD Exceptions and Special Provisions
Short-haul time records
The short-haul exception in 49 CFR 395.1(e)(1) exempts a qualifying driver from sections 395.8 and 395.11. A driver must operate within a 150 air-mile radius of the normal work reporting location, return there and be released within 14 consecutive hours, receive the required off-duty period between duty tours, and have carrier-maintained time records.
The carrier must retain accurate records of the driver’s reporting time, release time, total daily on-duty hours, and required prior-duty information for six months. A driver who does not satisfy every condition must prepare RODS for that day.
RODS on no more than 8 days in 30
A carrier may allow manual RODS instead of an ELD when the driver operates in a manner requiring RODS on no more than 8 days within any rolling 30-day period. This is not a calendar-month test. The carrier should be able to support the day count, and the driver must prepare compliant RODS on each day that records are required.
Driveaway-towaway operations
Manual RODS may be used when the operation is a driveaway-towaway operation and the vehicle being driven is part of the shipment being delivered. The exception also covers a driveaway-towaway operation in which the transported vehicle is a motor home or recreational-vehicle trailer. It does not cover every towing or vehicle-delivery activity, and it does not remove an otherwise applicable RODS duty.
Pre-2000 vehicles and engines
Section 395.8 permits manual RODS for a CMV manufactured before model year 2000, as reflected in the VIN on the registration. FMCSA’s revised guidance effective October 2, 2026 also states that a vehicle with an engine predating model year 2000 is excepted even when its VIN reflects a later model year. The motor carrier should keep documentation of motor and engine changes at its principal place of business. Review the current FMCSA pre-2000 guidance.
Agricultural operations and covered farm vehicles
Agriculture is not a blanket ELD exception. Under section 395.1(k), during planting and harvesting periods determined by each state, part 395 does not apply to specified transportation of agricultural commodities, farm supplies, and livestock within the applicable 150-air-mile radius. Once a driver operates beyond the exempt area, HOS and logging requirements apply unless another exception applies.
Drivers of covered farm vehicles, as defined in 49 CFR 390.5, are separately exempt from part 395 under section 395.1(s). FMCSA’s agricultural ELD guidance explains how the radius, RODS duty, and other exceptions interact.
Driver and Carrier Recordkeeping Responsibilities
Driver certification and log edits
Under 49 CFR 395.30, a driver must review the ELD record, correct inaccurate information, add missing information, and certify that each 24-hour record is true and correct. If the record is edited after submission, the driver must recertify it.
A carrier may propose edits only after the driver has submitted the record. The driver must confirm or reject each proposed change and recertify and resubmit the RODS before the carrier-proposed edit takes effect. Each change requires an annotation, and the ELD must retain the original record. Automatically recorded driving time generally cannot be converted to non-driving time, subject to limited reassignment rules such as correcting a team-driver assignment.
Submitting and retaining RODS
A driver must submit RODS to the carrier within 13 days of the 24-hour period to which the record applies. A carrier must retain RODS and required supporting documents for at least six months. Under 49 CFR 395.22, the carrier must also retain a backup copy of ELD records for six months on a device separate from the system containing the original records.
Supporting Documents
49 CFR 395.11 requires drivers to submit supporting documents within 13 days of the relevant 24-hour period or the day the driver receives the document, whichever is later. The document categories include trip records, dispatch records, certain expense receipts, fleet-management communications, and payroll or settlement records.
A carrier generally need not retain more than eight supporting documents for an individual driver’s 24-hour period. When more than eight exist, the retained group must include the documents with the earliest and latest time indications. The records must be linkable to the driver’s RODS and kept for the six-month retention period. At roadside, a driver must provide an official with supporting documents in the driver’s possession upon request, in the format possessed.
Roadside Data Transfer and Onboard Materials
At the request of an authorized safety official, the driver must produce and transfer HOS records using the carrier’s instruction sheet. A compliant ELD supports a prescribed telematics or local transfer method. The driver should follow the official’s direction and enter an output-file comment when requested.
The current text of 49 CFR 395.22(h) requires an onboard information packet containing:
- instructions for the device’s supported data-transfer mechanisms and the steps for producing and transferring HOS records;
- instructions for malfunction reporting and recordkeeping; and
- at least eight days of blank RODS graph grids.
Older resources may list a separate user manual as a fourth required packet item. It is not included in the current three-item text of section 395.22(h). If an electronic transfer fails, the driver must still be able to display the required records or provide a printout when the device supports printing. A transfer problem is reviewed in context and is not automatically proof of an HOS violation.
ELD Malfunction Procedures
Under 49 CFR 395.34, a driver must note the malfunction and give the carrier written notice within 24 hours. If necessary, the driver must reconstruct the current 24-hour period and previous seven consecutive days unless the records are already possessed or retrievable, then continue preparing manual RODS until the device returns to compliance.
The carrier must correct, repair, replace, or service the ELD within eight days of discovering the condition or receiving the driver’s notice, whichever occurs first. A carrier needing additional time must submit a signed extension request to the FMCSA Division Administrator within five days after the driver’s notice and continue following the remaining malfunction requirements. FMCSA’s malfunction guidance distinguishes a malfunction from a data diagnostic event.
Roadside Inspections, Investigations, and Safety Audits
These processes should not be treated as interchangeable:
- Roadside inspection: An authorized official reviews the driver, vehicle, HOS records, and other applicable requirements during an inspection. Findings are recorded on the inspection report.
- Offsite investigation: A safety investigator requests and reviews carrier records remotely to examine identified compliance concerns.
- Onsite focused investigation: An investigator examines selected compliance areas at the carrier’s place of business.
- Onsite comprehensive investigation: An investigator reviews the carrier’s broader safety operation. A comprehensive investigation may result in a safety rating.
- New-entrant safety audit: A separate review used to determine whether a new carrier has basic safety-management controls. It results in a pass or fail determination, not the same outcome as every investigation.
FMCSA describes the current intervention categories in its enforcement-program glossary. For practical preparation, see Geosavi’s guide to ELD compliance investigations and audits.
Violations, Penalties, and Out-of-Service Conditions
Common ELD-related findings can involve failure to use a required ELD, inaccurate or uncertified RODS, missing records, improper accounts, unidentified driving, prohibited edits or tampering, incomplete supporting documents, or failure to produce records. An underlying HOS violation is distinct from a device or recordkeeping violation even when both appear on the same inspection.
Consequences depend on the regulation, evidence, enforcement process, and current penalty schedule. A roadside finding may result in a citation or an out-of-service condition when the current criteria apply. An investigation may lead to corrective action, a notice of violation, a notice of claim asserting a civil penalty, or other enforcement. Not every finding produces a fixed fine, an automatic safety-rating downgrade, or an out-of-service order.
FMCSA guidance states that a driver required to use an ELD who is operating without one may be cited for lacking the proper RODS and placed out of service under the applicable criteria. That specific outcome should not be generalized to every ELD defect or data-transfer problem.
Selecting and Operating an ELD System
Confirm that the device is currently listed on FMCSA’s registered ELD list and compatible with the vehicles and engines in the fleet. Review the supported transfer methods, driver and support accounts, record exports, malfunction support, data retention, security, training, integrations, installation, and total cost.
Features such as GPS tracking, routing, fuel reporting, diagnostics, DVIR workflows, and driver messaging may be separate telematics functions. Their availability and results depend on the chosen product, hardware, configuration, vehicle support, data quality, and operating process. They should not be presented as guaranteed outcomes of ELD compliance.
ELD Compliance Checklist
- Determine the RODS duty for each driver and operation.
- Document the basis for each short-haul, 8-days-in-30, driveaway-towaway, pre-2000, agricultural, or covered-farm-vehicle exception.
- Use a currently registered ELD and verify vehicle compatibility.
- Maintain accurate accounts and review unidentified driving.
- Train drivers on duty status, annotations, certification, proposed edits, data transfer, and malfunctions.
- Keep the current onboard packet and eight days of blank graph grids.
- Collect, match, and retain RODS and supporting documents for the required period.
- Maintain a written malfunction process covering the 24-hour notice, reconstruction, eight-day repair period, and extension procedure.
- Test record retrieval and roadside transfer before a driver needs them.
Build Compliance Around Accurate Records
Effective ELD compliance depends on more than installing hardware. Carriers need a defensible applicability analysis, trained drivers, accurate records, documented exceptions, review controls, and a response process for transfers, edits, unidentified driving, and malfunctions.
Geosavi can help fleets compare ELD hardware, vehicle compatibility, data-transfer capabilities, and deployment requirements. Contact Geosavi to discuss an ELD implementation for your operation.