An ELD malfunction starts three response clocks

An ELD warning on a trip is a recordkeeping problem to classify before it becomes a missed deadline. Is the device showing a data diagnostic event, an active malfunction, or both? Can it still accurately record hours of service and present the records an inspector needs? This resource explains the existing federal malfunction procedure, not a new rule or a report of a particular outage. It applies to operations subject to the ELD requirement; an exempt driver's recordkeeping duties may differ. The immediate task is to preserve an accurate duty-status history while the carrier restores a compliant device.

Start with the indicator and the underlying record. FMCSA distinguishes a data diagnostic event, which flags a data inconsistency, from a compliance malfunction, which affects device integrity or compliance. Section 395.34 directs a driver facing a diagnostic event to follow the carrier's and ELD provider's recommendations to resolve the inconsistency. A diagnostic indicator alone is not a universal order to switch to paper. But an active malfunction must be reported to the carrier in writing within 24 hours. FMCSA's guidance says that if a malfunction does not hinder accurate hours recording, the rule does not require a separate documentation process; a short-lived event cleared by the ELD may not trigger the additional malfunction reporting steps. The driver and fleet should verify the specific status and whether the hours record remains accurate instead of making either assumption from a generic alert.

When the malfunction does impair accurate hours recording, the driver's record cannot wait for a replacement tablet. Section 395.34 calls for reconstructing the current 24-hour period and the previous seven consecutive days on compliant graph-grid records unless the driver already possesses those records or can retrieve them from the ELD. The driver must continue manually preparing records of duty status under section 395.8 until the ELD is serviced and compliant again. FMCSA says a printed copy or electronic PDF can present the prior seven days when the ELD cannot, but the current and future duty-status record still needs a compliant fallback. It is a recovery of actual time, not an invitation to estimate a legal driving window from memory or restart the driver's clock.

The cab should already contain the tools for that recovery. Current section 395.22 requires the carrier to provide an onboard information packet with transfer instructions, malfunction reporting and recordkeeping instructions, and enough blank duty-status graph grids for at least eight days. A driver who cannot find those materials when the device fails has discovered a readiness gap before the repair clock even begins. Editorial inference: confirm the fault code, time and location, preserve accessible ELD records, send the written carrier notice through a retained channel, and identify who will supply missing records and blank grids. That suggested handoff is an operating method, not a federally prescribed form.

The carrier's eight-day deadline has its own starting point. Section 395.34 requires the carrier to correct, repair, replace, or service the ELD within eight days of discovering the condition or receiving the driver's notice, whichever happens first. The deadline does not start later just because the malfunction message reached a different department before dispatch. FMCSA guidance warns that routine paper or other manual logging cannot continue beyond eight days after the malfunction without an applicable extension. Editorial inference: record the earliest discovery or notification time, the affected driver and unit, the device make and serial number, the repair owner, and the planned return-to-service test. This keeps the carrier's device task separate from the driver's continuing obligation to make accurate records.

An extension is a narrow request, not an automatic ninth day. Under section 395.34, a carrier seeking more repair time must notify the FMCSA Division Administrator for its principal-place-of-business state within five days after the driver's malfunction notice. The signed request identifies a carrier representative, each affected device by make, model and serial number, the reported date and location of each failure, the repair efforts, and why more time is needed. FMCSA can grant additional time based on continued good-faith effort and may impose conditions; its determination comes in writing. FMCSA's ELD support page provides current submission instructions. Editorial inference: decide early whether parts, vendor support, or multiple affected units make an extension request necessary, and retain the request and agency response with the incident record.

A roadside check during the fault tests both halves of the handoff. The regulation requires the driver to provide the manually kept records to an authorized safety official during an ELD malfunction. FMCSA also says that if a malfunction later clears, reconstructed records still must be presented along with ELD data to show the current day and previous seven days. A repaired screen cannot erase the period when paper or another compliant record was needed. The driver should know which days are in the device, which were reconstructed, and how to present the complete sequence without double-counting or silently losing time.

Use a hypothetical terminal drill to test the response before a real failure: show the driver a diagnostic alert, then a malfunction that interrupts accurate recording. Have the driver identify the difference, locate the onboard packet, send written notice, recover the prior records, and begin a current record. Ask dispatch to mark the earliest carrier discovery, arrange repair inside eight days, and determine whether a five-day extension request is needed. Finally, have a second person assemble the current and previous seven days as an inspector would see them. This is an editorial exercise; it is not a claim that every alert demands paper logs or that the eight-day repair window waives hours-of-service limits.