Skip to main content

ELD Mandate Compliance: What Every Owner-Operator Needs to Know

Reviewed by Ahmad Qazi, Founder & Editorial DirectorUpdated Oct 4, 2026
FMCSA & Regulations

ELD Mandate Compliance: What Every Owner-Operator Needs to Know

FMCSA & Regulations18 min readBy USA Trucker Choice Editorial TeamPublished March 23, 2026Updated October 4, 2026
ELDELD mandateFMCSAcomplianceelectronic logging deviceowner-operator
Share:

What Is the ELD Mandate and Who Must Comply?

The ELD mandate is a federal regulation under 49 CFR Part 395, Subpart B, requiring most commercial motor vehicle (CMV) drivers who are required to maintain records of duty status (RODS) to use an electronic logging device. The rule was finalized in December 2015, with a phased implementation that reached full enforcement on December 16, 2019, when all grandfathered automatic on-board recording devices (AOBRDs) had to be replaced with registered ELDs.

The mandate applies broadly. If you operate a CMV as defined under 49 CFR 390.5 — generally a vehicle with a GVWR of 10,001 pounds or more, transporting hazardous materials requiring placards, or carrying 16+ passengers — and you are required to keep RODS for any period, you must use a registered ELD. This includes owner-operators, company drivers, and lease-purchase drivers across all motor carrier types.

The FMCSA's goal was straightforward: eliminate paper log fraud. Before the mandate, studies estimated that up to 35% of paper logs contained some form of inaccuracy or falsification. ELDs connect directly to the vehicle's engine control module (ECM) and automatically record engine hours, vehicle movement, miles driven, and duration of operation. This makes it virtually impossible to drive undetected.

As of early 2026, the FMCSA maintains a list of over 900 registered ELD devices on its website (ai.fmcsa.dot.gov/ELD/List). However, registration does not mean certification or approval — the FMCSA does not test or certify ELDs. Manufacturers self-certify that their devices meet the technical specifications in 49 CFR 395.26. This distinction matters: if your registered ELD later fails to meet technical requirements during an inspection, you are still responsible for the compliance failure.

What 49 CFR 395 Actually Requires

The ELD duty sits in 49 CFR 395.8(a). It does not replace the hours-of-service limits. FMCSA's ELD page says the electronic logging device rule was congressionally mandated as part of MAP-21, and that an ELD synchronizes with a vehicle engine to automatically record driving time so records of duty status are easier to track, manage, and share. That page also says the ELD final rule does not change any of the basic hours-of-service rules or exceptions, and that the website is not a substitute for the rule. The contact line printed there is ELD@dot.gov and 800-832-5660.

Under 49 CFR 395.8(a)(1)(i), subject to paragraph (a)(1)(ii), a motor carrier operating commercial motor vehicles must install and require each of its drivers to use an ELD to record the driver's duty status in accordance with subpart B, no later than December 18, 2017. Section 395.20(b) says an ELD used after December 18, 2017 must meet the requirements of subpart B. The opening sentence of 395.8(a)(1) excepts a private motor carrier of passengers (nonbusiness), as defined in 49 CFR 390.5.

Section 395.8(a)(1)(ii)(A) is the manual-record permission. A motor carrier may require a driver to record duty status manually, rather than with an ELD, if the driver is operating a commercial motor vehicle in one of these ways: in a manner requiring a record of duty status on not more than 8 days within any 30-day period; in a driveaway-towaway operation in which the vehicle being driven is part of the shipment being delivered; in a driveaway-towaway operation in which the vehicle being transported is a motor home or a recreation vehicle trailer; or a vehicle that was manufactured before model year 2000, as reflected in the vehicle identification number as shown on the vehicle's registration. Those four are the permissions written in that paragraph. This section does not add a short-haul mileage, an agricultural season, or a temporary industry waiver. Those topics are in other parts of the regulations and are not restated here as a new exemption list.

A driver must record duty status by one of the methods in 395.8(a)(1) and submit that record to the motor carrier within 13 days of the 24-hour period (395.8(a)(2)). The carrier keeps records of duty status and supporting documents for not less than 6 months from the date of receipt (395.8(k)(1)). The driver keeps a copy of each record of duty status for the previous 7 consecutive days and must have it available for inspection while on duty (395.8(k)(2)). No driver or motor carrier may make a false report in connection with a duty status. No one may disable, deactivate, jam, or otherwise tamper with an ELD so that it does not accurately record and retain required data, and no one may permit or require someone else to do that (395.8(e)).

