When an ELD malfunctions, carriers and drivers should follow current FMCSA ELD malfunction guidance: document the issue, notify the carrier, keep required backup records, use paper logs where applicable, and repair or replace the device within the required window. Under 49 CFR 395.34 the driver generally provides written notice within 24 hours and the carrier repairs, replaces, or services the ELD within 8 days, with an extension process. Verify current requirements before relying on a timeline. This is general information, not legal advice.
A malfunctioning ELD is not the problem carriers think it is. The device breaking is normal. The failure that actually hurts you in an audit is the undocumented gap: no notice, no paper logs, no repair ticket, just a hole in the record that looks like avoidance. Here is how to handle it so it stays a non-issue.
What counts as an ELD malfunction?
An ELD malfunction may involve device, data transfer, power, synchronization, location, engine connection, or missing required data issues, depending on current ELD technical requirements. The device is generally designed to detect these conditions and flag them. Because the specifics are technical and can change, verify current FMCSA ELD guidance and your vendor's instructions rather than assuming. For the broader device pitfalls, see our common ELD mistakes, and for the service side, HOS and ELD auditing. Current FMCSA ELD guidance covers malfunction handling.
What drivers should do when an ELD malfunctions
- Notice the malfunction or diagnostic event.
- Notify the carrier.
- Follow the company process.
- Reconstruct required logs where applicable.
- Keep required supporting records.
- Avoid guessing or backfilling without documentation.
- Follow current FMCSA guidance and ELD provider instructions.
What carriers should document
The documentation is the whole point. Keep these for each malfunction. Verify current requirements for your operation.
| Record | What it shows | Why it matters | Common mistake |
|---|---|---|---|
| Malfunction date and time | When the issue started | Starts the repair clock | No timestamp recorded |
| Driver and vehicle involved | Who and what was affected | Ties the record to the unit | Not linking to the correct truck |
| ELD provider and device information | Which device and vendor | Supports the repair path | Missing device details |
| Description of the issue | What went wrong | Explains the event later | Vague or no description |
| Driver notification | That the driver told the carrier | A required step under the rule | No written notice kept |
| Backup log records where applicable | Paper records during the outage | Fills the HOS record gap | No backup logs |
| Repair or replacement communication | The service effort | Shows timely action | No repair ticket saved |
| Resolution date | When it was fixed | Closes the repair window | Not documenting the fix |
| Follow-up training or corrective action | What changed after | Prevents repeats | No follow-up |
ELD malfunction timeline and repair window
There is a current FMCSA repair or replacement timeline. Under 49 CFR 395.34, when an ELD malfunctions, the driver generally provides written notice to the carrier within 24 hours and keeps paper records of duty status in the meantime, and the carrier generally repairs, replaces, or services the device within 8 days of discovery or the driver's notification, whichever is first. If the carrier needs more time, the rule provides a process to request an extension from the FMCSA Field Administrator. Verify the current rule before relying on any specific number, since requirements can change, and follow current FMCSA guidance and your ELD provider instructions. Do not treat the window as optional or assume it resets on its own.
ELD malfunction vs data diagnostic event
These are not the same, and drivers confuse them. This is a general comparison; confirm the specifics with your ELD provider and current FMCSA guidance.
| Issue type | What it may indicate | Driver action | Carrier action | Record to keep |
|---|---|---|---|---|
| ELD malfunction | The device is not meeting a technical requirement | Note it, notify carrier, use paper logs | Document and arrange repair or replacement | Malfunction and backup records |
| Data diagnostic event | A condition flagged for review | Review and follow provider guidance | Investigate and resolve | The diagnostic and resolution |
| Data transfer issue | Trouble producing or transferring data | Follow provider steps at inspection | Confirm transfer methods work | Notes on the transfer problem |
| Power or engine sync issue | The device is not syncing with the engine | Report it and follow instructions | Check installation and vendor guidance | The sync issue and fix |
| Missing location or required data | Required data was not captured | Note and report the gap | Determine cause with the provider | The data gap and resolution |
Common ELD malfunction mistakes
- Ignoring malfunction indicators.
- Not notifying the carrier.
- Not keeping backup records.
- Not documenting repair communication.
- Missing the repair or replacement deadline.
- Treating recurring issues as one-offs.
- Not training drivers on the malfunction procedure.
- Waiting until audit time to reconstruct records.
How ELD malfunction records connect to HOS audits
A malfunction by itself is not the same as intentional falsification, and a documented one is generally manageable. Poor documentation is what makes an event hard to explain later. Repeat issues, missing logs, and unresolved device problems can create audit concerns. Fold malfunction review into your driver log auditing checklist, understand how long HOS violations stay on your record, prepare with DOT audit help, and see how gaps compound into cost in our DOT non-compliance cost report. Unresolved ELD issues also feed the public safety picture in how brokers look at HOS violations.
ELD malfunction recordkeeping checklist
- Malfunction notice.
- Date and time.
- Driver name.
- Vehicle or unit.
- Device and provider.
- Driver notification to the carrier.
- Backup records.
- Reconstructed logs where applicable.
- Repair ticket or vendor communication.
- Resolution date.
- Extension request documentation if applicable and verified.
- Driver coaching notes.
- Internal follow-up.
Nobody gets in trouble because a device broke. They get in trouble because there is no note, no paper log, and no repair ticket, so a normal malfunction looks like someone hiding hours. Write the notice, keep the paper, save the repair ticket, and fix it inside the window. A documented malfunction is boring, and boring is exactly what you want in an audit.
Need Help Organizing ELD Malfunction Records?
Book a free compliance review. We will look at how you handle device malfunctions and build a record process that holds up in an audit.
Book a Free Compliance Review →HOS & Log Auditing
We audit HOS and ELD records, organize malfunction documentation and backup logs, and document corrective action that holds up in a review.
Get HOS Support →How Fleet Regulators helps with ELD malfunction records: we help carriers organize ELD malfunction records, backup logs, repair follow-up, driver communication, and log-audit review. We do not guarantee HOS compliance, CSA improvement, audit outcomes, or insurance savings.
Frequently Asked Questions
Under 49 CFR 395.34, a driver should generally note the malfunction, provide written notice to the carrier within 24 hours, reconstruct the required records of duty status for the current period and recent prior days where not retained, and keep paper logs until the device is working again. Follow current FMCSA guidance and your ELD provider instructions.
The carrier should document the malfunction, keep the driver's backup records, and arrange to repair, replace, or service the device. Under 49 CFR 395.34, a carrier generally must correct the ELD within a set window from discovery or driver notification. Verify the current requirement, and request an extension through the proper channel if repair is delayed.
Under 49 CFR 395.34, a carrier generally must repair, replace, or service a malfunctioning ELD within 8 days of discovery of the condition or a driver's notification, whichever is first, with an extension available through the FMCSA process. Verify the current timeframe against the rule before relying on it, since requirements can change.
Keep the malfunction date and time, the driver and vehicle, the ELD provider and device information, a description of the issue, the driver notification, backup or reconstructed paper logs, repair or replacement communication, and the resolution date. Organized malfunction records are what make the event a non-issue in a later review.
No. A malfunction by itself is not the same as intentional falsification. A documented, properly handled malfunction is generally manageable. The risk comes from ignoring it, not keeping backup records, or missing the repair window, which can turn a device issue into a compliance problem.
Generally yes. Under 49 CFR 395.34, a driver reconstructs and keeps paper records of duty status while the ELD is malfunctioning, until it is repaired or replaced. Follow current FMCSA guidance and your ELD provider instructions for exactly what to record.
A malfunction generally means the ELD is not meeting a technical requirement and may require paper logs and repair. A data diagnostic event flags a condition to review, such as missing data or an unidentified driving issue, that may not require paper logs on its own. Confirm the specifics with your ELD provider and current FMCSA guidance.
Yes. We help carriers organize ELD malfunction records, backup logs, repair follow-up, driver communication, and log-audit review. We do not guarantee HOS compliance, CSA improvement, an audit outcome, or insurance savings, and this is not legal advice.