A carrier that waits until the eighth day to ask for more time to repair an electronic logging device may already have missed the request deadline. FMCSA's malfunction rule gives the repair and the extension request different clocks.
For a small fleet, that distinction belongs in the dispatch procedure before a driver calls with a failed ELD. A vendor support ticket does not replace the carrier's regulatory responsibilities.
This guide explains existing federal requirements checked November 2, 2026, for operations subject to the ELD rule. It does not announce a new rule or resolve specialized exemptions.
Eight days to fix it; five days to request more time
Under 49 CFR 395.34(d), the carrier must correct the malfunction within eight days of discovering it or receiving the driver's notice, whichever happens first.
An extension request has a separate deadline: within five days after the driver notifies the carrier. It goes to the FMCSA Division Administrator for the state where the carrier has its principal place of business. FMCSA's current malfunction FAQs confirm that distinction.
Do not treat those as eight business days, or assume the clocks always start together. Record the actual discovery and notification times and plan the response from there.
The regulation requires a signed request identifying the carrier representative and contact information, each affected device's make/model/serial number, the malfunction's reported date and location, and the repair efforts and reason more time is needed. FMCSA's FAQ also calls for the carrier's legal name, principal-business address and USDOT number. Use its current field-office directory to identify the proper office.
The driver has a 24-hour reporting duty
Section 395.34(a) requires the driver to note the malfunction and give the carrier written notice within 24 hours. A phone conversation may help dispatch respond, but should not be mistaken for that written notice.
The driver must reconstruct the current 24-hour period and previous seven consecutive days on compliant graph-grid records unless those records are already possessed or retrievable from the ELD. FMCSA explains that previous records may be available as a printed copy or electronic PDF; do not discard usable records and invent a replacement history.
Where the failure prevents accurate HOS recording and presentation, maintain the required manual records until the device is compliant again. Those records also need to be available to an authorized safety official during an inspection.
A diagnostic warning is not automatically a paper-log event
FMCSA's diagnostic guidance distinguishes a data diagnostic event from a malfunction. Drivers should follow the provider's and carrier's directions for resolving a diagnostic inconsistency.
The agency ties switching to another recording method to a technical problem that prevents accurate recording and presentation of hours-of-service data. Do not build a policy that treats every indicator identically—or one that dismisses an actual malfunction as a harmless warning.
The repair allowance does not create extra driving hours. The applicable property-carrier driving and duty limits continue to apply. Paper changes the recording method, not the driver's available hours.
A pending request has specific conditions
An extension is not simply whatever time a repair vendor needs. FMCSA determines whether to allow more time and provides a written decision, potentially with conditions.
Section 395.34(d)(5) provides a limited interim rule: a request meeting paragraph (d)(2) is deemed compliant with the specified ELD provisions of section 395.8 while FMCSA decides, provided the carrier and driver continue meeting the section's other requirements. That is not blanket relief from HOS rules. Preserve the request and FMCSA's determination; do not assume an informal email or vendor promise qualifies.
Put the backup process in the truck and the office
FMCSA's ELD information-packet guidance requires onboard operating and transfer instructions, malfunction/recordkeeping instructions, and enough blank graph-grid logs for at least eight days. The manuals and instruction sheets may be electronic.
Our suggested office control is one malfunction file containing the driver's notice, discovery time, affected device, repair contacts, available prior logs, any extension request and the final repair or FMCSA decision. That folder layout is advice, not a newly mandated form.
Keep this separate from deciding whether a route meets the short-haul exception. An ELD failure and an exception to using one are different questions.
For help reviewing an HOS process, explore DOT Consulting Solutions' services, call (910) 915-8804, or email info@dotconsultingsolutions.com.
Featured image: excerpt of FMCSA's ELD frequently asked questions, printed page 14, questions 10–11. Public-domain federal document, rendered and cropped; current requirements checked against section 395.34 and current FMCSA guidance. No government endorsement implied.