When the ELD Fails, the Driver Acts First
An ELD malfunction is not a free pass to stop logging. Under 49 CFR 395.34, the obligation to record duty status continues without interruption — it simply shifts from the device to paper. The moment a driver discovers a malfunction, three driver duties attach, and they all run in parallel. Getting any one of them wrong turns a routine equipment failure into a recordable hours-of-service violation at the next roadside inspection.
1. Notify the carrier within 24 hours
49 CFR 395.34(a)(1)The driver must note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours. A verbal heads-up is not enough — the regulation requires written notice, and it is the document the carrier needs to start its own 8-day clock and any extension request.
2. Reconstruct the current day plus the previous 7 days
49 CFR 395.34(a)(2)The driver must reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record those RODS on graph-grid paper logs that comply with 49 CFR 395.8 — unless the driver already possesses those records, or they are still retrievable from the ELD.
3. Keep manual paper logs until the ELD is fixed
49 CFR 395.34(a)(3)The driver must continue to manually prepare a record of duty status in accordance with 49 CFR 395.8 until the ELD is serviced and brought back into compliance. During an inspection in this window, the driver provides the authorized safety official the manually kept records.
Reconstruct, do not invent
The reconstruction requirement is for the current day and the previous 7 consecutive days — not the entire malfunction period from memory. If the driver still has the paper or electronic records for those days, or the data is retrievable from the malfunctioning unit, the driver does not have to recreate them. Drivers should carry a supply of blank graph-grid paper logs at all times precisely so they can comply the moment a device fails.
The Carrier 8-Day Repair Window
Once the carrier has notice of the malfunction, its own obligation under 49 CFR 395.34(d) begins. The carrier must repair, replace, or service the malfunctioning ELD within 8 days of either discovering the condition or the driver notification, whichever occurs first. Eight days is the outer limit for running on paper logs without seeking relief from FMCSA. It is a calendar-day window, not business days, so a malfunction discovered on a Friday is counted from that Friday.
The ELD Malfunction Timeline (49 CFR 395.34)
| When | Who | Action | Citation |
|---|---|---|---|
| Within 24 hours | Driver | Note the malfunction and give the carrier written notice | 395.34(a)(1) |
| Immediately | Driver | Reconstruct current day + previous 7 days on paper; keep manual logs until repaired | 395.34(a)(2)-(3) |
| Within 5 days of driver notice | Carrier | If more than 8 days is needed, notify the FMCSA Division Administrator and request an extension | 395.34(d) |
| Within 8 days | Carrier | Repair, replace, or service the ELD and bring it back into compliance | 395.34(d) |
When 8 Days Is Not Enough: The Extension
Supply-chain delays, back-ordered hardware, and vendor lead times can all push a repair past 8 days. FMCSA anticipated this. A carrier that cannot repair or replace the device in time may request an extension — but the request itself has a deadline. Under 49 CFR 395.34(d), the carrier must notify the FMCSA Division Administrator for the State of its principal place of business within 5 days after the driver notifies the carrier of the malfunction. Miss the 5-day window and the carrier has no sanctioned path past day 8.
The extension notification is not a formality. It must include the driver and ELD identifying information, the date the carrier was notified of the malfunction, why additional time is needed, and a description of the actions the carrier has taken in a good-faith effort to repair, replace, or service the device. A bare request with no evidence of effort is unlikely to be granted. The whole point is to show FMCSA that the carrier is actively resolving the problem, not simply choosing to operate on paper indefinitely.
The 5-day and 8-day clocks run together
Both timers start from the driver notification. The carrier has 5 days to decide whether it will make the 8-day repair deadline and, if not, to file the extension request — and 8 days to actually complete the repair if no extension is sought. A carrier that waits until day 7 to realize it cannot make the deadline has already blown the 5-day extension window. Build the decision point into the workflow at day 3 or 4.
Malfunctions vs. Data Diagnostic Events
49 CFR 395.34 distinguishes two conditions an ELD can flag. A malfunction is a condition that defeats the device's ability to accurately record or retain required data — the regulation enumerates power-compliance, engine-synchronization, timing, positioning, data-recording, and data-transfer malfunctions. A data diagnostic event signals a potential data problem, such as missing required data elements or unidentified-driving records, without necessarily destroying the record. The 8-day repair clock, the 24-hour notice, and the paper-log reconstruction attach to malfunctions. Diagnostic events must still be addressed and cleared, but they do not by themselves start the 8-day repair requirement.
The practical takeaway is that a driver and carrier need to recognize which condition the device is reporting. Treating a malfunction as a mere diagnostic event — and skipping the paper-log reconstruction and the notice — is the failure mode that produces violations. When in doubt, treat the condition as a malfunction and start the paper logs; the cost of an unnecessary paper log is trivial compared with a falsified-or-missing record finding.
The Malfunction Record: Proving You Complied
Compliance with 49 CFR 395.34 is only as good as the carrier ability to prove it after the fact. An auditor reviewing a malfunction event will want to reconstruct the whole sequence: the device failed, the driver gave written notice within 24 hours, paper logs covered the gap, and the device was repaired within 8 days (or an extension was timely requested). That story is told through documents, and a missing document breaks the chain.
The Malfunction File Should Contain
- The driver's written notice of the malfunction, with the date and time it was provided
- The reconstructed paper logs for the current day and previous 7 days, plus the ongoing manual RODS kept during the outage
- Repair or replacement documentation — work order, invoice, or vendor record showing the device was serviced and returned to compliance
- Any extension request sent to the FMCSA Division Administrator and the agency's response
- The date the device was confirmed back in compliance, closing the malfunction window
Where the Records Live: FileFlo
FileFlo is not an ELD and does not log duty status — your ELD vendor handles the device, the malfunction flags, and the diagnostic events. What FileFlo does is hold the records and proof that surround a malfunction event: the driver written malfunction notice, the repair invoices and vendor documentation, any FMCSA extension correspondence, and the dated confirmation that the device was brought back into compliance. When a compliance review lands on a malfunction period, the carrier has to produce that file — and FileFlo keeps it organized, complete, and exportable instead of scattered across email threads and a glovebox.
Key Takeaways
- Driver: written notice within 24 hours. A verbal heads-up does not satisfy 49 CFR 395.34(a)(1).
- Reconstruct the current day plus 7 prior days on paper — unless the driver already has those records or they are retrievable from the ELD — and keep manual logs until the device is fixed.
- Carrier: repair or replace within 8 days. That is the maximum on paper logs without FMCSA relief.
- Need more time? File within 5 days. Notify the FMCSA Division Administrator and show a good-faith repair effort.
- Keep the malfunction file. Notice, paper logs, repair documentation, and any extension correspondence are what prove compliance in an audit.
ELD Malfunctions: FAQ
Answers to common questions about ELD malfunctions, paper logs, and the 8-day repair rule under 49 CFR 395.34.
Under 49 CFR 395.34, when an ELD malfunctions the driver must do three things: note the malfunction of the ELD and provide written notice to the motor carrier within 24 hours; reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days on graph-grid paper logs that comply with 49 CFR 395.8 (unless the driver already possesses those records or they are retrievable from the ELD); and continue to manually prepare a record of duty status on paper until the ELD is serviced and brought back into compliance.
The motor carrier must repair, replace, or service the malfunctioning ELD within 8 days of discovering the condition or the driver's notification, whichever occurs first, under 49 CFR 395.34(d). During those 8 days the driver keeps paper records of duty status. A carrier that needs more than 8 days must request an extension from the FMCSA Division Administrator for the State of its principal place of business.
Only with an FMCSA extension. The 8-day window in 49 CFR 395.34(d) is the maximum a carrier may operate on paper logs after an ELD malfunction without seeking relief. If the carrier cannot repair or replace the device in time, it must notify the FMCSA Division Administrator within 5 days of the driver's notification and request an extension. The request must describe the actions the carrier has taken in a good-faith effort to repair the device and explain why additional time beyond 8 days is needed.
A motor carrier seeking to extend the time permitted for repair, replacement, or service of one or more ELDs must notify the FMCSA Division Administrator for the State of the carrier's principal place of business within 5 days after the driver notifies the carrier of the malfunction, per 49 CFR 395.34(d). The notification must include the driver and ELD information, the date the carrier was notified, why additional time is needed, and a description of the carrier's good-faith repair efforts.
A malfunction is a condition that prevents the ELD from accurately recording or retaining the required data — for example, a power-compliance, engine-synchronization, timing, positioning, data-recording, or data-transfer malfunction. A data diagnostic event flags a potential issue (such as missing data or an unidentified-driving condition) without necessarily defeating the record. The 8-day repair clock and paper-log reconstruction in 49 CFR 395.34 apply to malfunctions. Diagnostic events must be resolved but do not by themselves trigger the 8-day repair requirement.
The carrier should retain the driver's written notice of the malfunction, the reconstructed and ongoing paper records of duty status kept during the outage, documentation of the repair or replacement (work orders, invoices, or vendor records showing the device was serviced and brought back into compliance), and a copy of any extension request and FMCSA response. Together these records prove the carrier met the 24-hour notice, the paper-log reconstruction, and the 8-day repair obligations in 49 CFR 395.34.
Hold the Malfunction Record Where an Auditor Can See It
FileFlo is the records and proof layer for FMCSA compliance — it is not an ELD and does not log duty status. It holds the driver malfunction notice, repair invoices, FMCSA extension correspondence, and the dated proof the device returned to compliance. When a review asks how you handled an ELD outage, export the whole file in minutes.
From $89/month — No credit card required — 5-day free trial