If your ELD quits in the middle of a load, you still have to track your hours. FMCSA ELD malfunction rules tell drivers what to document, when to switch to paper records, what to show at a roadside inspection, and how fast the motor carrier has to repair or replace the device.
This guide is built like a field checklist for owner-operators and small fleets. It separates driver duties from motor carrier duties, explains the difference between a diagnostic event and a real compliance malfunction, and shows what to do when you’re the driver and the carrier.
ELD Malfunction Rules: The Fast Answer for Drivers#
The fast answer is this: document the problem, notify the motor carrier within 24 hours, start paper RODS if required, and keep any ELD records you can still access. FMCSA’s rules don’t let you ignore Hours of Service just because the screen froze, the app crashed, or the device won’t transfer data.
An Electronic Logging Device (ELD) is the hardware and software that automatically records driving time and supports a driver’s Hours of Service records. A Record of Duty Status (RODS) is the driver’s log showing driving, on-duty, sleeper berth, and off-duty time.
The first mistake drivers make is treating any ELD problem like a free pass. It isn’t. If the device stops doing what the rules require, you still need a compliant record of your duty status under FMCSA rules in 49 CFR Part 395.
The first four actions to take#
First, note what happened. Write down the date, time, location, truck or unit number, the ELD name, the warning or error shown, and what stopped working.
Second, notify the motor carrier within 24 hours. If you’re leased on, that usually means safety, dispatch, or whoever handles log compliance. If you’re running under your own authority, you’re notifying your own carrier operation and should create a real record of that notice.
Third, start paper RODS when the malfunction requires it. Don’t wait until the end of the day and don’t assume a screenshot alone covers you.
Fourth, keep whatever the ELD still provides. That can include displayed logs, malfunction messages, transfer-failure messages, and troubleshooting records.
What changes when you are both driver and carrier#
If you’re an owner-operator with your own USDOT number and operating authority, you may wear both hats. A motor carrier is the business responsible for operating the commercial vehicle and maintaining compliance, even if that business is just you.
That means the driver side and carrier side both matter. You still have to log your hours accurately, and you also have to handle the repair, service, or replacement process. The general repair window is eight days, with a possible extension request by the carrier if the device can’t reasonably be fixed in time.
Is It an ELD Data Diagnostic Event or a Compliance Malfunction?#
A data diagnostic event means the ELD detected a data-quality or monitoring issue that needs attention, but it is not automatically a compliance malfunction. A compliance malfunction means the ELD can no longer meet one of the required technical functions long enough to trigger the malfunction rules, so the driver and carrier need to act accordingly.
This matters because not every warning light means the same thing. Drivers often see an alert and assume the whole device is out of service. Sometimes that’s true. Sometimes it means the device spotted a problem that still might be corrected before it becomes a compliance malfunction.
What a data diagnostic event means#
A data diagnostic event is the ELD’s way of flagging that something is off in the data capture, monitoring, or transfer process. Think of it as the device saying, “Something needs attention.”
That could involve weak connections, missing information, or a transfer issue that hasn’t crossed into full malfunction territory yet. The right move is to follow the device instructions and your carrier’s process right away instead of guessing based on a forum post or another driver’s app.
Different registered ELD providers may display different warnings, labels, or error codes. Don’t treat one brand’s code list as universal. What matters is whether the device can still meet the functions required under the ELD rule.
What makes an issue a compliance malfunction#
A compliance malfunction is a failure of the ELD to meet required technical standards under the federal ELD rule. When that happens, the driver’s response shifts from basic troubleshooting to documented malfunction handling.
Under the federal rules, the line between a diagnostic event and a malfunction depends on the specific function involved and how long or how seriously the device fails. That is why drivers should not self-diagnose based only on a warning color or a vague “sync error” message.
If you’re unsure which one you’re dealing with, act conservatively. Document the issue, notify the carrier, and be ready to switch to paper logs if the ELD cannot provide the required records.
The six ELD monitoring functions#
The six big monitoring functions are power, engine synchronization, timing, positioning, data recording, and data transfer. In plain English, the ELD has to stay powered, connect properly to the engine, keep accurate time, know the vehicle’s location when required, record the data correctly, and transfer the records when the rules require it.
Power means the ELD has to stay on and connected to vehicle power as required.
Engine synchronization means the ELD has to link with the engine data it uses to identify driving time and vehicle movement.
Timing means the device has to maintain the required time standard for recording duty status events.
Positioning means it has to capture location information as required by the rule.
Data recording means it has to store the required records properly.
Data transfer means it has to send the records to an authorized safety official using an approved method when required under 49 CFR 395.26.
A problem in any one of those areas can start as a diagnostic event and later become a compliance malfunction. That’s why a prompt response matters.
What To Do First When Your ELD Stops Working#
When your ELD stops working, your first job is to build a clean paper trail and a clean hours-of-service trail at the same time. Start by documenting exactly what failed, notify the carrier within 24 hours, switch to paper RODS when required, and preserve any records the device still shows, based on FMCSA’s ELD guidance at fmcsa.dot.gov.
Step 1 – Safely document the issue#
Start at the moment you notice the failure. If you’re driving, deal with it safely when you’re stopped.
Write down:
- date
- time
- location
- truck or unit number
- trailer number if relevant
- ELD device or app name
- exact error message or warning
- what feature failed
Be specific. “ELD messed up” is weak documentation. “10:42 a.m., I-40 MM 188, unit 12, app froze and would not display current RODS” is useful.
If the device shows a malfunction screen, capture it if you can do so safely. Screenshots and photos help preserve facts, but they do not replace required paper logs when paper logs are required.
Step 2 – Notify the carrier within 24 hours#
The next move is formal notice. FMCSA expects the driver to notify the motor carrier of the malfunction within 24 hours.
Make that notice usable. An email, in-app message, text preserved by dispatch, maintenance ticket, or safety report is better than a phone call with no record. If your carrier has a set process, use it. If you’re the carrier, create a record anyway so you can show when the issue was discovered and what you did next.
Step 3 – Start a paper RODS for the current day#
If the ELD cannot provide the required duty-status record, begin a paper RODS for that day. A paper RODS is a handwritten duty-status log on graph-grid paper that tracks the same duty categories as an ELD record.
Don’t assume you can “fix it later” in the portal and skip the paper log now. If the device isn’t doing its job, you need a compliant backup record for the current day and, if necessary, the prior seven days.
This is where drivers get burned at roadside. The device fails, they keep moving, and then they have no clean record to show what happened and when.
If you want help sorting out compliance problems before they turn into violations,
Step 4 – Preserve what the ELD still shows#
Keep every piece of usable evidence. That includes current-day displays, prior logs still visible on the screen, malfunction notices, transfer-failure notices, troubleshooting steps, support ticket numbers, and vendor messages.
If the app still opens but won’t transfer data, preserve the records it does show. If the in-cab unit is dead but the back-office portal still has logs, note that immediately and work with the carrier to retrieve them.
The key idea is simple: save everything, but don’t confuse saved evidence with your actual logging duty. Evidence supports your records. It doesn’t replace them.
How Long Can You Use Paper Logs After an ELD Malfunction?#
Paper logs are a temporary backup during an ELD malfunction, not an open-ended substitute for an ELD. Under 49 CFR 395.34, the motor carrier generally must repair, service, or replace the malfunctioning ELD within eight days after learning of the condition, and paper RODS are used during that period unless FMCSA grants more time.
The eight-day repair or replacement window#
This is the deadline most drivers remember, but they often remember it wrong. The eight-day period is not a free choice to run paper because it feels easier.
It is a limited window tied to a real malfunction. During that period, the driver keeps compliant RODS while the carrier works on the fix. The regulatory basis is 49 CFR via eCFR, specifically 49 CFR 395.34.
When a carrier may request more time#
Sometimes a repair or replacement can’t reasonably be completed in eight days. In that situation, the motor carrier may request an extension from FMCSA.
That is a carrier responsibility, not a driver shortcut. If you’re a company driver or leased owner-operator, follow the carrier’s written instructions and keep your records straight. If you’re operating under your own authority, you may be the person responsible for making sure that extension request is handled correctly.
An extension is not automatic. Drivers should not assume that “the vendor is working on it” equals unlimited paper logging time.
When to return to the ELD#
Go back to normal ELD use as soon as a compliant device is available. Don’t keep running paper after the issue is fixed just because it’s convenient.
Once the ELD is working again, follow the carrier’s process for retaining, entering, or reconciling any required records from the malfunction period. That may include keeping the paper logs with your records and making sure the timeline is complete and accurate.
How To Reconstruct Your Current Day and Prior Seven Days of Logs#
If your ELD malfunction leaves you without accessible recent records, you must reconstruct the current day and the prior seven consecutive days of RODS unless those records are already available from the ELD. That means building a duty-status record from reliable documents and available data, not just telling an inspector or safety department that the system was down.
Records required after a malfunction#
This requirement catches drivers off guard. They think the issue is only today’s outage. It isn’t always.
If the recent records can’t be retrieved from the ELD, the driver has to recreate the current day and the previous seven consecutive days. The point is to show actual recent duty status, not just the fact that a device broke.
That reconstruction should cover driving, on-duty not driving, sleeper berth if used, and off-duty time as accurately as the available records allow.
When ELD records can still be retrieved#
Sometimes the device in the truck fails, but the records still exist somewhere else. The mobile app may be dead while the web portal still works. The display may be frozen while support can still pull prior logs. A transfer function may fail even though the duty records remain visible.
If the ELD still provides the required records, use them. The reconstruction duty applies when those records are unavailable to you and need to be rebuilt.
That is why the first step after a malfunction is preserving what still exists. A partial record is a much better starting point than a blank page.
Using supporting documents without guessing#
Use contemporaneous records to rebuild the timeline. Contemporaneous means created at the time of the events, not days later from memory alone.
Useful sources include:
- available ELD displays or portal records
- dispatch messages
- bills of lading
- fuel receipts
- toll records
- GPS history
- scale tickets
- pickup and delivery appointments
- personal notes made that day
Build the day in order. Start with when you came on duty, when you began driving, when you stopped, when you fueled, when you arrived, and when you went off duty or into the sleeper berth.
Don’t guess to make the page look neat. If you’re unsure about a time, use the best supporting document you have and tell the carrier or safety contact where the uncertainty is. It is better to flag a genuine gap than to invent a clean but inaccurate log.
If the provider’s portal, mobile device, or in-cab unit cannot retrieve the prior seven days, say that clearly in your internal report and start the reconstruction from the documents you do have. The goal is an honest record supported by real evidence.
What To Carry and Show During a Roadside Inspection#
During a roadside inspection, you need to be able to produce your current and recent duty-status records and the ELD support materials required by the rule. Under 49 CFR 395.24 and 49 CFR 395.26, that means more than just having the app on your phone; you should also have instructions, blank graph grids, and any malfunction-related backup records ready to show.
Required ELD information and instructions#
Drivers subject to the ELD rule are expected to have required ELD information available. The support package matters.
Per the federal ELD requirements at eCFR, a practical roadside kit should include:
- ELD user instructions
- instructions for transferring ELD records to an authorized safety official
- blank graph-grid paper logs
- malfunction instruction sheets if your provider supplies them
- charging cable or power backup if your device depends on one
Those basics get overlooked until inspection day. Then the driver realizes the tablet is dead, the charger is missing, and nobody knows where the instruction card went.
Paper logs and prior records#
If you’re operating under the malfunction process, have your paper RODS and any reconstructed prior records organized and readable. If some records still exist in the ELD and some are on paper, carry both.
Don’t assume a phone photo or a verbal explanation is enough. If records must be produced, produce the records you have, along with the required ELD instructions and malfunction documentation.
A professional roadside approach goes a long way: stay calm, explain the issue briefly, provide the available records, and note the inspection result for the carrier file.
When data transfer is the problem#
A data-transfer problem is not always the same as a total ELD malfunction. The device may still display the records even if one transfer method fails.
That distinction matters because the inspection response may depend on whether the issue is limited to transfer or whether the device can no longer perform required functions more broadly. Either way, document the problem and follow your provider’s and carrier’s troubleshooting process.
The main point is this: don’t show up to an inspection with nothing but a story. Show the records, the instructions, and the malfunction trail you do have.
What the Motor Carrier Must Do After an ELD Malfunction#
After an ELD malfunction, the motor carrier must handle the repair, service, or replacement process while the driver keeps accurate records of duty status. In practice, that means tracking the malfunction report, troubleshooting steps, vendor contact, repair progress, replacement timing, and any extension request, while making sure the driver has a workable compliance plan.
Repair, service, or replacement responsibilities#
The carrier side is different from the driver side. The driver logs hours and reports the issue. The carrier fixes the equipment problem or replaces the unit.
A clean carrier file should show when the malfunction was reported, what the issue was, what troubleshooting was attempted, whether the vendor was contacted, and what the repair or replacement plan is. If a device has to be swapped out, the file should show that too.
Tracking the malfunction and driver notice#
The carrier should keep the notice from the driver and any follow-up communications. That includes messages, tickets, service requests, vendor case numbers, and internal instructions given to the driver.
That paper trail matters if there is later confusion about when the carrier learned of the problem or whether the issue was handled within the required timeframe. Good documentation protects against a lot of avoidable arguing later.
Extension responsibilities for owner-operators#
If you run under your own authority, you may be both the person keeping the paper logs and the person responsible for the extension request. That’s common for solo operators, and it makes advance planning important.
If you’re leased on, confirm now who handles ELD service, replacement, and any FMCSA extension request. Check your lease, safety policy, and vendor support process before you have a breakdown on the road.
Common ELD Violations and How To Avoid Them#
The most common ELD violations usually come from missing or inaccurate records, inability to produce required information, missing backup materials, or a malfunction that was not handled under the rules. Not every technical alert is a violation by itself, but unresolved device problems combined with weak recordkeeping can quickly turn into one.
Incomplete or inaccurate duty-status records#
A bad log is still a bad log whether it started on paper or on a tablet. Inaccurate duty-status changes, missing segments, guessed times, and reconstructed records that don’t match supporting documents create problems fast.
The best prevention habit is to keep logs current and document problems the moment they happen.
Failure to retain or produce required records#
Another common issue is not having the recent records available. That can mean missing the current day, missing prior days, or failing to reconstruct the prior seven days when the ELD records are unavailable.
If an inspector asks for records, “the app crashed” is not the record. The record is the log you can show.
Missing ELD instructions or blank paper logs#
Drivers also get tripped up by missing support materials. No blank graph-grid paper, no transfer instructions, no user guide, dead tablet battery, forgotten password, or no charger in the cab.
A simple weekly cab check prevents a lot of this. Keep paper logs, instructions, charging gear, login access, and carrier support numbers together.
Ignoring unresolved malfunctions#
The final big one is delay. Drivers keep running with a known issue, nobody creates a clean report, and the repair window gets fuzzy.
Before your next trip, build a repeatable compliance kit and review your malfunction process. If you want help reviewing the coverage side of your trucking operation while you tighten up compliance habits,
Frequently Asked Questions About ELD Malfunctions#
What do you do if your ELD is malfunctioning?
Document the problem right away, notify the motor carrier within 24 hours, begin paper RODS if required, and preserve any records the ELD still shows. Then follow the carrier’s process for troubleshooting, repair, or replacement so your Hours of Service record stays compliant while the device issue is being handled.
Start with the facts: date, time, location, unit number, device name, and the exact error or failed function. If you’re leased on, send that notice through the carrier’s normal channel and make sure there’s a record of it. If you’re operating under your own authority, create your own written record and start the carrier-side follow-up too.
How long can you use paper logs after an ELD malfunction?
Paper logs are generally a short-term backup during the malfunction period, not a permanent alternative to the ELD. Under 49 CFR 395.34, the motor carrier generally has eight days to repair, service, or replace the malfunctioning device, unless FMCSA grants more time through an extension.
During that period, the driver should keep accurate paper RODS and carry any supporting records needed for inspection. Once a compliant ELD is available again, the driver should return to normal ELD use and follow the carrier’s instructions for retaining or reconciling the malfunction-period records.
What happens if my ELD malfunctions and I can’t get my 7 day log?
If you cannot retrieve the current day and prior seven consecutive days from the ELD, you must reconstruct those records using reliable documents and available data. That means building an honest Record of Duty Status from contemporaneous sources instead of guessing or filling in times from memory alone.
Use whatever you have: dispatch messages, bills of lading, fuel receipts, toll data, GPS history, appointments, scale tickets, and personal notes. If some times are uncertain, tell the carrier or safety contact where the uncertainty is. The goal is an accurate recent-duty record, not a perfect-looking page unsupported by facts.
What are the most common ELD violations for truck drivers?
The most common ELD-related problems are incomplete or inaccurate duty-status records, missing recent logs, failure to produce required ELD information during inspection, missing blank graph-grid paper, and not handling a device malfunction under the federal rules. The violation usually comes from the missing record or poor response, not just from seeing a warning on the device.
A practical way to reduce risk is a weekly cab compliance check. Make sure you have blank paper logs, ELD instructions, transfer instructions, login access, charging equipment, and current carrier support contacts. When a problem appears, document it and act early.
Can I keep driving if my ELD screen or app stops working?
You may still be able to continue operating if you maintain compliant Hours of Service records and follow the malfunction process, but you cannot simply drive with no duty-status documentation. If the ELD cannot provide the required records, switch to paper RODS and notify the carrier within 24 hours.
The key question is not whether the screen is annoying or the app is glitchy. The key question is whether you can still produce the required records and whether the device still meets the rule’s required functions. If not, treat it seriously, document everything, and move into the backup process right away.
