When the ELD breaks: the malfunction drill

← All guides

Every device fails someday. A screen goes dark, the unit stops recording, the connection to the engine drops and does not come back. For a driver, the frightening part is not the failure itself. It is the question that follows it: am I still legal to drive, and what do I do with my hours now?

The rules answered that question in advance. Section 395.34 of the federal hours rules is a drill, written for the bad day, and it splits the work cleanly in two. The driver has three duties, in a set order. The carrier has one clock: eight days to correct the malfunction, counted from whichever comes first — the day the carrier discovers the condition, or the driver's notification. There is also a written path to ask for more time when eight days genuinely is not enough. This guide walks through all of it, in the order you would live it.

The driver's drill, in order

Do these three things in this order. The order matters because each step protects the next one: the note proves when you knew, the notice starts the carrier's clock, and the paper record keeps your week lawful while the device is down.

1. Note it, and notify the carrier in writing within 24 hours

   Note the malfunction — what happened, and when you first saw it. Then give the carrier written notice of it within 24 hours. Written is the word to hold onto. A phone call can start the conversation, but the duty is a notice in writing that reaches the carrier within 24 hours. Keep your own copy with the time you sent it. That notice does two jobs: it tells the office the record is now on paper, and it starts the count toward the carrier's repair deadline.

2. Reconstruct the current day and the previous 7 days

   Rebuild the record of duty status for the current 24-hour period and the previous 7 consecutive days, on graph-grid paper logs — the same blank grids the truck is required to carry. There are two honest exceptions, and only two: you do not need to reconstruct days you already have records for, and you do not need to reconstruct what can still be retrieved from the ELD itself. If part of the week is still in the device, use it. Rebuild the rest from your own notes, your trip papers, and your memory while the week is fresh. This is the step drivers put off, and it gets harder every day they wait. Do it the same day.

3. Keep the record by hand until the device is back

   From the malfunction onward, keep your record on paper under 49 CFR 395.8, the ordinary record-of-duty-status rule, until the ELD is serviced and back in compliance. Paper here is not a rough draft. It is your record: statuses, times, locations, and the day's totals, kept as carefully as the device kept them. When the device returns, the paper days stay part of your record history. They are not thrown away, and the carrier keeps them like any other records.

Why the blank grids live in the cab

None of this works without paper on hand, which is why a separate rule stocks the truck in advance. Under 49 CFR 395.22(h), the carrier must ensure the driver has onboard an instruction sheet for malfunction reporting and recordkeeping, and a supply of blank record-of-duty-status graph-grids sufficient for at least 8 days.

Eight days is not an accident of drafting. It matches the shape of the problem: a reconstructed week behind you, plus the days ahead of you while the device is being fixed. Check your supply the way you check the rest of the packet. Grids used as note paper in June are a crisis in October. If the count is low, tell the office before the road tells you.

At an inspection during a malfunction

If you are stopped while the device is down, the drill holds. Under 49 CFR 395.34(b), the driver shows the officer the hand-kept records: the reconstructed days and the paper record for today. This is the moment the first two steps pay off. A written notice sent on time, a rebuilt week in the folder, and a paper log kept up to the hour read as a driver following the rule — because that is exactly what they are. An officer can work with a clean paper record. What an officer cannot work with is a dead device and no record at all, which is the one outcome the drill exists to prevent.

Keep the paper in the same place you keep the rest of the inspection packet, in order by day, where you can hand it over without digging. How the normal transfer stop works when the device is healthy is covered in our guide to roadside inspection and the transfer.

The carrier's clock: 8 days to correct it

The driver's duties start the story; the carrier's clock finishes it. Under 49 CFR 395.34(d)(1), the carrier must correct the malfunction — repair it, replace the device, or have it serviced — within 8 days of discovering the condition or of the driver's notification, whichever comes first.

Note the two starting points. The clock does not politely wait for the driver's letter if the office already knows. Whichever knowledge comes first starts the count, and the eighth day is the deadline either way. For a small carrier, the practical habit is simple: the day a malfunction notice lands, write the deadline on the calendar in plain sight, and treat the repair as scheduled work, not as something to fit in. Eight days passes quickly in a busy week, and the driver is keeping paper the whole time the device sits.

When 8 days genuinely is not enough

Sometimes the fix cannot be done in eight days. A part is back-ordered, a unit must be replaced, the truck is far from anywhere the work can happen. The rule has a path for that too, and it is strict about timing and content. Under 49 CFR 395.34(d)(2), the carrier must notify the FMCSA Division Administrator for the state of the carrier's principal place of business within 5 days after the driver's notice of the malfunction.

Five days is shorter than eight, on purpose: the request for more time must be made before the repair deadline runs out, not after. The signed request names:

• The carrier representative asking — name, address, and phone number.
• The make, model, and serial number of each affected ELD.
• The date and location of each malfunction, as the driver reported it.
• A concise statement of the good-faith effort made to repair, replace, or service the device, and why more time is needed.

If the request meets the requirements, the carrier is treated as compliant while FMCSA decides, under 49 CFR 395.34(d)(5). FMCSA answers in writing, and may attach conditions to any extra time it grants, under 49 CFR 395.34(d)(3)–(4). Two lessons sit inside that. First, the driver's written notice is the paper the whole request stands on — another reason it must be in writing, on time, and kept. Second, good faith has to be real and describable: what was tried, when, and what is still in the way. A carrier that started the repair on day one can write that statement in a paragraph. A carrier that waited cannot.

A diagnostic light is not the same thing

Not every warning on the device is a malfunction, and treating the two as one causes needless paper — or worse, needless driving on a record that is quietly wrong. The device also watches its own data — position, motion, and timing among them — and raises diagnostic events when it finds inconsistencies in that data. A diagnostic event is a smaller class of problem: the device is telling you something in its data does not line up.

For diagnostic events, under 49 CFR 395.34(c), the driver follows the carrier's and the provider's instructions to resolve the inconsistency. The ELD shows the two kinds of problem separately, so read the screen for which one you have. A diagnostic light is not the paper-log drill unless it becomes a true malfunction — a device that can no longer record or produce the record as the rule requires. If you are unsure which kind you are looking at, ask. Guessing wrong in one direction wastes a day; guessing wrong in the other leaves you with no lawful record.

The habit that makes the bad day small

Everything in this guide gets easier if two small habits are already in place. Keep the packet stocked — the malfunction instruction sheet and at least 8 days of blank grids, checked like fuel. And keep your own trip notes, even brief ones, as you go. The reconstruction step is ten minutes of work for a driver who jotted times and places all week, and a long, uncertain evening for a driver reconstructing from nothing. The device will break someday. With the notice sent, the week rebuilt, and paper running, that day stays what the rule intends it to be: an inconvenience, handled in order, inside the law.

Rules checked October 2026. Rule sources: 49 CFR 395.34; 49 CFR 395.22(h).