A carrier required to use an ELD must use only an ELD on FMCSA's registered ELDs list, which 49 CFR 395.22(a) says is accessible at www.fmcsa.dot.gov/devices. Appendix A to Subpart B says it specifies the minimal requirements for a provider to build and certify that its technology is compliant. The driver's license number or Social Security number must not be used as, or as part of, the username on the ELD account (395.22(c)(2)). If the driver uses a portable ELD, the carrier must mount it in a fixed position during operation and keep it visible to the driver in the normal driving position (395.22(g)).

The vehicle must carry an ELD information packet with three items: an instruction sheet describing the data-transfer mechanisms that ELD supports and the steps to produce and transfer hours-of-service records to an authorized safety official; an instruction sheet for malfunction reporting and recordkeeping during malfunctions; and a supply of blank driver's records of duty status graph-grids sufficient for a minimum of 8 days (395.22(h)). The carrier must retain, for 6 months, a backup copy of the ELD records on a device separate from the one that stores the original data (395.22(i)(1)).

Section 395.26(b) lists what the ELD automatically records: date, time, CMV geographic location information, engine hours, vehicle miles, driver or authenticated user identification data, vehicle identification data, and motor carrier identification data. If the vehicle is in motion and there has not been a duty-status change or another intermediate recording in the previous 1 hour, the ELD records an intermediate log of those same elements (395.26(d)(1)). When the record is created during authorized personal use, engine hours and vehicle miles are left blank, and location is recorded with a single decimal point resolution, which the section describes as approximately within a 10-mile radius (395.26(d)(2) and 395.26(i)).

Appendix A section 4.3.1.5 says ELD time must be synchronized to Coordinated Universal Time and the absolute deviation must not exceed 10 minutes. Section 4.3.1.6 says a valid position measurement must be accurate to plus or minus 0.5 mile, and that measurement accuracy combined with the reporting precision means position reporting accuracy will be on the order of plus or minus 1 mile during commercial operation. During personal use, reporting precision is reduced to tenths of a degree. Section 4.3.1.1 says the ELD must be powered and fully functional within 1 minute of the engine receiving power and must stay powered while the engine is powered. Section 4.2 says an ELD used in a model year 2000 or later CMV that has an engine ECM must link to that ECM when the engine is powered. If the vehicle does not have an ECM, the ELD may use alternative sources, within the accuracy requirements in section 4.3.1.

A carrier may configure two special driving categories: authorized personal use, and yard moves (395.28(a)). The driver must select the category before the status starts, deselect it when the status ends, and annotate the record when the ELD prompts. The four duty statuses the driver selects are off duty, sleeper berth (only if a sleeper berth is used), driving, and on-duty not driving (395.24(b)).

The driver must certify the record for every 24-hour period by selecting Agree immediately after this statement: "I hereby certify that my data entries and my record of duty status for this 24-hour period are true and correct." Certification is required immediately after the final required entry for that period is made or corrected (395.30(b)(2)). If edits are needed after the driver submits the record, the driver must recertify (395.30(b)(4)). A carrier may request edits only after the driver has submitted the records, and those edits take effect only if the driver confirms them, makes them, and recertifies. Edits requested by anyone other than the driver require the driver's electronic confirmation or rejection (395.30(d)). A carrier may not coerce a driver to make a false certification (395.30(e)). The carrier must not alter or erase, or permit or require alteration or erasure of, the original hours-of-service information, the source data streams, or information in an ELD that uses that original information (395.30(f)).

If nobody is logged in, the ELD must associate movement with a single account labeled Unidentified Driver as soon as the vehicle is in motion (395.32(a)). When the driver logs in, the driver must review unassigned driving time and either assume the records that belong to that driver or indicate that the records are not attributable (395.32(b)). The carrier must annotate why the time is unassigned or assign the record to the correct driver, retain unidentified driving records for each ELD for at least 6 months from receipt, and make those records available during an inspection, audit, or investigation for the period ELD records are required (395.32(c)).

