ELD Malfunctions: The 3 Things a Driver Must Do (49 CFR 395.34)

Quick answer: When an ELD malfunctions, 49 CFR 395.34 requires the driver to (1) notify the carrier in writing within 24 hours, (2) reconstruct records of duty status on graph-grid paper for the current 24 hours and the previous 7 days (unless retrievable from the device), and (3) keep paper logs until the ELD works again. The carrier must repair or replace the device within 8 days of discovering the malfunction or being told about it.

Regulatory-change disclaimer: Last reviewed July 17, 2026 against the eCFR. Confirm the current 49 CFR 395.34 and FMCSA's ELD site before relying on this. Not legal advice.

Malfunction vs. data diagnostic — know which one you have

The ELD technical standard (49 CFR Part 395, Subpart B and its Appendix A) defines two families of events, and your duties differ:

• Data diagnostic events — the device flags a data issue (for example, missing required data elements or unidentified driving). You resolve or annotate; the device still works.
• Malfunctions — the device can no longer reliably record or transfer duty status (power, engine-synchronization, timing, positioning, data recording, or data transfer compliance failures). This is what triggers 395.34.

The device is required to show a visible malfunction indicator. When that indicator is on, assume 395.34 applies until proven otherwise.

Why the rule exists

Your ELD record is the compliance record. When the recorder fails, the rule bridges the gap with the old technology — paper — so there is never a stretch of driving that no record covers, and it puts a hard deadline on the carrier so "the ELD's been broken for a month" cannot become normal.

Who does what

• Driver (49 CFR 395.34(a)): written notice to the carrier within 24 hours; reconstruct the current 24-hour period and prior 7 days on paper graph-grid logs (unless the records are retrievable from the ELD); continue paper logs until the device is compliant again.
• Carrier (49 CFR 395.34(d)): correct, repair, replace, or service the ELD within 8 days of discovery or driver notification — whichever comes first. Under 49 CFR 395.34(e), carriers may request an extension from the FMCSA Division Administrator for the state of their principal place of business.

What to do, step by step

• Step 1 — confirm. Malfunction indicator on? Note the code the device shows and what you were doing when it appeared.
• Step 2 — tell the carrier in writing within 24 hours. A message through the carrier's system, an email, even a text — written means reviewable. Keep your copy.
• Step 3 — rebuild the paper trail. If the device cannot produce the current day and previous 7 days, reconstruct them on graph-grid sheets from memory, receipts, and any partial data. Good practice (not a federal requirement): carry blank paper logs for exactly this day.
• Step 4 — run on paper. Log duty status manually until the ELD is fixed. Your HOS limits have not changed — only the recording method has.
• Step 5 — at roadside. Tell the inspector the device is malfunctioning, show the written notice if you have it, and present your paper logs for the required period. That paper trail is what stands between you and a no-record-of-duty-status problem.
• Step 6 — confirm the fix. When the device is repaired, verify past data transferred correctly before you shred anything. Good practice: keep the paper originals per your carrier's retention policy.

Real-world example

Example (illustration, not legal advice): Tuesday 09:15, mid-trip, the malfunction icon lights: positioning failure. You finish the leg safely, then at the next stop message dispatch — "ELD positioning malfunction since ~09:15, request service, running paper" — and photograph the message. The device still displays the past week, so no reconstruction is needed; you print nothing but start a paper log at 09:15 Tuesday. The carrier's shop swaps the unit Thursday — inside its 8-day clock — and you verify Tuesday–Thursday appear correctly before returning to electronic logging.

Common mistakes

• Treating a data-diagnostic flag as a full malfunction (or the reverse — driving for days with the malfunction icon on and no paper logs).
• Telling a dispatcher verbally and calling it "notice." The rule says the notice must be written.
• Reconstructing only today. The requirement covers the current 24 hours and the previous 7 days when the device cannot produce them.
• Assuming the 8-day repair clock is the driver's problem to manage — it is the carrier's duty, but your paper logs must not stop while it runs.
• "The ELD is down, so nothing is being recorded" — the limits never paused; missing records are their own violation under 49 CFR 395.8.

Violations and compliance risks

Operating without records — electronic or paper — during a malfunction is a record-of-duty-status violation, discoverable at any inspection, and it removes your ability to prove the hours you drove were legal. Both the missing-records problem and any underlying HOS overruns feed the same Safety Measurement System records as other Part 395 violations. Specifics: FMCSA's ELD pages.

Driver checklist

• Blank graph-grid logs and a pen in the truck, always.
• Malfunction indicator on → note the code and time immediately.
• Written notice to the carrier within 24 hours — keep proof.
• Paper logs from the moment of failure; reconstruct back 7 days if the device cannot show them.
• At inspection: disclose the malfunction, show the paper.
• After repair: verify the data before ending the paper routine.

Keep learning

• The limits your paper logs must still respect: CDL Hours of Service Rules Explained · The 11-Hour Driving Limit · The 14-Hour Driving Window
• Where ELD categories go wrong: Personal Conveyance Explained · Yard Move Explained
• What the officer checks at the scale: Level 1 DOT Inspection Explained
• Drill the rules free: the General Knowledge practice test covers logging and hours-of-service questions.
• Get inspection-ready for real: TLWS Academy · new guides via the email list.