A driver pulled off I-95 outside the Hialeah yard last spring when his ELD screen froze mid-shift. He called dispatch, dispatch called the ELD provider, and three days passed before anyone wrote down the malfunction date. By the time an inspector pulled the truck over on the fourth day, the paper logs didn't match the window FMCSA expects. The fine landed on the carrier, not the ELD vendor.
What Counts as a Malfunction
FMCSA splits ELD problems into two buckets: malfunctions and diagnostic events. A malfunction means the device can't reliably record or display hours-of-service data anymore. A diagnostic event flags a smaller issue the driver can usually work through without switching to paper.
A cracked mount or a dead cellular signal isn't automatically a malfunction. The test is whether the ELD still captures accurate driving time, engine hours, and location. A screen that won't display current status but keeps logging in the background is a different problem than a unit that stopped recording the moment the engine turned over.
The 24-Hour Notice Rule
Once a driver spots a malfunction, the clock starts. The driver must notify the motor carrier in writing within 24 hours. A text to dispatch counts. A verbal mention during a break doesn't, because nothing documents the date the malfunction started.
Dispatch offices that wait for a driver to mention a problem a second or third time lose days off that 8-day window without realizing it. Log the first report, even an informal one, the moment it comes in.
The 8-Day Paper Log Window
Once the malfunction hits, the driver reconstructs the current 24-hour period and the previous 7 consecutive days on paper records of duty status. That paper trail has to hold up through roadside inspections until the ELD gets fixed or replaced.
The 8-day limit isn't a suggestion. After 8 days, a carrier running an unresolved malfunction without an FMCSA extension is operating out of compliance, even if the driver filled out every paper log correctly. A broken ELD that sits in a maintenance queue for two weeks because a part needs to ship from out of state doesn't buy extra time on its own.
For Miami drayage fleets running short port-to-warehouse turns, the paper log burden feels light since most drivers already qualify for short-haul exemptions on logging hours. The malfunction clock still runs regardless of exemption status, because the 8-day repair window applies to the equipment, not the driver's duty-status category.
Reading the Malfunction Codes
ELDs report problems using single-letter malfunction codes and numbered diagnostic codes. Knowing the difference saves a dispatcher from treating a minor diagnostic flag like a full malfunction, or missing a real one because the code looked unfamiliar.
Diagnostic events, numbered 1 through 6, flag smaller issues like a brief power gap or an unidentified driving segment. Most resolve on their own once the condition clears. A malfunction code doesn't clear itself. It needs a technician or a replacement unit.
What an Inspector Checks
Florida Highway Patrol and DOT officers look for three things during a roadside stop when a driver claims an ELD malfunction: the paper logs covering the current period plus the prior 7 days, a record of when the malfunction started and when it was reported, and proof the carrier is actively working toward a repair rather than ignoring the problem.
- Paper RODS covering the full 8-day window, filled out completely for every one of those days.
- A written malfunction notice with a date and time, matching what the driver tells the officer.
- Evidence of a repair ticket, replacement order, or service call showing the carrier isn't sitting on the problem.
A driver who can't produce paper logs because "the ELD broke so I just didn't log anything" walks straight into a violation. The malfunction excuses the device. It doesn't excuse the driver from keeping records.
Requesting an Extension
If a repair can't happen inside 8 days, a motor carrier can request an extension from FMCSA under 49 CFR 395.34. The request needs to go in before the 8-day window closes, not after.
Extensions aren't automatic. A carrier that waited six days to order a replacement part has a weaker case than one that ordered the part on day one and is waiting on a shipping delay outside its control.
Building a Response Plan
The fleets that handle malfunctions cleanly treat it like any other equipment failure: someone owns the problem from the first report to the final fix, and every step gets a timestamp.
- Keep blank paper RODS forms in every truck. A driver who has to search for a form on day one of a malfunction loses time he needs for the log itself.
- Require written notice, even a text message, the moment a driver spots a problem. Verbal reports get forgotten or misremembered.
- Log the malfunction date in a shared tracker the moment dispatch hears about it, so nobody has to reconstruct the timeline later from memory.
- Call the ELD vendor same day. A replacement unit ordered on day one beats one ordered on day five, and it strengthens any extension request if the repair runs long.
- Brief the driver on what to hand an inspector: paper logs, the malfunction notice, and the repair ticket number if one exists.
At One A Trucks, dispatch treats an ELD malfunction report the same way it treats a mechanical breakdown call: logged, timestamped, and assigned to someone who follows it through to the fix. The 8-day window is short enough that a day of confusion at the start can eat a third of it before anyone picks up the phone.