Hours of Service • ELDT.LIVE
ELD Malfunction for CDL Drivers: Paper Logs, 24-Hour Notice, and the 8-Day Repair Rule
A frozen screen, lost power, or missing vehicle data does not pause hours-of-service duties. Learn the driver's immediate steps, which logs must be reconstructed, what to show during an inspection, and when the carrier must repair or replace the ELD.
Treat a true malfunction as a recordkeeping event
An ELD problem does not create extra driving time or erase the duty-status record. Under 49 CFR 395.34, the driver must recognize the malfunction, preserve or recover available records, notify the motor carrier, and continue recording duty status manually until the device is serviced and returned to compliance. The first operational question is not whether the truck can still move; it is whether the system can accurately record, retain, display, and transfer the required hours-of-service information. Stop in a safe place before troubleshooting or writing a log, then follow the carrier's procedure without changing a duty status merely to make the display look correct.
Distinguish a malfunction from a data diagnostic event
The regulation addresses ELD malfunctions and data diagnostic events separately. A malfunction can involve a loss of required functionality, while a diagnostic event flags a data inconsistency that may still be resolvable. When the ELD displays a diagnostic event, Section 395.34 directs the driver to follow the motor carrier's and ELD provider's recommendations for resolving it. Do not assume every warning requires immediate paper logs, and do not dismiss a malfunction as a harmless diagnostic message. Record the alert text or code, time, location, vehicle, and steps attempted, then confirm the classification with the carrier or provider.
Give the carrier written notice within 24 hours
Once an ELD malfunction is identified, the driver must note it and provide written notice to the motor carrier within 24 hours. Use the carrier's approved channel—such as an in-app report, email, maintenance form, or dispatch message—and keep evidence of the submission when allowed. A useful notice identifies the driver, truck and trailer, ELD make or unit, date and time discovered, location, visible error message, missing functions, last known accurate record, and any troubleshooting already completed. A phone call may help obtain immediate support, but the federal rule specifically requires written notice.
Reconstruct today and the previous seven days when needed
The driver must reconstruct the record for the current 24-hour period and the previous seven consecutive days on graph-grid paper logs unless those records are already in the driver's possession or can be retrieved from the ELD. Use actual supporting information rather than estimates whenever possible: dispatch timestamps, fuel receipts, bills of lading, toll records, inspection documents, GPS or telematics information, and the driver's own notes. Reconstruct duty status—not merely driving time—and include off-duty, sleeper-berth, driving, and on-duty-not-driving periods. Never invent a clean log to fit the remaining clock.
Complete manual records with the required details
A paper record of duty status must follow 49 CFR 395.8. In addition to the graph, it includes the date, total miles driven, truck or tractor and trailer numbers, carrier name, driver certification, the home-terminal 24-hour starting time, main-office address, remarks, co-driver name when applicable, totals for each duty-status line, and shipping-document number or the shipper and commodity. Record the location of each duty-status change and keep the log current to the last change. The four duty-status totals must equal 24 hours, and the driver's signature certifies that the entries are true and correct.
Keep logging manually until the ELD is compliant again
After reconstructing the required history, the driver must continue preparing manual records in accordance with Section 395.8 until the ELD is serviced and brought back into compliance. Do not stop after one paper page because the tablet briefly restarts. Confirm with the carrier that the malfunction has been corrected, required data are recording properly, and the device can perform the functions needed for roadside review or transfer. Follow the provider's instructions for entering annotations or reconciling paper records after restoration; do not create duplicate driving events or accept suggested edits that make the record inaccurate.
Know what to provide during a roadside inspection
If inspected during a malfunction, the driver must provide the authorized safety official the manually maintained records required by Section 395.34. Explain the malfunction calmly, present the reconstructed and continuing paper logs, and make retrievable electronic records available through the device when possible. Keep the written malfunction notice and provider or carrier instructions accessible under company policy. A malfunction does not excuse missing hours, false entries, driving beyond applicable limits, or failure to retain the previous seven days of records. Let the official direct the inspection rather than experimenting with the device while being questioned.
The 8-day deadline belongs to the motor carrier
The often-repeated 'eight-day rule' is the carrier's deadline to correct the malfunction—not a new hours-of-service allowance for the driver. Section 395.34 requires the motor carrier to repair, replace, or service the ELD within eight days of discovering the condition or receiving the driver's notice, whichever occurs first. The driver continues to follow the normal hours-of-service limits and manual-record procedures during the malfunction. Safety personnel should track the earliest discovery or notice time, coordinate service, and tell the driver exactly when and how the repaired or replacement unit returns to compliant use.
An extension request has its own five-day clock
If the carrier needs more than eight days, it must notify the FMCSA Division Administrator for the state of its principal place of business within five days after the driver's malfunction notice. The signed request must identify the carrier representative; list each ELD's make, model, and serial number; give the date and location of each reported malfunction; and describe the carrier's good-faith repair, replacement, or service efforts and why additional time is needed. FMCSA decides whether to allow more time and may impose conditions. A driver, dispatcher, or vendor cannot grant the extension informally.
Carry the required ELD information packet before departure
Section 395.22 requires the carrier to ensure that drivers have an onboard ELD information packet. It includes instructions for producing and transferring records to an authorized safety official, instructions for malfunction reporting and recordkeeping, and enough blank graph-grid records to document at least eight days. Check this packet during orientation and when assigned a different tractor. Saving a PDF on a phone can be helpful only if it remains accessible when needed and the carrier's method satisfies the requirement; a dead phone, forgotten password, or missing cellular signal is a poor time to discover that no usable instructions or blank logs are available.
Do not confuse the occasional-paper-log exception with a malfunction
Section 395.8 contains limited situations in which a carrier may use manual records instead of requiring an ELD, including operations needing records of duty status on no more than eight days in a rolling 30-day period and specified driveaway-towaway or pre-2000-vehicle situations. Those exceptions are separate from the malfunction procedure. A normally ELD-required driver cannot treat repeated device failures as the occasional-paper-log exception. The carrier must address the malfunction under Section 395.34 and maintain accurate records throughout the process.
Practice a five-minute malfunction routine
Before dispatch, locate the ELD instruction packet, blank logs, carrier support contact, home-terminal time standard, vehicle numbers, and the device's make, model, and serial number. If a problem occurs: park safely; capture the error and time; check whether records remain retrievable; contact support; send written notice within 24 hours; reconstruct the current day and prior seven days when required; continue accurate paper logs; preserve supporting documents; and confirm restoration before returning to electronic-only logging. This article reflects eCFR text displayed as current through September 17, 2026, so carriers should recheck the official provisions when handling a live malfunction or extension request.
Educational summaries help you prepare, but official FMCSA and state licensing sources remain the authority for current requirements.
Official sources
49 CFR 395.34 — ELD malfunctions and data diagnostic events ↗49 CFR 395.8 — Driver's record of duty status ↗49 CFR 395.22 — Carrier responsibilities and in-vehicle ELD information ↗FMCSA — Electronic Logging Devices portal ↗FMCSA — Registered ELD list ↗ELDT.live independently creates and reviews its content. We do not present practice questions as official examination questions and do not guarantee a licensing result.