What to do when an ELD malfunctions

Treat the malfunction as an operating event

An ELD problem can start with a frozen screen, failed connection, missing vehicle data, incorrect location, or a diagnostic code. The first mistake is waiting to see if it fixes itself. The driver should report the issue as soon as it affects accurate HOS recording. The carrier needs a clear time of discovery because that starts the response process.

Not every warning is a full malfunction. Some are data diagnostic events that point to missing or inconsistent information. Your procedure should tell drivers how to capture the message, who to contact, and whether the device can still create an accurate record.

Keep the driver legal and moving safely

If the malfunction prevents accurate HOS recording, the driver generally needs to reconstruct the current day and the previous seven days, then use paper RODS until the device is back in service. The vehicle should carry blank graph-grid records for at least eight days as part of the required ELD information packet.

The driver should know how to show the malfunction, paper records, and available electronic history during an inspection. A rushed explanation at roadside creates avoidable confusion. Practice the process before a device fails.

• Record the malfunction code, time, vehicle, and driver.
• Notify the carrier using the approved channel.
• Reconstruct required records when accurate electronic records are unavailable.
• Keep paper logs current until the ELD is restored.
• Save support tickets, screenshots, and repair details.

The carrier has a deadline

FMCSA states that a carrier must correct, repair, replace, or service a malfunctioning ELD within eight days of discovery or driver notification, whichever occurs first. If more time is needed, the carrier may request an extension from the FMCSA Division Administrator. That request has its own timing and content requirements.

Assign one person to own the issue. They should confirm the driver is logging correctly, contact the ELD provider, track the repair, preserve communications, and close the event only after accurate recording is confirmed.

Give each role a short checklist

The driver should report the fault, keep an accurate record, and remain available for troubleshooting. Dispatch should avoid assigning a trip that depends on time the driver cannot prove. Safety should verify the paper record and track the repair deadline. Maintenance or IT should document the technical fix.

Keep these checklists inside the vehicle packet and the carrier procedure. During onboarding, ask the driver to explain the steps back to the trainer. A plan that only exists in a policy folder will not help during a roadside stop at night.

Prevent a device problem from becoming a process problem

Review malfunction events monthly. Repeated power faults may point to vehicle wiring. Repeated login or synchronization problems may point to training or account setup. A high number of unresolved diagnostics may mean nobody owns the queue.

ELD Engine helps monitor diagnostic and malfunction events beside the driver log and operating context. Our team can create follow-up tasks, contact the right people, and document the timeline. The technology finds the signal. The process makes sure someone responds.