ELD malfunction contingency recordkeeping for US fleets

An electronic logging device (ELD) failure can leave a driver unable to present or record hours of service accurately. The response needs two tracks: keep a lawful record of duty status (RODS) while the unit is out of compliance, and repair or replace the ELD within the applicable time. A good contingency file shows when the problem was found, who was notified, how logs were reconstructed and what the carrier did to restore the device.

This guide applies to US drivers and motor carriers subject to the FMCSA ELD rule. It focuses on a malfunction that affects required records, not every minor data diagnostic event or every driver exemption. FMCSA's current ELD malfunction guidance and ELD malfunction FAQ explain 49 CFR 395.34. Verify the driver's eligibility, any exemption and the exact malfunction before applying the process.

Note and notify promptly

When a driver becomes aware of a malfunction, record the event, device, vehicle, time, symptoms and whether the hours-of-service data can be retrieved. Under FMCSA guidance, the driver must note the malfunction and provide written notice to the motor carrier within 24 hours. Preserve that notice and the carrier's receipt time. A phone call may help immediate dispatch decisions, but the required written or electronic notice should not disappear into an informal conversation.

Determine whether the issue is a malfunction or a diagnostic event and whether accurate RODS can still be produced. The device manual and FMCSA technical guidance can help; do not assume every warning light triggers identical logging steps. If the malfunction hinders accurate recording or presentation, the driver and carrier need the fallback records.

Reconstruct the required duty-status history

FMCSA instructs the driver to reconstruct RODS for the current 24-hour period and previous seven consecutive days, unless those records are already available or retrievable from the ELD. If the malfunction prevents accurate recording, the driver continues preparing compliant paper logs until the ELD is back in compliance. The driver should use actual supporting information—dispatch records, fuel receipts, prior ELD data and personal notes—rather than inventing a neat history.

Mark which entries were reconstructed and the sources used. Preserve the available electronic record separately. If later ELD repair restores data, reconcile differences rather than silently replacing the fallback log. The purpose is an accurate record for the driver and a safety official, not a cosmetic match between systems.

Track the carrier's repair clock

FMCSA's FAQ says the carrier must correct, repair, replace or service the malfunctioning ELD within eight days of discovering the condition or receiving the driver's notice, whichever occurs first. Log both dates. Assign a repair owner, vendor contact, appointment and expected return-to-service date. Do not start the clock only when a support ticket is opened if the carrier learned of the fault earlier.

The carrier should ensure the driver follows fallback RODS requirements while the ELD remains out of compliance. An unavailable service appointment does not itself extend the regulatory period. If more time is needed, review FMCSA's extension process promptly. FMCSA says a carrier seeking an extension must contact the relevant Division Administrator within five days after the driver notifies the carrier and provide the required information. Do not assume an extension is granted merely because a request was sent.

Keep dispatch aware of the contingency

Dispatch needs to know that the driver's logs are in fallback mode and that the eight-day deadline is approaching. Before assigning a trip, confirm the driver can maintain and present RODS and that the planned operation remains lawful. If the ELD cannot be repaired in time and no extension applies, take the necessary operational action rather than asking a driver to continue on paper indefinitely.

When a replacement ELD is installed, test that it is compliant and that the driver can access the required current and historical RODS. Keep service evidence, device identifiers and the return-to-service decision. A vendor invoice alone may not show the records are available to the driver or enforcement officer.

Example: a failed data-recording unit

A driver receives an ELD malfunction alert during a trip and cannot view a complete duty-status record. The driver notes the event and emails the carrier within 24 hours. Using available ELD exports and dispatch records, the driver reconstructs the required current and prior seven-day history and continues paper RODS. The carrier records the earlier of its discovery and notification date, books a replacement and tells dispatch the repair deadline. After installation, the coordinator checks that the unit records correctly and the required history is available. The file keeps the notice, reconstructed records, vendor work and final check.

Test the contingency before a failure

Drivers should know where to find compliant paper logs or other approved fallback tools, who receives notice and how to reconstruct records. Carriers should know how to track the repair period and request an extension if genuinely necessary. A drill can expose a missing phone number or inaccessible history before a roadside inspection does. Document the process, but keep the actual RODS and repair evidence event-specific.

The mapped Complys US DOT compliance page is a commercial context for record governance. Verify current product functions. This guide does not claim Complys is an FMCSA-registered ELD, generates compliant fallback logs, files an extension request or decides HOS compliance.

Preserve the diagnostic trail

When a device fails, record the malfunction or diagnostic event, what the driver observed, when it began and the action taken to notify the motor carrier. Keep any available ELD output and the paper or alternative record used during the interruption. A later repair should not erase the period that requires reconstruction. Distinguish a true malfunction from a single missing edit or an unfamiliar interface; the FMCSA guidance has different implications.

On return to service, identify the repaired or replacement device and check that required records were restored or retained. The carrier should review whether the driver followed the applicable contingency and whether training or maintenance needs to change. Do not claim the software itself grants an extension or that a carrier can set its own deadline; any regulatory relief must be grounded in the current FMCSA process.