Key takeaways:
- An electronic logging device (ELD) is required for many drivers who must prepare records of duty status (RODS), but the duty to use an ELD depends on the driver, vehicle, trip, and applicable exception.
- Short-haul operations can be exempt from RODS when every condition is met. Other exceptions, including the rolling 8-days-in-30, driveaway-towaway, and pre-2000 provisions, may remove the ELD requirement while leaving a duty to prepare RODS.
- FMCSA requires carriers to use a device on its registered ELD list. Providers self-certify their devices; registration is not FMCSA certification or endorsement.
- Core ELD functions are different from optional GPS tracking, telematics, video, routing, maintenance, IFTA, DVIR, and fleet-management tools.
- Compare total cost rather than a headline price. Include hardware, subscriptions, activation, connectivity, installation, training, support, replacements, contract terms, and optional features.
What Is an Electronic Logging Device?
An electronic logging device synchronizes with a commercial motor vehicle’s engine to record driving time and other data used in a driver’s RODS. The device supports hours-of-service recordkeeping, but it does not decide whether a trip is legal, prevent every violation, or guarantee compliance.
Drivers and motor carriers remain responsible for accurate records and for following the applicable hours-of-service rules. An ELD also is not automatically a complete fleet-management system. A vendor may bundle extra capabilities, but those features should be evaluated separately.
Who Must Use an ELD?
The federal ELD rule generally applies when a driver is subject to 49 CFR Part 395 and must prepare RODS under 49 CFR 395.8. That analysis comes before device selection.
Federal coverage depends on the motor carrier, driver, vehicle, commerce, and trip. A vehicle can fall within the federal commercial-motor-vehicle definition based on weight, passenger design or use, or placarded hazardous-material transportation. State intrastate rules may differ.
For property-carrying drivers subject to 49 CFR 395.3, the familiar limits include up to 11 hours of driving after 10 consecutive hours off duty and no driving beyond the 14th consecutive hour after coming on duty. The 30-minute break is generally triggered after eight cumulative hours of driving without at least a 30-minute interruption. These limits are not an ELD feature; they are operating rules that the driver and carrier must follow.
Short-Haul Operations
The short-haul provision in 49 CFR 395.1(e)(1) exempts a qualifying driver from RODS and supporting-document requirements for that operation. In general, the driver must operate within a 150 air-mile radius of the normal work-reporting location, return to that location and be released within 14 consecutive hours, receive the required off-duty time, and have the carrier maintain accurate time records for six months.
Crossing a state line does not by itself disqualify a driver from the federal short-haul exception. Missing any condition can require RODS, which may also trigger ELD use.
Rolling 8-Days-in-30 Exception
A driver who must prepare RODS on no more than eight days within any rolling 30-day period may use an ELD exception. This is not an exception from RODS on those days. The driver must still prepare complete records using a permitted method, and the carrier should track the rolling count carefully.
Driveaway-Towaway Operations
The driveaway-towaway exception applies when the vehicle being driven is part of the shipment being delivered. It also covers transportation of a motor home or recreational-vehicle trailer when at least one set of the transported vehicle’s wheels is on the roadway. It does not apply merely because a driver routinely delivers vehicles, and RODS may still be required.
Pre-2000 Vehicle and Engine Guidance
Section 395.8 allows manual RODS when the commercial motor vehicle was manufactured before model year 2000, based on the VIN shown on the registration. Current FMCSA guidance issued October 2, 2026 also recognizes vehicles with engines predating model year 2000, even when the vehicle VIN reflects a later model year. The carrier should keep documentation of engine or motor changes at its principal place of business.
Agricultural Operations and Covered Farm Vehicles
Agricultural relief is not a general exemption for every farm-related trip. Under 49 CFR 395.1(k), specified transportation of agricultural commodities, farm supplies, and livestock can be outside Part 395 during state-determined planting and harvesting periods and within the applicable 150 air-mile radius. Beyond that radius, RODS and ELD requirements may apply unless another exception is available.
A separate rule in 49 CFR 395.1(s) excludes drivers of qualifying covered farm vehicles from Part 395. Qualification depends on the vehicle, ownership or operation, cargo, identification, and geographic limits in the covered-farm-vehicle definition. FMCSA’s agricultural ELD guidance explains the distinction.
Core ELD Compliance Responsibilities
Use a Registered, Provider-Self-Certified Device
A carrier required to use an ELD must select the exact device model and software version from FMCSA’s registered ELD list. Providers test and self-certify their devices. FMCSA states that it does not endorse any listed ELD, and devices can later be moved to the revoked list.
Registration is a threshold compliance check, not a product-quality rating. Fleets should confirm the listing at purchase and monitor FMCSA notices after deployment.
Driver Review, Certification, and Edits
Under 49 CFR 395.30, drivers must review their ELD records, correct inaccurate information, add missing information, and certify each 24-hour record after the final required entry or correction. A driver must recertify a record after later edits.
Drivers or authorized support personnel must annotate changes and additions. A motor carrier may propose an edit only after the driver submits the record. The driver must confirm or reject the proposed change and recertify for it to take effect. Original ELD information and source data must not be erased.
Supporting Documents
Supporting documents verify on-duty-not-driving time and are separate from the materials carried in the vehicle. Under 49 CFR 395.11, they can include trip documents, dispatch records, relevant expense receipts, mobile communications, and payroll or settlement records.
Drivers generally submit supporting documents within 13 days. Subject to the rule’s exceptions, a carrier need not retain more than eight for a driver’s 24-hour period and must preserve the earliest and latest time indications when more than eight exist. The records must be matched to the corresponding RODS and retained with RODS for at least six months.
Onboard Materials and Roadside Transfer
The current in-vehicle ELD information packet must include:
- instructions describing the device’s supported data-transfer mechanisms and the steps for producing and transferring HOS records;
- instructions describing malfunction reporting and recordkeeping procedures; and
- enough blank RODS graph-grid pages to record at least eight days.
FMCSA’s 2026 final rule removed the requirement to keep the ELD operator’s manual in the vehicle, although drivers still must know how to operate the device. At roadside, a driver must produce and transfer the requested HOS records using the supported method and be able to present the current day and previous seven consecutive days. If connectivity prevents a transfer, an authorized official may review the standardized display or printout as applicable.
ELD Malfunctions
A malfunction does not suspend recordkeeping. Under 49 CFR 395.34, the driver must note the malfunction and notify the carrier in writing within 24 hours. If required records cannot be retrieved, the driver must reconstruct the current day and previous seven consecutive days and continue manual RODS when the malfunction prevents accurate recording.
The carrier must correct, repair, replace, or service the ELD within eight days of discovery or driver notification, whichever occurs first. A carrier needing more time may request an extension from the appropriate FMCSA division administrator within the rule’s deadline.
Carrier Retention and Backups
The carrier must retain RODS and required supporting documents for at least six months from receipt. ELD records must be protected against alteration, and required backup records must be maintained separately from the primary data. Access controls, driver privacy, account management, and a repeatable retrieval process should be part of the implementation plan.
Required ELD Functions Versus Optional Fleet Features
Every registered ELD must meet the technical requirements in 49 CFR Part 395, Subpart B and Appendix A. That core function centers on recording and presenting HOS data. The following capabilities may be offered by the same vendor, but they are not interchangeable:
- ELD/HOS: Engine-synchronized driving-time records, duty-status workflows, certification, edits, annotations, diagnostics, and roadside output.
- GPS tracking: Location reporting for fleet visibility. An ELD records location data required by the rule, but that does not guarantee continuous, real-time tracking.
- Telematics: Broader vehicle and operational data transmitted to a software platform, potentially including engine diagnostics and utilization.
- Video telematics: Camera footage, event detection, driver-facing or road-facing video, storage, review, and coaching workflows.
- Routing and dispatch: Assignment, route planning, navigation, ETA, messaging, and workflow tools.
- Maintenance: Service schedules, inspections, work orders, diagnostic alerts, parts, and repair history.
- DVIR: Electronic inspection-report workflows. Availability and required inspection processes depend on the operation and product.
- IFTA tools: Distance and fuel records used to support tax reporting. The fleet remains responsible for validating source data and filings.
- Fleet-management software: A broader system that may combine several modules, integrations, reports, and administrative workflows.
Do not assume that an ELD subscription includes these modules or that data from one module is automatically suitable for another purpose.
How to Compare ELD Costs
There is no dependable market-wide price that fits every fleet. Quotes vary by hardware, vehicle type, service level, contract, fleet size, connectivity, integrations, and optional modules. Build a total-cost comparison using the same scope and term for every vendor.
Total-Cost Checklist
- Hardware: Vehicle gateway, cables, adapters, mounts, tablets or phones, and spare units.
- Subscription: Per-vehicle or per-driver fees, included features, data allowances, and billing minimums.
- Activation and setup: Account creation, configuration, data migration, and professional services.
- Connectivity: Cellular plans, roaming, offline operation, and replacement SIM or device costs.
- Installation: Internal labor, professional installation, vehicle downtime, and special harnesses.
- Training and implementation: Driver, dispatcher, administrator, and maintenance-team time.
- Support and replacement: Support hours, escalation, warranties, damaged equipment, shipping, and advance replacement.
- Contract terms: Minimum term, renewal, price changes, early termination, suspension, and data-export rights.
- Integrations: API access, connector fees, development, testing, and ongoing maintenance.
- Optional features: GPS tracking, cameras, routing, maintenance, IFTA, DVIR, asset tracking, and analytics.
For a deeper framework, see Geosavi’s guide to ELD pricing, total cost, and ROI. Calculate ROI from measured, attributable results after implementation. Do not assume automatic fuel savings, insurance discounts, crash reductions, fewer violations, or a guaranteed payback period.
How to Choose an ELD
- Define the regulatory use case. Identify which drivers require RODS, which exceptions are used, and whether the fleet crosses jurisdictions with different rules.
- Verify the exact FMCSA listing. Match the device name, model, software version, provider, and supported transfer methods.
- Check vehicle compatibility. Confirm engine protocols, model years, cables, mounts, mobile operating systems, power requirements, and installation constraints.
- Test driver workflows. Evaluate login, team driving, personal conveyance and yard moves when authorized, edits, annotations, certification, unidentified driving, malfunctions, and roadside transfer.
- Separate required and optional capabilities. Price HOS compliance first, then add only the GPS, telematics, video, routing, maintenance, DVIR, IFTA, asset, or analytics modules the fleet needs.
- Evaluate administration and reporting. Review user permissions, proposed-edit workflows, alerts, supporting-document matching, backups, exports, retention, and audit access.
- Review integrations and data ownership. Confirm API scope, update frequency, failure handling, export formats, access after termination, and responsibility for data quality.
- Compare service and contracts. Check implementation help, training, support coverage, replacement process, uptime commitments, renewal, cancellation, and the total cost for the same period.
- Run a representative pilot. Include different vehicles, drivers, routes, dispatchers, and roadside-transfer scenarios before a fleetwide rollout.
Implementing an ELD System
A good implementation connects compliance policy, technology, and daily operations:
- Document which drivers and trips require ELDs and how exceptions will be verified.
- Install and configure the correct hardware for each vehicle; validate engine synchronization and location reporting.
- Train drivers to log in, select duty status, handle unidentified driving, make annotations, certify records, respond to carrier-proposed edits, transfer logs, and follow malfunction procedures.
- Train administrators on account permissions, proposed edits, supporting documents, unassigned records, retention, backups, alerts, and escalation.
- Test roadside transfer and the display or printout process before deployment.
- Define privacy, access, coaching, retention, and data-export policies for any optional telematics or video features.
- Monitor the registered and revoked ELD lists and install provider software updates after appropriate review and testing.
An ELD can reduce manual transcription and make duty-status records easier to review, but results depend on correct configuration, training, driver behavior, carrier supervision, connectivity, integrations, and operating practices.
Data Security, Privacy, and Access
Security and privacy capabilities vary by provider. Ask how data is encrypted, where it is stored, who can access it, how administrator actions are logged, how long optional data is retained, and how the fleet can export or delete data when a contract ends. Confirm how subcontractors, mobile devices, software updates, and incident notifications are handled.
Limit access according to job responsibilities and distinguish compliance review from driver coaching or performance management. Camera events, diagnostic alerts, and driver scores require appropriate context and human review; they should not automatically be treated as proof of unsafe driving, fault, or a compliance violation.
Build Compliance Around the Operation, Not a Product Claim
The right ELD is one that meets the regulatory requirement, works reliably with the fleet’s vehicles and driver workflows, supports roadside inspections, and fits the organization’s implementation and support capacity. Optional fleet tools can add value when the data and workflows are appropriate, but no device guarantees compliance, safety, savings, or operational improvement.
For help comparing device compatibility, implementation requirements, and optional fleet features, contact Geosavi. For a legal determination about an exception or specific operation, consult the current eCFR, FMCSA guidance, and a qualified transportation-compliance professional.
This article provides general information, not legal advice. Regulations and agency guidance can change, and state requirements may differ.