ELD driving means using an electronic logging device to create and manage required records of duty status (RODS). An ELD synchronizes with a commercial motor vehicle to record driving time and other required data, but it does not decide whether a driver is subject to the hours-of-service rules, guarantee compliance, or replace the driver and motor carrier’s responsibility for accurate records.
The key question is not simply whether someone drives a commercial vehicle. It is whether the operation is subject to 49 CFR part 395 and the driver must prepare RODS under 49 CFR 395.8. Drivers who qualify for an exception may use time records or paper RODS instead of an ELD, depending on the exception.
Key Takeaways
- An ELD is generally required when a driver subject to part 395 must prepare RODS, unless a specific ELD exception applies.
- The short-haul exceptions and the rolling 8-days-in-30 exception are different rules and should not be combined.
- ELD providers self-certify and register devices with FMCSA; FMCSA does not “certify” or endorse individual ELDs.
- Drivers must review and certify records, and carrier-proposed edits do not take effect unless the driver confirms or rejects them and recertifies as appropriate.
- An ELD helps document HOS activity, but it does not by itself establish compliance with every HOS, safety, maintenance, licensing, or operating requirement.
How ELD Driving Relates to RODS and Hours of Service
The federal ELD rule is a recordkeeping rule within the hours-of-service framework. Under § 395.8(a), a motor carrier subject to part 395 generally must require each driver to record duty status for each 24-hour period. When the driver is required to use RODS, the default method is an ELD that meets subpart B, unless one of the manual-record exceptions applies.
That distinction matters:
- HOS rules set limits and required rest periods for covered operations.
- RODS document how a driver used time across off-duty, sleeper-berth, driving, and on-duty-not-driving statuses.
- An ELD is the required recording method for many drivers who must prepare RODS.
Using an ELD does not create new driving time, waive an HOS limit, or guarantee that entries are accurate. Drivers and carriers remain responsible for correct duty statuses, annotations, certifications, supporting documents, unidentified driving, and lawful dispatch decisions. FMCSA also emphasizes that the ELD rule does not change the underlying HOS rules or exceptions.
When Is an ELD Required?
A motor carrier generally must use a registered ELD when a driver is subject to part 395 and must complete RODS. The following provisions may change the recording method or remove the RODS duty for a qualifying operation.
Short-Haul Exceptions
The short-haul provisions in 49 CFR 395.1(e) exempt qualifying drivers from §§ 395.8 and 395.11. A driver using the 150-air-mile-radius provision must operate within that radius, return to the normal work reporting location, be released within 14 consecutive hours, receive the required off-duty period, and have the carrier maintain the required time records for six months.
A driver who fails to meet the short-haul conditions on a particular day may have to prepare RODS for that day. Whether an ELD is then required depends on the rolling 8-days-in-30 rule and any other applicable exception.
Rolling 8 Days in Any 30-Day Period
Under § 395.8(a)(1)(ii)(A)(1), a carrier may allow manual RODS instead of an ELD when the driver operates in a manner requiring RODS on not more than eight days within any 30-day period. This is a rolling period, not a calendar month.
This exception does not eliminate HOS or RODS obligations on the days when RODS are required. It changes the permitted recording method. If the driver requires RODS on more than eight days in the rolling 30-day period, the exception is no longer available for that operation.
Driveaway-Towaway Operations
The manual-record exception is narrow. It applies when the vehicle being driven is part of the shipment being delivered, or when the vehicle being transported is a motor home or recreational-vehicle trailer. “Driveaway-towaway operation” has a specific definition in 49 CFR 390.5. Ordinary towing, repair, roadside-assistance, or vehicle-delivery work should not be assumed to qualify without checking the definition and facts.
Pre-2000 Vehicle and Engine Guidance
The regulation permits manual RODS for a CMV manufactured before model year 2000, as reflected by the VIN on the registration. FMCSA’s revised October 2, 2026 guidance also explains that a vehicle with an engine predating model year 2000 is excepted even when the registered vehicle model year is later. The motor carrier should keep documentation of motor and engine changes at its principal place of business. See FMCSA’s current pre-2000 model-year and engine guidance.
The exception is from required ELD use, not necessarily from HOS or RODS. A carrier may voluntarily use a compliant ELD in an older vehicle.
Agricultural Operations and Covered Farm Vehicles
Under § 395.1(k), part 395 does not apply during State-determined planting and harvesting periods to specified transportation of agricultural commodities, farm supplies, and livestock within defined 150-air-mile radii. The details depend on the commodity, source or distribution point, destination, and operation.
Under § 395.1(s), the part 395 rules do not apply to drivers of a “covered farm vehicle” that meets the definition in § 390.5. That definition includes State identification as a farm vehicle, operation by a farm or ranch owner, operator, employee, or family member, qualifying agricultural use, restrictions on for-hire operation, and weight and geographic conditions.
These provisions are not blanket exemptions for every load connected with agriculture. FMCSA’s agricultural HOS and ELD guidance explains how the 150-air-mile agricultural provision, covered-farm-vehicle rules, and separate ELD exceptions interact.
Core Driver and Carrier Responsibilities
Use a Registered ELD
A carrier required to use an ELD must select a device on FMCSA’s registered ELD list under § 395.22(a). Providers self-certify that their devices meet the technical specifications and register them with FMCSA. Agency listing is not certification or endorsement. Carriers should confirm a device’s current registration status and review any revocation information before purchase and during service.
Log In and Record Duty Status Correctly
Drivers must use their own accounts, respond to ELD prompts, select the correct duty status, and provide required vehicle, trailer, shipping-document, location, annotation, and output-file information when applicable. A portable ELD must be mounted in a fixed position and visible to the seated driver while the vehicle is operated.
Review, Certify, and Correct Records
Under 49 CFR 395.30, the driver must review the record, correct inaccurate information within the ELD’s edit limits, add missing information, and certify the completed 24-hour record. Changes and additions require annotations.
A carrier may propose edits only after the driver submits the record. The driver must confirm or reject the proposed change, make the appropriate edit, and recertify and resubmit when necessary. The system must preserve the original data; an edit does not erase the event history. Automatically recorded driving time has additional edit restrictions.
Supporting Documents and Carrier Retention
Supporting documents help verify on-duty-not-driving time. Under 49 CFR 395.11, covered categories include trip documents, dispatch records, applicable expense receipts, fleet-management communications, and payroll or settlement records.
- Drivers generally must submit supporting documents within 13 days of the relevant 24-hour period or the day the document comes into their possession, whichever is later.
- A carrier generally need not retain more than eight supporting documents for a driver’s 24-hour period, subject to the rule’s details and exceptions.
- Documents must be retained so they can be matched to the driver’s RODS and must not be obscured, destroyed, or altered.
- Under § 395.8(k), carriers must retain required RODS and supporting documents for at least six months from receipt.
Separate ELD duties require a six-month backup copy of ELD records on a device separate from the original storage and protection of driver privacy consistent with sound business practices. Unidentified driving records also have a six-month retention requirement.
Roadside Transfer and Onboard Materials
When an authorized safety official requests records, the driver must produce and transfer the required HOS records using the ELD and its supported transfer method. Under the current § 395.22(h), the onboard ELD information packet consists of:
- An instruction sheet describing the supported data-transfer mechanisms and the steps to produce and transfer HOS records;
- An instruction sheet describing malfunction reporting and recordkeeping procedures; and
- Blank RODS graph-grids sufficient for at least eight days.
The current federal list no longer includes a separate operator’s manual as a mandatory fourth item. Drivers should still be trained to use the device, understand its display or printout, enter an output-file comment when directed, and follow the roadside officer’s instructions. A failed transfer does not automatically establish the underlying HOS result; the driver must still present the records through the compliant methods available for the device and circumstances.
What to Do When an ELD Malfunctions
49 CFR 395.34 assigns duties to both the driver and carrier.
Driver Duties
- Note the malfunction and provide written notice to the carrier within 24 hours.
- If the records are not already available or retrievable, reconstruct the current 24-hour period and the previous seven consecutive days on compliant graph-grid records.
- If the malfunction prevents accurate HOS recording, continue preparing manual RODS until the ELD is serviced and compliant.
- Present the manually maintained records during a roadside inspection.
Carrier Duties
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 that needs more time must submit a signed extension request to the appropriate FMCSA Division Administrator within five days after the driver provides notice and include the information required by § 395.34(d)(2).
FMCSA’s malfunction and data-diagnostic guidance provides additional operational detail. A malfunction, data-diagnostic event, connectivity problem, and ordinary user error are not interchangeable; the device indication and actual effect on accurate records matter.
Benefits of ELD Driving, Without Overpromising
An ELD can automate the capture of driving time and organize RODS, which may reduce manual transcription and make records easier to review and transfer. Alerts may help a driver or carrier identify a potential issue before a record is certified. These are recordkeeping and workflow benefits, not guarantees.
An ELD alone does not prevent fatigue, collisions, violations, or fines. It does not guarantee lower insurance costs, fuel use, labor expense, or higher productivity or profitability. Those outcomes depend on dispatch practices, driver decisions, training, vehicle condition, route and load characteristics, management processes, and optional fleet-management capabilities that may not be part of the ELD.
Features such as live GPS tracking, routing, maintenance, fuel analytics, driver scoring, and video are optional telematics services, not required ELD functions. Fleets should evaluate those features separately and measure any claimed benefit against a documented baseline.
Choosing and Implementing an ELD
- Verify registration: Confirm the exact device and software version on FMCSA’s current list and monitor its status.
- Match the operation: Review vehicle compatibility, team driving, personal conveyance and yard-move configuration, exemptions, cross-border needs, and supported transfer methods.
- Test usability: Drivers should be able to change duty status, add annotations, review unidentified driving, certify records, respond to edits, and transfer records.
- Plan for failure: Keep the required onboard materials and define support, replacement, escalation, and extension-request procedures.
- Compare total cost: Include hardware, service, connectivity, installation, training, integrations, support, replacements, contract term, renewal, and data export.
For a broader selection guide, see Geosavi’s electronic logging device guide.
Training and Ongoing Review
Training should cover more than tapping status buttons. Drivers and support staff need to understand when RODS are required, how exceptions are documented, which activities are driving or on-duty-not-driving, how to handle unassigned time, how certification and proposed edits work, how to transfer records, and what to do during a malfunction.
Carriers should periodically review account access, unidentified driving, edit practices, device registration, record retention, backup procedures, and recurring data-diagnostic events. Dispatch and safety staff should understand that ELD data supports HOS administration but does not replace a complete compliance program.
Frequently Asked Questions
Does every commercial driver need an ELD?
No. ELD use generally follows the duty to prepare RODS under part 395, and specific exceptions may allow time records or manual RODS. The operation must be evaluated against the actual rule.
Is a short-haul driver automatically exempt from all HOS rules?
No. A qualifying short-haul driver is exempt from the RODS and supporting-document requirements identified in § 395.1(e), but must meet every condition of the applicable provision and remains subject to the HOS requirements that still apply.
Can a carrier edit a driver’s ELD record?
A carrier may propose an edit after submission, but the driver must confirm or reject it and recertify as required. Original data must remain preserved.
How long must a carrier retain ELD records?
Required RODS and supporting documents must generally be retained for at least six months from receipt. ELD backup and unidentified-driving requirements also use a six-month period.
What happens if the ELD fails?
The driver must notify the carrier in writing within 24 hours, reconstruct unavailable records for the current day and previous seven days, and continue compliant manual records when accurate electronic recording is unavailable. The carrier generally has eight days to restore compliance or must timely request an extension.
Conclusion
ELD driving is best understood as one part of HOS recordkeeping. The requirement depends on whether RODS are required and whether a specific exception applies. Compliance then depends on accurate entries, driver certification, controlled edits, supporting documents, roadside readiness, malfunction procedures, and carrier retention.
A registered ELD can make those tasks easier, but it cannot guarantee broader HOS or safety compliance or operational savings. Drivers and carriers should rely on the current regulation and FMCSA guidance, train users for their actual operation, and review the program as rules, equipment, and routes change.