ELD Paper Logs Malfunction Rule: Key Takeaways
- Under 49 CFR § 395.34, a driver must note an ELD malfunction and notify the motor carrier in writing within 24 hours.
- The driver reconstructs the current 24-hour period and the previous seven consecutive days on compliant graph-grid records unless those records are already possessed or retrievable from the ELD.
- FMCSA says a driver should switch to another recording method only when the technical issue prevents the ELD from accurately recording and presenting Hours of Service data.
- The carrier must correct, repair, replace, or service the ELD within eight days of discovering the condition or receiving the driver’s notice, whichever happens first.
- An extension request must reach the FMCSA Division Administrator within five days after the driver’s notification and contain the information required by § 395.34(d)(2).
Introduction
When an ELD fails, the immediate question is how long the driver may use paper logs. The short answer is generally no more than eight days without an FMCSA extension, but the rule includes separate duties for the driver and carrier, and not every warning or connectivity problem requires the same response.
The ELD paper logs malfunction rule is designed to preserve an accurate record of duty status while a genuine device malfunction is corrected. It does not suspend Hours of Service limits or turn paper logs into an alternative that a fleet can choose indefinitely. A compliant response starts with the device’s malfunction indicator and instructions, followed by prompt written notice, accurate records, documented repair action, and an extension request when additional time is genuinely needed.
What Does the Eight-Day ELD Malfunction Rule Mean?
The eight-day period is the carrier’s standard window to correct the malfunction. Section 395.34(d)(1) requires action within eight days of the carrier’s discovery of the condition or the driver’s notification, whichever occurs first.
During a malfunction that prevents accurate recording and presentation of HOS data, the driver uses a compliant manual record until the ELD is serviced and back in compliance. FMCSA’s current malfunction guidance states that paper logs cannot continue beyond eight days unless an extension has been granted or a qualifying extension request is pending under the rule.
All applicable Hours of Service limits remain in effect. For a property-carrying driver subject to § 395.3, that may include the 11-hour driving limit, 14-hour driving window, applicable 30-minute break requirement, and 60/70-hour limits. The recording method changes temporarily; the legal limits do not.
When Does the Eight-Day Period Start?
The carrier deadline runs from the earlier of two events:
- the carrier discovers information concerning the malfunction; or
- the driver notifies the carrier.
The driver’s separate notification duty is to provide written notice within 24 hours after noting the malfunction. Fleets should record the date and time the condition was identified, the device and vehicle involved, the displayed malfunction code, the driver’s written notice, and the repair steps. That creates a defensible timeline without inventing a later start date.
If a device issue resolves immediately, review the ELD’s instructions and data to determine whether an actual compliance malfunction occurred and whether HOS data remained accurate and presentable. Do not clear or disregard a malfunction indicator without following the provider’s instructions.
What Must the Driver Do After an ELD Malfunction?
1. Note the malfunction
Record what the ELD displayed, including the malfunction code, date, time, vehicle, and any symptoms. Follow the malfunction instructions for the installed device.
2. Notify the carrier in writing within 24 hours
Use an email, electronic message, or documented form that the carrier can retain. A phone call may help operations respond quickly, but it does not replace the written-notice requirement in § 395.34(a)(1).
3. Reconstruct records when required
Reconstruct the current 24-hour period and the previous seven consecutive days on graph-grid records that comply with § 395.8, unless the driver already possesses the records or can retrieve them from the ELD. FMCSA permits a printed or electronic copy, such as a PDF, for prior days when it accurately presents the required records.
4. Maintain a manual RODS when the malfunction affects HOS data
Continue manually preparing a record of duty status when the malfunction prevents accurate recording and presentation, until the device is serviced and compliant. The manual record must accurately reflect the driver’s duty status; it is not permission to exceed HOS limits.
What Must the Motor Carrier Do?
Once the carrier discovers or receives notice of the malfunction, it should:
- confirm the device, vehicle, driver, code, and time of discovery;
- ensure the driver can maintain and present compliant records;
- contact the provider or technician and document troubleshooting;
- repair, replace, service, or correct the device within the eight-day window;
- verify that the device is compliant before returning to normal electronic recording; and
- request an extension within five days after the driver’s notification if more time may be needed.
A spare device can reduce disruption, but it must be a compatible, currently registered ELD and properly installed and configured. Fleets evaluating replacement equipment can review the Geosavi ELD store and should confirm the exact device model on FMCSA’s registered list before use.
What Are the ELD Malfunction Codes?
FMCSA’s technical specifications identify standard compliance-malfunction codes. The ELD provider’s instructions should explain how the installed product displays and resolves them:
- P — Power compliance malfunction: the device has not met the applicable power-monitoring requirement.
- E — Engine synchronization compliance malfunction: required engine data are not being synchronized correctly.
- T — Timing compliance malfunction: the ELD time exceeds the permitted deviation from Coordinated Universal Time.
- L — Positioning compliance malfunction: required vehicle-position information is not being acquired within the technical threshold.
- R — Data recording compliance malfunction: the ELD cannot properly record, retain, or retrieve required data.
- S — Data transfer compliance malfunction: the ELD’s transfer mechanism remains unconfirmed through the specified monitoring sequence.
A data diagnostic event is not the same as a compliance malfunction. Under § 395.34(c), a driver who receives a data-diagnostic indication follows the carrier’s and ELD provider’s recommendations to resolve the inconsistency. FMCSA advises switching to another HOS recording method only when the technical issue prevents accurate recording and presentation of HOS data.
What Must a Manual Record of Duty Status Include?
A malfunction does not relax the recordkeeping standard. A manual RODS must comply with 49 CFR § 395.8, including the duty-status grid and the information applicable to the driver’s operation. The record should accurately show dates, locations or location descriptions, duty-status changes, total hours, carrier and vehicle information, shipping-document information when applicable, and the driver’s certification.
Do not estimate when reliable records are available. Use dispatch records, fuel receipts, bills of lading, toll data, vehicle information, and other supporting documents to reconstruct an accurate timeline. Keep the reconstructed and subsequent manual records available with any retrievable ELD records for inspection.
What Happens During a Roadside Inspection?
Section 395.34(b) requires the driver to provide the manually kept records during an inspection. If previous records remain available from the ELD, the driver may present them through the device’s supported method. FMCSA guidance also recognizes printed or electronic copies for reconstructed prior days when appropriate.
A data-transfer failure does not always mean that HOS data are unavailable. If another supported transfer method works, an officer may use it; the officer may also review the required display or printout supported by the device.
Current § 395.22(h) requires the onboard ELD information packet to contain:
- instructions describing the supported data-transfer mechanisms and the steps to produce and transfer HOS records;
- instructions describing malfunction reporting and recordkeeping procedures; and
- enough blank graph-grid records for at least eight days.
Make sure the instructions match the installed device and drivers know where to find them.
How Does an ELD Malfunction Extension Work?
The carrier must notify the FMCSA Division Administrator for the state of its principal place of business within five days after the driver provides malfunction notice. The signed request must include:
- the filing representative’s name, address, and telephone number;
- the make, model, and serial number of each affected ELD;
- the date and location of each malfunction as reported by the driver; and
- a concise description of the carrier’s good-faith repair, replacement, or service efforts and why more time is needed.
FMCSA may allow additional time when the carrier continues making a good-faith effort. Under § 395.34(d)(5), a carrier that submits a request meeting the rule’s requirements is deemed compliant with the identified ELD-use provisions until FMCSA makes its determination, provided the carrier and driver continue complying with the other malfunction requirements.
What Happens If the ELD Is Still Not Fixed After Eight Days?
Without an extension or a qualifying pending request, the carrier cannot keep treating paper logs as an open-ended substitute for the required ELD. FMCSA guidance states that a driver who continues using paper logs beyond eight days without proof of an extension may be placed out of service.
Avoid quoting one fixed penalty for every situation. Enforcement depends on the violation, facts, responsible party, current penalty schedule, and applicable out-of-service criteria. The practical response is to escalate repair or replacement early and submit a complete extension request within the five-day filing window when necessary.
Which Mistakes Make an ELD Malfunction Worse?
- Waiting longer than 24 hours to send written notice.
- Assuming the eight-day period begins only when a repair ticket is opened.
- Reconstructing prior days even though accurate records are already possessed or retrievable, while overlooking the current manual record.
- Treating every data-diagnostic icon as a full malfunction without checking the device instructions.
- Continuing to rely on an ELD that cannot accurately record and present HOS data.
- Failing to keep the required transfer and malfunction instructions or eight days of blank graph grids onboard.
- Waiting until day eight to consider an extension even though the filing window is five days after driver notice.
- Returning to electronic logs without confirming that the device is serviced and compliant.
ELD Malfunction Response Comparison
| Situation | Driver response | Carrier response |
|---|---|---|
| Data diagnostic event | Follow carrier and provider recommendations; verify data accuracy | Help resolve the inconsistency and document action |
| Malfunction, but required records remain retrievable | Notify carrier; retain accessible records; manually record when accurate electronic recording or presentation is impaired | Correct the malfunction within the regulatory window |
| Malfunction prevents access to prior records | Reconstruct current day and previous seven days; continue required manual RODS | Support reconstruction and repair or replace the ELD |
| Roadside transfer fails | Try another supported transfer method or provide the supported display or printout | Assist with retrieval if requested and correct any confirmed malfunction |
| Repair may exceed eight days | Continue accurate records and carry extension documentation when applicable | Submit a complete extension request within five days after driver notice |
Questions to Ask Before an ELD Malfunction
- Does every vehicle carry current transfer instructions, malfunction instructions, and at least eight days of blank graph grids?
- Do drivers know how to distinguish the malfunction indicator from the data-diagnostic indicator?
- Can drivers send written malfunction notice from the road?
- Who records the earlier of carrier discovery and driver notification?
- Can the back office retrieve prior RODS and supporting documents quickly?
- Who decides whether an extension request is necessary before the five-day filing period closes?
- Is the exact ELD model still on the FMCSA registered ELD list?
- Are replacement devices compatible, registered, and ready to configure?
Frequently Asked Questions
How long can a driver use paper logs after an ELD malfunction?
Generally, paper logs may be used for no more than eight days while the ELD is corrected. Additional time requires compliance with the extension process in § 395.34(d).
When does the carrier’s eight-day deadline start?
It starts from the carrier’s discovery of the condition or the driver’s notification, whichever occurs first.
Do HOS limits still apply during the malfunction?
Yes. The malfunction changes the recording method, not the applicable driving, on-duty, break, or weekly limits.
Must the driver reconstruct all previous seven days?
Only when the driver does not already possess the records and cannot retrieve them from the ELD. Accurate printed or electronic copies may be used for available prior records.
Does every ELD warning require paper logs?
No. A data-diagnostic event and a compliance malfunction are different. FMCSA says to switch recording methods when the issue prevents accurate recording and presentation of HOS data.
Can a compliant electronic logging program replace graph-grid paper during a malfunction?
The regulation specifies graph-grid paper logs for reconstruction, while FMCSA guidance recognizes certain printed or electronic copies for prior records. Follow § 395.34, § 395.8, the device instructions, and current FMCSA guidance for the specific situation.
Can the carrier request more than eight days?
Yes. The signed request must be sent to the appropriate FMCSA Division Administrator within five days after driver notification and include all information required by § 395.34(d)(2).
Does a correctly handled malfunction automatically affect SMS?
No. A malfunction is not automatically an SMS violation. An inspection violation may affect SMS according to the applicable methodology, but the system is an intervention-prioritization tool rather than a federal safety rating.
What should drivers carry in the vehicle?
Current § 395.22(h) requires transfer instructions, malfunction reporting and recordkeeping instructions, and enough blank graph-grid records for at least eight days.
Where can drivers get help with a Geosavi ELD malfunction?
Contact the Geosavi team or call (800) 261-4361. Drivers should also follow the malfunction instructions for the installed device and notify their carrier in writing within 24 hours.
Conclusion
The ELD malfunction process is manageable when the driver and carrier act early. The driver documents the malfunction, sends written notice within 24 hours, and maintains accurate records when the device cannot do so. The carrier tracks the earlier trigger date, restores compliance within eight days, and files a complete extension request within five days when more time may be needed.
Keep current instructions and blank graph grids onboard, verify the exact device on FMCSA’s registered list, and practice the process before a failure occurs. That preparation protects the integrity of the driver’s Hours of Service record without overstating penalties or treating every technical warning as the same event.