The truck is already loaded when the ELD displays an active malfunction and can no longer record or present required hours-of-service information correctly. Dispatch needs the truck moving, but the issue is no longer just technical: it has become a records-compliance incident with a clock attached to it.
An ELD malfunction does not automatically put the truck out of service at that moment. It does create specific driver and carrier obligations, and those become harder to repair if the first hours are poorly documented.
The useful response is not simply:
“Call the ELD company and see what happens.”
It is to identify what failed, preserve the records, move to the lawful backup method when required, start the repair clock and document the return to compliance.
Minute zero: decide what failed
Not every warning on an ELD requires the same response.
Part 395 distinguishes between ELD malfunctions and data diagnostic events.
A data diagnostic event can indicate a data inconsistency or another condition the driver and carrier need to resolve. Section 395.34(c) directs the driver to follow the motor carrier’s and ELD provider’s recommendations for resolving that inconsistency.
The distinction matters with data transfer. FMCSA says a data transfer diagnostic event occurs when the operation of the transfer mechanism cannot be confirmed. A data transfer compliance malfunction is reached only when the ELD remains in that unconfirmed mode after the next three consecutive monitoring checks. A single warning therefore should be classified before the carrier treats the entire device as failed.
A malfunction is more serious.
FMCSA describes multiple malfunction categories, but the practical question for the carrier is simpler:
Can the ELD still accurately record, retain and present the driver’s required hours-of-service information?
If the answer is no, the carrier should not keep treating the device as though nothing happened.
That is the decision point.
The driver’s immediate compliance response
Written notice within 24 hours
Under § 395.34(a)(1), the driver must:
- note the malfunction; and
- provide written notice to the motor carrier within 24 hours.
The regulation does not make a phone call the complete compliance process.
A phone call may be operationally useful. Dispatch may need to know immediately.
But the rule specifically calls for written notice.
For a small carrier, that notice does not need to become a complicated form. It should simply establish what happened and when.
A useful notification can record:
- driver’s name;
- vehicle or unit;
- ELD make or identifier;
- date and approximate time of the malfunction;
- location;
- symptom observed;
- whether HOS records remain accessible;
- whether data can still be displayed or transferred;
- time the carrier was notified.
The important part is not creating administrative theater.
It is creating evidence that the malfunction entered the carrier’s compliance process.
The 24-hour deadline is not permission to wait
The driver has up to 24 hours to provide the required written notice.
That does not mean the driver should continue operating for 23 hours with unusable records and deal with the problem later.
If the malfunction prevents compliant electronic recording, the backup-record process matters immediately.
The 24-hour period is a notification deadline.
It is not a grace period during which HOS records can disappear.
Reconstruct the records that are unavailable
Section 395.34(a)(2) requires the driver to reconstruct the RODS for:
- the current 24-hour period; and
- the previous 7 consecutive days,
using graph-grid paper logs that comply with § 395.8 unless the driver already possesses those records or they can be retrieved from the ELD.
That final qualification matters.
A malfunction does not automatically mean rewriting eight full days by hand.
If the prior records remain retrievable, the regulation does not require pointless reconstruction merely because another part of the device failed.
The correct question is:
Which required records are no longer available?
Reconstruct those.
Preserve what is still accessible.
Continue manual RODS when the malfunction requires it
If the malfunction prevents the ELD from properly recording the driver’s HOS information, § 395.34 requires the driver to continue manually preparing RODS until the ELD is serviced and brought back into compliance.
This is the bridge between the failed electronic system and the repaired one.
A carrier should not rely on:
- text messages to dispatch;
- fuel receipts alone;
- GPS history alone;
- a payroll timesheet;
- a driver’s memory at the end of the week.
Those records may help reconstruct events.
They are not substitutes for the required RODS when manual RODS are required.
A practical first-hour response
The first hour after a meaningful ELD failure can be handled with a short sequence.
| Step | Driver | Carrier |
|---|---|---|
| 1 | Note the malfunction | Open an incident record |
| 2 | Preserve screenshots or accessible logs if practical | Record discovery/notification time |
| 3 | Send written notice | Determine whether accurate HOS recording is affected |
| 4 | Reconstruct unavailable required RODS | Confirm the backup logging method |
| 5 | Begin manual RODS if required | Contact the ELD provider or service channel |
| 6 | Keep records available for inspection | Start tracking the 8-day deadline |
This is not a substitute for § 395.34.
It is a way to turn the rule into something dispatch can actually follow at 6:40 on a Monday morning.
The carrier’s eight-day clock may start before the email arrives
This is one of the more important details in § 395.34.
The motor carrier must correct the malfunction within 8 days of:
- discovering the condition; or
- receiving the driver’s notification,
whichever occurs first.
That wording matters.
Suppose telematics staff notice a malfunction on Monday.
The driver sends formal written notice on Tuesday.
The carrier should not automatically treat Tuesday as day one.
The regulation looks to the earlier event.
This is why the incident file should capture both:
When did the carrier first know?
and:
When did the driver provide the required notice?
The repair deadline should not depend on whichever timestamp is more convenient.
Eight days means correcting the problem
FMCSA gives the motor carrier eight days to:
- correct;
- repair;
- replace; or
- service
the malfunctioning ELD.
Opening a vendor ticket on day seven does not itself restore compliance.
Ordering a replacement on day eight does not itself restore compliance.
The operational objective is to have the ELD brought back into compliance within the permitted period unless FMCSA grants additional time.
The clock is therefore a completion deadline, not a deadline to begin investigating.
There is also an enforcement consequence worth making explicit. FMCSA warns that a driver who continues recording HOS on paper for more than eight days without proof of an approved malfunction extension may be placed out of service. The carrier should therefore treat day eight as an operational boundary, not an administrative target.
A carrier should work backward from day eight
A useful timeline looks like this.
Day 0 — malfunction identified
Capture the condition.
Preserve available records.
Obtain the driver’s written notice.
Move to manual RODS where required.
Contact the ELD provider.
Days 1–2 — diagnose and choose a repair path
Determine whether the issue can be corrected remotely.
If hardware is involved, determine availability and replacement timing.
Do not assume vendor support can solve the problem before the deadline simply because a ticket exists.
Days 3–4 — escalate if the repair path is uncertain
A carrier should know by this point whether:
- replacement hardware is available;
- an installer is required;
- the defect affects one unit or multiple units;
- records are being preserved correctly;
- a return-to-service date is realistic.
If the answer to the last question is unclear, the extension issue should already be under consideration.
Day 5 — extension deadline becomes critical
A carrier seeking additional time under § 395.34(d)(2) must notify the appropriate FMCSA Division Administrator within five days after the driver notifies the motor carrier.
That is not the same as five days before the eight-day period expires.
Do not mix the two clocks.
Days 6–8 — finish and verify
Repair or replace the ELD.
Confirm that required functionality is restored.
Make sure the driver has transitioned correctly from manual records back to the compliant ELD.
Preserve evidence of the repair and return to service.
Extension requests need their own timeline
Additional me is not automatic
A carrier that genuinely needs more than eight days can request additional time.
FMCSA’s current ELD support guidance says the request should go to the Division Administrator for the State where the motor carrier has its principal place of business.
The request must be made within the regulatory timeframe and should explain why additional time is needed.
FMCSA identifies information including:
- motor carrier legal name;
- principal place of business;
- USDOT Number;
- contact information for the representative making the request;
- make, model and serial number of each affected ELD;
- date and location of each malfunction;
- actions taken in good faith to repair, service or replace the ELD;
- why the carrier needs time beyond the ordinary eight days.
That final part is important.
“We have not got around to it” is not a repair strategy.
A credible request should show that the carrier has been working the problem.
The extension request has a five-day deadline
The carrier must notify the FMCSA Division Administrator within 5 days after the driver notifies the carrier of the malfunction.
Consider this sequence:
| Event | Date |
|---|---|
| Driver detects malfunction | September 1 |
| Driver sends written notice | September 1 |
| Carrier opens vendor ticket | September 1 |
| Vendor confirms hardware replacement required | September 3 |
| Replacement unit becomes backordered | September 4 |
If the carrier believes an extension is necessary, waiting until September 9 to ask for one is the wrong process.
The extension mechanism is designed to be used while the repair window is still active.
The paperwork should not become an autopsy of an already missed deadline.
What the driver needs during a roadside inspection
Section 395.34(b) addresses inspections during an ELD malfunction.
When inspected for HOS compliance, the driver must provide the authorized safety official with the manually maintained RODS required under the malfunction provisions.
This is where a good office process becomes visible on the roadside.
The driver should not have to explain:
“The ELD stopped working three days ago, but the office has the paperwork somewhere.”
The required records need to be available in the form the driver is expected to produce.
For the carrier, that means the malfunction response needs to reach the cab, not just the compliance inbox.
Diagnose the failure before choosing the response
Not every malfunction requires the same backup records
FMCSA makes a useful distinction.
If an event or malfunction does not interfere with accurate recording of HOS, the agency says the rule does not require the same documentation process that applies when accurate records are affected.
But the underlying malfunction obligations do not simply disappear.
FMCSA’s guidance still points to:
- reporting the malfunction within 24 hours; and
- repairing or replacing the malfunctioning ELD within 8 days.
So the carrier should avoid two opposite mistakes.
Mistake 1: treating every warning as a total ELD failure
That creates unnecessary paper logs and confusion.
Mistake 2: treating a functioning screen as proof that the ELD is compliant
An ELD can have problems involving data recording, synchronization or transfer even when some visible functions still operate.
The relevant question is what required function has failed.
Data diagnostic events are different
A diagnostic event is not automatically an ELD malfunction.
Section 395.34(c) tells the driver to follow the motor carrier’s and ELD provider’s recommendations for resolving a data inconsistency that generates a diagnostic event.
That is why the first step should be classification rather than panic.
For example, a carrier should determine whether the issue is:
- a temporary diagnostic condition;
- an unresolved data inconsistency;
- a malfunction affecting a required ELD function;
- a connectivity issue that does not prevent compliant recording;
- a broader hardware or software failure.
The device provider can help identify the technical category.
The carrier remains responsible for the compliance response.
Fleet size changes the operational response
One truck: the failure is obvious
Consider an owner-operator with one tractor.
The ELD stops recording correctly on Tuesday morning.
The driver:
- notes the problem;
- gives written notice to the motor carrier operation;
- preserves the available electronic records;
- reconstructs missing required records;
- moves to compliant manual RODS;
- contacts the ELD provider.
For a one-truck business, the malfunction is difficult to ignore.
The entire operation is looking at the same problem.
That can actually make the compliance response simpler.
The risk is assuming that because the driver and owner are effectively the same business, formal records do not matter.
They still do.
Ten trucks: one failure can reveal a wider problem
Now consider a ten-truck fleet.
Driver 4 reports a malfunction.
Two days later, Driver 7 reports the same symptom.
The question changes.
This may no longer be one defective device.
The carrier should determine whether the issue involves:
- a model-specific defect;
- an installation problem;
- an account or configuration problem;
- a provider-wide outage;
- multiple independent failures.
The regulatory deadline still applies to each affected ELD.
But the operational response should now examine the fleet.
Waiting for every driver to discover the same problem separately can waste valuable repair time.
The evidence file should tell the story without reconstruction
A clean malfunction file can be small.
It should nevertheless make the sequence understandable months later.
I would want it to contain, where applicable:
- driver’s written malfunction notice;
- date the carrier first discovered the condition;
- device identification;
- screenshots or error information;
- accessible electronic logs preserved at the time;
- reconstructed RODS;
- subsequent manual RODS;
- provider support ticket;
- emails or service communications;
- replacement order;
- repair invoice or technician record;
- extension request and FMCSA response, if any;
- date the ELD returned to compliant service;
- evidence that the driver resumed electronic logging correctly.
The file does not need decorative paperwork.
It needs chronology.
Three weak malfunction files
Certain files look compliant until someone tries to understand what actually happened.
File 1: the support-ticket file
It contains a vendor ticket.
Nothing shows when the driver noticed the problem, what happened to the logs or how the driver recorded HOS during the outage.
The carrier documented the technology problem.
It did not document the compliance response.
File 2: the paper-log pile
There are handwritten logs for several days.
Nobody recorded why they exist.
There is no malfunction notice, device information or repair evidence.
The records may be genuine, but the carrier has made the reviewer reconstruct the incident.
File 3: the repaired-device file
The ELD was replaced successfully on day six.
The carrier keeps the installation receipt.
The previous six days are poorly documented.
Fixing the hardware does not erase the recordkeeping period that occurred before the repair.
Do not merge malfunction and revocation procedures
A malfunction affects an individual device or system condition.
An ELD revocation is different: FMCSA removes an ELD model from the registered list because it no longer satisfies the agency’s requirements.
The operational consequences can overlap because both situations may require temporary alternative records and a replacement device.
The legal triggers are not the same.
For a malfunction, § 395.34 supplies the repair and extension framework.
For a revoked device, the carrier should follow the specific FMCSA removal notice and replacement deadline associated with that device. The process is covered separately in the guide on what to do when an ELD is removed from the FMCSA list.
A carrier procedure labeled simply “ELD problem” is too vague if it treats both situations identically.
Returning to electronic records deserves a deliberate handoff
The incident does not end when the new screen lights up.
Before closing the file, confirm that:
- the ELD is registered and appropriate for the operation;
- driver credentials are correct;
- vehicle assignment is correct;
- the device is recording driving events;
- required records are available;
- data transfer works as required;
- manual RODS and electronic records do not leave an unexplained gap.
The transition back matters because a repaired device can create a second problem if the historical record becomes fragmented.
A five-minute verification is cheaper than explaining a missing day later.
The carrier’s malfunction playbook
For day-to-day use, the whole process can be reduced to this:
Driver
- Identify and note the malfunction.
- Notify the carrier in writing within 24 hours.
- Preserve records that remain available.
- Reconstruct unavailable required RODS.
- Continue manual RODS when the malfunction prevents proper electronic recording.
- Present those records during an inspection.
Carrier
- Record when the malfunction was discovered or reported.
- Confirm the driver’s backup records.
- Contact the ELD provider.
- Track the earlier event that starts the eight-day clock.
- Repair, service or replace the ELD within eight days.
- Request an extension within five days of driver notice if necessary.
- Verify the ELD is compliant before closing the incident.
- Preserve the incident evidence.
Nothing in that workflow is especially complicated.
The difficulty comes from starting it too late.
An ELD malfunction is a timed records incident
The technical repair is only one part of the event.
The driver has records to preserve.
The carrier has a repair deadline.
The extension process has its own deadline.
Roadside enforcement continues while the device is unavailable.
Those obligations overlap.
That is why the best malfunction process does not begin with the question:
“Can the vendor fix this?”
It begins with:
What records are at risk right now, what clock has started, and what must remain provable until the ELD is compliant again?