If the ELD malfunctions, 395.34(a) requires the driver to note the malfunction and give the motor carrier written notice within 24 hours; reconstruct the current 24-hour period and the previous 7 consecutive days on graph-grid paper logs that comply with 395.8, unless the driver already has the records or they can be retrieved from the ELD; and continue a manual record until the ELD is serviced and brought back into compliance. During an inspection while the malfunction continues, the driver provides those manual records (395.34(b)). The carrier must take action to correct the malfunction within 8 days of discovery or of the driver's notification, whichever occurs first (395.34(d)(1)). A carrier that needs longer must notify the FMCSA Division Administrator for the state of the carrier's principal place of business within 5 days after the driver gives notice under 395.34(a)(1). The request must be signed by the carrier and must contain the name, address, and telephone number of the representative who files it; the make, model, and serial number of each ELD; the date and location of each malfunction as the driver reported it; and a concise statement of the good-faith effort to repair, replace, or service the units, including why more than 8 days is needed (395.34(d)(2)). A request that meets paragraph (d)(2) is deemed in compliance with 395.8(a)(1)(i) and 395.8(a)(2) until FMCSA makes its determination, if the carrier and driver continue to meet the other requirements of that section (395.34(d)(5)). The section does not say the driver must stop operating on day 8 while a qualifying request is pending.

Drivers must be able to access their own ELD records. The carrier must not use a process that forces the driver to go through the carrier to obtain copies if those records exist on, or are automatically retrievable through, the ELD the driver operates (395.36(a)). On request, the carrier must also provide access to copies of the driver's own ELD records that are not available that way, during the retention period in 395.8(k) (395.36(b)).

Sources read for this section on October 4, 2026: the eCFR text of 49 CFR Part 395 Subpart B, including the Appendix A sections cited above, and 49 CFR 395.8; and FMCSA's ELD page at https://www.fmcsa.dot.gov/hours-service/elds/electronic-logging-devices. No fine amount was added. The eCFR pages read for this update do not state a civil penalty figure for an ELD violation.

Technical Requirements: What Your ELD Must Do

A compliant ELD must meet specific technical requirements defined in 49 CFR 395.26. Understanding these requirements helps you evaluate devices and avoid purchasing a unit that could leave you non-compliant during an inspection.

At its core, an ELD must synchronize with the vehicle's ECM to automatically record engine power status (on/off), vehicle motion status (moving/stopped at 5 mph threshold), miles driven, engine hours, date and time (with automatic UTC synchronization), and vehicle location (latitude/longitude with accuracy of plus or minus 1 mile during normal operation). The device must capture this data at every change of duty status, at 60-minute intervals during driving, and when the vehicle's engine is powered on or off.

The ELD must support all four RODS duty status categories: off-duty, sleeper berth, driving, and on-duty not driving. When the vehicle is in motion, the ELD must automatically record driving time unless, before the vehicle moves, the driver has set the duty status to off duty and indicated authorized personal use, or set it to on-duty not driving and indicated yard moves (Appendix A to Subpart B, section 4.4.1.1). The in-motion speed threshold must not be configurable to greater than 5 miles per hour. Once the vehicle is in motion, it stays in motion until speed falls to 0 miles per hour and stays at 0 for 3 consecutive seconds (section 4.3.1.2). If duty status is still driving and the vehicle has not been in motion for 5 consecutive minutes, the ELD must prompt the driver to confirm continued driving or enter the proper duty status. If the driver does not respond within 1 minute, the ELD must switch the status to on-duty not driving. Those time thresholds must not be configurable (section 4.4.1.2).

On request by an authorized safety official, the driver must produce and transfer hours-of-service records from the ELD (49 CFR 395.24(d)). Appendix A to Subpart B names four data-transfer mechanisms: wireless transfer via web services (section 4.10.1.1), wireless transfer through email (section 4.10.1.2), USB 2.0 (section 4.10.1.3), and Bluetooth (section 4.10.1.4). The rule text checked for this update does not add a separate date that makes wireless transfer newly mandatory in mid-2026. What the carrier must keep in the cab is an instruction sheet describing the transfer mechanisms that particular ELD supports and the steps to produce and transfer the records (49 CFR 395.22(h)(1)).

