A data diagnostic event signals a monitored data inconsistency; a malfunction is a defined failure that can prevent the ELD from meeting a technical requirement. The icon alone is not enough—drivers and carriers should open the detail, follow the documented procedure, and preserve the event record.
What this means for your fleet
Give drivers a two-path response card: capture the code and context for either event, then follow the stricter malfunction workflow when the device indicates a malfunction or cannot produce a compliant record.
Driver and carrier response
A data diagnostic event flags a monitored inconsistency and normally follows the carrier’s and provider’s resolution procedure. A malfunction is a defined failure the carrier must correct.
Report an ELD malfunction to the carrier in writing within 24 hours, even if HOS recording remains accurate. FMCSA guidance excepts an event from additional reporting when it does not affect HOS and the ELD clears it itself. If accurate recording is hindered, reconstruct the current day and previous seven days unless the records are already available or retrievable, and maintain permitted manual records until service is restored. The carrier must correct the malfunction within eight days of discovery or driver notification, whichever comes first, unless an extension applies.
What to check
| Check | How to verify |
|---|---|
| 1. Open the event details | Capture the exact icon, event detail, code, date, time, vehicle, driver, device/app version, and affected functions. |
| 2. Record code time and vehicle | Keep the original event record and a timeline showing when the code appeared, who was notified, and what the vehicle was doing. |
| 3. Check whether required functions still work | Test required recording, display, transfer, location, engine synchronization, and account functions; record each result. |
| 4. Notify the carrier under policy | Preserve the driver’s notice, carrier acknowledgment, policy deadline, assigned owner, and escalation outcome. |
| 5. Follow reconstruction and repair steps when required | Keep reconstructed records, repair ticket, repair date, supporting documents, cleared-event evidence, and repeat test. |
Common failure modes
- Ignoring a diagnostic until inspection.
- Calling every warning a malfunction.
- Rebooting before capturing evidence.
Limits and exceptions
Use this guide to plan your checks; it does not determine whether a legal exception applies, certify a record, or guarantee compliance, safety, savings, or audit results. Preserve original ELD records and edit history. Use the current rules to determine applicability and the manual for your installed device for operating instructions.
Sources and review date
Reviewed August 10, 2026. Check the latest rules and product information before changing your procedures or signing a contract.
- ELD malfunction and data-diagnostic responsibilities — Federal Motor Carrier Safety Administration.
- FMCSA ELD resources for carriers and drivers — Federal Motor Carrier Safety Administration.
- Factor ELD products, plans, and support — Factor ELD.
Discuss your ELD workflow
Ask Factor ELD to demonstrate the workflow on your installed system. Have the driver, vehicle, trip details, and original ELD record ready. A qualified compliance reviewer should determine how the current rules apply to the trip.