Compliance

Paper Records During an ELD Malfunction

Factor ELD explains how to organize records when an ELD malfunction requires the carrier’s fallback procedure. Separate the device problem from the driver’s recordkeeping duties so the required history stays available during repair.

Factor ELD

Use the current malfunction procedure

49 CFR 395.34 requires a driver to note an ELD malfunction and give the carrier written notice within 24 hours. The driver must reconstruct the current 24-hour period and previous seven consecutive days on compliant graph-grid records unless those records are already possessed or retrievable, and continue the required manual records until the ELD is serviced and compliant.

A data diagnostic event is not automatically the same as an ELD malfunction. The rule directs the driver to follow the carrier’s and provider’s recommendations for a diagnostic inconsistency. Preserve the exact message and have the condition identified instead of deciding only from a warning color.

Assemble the fallback record packet

ItemWhat to retain
Malfunction noticeDevice, vehicle, time, symptoms and written notice to the carrier
History inventoryWhich required dates are already available and which must be reconstructed
Reconstructed recordsAccurate graph-grid records for the missing required periods
Continuing recordsThe manual record maintained during the applicable fallback period
Recovery handoffRepair details, the return-to-service check and how both record sets remain accessible

For example, if the driver can retrieve the required earlier days but cannot reliably record the current day, first inventory what is actually available. Do not discard retrievable history or invent events to fill a gap. Use the relevant supporting information and carrier procedure to reconstruct accurate records where required.

Assign the repair deadline separately

The carrier must correct the malfunction within eight days of discovery or driver notification, whichever occurs first, under 395.34(d). Any extension follows the specified FMCSA process; submitting a support ticket is not itself an extension. Keep the date and responsible person visible to the fleet.

Returning to electronic records should include a review of the transition point, missing periods and duplicate entries. Preserve originals and the paper records; do not erase the malfunction history after the connection returns. ELD Malfunctions vs Diagnostic Events. ELD Issues at Roadside: A Driver's Response Checklist.

Paper-record questions

Do I have to recreate days that are still retrievable?

The reconstruction provision has an exception for records already possessed or retrievable from the ELD. Verify actual access before deciding which periods need reconstruction.

Can paper logs be used indefinitely after a device problem?

No. The carrier must meet the applicable repair or authorized extension requirements while maintaining the required records.

Prepare your fallback workflow with Factor ELD

Contact Factor ELD to review ELD equipment, support and the malfunction-record workflow for your fleet. Ask the team to demonstrate where drivers find the instructions for the proposed device and app version.

support@factoreld.com
(330) 537 8151

Consent