The display requirements specify that an ELD must show the driver's RODS in a graph grid format that mirrors the traditional paper log format. The display must show the current 24-hour period plus the previous 7 days, and include the driver's name, vehicle information, carrier information, and odometer readings. Many modern ELDs display this information on a smartphone or tablet app paired with the hardware device via Bluetooth.

Looking for Dispatch Services?

Our expert team has reviewed and ranked the top dispatch companies so you can make an informed decision.

See Top-Rated Dispatch Companies

Choosing the Right ELD: What Actually Matters

With over 900 registered ELDs on the market, choosing the right device can feel overwhelming. Price points range from under $100 for hardware-only units to over $50/month for full fleet management platforms. The right choice depends on your operation's size, complexity, and needs beyond basic compliance.

For solo owner-operators running one truck, cost-effectiveness is typically the priority. Devices like the Garmin eLog (around $250 hardware, no monthly fees), ELD Rider (approximately $20/month subscription with minimal hardware), or the Motive Vehicle Gateway (starting at $25/month) offer solid compliance without the overhead of enterprise features. The key is choosing a device with reliable ECM connectivity for your truck's make, model, and year — compatibility issues are the number one complaint among owner-operators.

For small fleets (2-20 trucks), the value equation shifts toward devices with fleet management capabilities. Platforms like Samsara, Motive (formerly KeepTruckin), and GPS Trackit bundle ELD compliance with GPS tracking, dispatch integration, IFTA fuel tax reporting, DVIR (Driver Vehicle Inspection Report) management, and driver performance monitoring. Monthly costs typically run $25-45 per vehicle, but the operational efficiency gains — particularly automated IFTA calculations and real-time visibility — often justify the premium.

