A dump-truck driver may start the day within the short-haul boundary, then cross it on a later run and need to prepare RODS. When federal Electronic Logging Device (ELD) rules apply, ELD compliance means using a device registered with the Federal Motor Carrier Safety Administration (FMCSA) that records driving time. The device synchronizes with a commercial motor vehicle's (CMV's) engine to record a driver's hours of service (HOS). Covered carriers must retain records and a separate backup for six months. They must also require drivers to certify each daily log and keep the current required materials in the cab.
For built world fleets, applicability depends on more than vehicle type. A dump truck, water truck, concrete mixer, lowboy, or equipment hauler may require an ELD. This applies when it operates in interstate commerce, and the driver must prepare records of duty status (RODS). Short-haul work and occasional paper-log use can change the answer. Vehicle age and construction-specific provisions can also affect applicability, as can state intrastate rules such as California's requirements.
This guide explains who must use an ELD, which exemptions apply, what drivers and carriers must do each day, how to handle malfunctions and revoked devices, and which compliance failures create the most risk.
What ELD Compliance Requires Under FMCSA Rules
Start with five controls. A device in the truck must remain registered and capture required engine data. The carrier must review and retain the records it produces.
Validate the Device and Engine Connection
Run these checks during procurement and after installation. Repeat them whenever software or vehicle assignments change.
Use a registered, self-certified ELD: A carrier required to use an ELD must select a device from the official Registered Devices list. Manufacturers self-certify their devices against the technical specifications. Listing confirms the manufacturer submitted that certification; it is not an independent endorsement of the device.
Compliance leaders should verify the device name, model, software version, and registration ID during procurement and then check the list regularly. FMCSA can remove a device after installation, so registration checks can't be treated as a one-time purchasing task.
Confirm engine synchronization: An ELD generally must synchronize with the commercial motor vehicle's engine to capture engine power status, motion status, miles driven, and engine hours. The technical requirements appear in Appendix A.
Test this control on every vehicle class in the fleet. A configuration that works in a highway tractor may not behave the same way after installation in a mixer, water truck, or older equipment hauler. Document reviews of missing engine data and inconsistent vehicle assignments. Apply the same review to connectivity failures before accepting the vendor dashboard.
Control Records and Driver Certifications
Review these controls at daily close and test record retrieval whenever a driver, device, or subscription changes.
Retain RODS and a separate backup: Carriers must retain each driver's RODS and required supporting records for at least six months. They must also retain a six-month backup copy of ELD records on a device separate from the system storing the original data. Drivers must also possess the current day's record and records for the previous seven consecutive days while on duty.
Build the retention plan around retrievable records and a separate backup. Confirm that records remain exportable after a driver leaves or a subscription changes. Repeat the check when you replace a device. Test the backup by retrieving a specific driver, vehicle, and date range rather than relying on a successful backup notification.
Require daily driver certification: At the end of each 24-hour period, the driver must review the ELD record and correct inaccurate entries. The driver must add missing information and certify that the record is true and correct. If later edits affect a submitted record, the driver must review and recertify it. Carrier-proposed edits require driver approval, and the original record must remain preserved under the certification and edit rules.
A practical daily close report should separate uncertified logs, rejected edits, missing annotations, and unresolved driving events. Certification is a driver action. Supervisors or AI agents should never certify a log or accept an edit on the driver's behalf.
Maintain the Current In-Cab Materials
Inspect the in-cab packet during preventive maintenance and after a vehicle moves between terminals or project teams.
Keep the current materials in the cab: Drivers must carry the current in-cab materials listed below; the operator's manual requirement changed in 2026.
Data-transfer instructions for producing and sending HOS records to an authorized safety official
Instructions covering ELD malfunction reporting and recordkeeping
Enough blank RODS graph-grid pages to record at least eight days
These current in-cab requirements apply even when drivers believe the device is reliable. Inspect packets during preventive-maintenance checks and after vehicles move between terminals or project teams.
Which Built World Drivers Must Use an ELD?
Apply the federal ELD test based on the vehicle's use and the nature of the movement. Then determine whether the driver must keep RODS.
Apply the Federal CMV Test
A vehicle must operate on a highway in interstate commerce, and its driver must be required to keep RODS. Under the federal CMV definition, the threshold includes a self-propelled or towed vehicle with a weight rating of 10,001 pounds or more.
That commonly captures dump trucks, water trucks, concrete mixers, lowboys, and equipment haulers. A lowboy moving an excavator between job sites does not become exempt merely because its load is construction equipment.
Separate Off-Road and Intrastate Work
Off-road motorized equipment is different. Backhoes, motor graders, scrapers, and compactors operating at a jobsite are not treated as CMVs when their public-road movement is not in furtherance of a transportation purpose. The federal equipment guidance distinguishes the equipment itself from trucks that transport equipment or materials.
Interstate commerce can also exist without crossing a state line when a trip is part of a broader interstate movement. Conversely, state HOS and ELD rules may govern an intrastate-only fleet and differ from the federal standard. Mixed fleets should document the rule set assigned to each terminal and driver group. They should also document vehicle assignments to support distinct rules across the company.
ELD Exemptions and Construction-Specific Provisions
Use an exemption only after documenting every condition. Several provisions reduce ELD or HOS burdens. Each provision provides a distinct form of relief.
Apply Logging-Frequency and Short-Haul Exceptions
Run these tests before dispatch when a driver usually works locally or only occasionally needs to prepare RODS.
The 8-in-30 paper-log exception
A driver who must prepare RODS on no more than eight days during any rolling 30-day period may use paper logs on those days instead of an ELD. This exception has no mileage limit. Count the days requiring RODS regardless of the number of trips or total distance traveled.
This provision can fit an operator who usually works locally but occasionally hauls equipment beyond the short-haul boundary. Track the rolling 30-day total before dispatch. Waiting until the ninth RODS day creates a preventable compliance failure.
The federal short-haul exception
A driver holding a commercial driver's license (CDL) can qualify for the federal short-haul exception by meeting all of these conditions:
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 at least 10 consecutive hours off duty between on-duty periods.
The carrier must retain accurate time records for six months.
The complete short-haul rules establish a 150-air-mile radius from the normal reporting location. Route mileage does not define the compliance boundary.
Qualifying drivers do not need paper RODS or an ELD for that day. They remain subject to applicable driving, off-duty, and weekly limits. If a driver exceeds the radius or 14-hour window, the exception is lost for that day, and the driver must prepare a full daily RODS.
Check Vehicle and Movement Exceptions
Use these tests when the vehicle predates model year 2000, or the movement is a drive-away-tow-away operation.
Pre-2000 and drive-away-tow-away exceptions
A vehicle with a pre-2000 model year, as reflected in the VIN on its registration, can qualify for the pre-2000 exception. A model-year 2000 or newer vehicle without an engine control module still requires a compliant ELD configuration if no other exception applies.
Drive-away-tow-away operations can use paper RODS when the vehicle being driven is itself part of the shipment. This does not normally cover a tractor or lowboy carrying a separate piece of equipment.
Apply Construction-Specific Provisions
Check these provisions when drivers transport construction materials or equipment or deliver ready-mixed concrete.
Construction materials and equipment provision
The construction materials provision applies to drivers used primarily to transport construction or pavement materials, construction equipment, or construction maintenance vehicles. The transport must be to or from an active construction site within the specified radius. It permits a 24-hour restart of the seven- or eight-day period under qualifying conditions.
It does not waive the 11-hour driving limit, 14-hour window, weekly limits, or ELD requirements. The construction definition generally uses a 75-air-mile radius, although a state may establish a lower radius within the permitted range for movements entirely inside that state.
Ready-mixed concrete waiting time
A ready-mixed concrete delivery driver may count at least 30 minutes spent waiting with the vehicle at a jobsite or terminal toward the required break. The driver must perform no other work during that period. This applies to a delivery vehicle whose propulsion engine powers a mixer drum that agitates the product in transit.
The provision does not automatically cover dump trucks used for concrete paving. The provision leaves ELD requirements unchanged. Ready-mix fleets still need to determine whether each driver qualifies under short-haul or another applicable exception.
Daily ELD Compliance Workflow
Use this workflow at driver login and daily close. Supervisors should review the results. The goal is to resolve exceptions while records and jobsite details are still fresh.
Validate Assignments and Unassigned Driving
Run these checks when the driver logs in and whenever unidentified vehicle movement remains at daily close.
Verify the driver, vehicle, and trailer assignment: The driver should log in under a unique account and confirm the power unit, trailer, shipping record, and applicable special driving categories. Shared credentials undermine accountability and can scatter events across the wrong records.
Review unassigned driving: When a vehicle moves without a logged-in driver, the ELD records the event under an unidentified profile. At login, the driver must review unassigned time. The driver should claim attributable events or indicate that they belong to someone else. The carrier must assign or annotate the time or explain why it remains unassigned.
Use this check whenever unassigned driving remains unresolved at daily close. Yard repositioning and trucks moving between a batch plant and washout area are common causes. Maintenance road tests can create the same issue, but each explanation still requires validation. More than 30 minutes of unidentified driving in a 24-hour period triggers a data diagnostic event under the unassigned-driving guidance.
Check HOS Limits and Special Categories
Run this review before dispatch continues when the ELD shows limited remaining time or a special driving category.
Apply the current limits: For property-carrying drivers, review the 11-hour driving limit after 10 consecutive hours off duty and the 14-hour duty window. Also review the break after eight cumulative hours of driving and the applicable 60- or 70-hour cycle. The current HOS limits continue to apply even when the ELD displays remaining time incorrectly because of a configuration or data problem.
Yard moves remain on-duty, not driving, and count toward the duty window and weekly cycle. The carrier must configure personal conveyance, and drivers may use it only when the movement qualifies. Neither label should become a convenient way to hide dispatch-directed travel.
Resolve Edits and Certify the Daily Record
Complete these steps at daily close and repeat the review if a later edit affects a submitted record.
Review edits and annotations: You cannot change automatically recorded drive time to non-driving time. Drivers may correct other eligible records, but edits require an explanatory annotation. Carrier reviewers may propose edits; drivers decide whether to accept them.
Compare suspicious gaps against dispatch records, fuel receipts, toll records, project gate logs, payroll time, and maintenance work orders. Conflicting systems create an exception that someone must investigate; on their own, they provide insufficient evidence of falsification.
Certify the daily log: After the final required entry, the driver reviews the full 24-hour record and selects the certification statement. Supervisors should monitor missing certifications and post-certification edits, but the driver retains responsibility for reviewing and certifying the record.
How to Handle an ELD Malfunction
Trigger the malfunction workflow when the ELD cannot accurately record, display, or transfer required information. A recordkeeping malfunction prevents compliant recordkeeping; a minor diagnostic notification may not.
Driver Notice and Record Reconstruction
The driver must notify the carrier in writing within 24 hours. If records are not retrievable, the driver reconstructs the current day and seven prior days on graph-grid logs, then continues using paper RODS until the device is repaired.
Carrier Repair and Documentation
The carrier generally has eight days from discovery or driver notification, whichever occurs first, to correct the malfunction. If the carrier needs more time, it must follow the extension procedure. The same requirements specify the notice, reconstruction, repair, and extension obligations.
A complete malfunction record should identify the driver, vehicle, ELD make and model, serial number, date, location, symptoms, temporary logging method, repair actions, and return-to-service test. Field teams should know where blank logs are stored before the device fails.
Prepare for Roadside Transfer and Compliance Audits
Test both roadside transfer and audit retrieval before an inspection exposes a configuration or retention failure.
Test Roadside Data Transfer
Use a transfer test after installation, software updates, device replacement, or repeated inspection failures. At roadside, the driver must be able to display or transfer the current 24-hour record and the seven-day history using the ELD's supported method.
An authorized safety official may request a telematics transfer through web services or email or a local transfer through USB or Bluetooth. The device determines whether the driver uses telematics or local transfer. Drivers should certify and annotate records before using the applicable data-transfer procedure.
Assemble Audit Records
For an audit, organize records by driver and date so reviewers can match RODS with supporting records. Required categories can include bills of lading or itineraries, dispatch records, expense receipts showing on-duty-not-driving time, mobile communications, and toll receipts. Drivers generally submit supporting records within 13 days, and carriers retain the required records for six months under the supporting-record rules.
A practical audit checklist should confirm:
Every active device remains on the registered list.
Six months of RODS and a separate backup are retrievable.
Proposed edits retain the originals and driver decisions.
Unassigned driving has an assignment or annotation.
Supporting records can be matched to the corresponding RODS.
Malfunctions show timely notice, paper logs, repair, and testing.
Roadside and six-month audit exports have been tested.
Resolve failed checklist items before an audit or roadside inspection.
Common ELD Violations and Enforcement Risks
Prioritize controls around records that are missing, false, incomplete, or impossible to verify. Common violations include driving beyond HOS limits, failing to maintain a current RODS, using no RODS when one is required, failing to review unassigned driving, missing prior days of records, unsuccessful electronic transfer, and missing malfunction materials.
False RODS and tampering carry particular risk because they undermine the reliability of the entire record. Common violation codes include false RODS violations, driving beyond the 11-hour or 14-hour limits, and failure to review unassigned driving.
Civil penalties vary by violation, circumstances, and adjustment year. A carrier may also face out-of-service action, compliance review consequences, and safety-management scrutiny. Compliance leaders should confirm the current penalty schedule directly with FMCSA rather than relying on a dollar amount carried over from an older training deck.
What Changed for ELD Compliance in 2026?
Update in-cab materials and device-monitoring workflows to account for the 2026 changes.
Update In-Cab Materials
Effective July 22, 2026, the 2026 final rule removed only the requirement to carry the ELD operator's manual in the commercial motor vehicle. The earlier in-cab checklist remains current.
Monitor Revoked Devices
Device revocations also require active monitoring. If a fleet's ELD appears on the Revoked Devices list, drivers should immediately revert to paper logs or another permitted logging method while the carrier replaces the device. Carriers generally receive 60 days to install a compliant registered device. Continued use after the deadline can be treated as having no required RODS and can lead to an out-of-service order.
Maintain a current inventory of device names, models, registration IDs, software versions, assigned vehicles, and vendor contacts. Registration monitoring should have a named owner and escalation path; an email alert without an accountable workflow is easy to miss.
Where Supplementary AI Agents Fit in an ELD Compliance Workflow
Use supplementary AI agents only after the carrier has established the governing rules and human decision owners. The carrier must also approve the source systems. ELDs remain the recordkeeping devices, drivers certify logs, and the carrier retains legal responsibility.
Connect Approved Source Systems
Before using a supplementary AI agent, confirm it can access approved ELD exports, spreadsheets, databases, email attachments, and project records through authorized methods. Do not assume compatibility with a specific ELD vendor; confirm connector or API availability before designing the workflow.
Assign Review and Decision Roles
AI agents can compare exported records and identify missing certifications. They can also assemble unresolved-driving queues and route exceptions for human review. Datagrid's Audit Agent can check supplied project files against defined audit requirements and flag compliance gaps, and Datagrid's search agents can provide quick, structured answers across connected spreadsheets, documents, databases, and web pages. People still decide whether an event belongs to a driver, whether an exemption applies, whether an edit is valid, and whether a record is ready for submission.
Source-data quality sets the boundary. Incorrect driver mappings, stale vehicle assignments, missing exports, and poorly configured rule sets will produce incomplete findings. Early workflows may also generate false positives. Compliance managers should validate agent output against sample records, document rule changes, restrict access by role, and retain a clear approval history.
Clear the ELD Exception Queue With Datagrid's Agentic AI
Datagrid's AI agents compare exported ELD records against approved source systems and route only the exceptions a compliance team actually needs to decide:
Certification and edit checks: Compare exported records against approved source systems to identify missing certifications and flag unresolved edits for review.
Unresolved-driving queues: Assemble unassigned-driving and other unresolved-event exceptions into a single queue instead of a folder of individual alerts.
Audit-ready file checks: Check supplied project files against defined audit requirements and flag compliance gaps for an operator, using the Audit Agent.
Cross-source answers: Provide quick, structured answers across connected spreadsheets, documents, databases, and web pages when a compliance manager needs to check a record fast.
Drivers still certify every log, and the carrier's compliance team still decides whether an event belongs to a driver, whether an exemption applies, and whether an edit is valid; Datagrid's agents make sure that team reviews a clean queue instead of searching for exceptions themselves.
Get started with Datagrid to run one week of ELD exports through the workflow and see what reaches your compliance team's queue.
Frequently Asked Questions About ELD Compliance
Can a Driver Operate a Truck Without an ELD?
Yes, a driver may operate without an ELD only when an applicable exemption allows it. Otherwise, federal rules require a compliant ELD when the driver must prepare RODS.
How Many Miles Can a Driver Run Without an ELD?
No universal mileage cap applies. The federal short-haul exception uses a 150-air-mile radius from the normal work reporting location and a 14-hour duty window; other exemptions depend on different conditions.
What Are the Most Common ELD Violations?
The most frequent violations involve driving beyond the 11-hour or 14-hour limits, an incomplete or missing RODS, unresolved unassigned driving, and a failed electronic data transfer at roadside. False or tampered records draw the most scrutiny because they call the entire log into question, and civil penalties vary by violation, circumstances, and adjustment year.
What Happens When an ELD Appears on the Revoked Devices List?
The carrier must move drivers back to paper logs or another permitted method right away, then install a compliant registered device before the 60-day window the FMCSA allows closes. Missing that deadline exposes the fleet to an out-of-service order, since the vehicle no longer carries a valid electronic record.