Regardless of fleet size, prioritize these factors: ECM compatibility (verify with the manufacturer for your specific truck before purchasing), customer support quality (check reviews — a device is worthless if you can't get help during an inspection), data transfer reliability (test both Bluetooth and USB/email methods), driver app usability (your drivers will use this daily), and update frequency (the FMCSA periodically updates technical specifications, and your provider should push firmware updates promptly).

Avoid devices that are not on the FMCSA's registered ELD list. During a roadside inspection, the officer will verify your device against this list. If your ELD is not registered, or if it was registered but subsequently revoked (the FMCSA does remove non-compliant devices), you will be cited for operating without an ELD — a violation that results in being placed out of service.

Common ELD Compliance Issues and How to Avoid Them

Even with a registered ELD installed and functioning, drivers frequently encounter compliance issues during inspections. Understanding the most common problems helps you avoid them.

Unassigned driving time is the most frequently cited ELD-related issue. This occurs when the ELD records vehicle movement that isn't assigned to a specific driver — typically when a driver forgets to log in before moving the vehicle, or when a yard jockey or mechanic moves the truck without logging in. FMCSA regulations require carriers to review unassigned driving time and assign it to the appropriate driver. Inspectors specifically look for patterns of unassigned time, which can suggest log manipulation.

ELD malfunction procedures trip up many drivers. Under 49 CFR 395.34, if your ELD malfunctions (loses connectivity, displays errors, or fails to record accurately), you must note the malfunction on the RODS, continue to manually record your RODS on paper or a printout for the remainder of the day and the next 7 days, notify your carrier within 24 hours, and have the malfunction repaired or replaced within 8 days. Failing to carry paper log supplies as a backup is itself a violation — always keep blank graph paper logs in your cab.

Data transfer failures during inspections are increasingly common. If an officer requests data via Bluetooth and your device fails to connect, they'll ask you to use the backup method (USB/email). If both fail, the officer may record a data transfer violation. Keep your ELD's Bluetooth enabled before approaching inspection stations, ensure your device firmware is current, and know how to initiate the backup transfer method.

Editing and annotation issues also draw scrutiny. Drivers are allowed to edit their ELD records (for example, to change on-duty not driving time that was auto-recorded as driving during a slow yard movement), but every edit must include an annotation explaining the reason. The original record is preserved alongside the edit. Officers can view the edit history, and excessive edits — particularly those that consistently reduce driving time — will raise red flags. Be honest and consistent with your annotations: "Yard movement at shipper facility" is far more credible than vague entries like "correction."

What Happens During an ELD Inspection

Knowing exactly what to expect during an ELD inspection reduces stress and helps you present your records confidently. The inspection process follows a structured protocol defined in the FMCSA's inspection procedures guide.

When an officer begins the HOS portion of the inspection, they will first verify that you have an ELD installed and that it's on the FMCSA's registered device list. They'll ask you to display your current day's RODS in graph grid format. The officer will examine the grid for obvious issues: proper recording of duty statuses, no unexplained gaps in the record, and consistency with your current situation (if you've been driving for 4 hours, your log should show approximately 4 hours of driving time).

Next, the officer will typically request the previous 7 days of records, either by viewing them on your display or requesting a data transfer. During the review, they'll check for compliance with all HOS limits — the 11-hour driving limit, 14-hour window, 30-minute break rule, and 60/70-hour cumulative limits. They'll also verify that your ELD data is consistent with supporting documents. If your bill of lading shows you were loaded at a facility in Memphis at 2:00 PM, but your log shows you were in Nashville at that time, there's a problem.

The officer will check for proper ELD functionality including: correct time zone settings, accurate vehicle odometer readings (compared against the physical odometer), proper driver identification, and evidence that the device is connected to the ECM (not running in an unconnected or yard mode state while the vehicle is on a public road).

If violations are found, the officer will document them on the inspection report form. For OOS violations, they'll note the specific off-duty time required before you can resume driving. You'll receive a copy of the report. Remember: sign the report to acknowledge receipt, but understand that your signature is not an admission of guilt. If you believe the violation was issued in error, note your disagreement respectfully and file a DataQs challenge after the inspection.

ELD Data Privacy and Driver Rights

ELD data raises legitimate privacy concerns, and drivers have specific rights regarding how their data is collected, stored, and used. Understanding these rights protects you from potential employer overreach.

Under 49 CFR 395.22, a motor carrier must not use ELD data to harass a driver. The regulation specifically states that carriers cannot use ELD data to take adverse action against a driver for legitimate rest breaks, off-duty time decisions, or for reporting a malfunction. If you believe your carrier is using ELD data to pressure you into driving beyond legal limits or to punish you for taking required breaks, you can file a complaint with the FMCSA's National Consumer Complaint Database (NCCDB) or call the FMCSA safety hotline at 1-888-DOT-SAFT (1-888-368-7238).

Location tracking during off-duty time is a common concern. When you are off-duty, your ELD is not required to record your location. However, many ELD platforms double as fleet management tools with continuous GPS tracking that operates independently of the RODS function. Whether your carrier can track you during off-duty time depends on the employment agreement and applicable state privacy laws. Some states, including California, Illinois, and Connecticut, have stronger employee privacy protections that may limit continuous tracking during non-work periods.

ELD records must be retained by the motor carrier for a minimum of 6 months. During this period, the records must be available to the FMCSA and authorized enforcement officials upon request. Drivers can request copies of their own ELD records from their carrier, and carriers must provide them within a reasonable timeframe.

For owner-operators who are both the driver and the carrier, you control your own ELD data. However, you still must retain 6 months of records and make them available during audits or investigations. Cloud-based ELD platforms typically handle this automatically, but if you use a device with local-only storage, implement a backup routine. Losing your ELD data during an audit can result in a records-keeping violation and potential adverse findings.

Need Help Finding the Right Dispatch Service?

Compare top-rated dispatch companies, read honest reviews, and find the best match for your operation — all in one place.

Compare Dispatch Companies

Managing ELD Costs as an Owner-Operator

ELD compliance represents an ongoing operational cost that owner-operators must factor into their business planning. The total cost of ELD ownership goes beyond the monthly subscription or hardware price and includes several factors that are easy to overlook.

Hardware costs range from approximately $100 for basic plug-and-play devices to $300+ for advanced units with built-in cameras, Wi-Fi hotspots, or integrated driver tablets. Some providers offer the hardware free with a service contract commitment, but be cautious — these contracts often run 24-36 months and include early termination fees of $200-500. Calculate the total contract cost versus buying hardware outright with a month-to-month subscription.

Monthly subscription fees typically range from $15 to $50 per vehicle. Basic compliance-only plans are at the lower end, while plans including GPS tracking, IFTA reporting, DVIR management, dispatch integration, and dashcam services are at the higher end. For a solo owner-operator, a $20-25/month plan that includes ELD compliance and basic GPS tracking is often the sweet spot. Features like IFTA mileage tracking can save you 2-3 hours per quarter that you would otherwise spend manually calculating state-by-state miles.

Hidden costs include: replacement hardware when devices fail (warranty terms vary significantly between manufacturers), data usage if your plan runs on your cellular data rather than a carrier SIM, tablet or smartphone replacement (many ELD apps are resource-intensive and can wear out older devices), and training time when switching between ELD providers. Switching costs are real — expect 1-2 weeks of reduced productivity as you and any co-drivers learn a new system.

The tax treatment of ELD expenses is favorable. Hardware and monthly subscriptions are fully deductible business expenses for owner-operators (Schedule C, Line 27a — Other Expenses). If you purchase a higher-end device that also serves as a GPS navigation tool or dashcam, the entire cost is typically deductible as a business equipment expense. Consult your tax professional, but don't overlook this deduction — at $300 annual subscription cost, the tax savings are modest individually but add up alongside other compliance-related deductions.

Frequently Asked Questions

Under 49 CFR 395.34(a), note the malfunction and give your motor carrier written notice within 24 hours. Reconstruct the current 24-hour period and the previous 7 consecutive days on graph-grid paper logs that comply with 395.8, unless you already have those records or can retrieve them from the ELD, and keep a manual record until the ELD is serviced and back in compliance. The carrier must correct the malfunction within 8 days of discovery or of your notice, whichever comes first (395.34(d)(1)). The in-cab packet must include blank graph-grids sufficient for a minimum of 8 days (395.22(h)(3)). If more time is needed, the carrier notifies the FMCSA Division Administrator for the state of its principal place of business within 5 days after you notify the carrier, using the contents required by 395.34(d)(2). A request that meets that paragraph is deemed in compliance with 395.8(a)(1)(i) and 395.8(a)(2) until FMCSA decides, if the other requirements of that section are still met (395.34(d)(5)). The section does not say the driver must stop driving on day 8 while a qualifying extension request is pending.
Yes, and this is an important distinction. The FMCSA does not certify or approve ELDs. The registered ELD list on the FMCSA website simply reflects manufacturers who have self-certified that their devices meet the technical specifications in 49 CFR 395.26. The FMCSA does not independently test these devices before listing them. However, the agency can and does remove devices from the list if they are found to be non-compliant. Always verify your device is currently on the list, not just that it was once listed.
Under FMCSA regulations, the ELD is not required to record your location during off-duty time. However, many carriers use ELD platforms that include continuous GPS tracking as a fleet management feature separate from the ELD function. Whether your carrier can or should track you during off-duty time depends on your employment contract, company policy, and applicable state privacy laws. States like California and Illinois have employee privacy statutes that may limit this practice. If you're concerned, review your carrier agreement and consult the privacy policy of your ELD provider.
If you operate within a 150 air-mile radius of your normal work-reporting location, return to that location at the end of each duty period, and your total duty period does not exceed 14 hours, you qualify for the short-haul exception and are exempt from both the ELD mandate and RODS requirements. You still must comply with HOS rules and your carrier must maintain time records showing your start time, end time, and total hours on duty. If you exceed the 150-mile radius or the 14-hour window even once, you must use an ELD for that day.
A solo owner-operator should budget approximately $400-800 for the first year and $200-500 annually thereafter. This includes hardware ($100-300 if purchased outright), monthly subscription ($15-35/month or $180-420/year), backup paper logs ($10-20 for a supply), and potential data costs. Some providers offer hardware-included plans at $25-40/month with no upfront cost but require 2-3 year contracts. The most cost-effective approach for a single truck is typically a mid-range device like the Garmin eLog (one-time $250, no monthly fees) or a low-cost subscription service at $15-20/month.

USA Trucker Choice Editorial Team

Our team of industry experts reviews and fact-checks all content to ensure accuracy and relevance for trucking professionals. We follow strict editorial standards and regularly update articles to reflect the latest regulations, market conditions, and industry best practices.

Found this article helpful?
Share:

Related Articles

Related Guides

Related Reviews & Comparisons

Helpful Tools