What Is a Reconstruction of Records of Duty Status, and When Is Your Driver Required to Complete One?

Key Takeaways

• Reconstruction of records of duty status is required under 49 CFR 395.34 when an ELD malfunctions and the driver’s hours of service data cannot be retrieved electronically.
• Your driver must give the carrier written notice of an ELD malfunction within 24 hours, per 49 CFR 395.34(a)(1).
• Once notified, the carrier has 8 days to repair, replace, or otherwise correct the malfunctioning ELD, per 49 CFR 395.34(d)(1).
• A reconstruction generally needs to cover the current 24-hour period plus the previous 7 consecutive days, per 49 CFR 395.34, unless those records are already available in another compliant form.
• Driving without a valid record of duty status, including a failure to reconstruct one properly, can lead to a citation under 49 CFR 395.8(a)(1).
• CVSA recorded 58,382 falsification violations in 2024, a reminder of how closely inspectors review handwritten and reconstructed logs, according to CVSA’s 2026 International Roadcheck.
• Reconstructed paper records still fall under the 6-month retention requirement in 49 CFR 395.8(k)(1), the same as normal ELD records.
• Only devices on the FMCSA registered ELD list count as compliant equipment, which matters if a malfunction forces a temporary switch to paper logs.

Introduction

Your driver’s hours of service record is supposed to update itself automatically every time the truck moves, stops, or changes duty status, since that’s the whole point of an ELD. But devices fail, connections drop, and data doesn’t always make it where it needs to go. When that happens, your driver can’t just wait around for the system to fix itself. They have to sit down, usually with a pen and a graph-grid paper log, and rebuild the record of duty status from memory, receipts, dispatch notes, and anything else that shows what they were doing and when.

This matters more than it might seem at first. A record of duty status isn’t paperwork for its own sake. It’s the document a DOT officer checks at a roadside inspection to confirm your driver hasn’t been on the road longer than the hours of service rules allow. If that record is missing, incomplete, or clearly wrong, the inspection stops being routine. Officers can place a driver out of service, and your fleet can end up with a violation that affects your compliance record for months.

Here’s what a reconstruction of records of duty status actually involves, when your driver is required to do one, how far back it has to reach, and what happens if the reconstructed record doesn’t hold up. We’ll also cover how reconstructed paper logs compare to normal ELD logs, since the two are held to different standards even though they’re supposed to represent the same information. Our compliance team in Tucson works through questions like this with fleets every week, so the steps below reflect what actually happens on the road, not just what the regulation says on paper.

Malfunctions happen less often with equipment built for the job, but if one does show up and you’d rather just talk it through with someone, that’s what we’re here for. You can reach out to our team with your specific situation, or take a look at how our ELD platform and hardware handles malfunction reporting and data backup before it becomes a problem on the road. Either way, it’s worth doing before your next trip, not after something goes wrong.

What Does It Mean to Reconstruct a Record of Duty Status?

Reconstructing a record of duty status means your driver manually rebuilds their hours of service log for a period when the ELD wasn’t capturing or providing accurate data. Instead of the device logging duty status changes automatically, your driver fills in the same information by hand on a paper log, using whatever accurate records they have available.

This isn’t guesswork, and it shouldn’t be treated like a rough estimate of a normal day. Your driver is expected to use real information, things like fuel receipts, toll records, dispatch communications, bills of lading, or their own memory of the day’s activity, to recreate an honest picture of driving time, on-duty time, and off-duty time. The goal is a record that would match what the ELD should have shown if it had been working correctly.

Reconstruction is different from an edit or annotation. An edit under 49 CFR 395.30 corrects a mistake in an existing electronic record, and the driver has to certify the change. A reconstruction happens when there’s no usable electronic record at all for a stretch of time, so your driver is building the log from scratch on paper.

When Is Your Driver Required to Reconstruct Records?

Reconstruction is required whenever an ELD malfunctions and the driver’s hours of service data for the current period isn’t retrievable in a compliant electronic form. The most common trigger is a device that stops recording, loses connection to the engine, or can’t produce the required data for a roadside pull.

Once a malfunction is confirmed, your driver has to reconstruct their record of duty status going back a set window under 49 CFR Part 395 HOS rules, unless that information already exists somewhere your driver or the carrier can access it, like an unaffected ELD backend or a properly stored paper log from earlier in the trip. The exact number of days that window covers is explained below.

A few other situations can also call for a paper-based record instead of relying on an ELD alone. Drivers operating under the pre-2000 engine exemption, covered under 49 CFR 395.8(a)(1)(iii), aren’t required to use an ELD in the first place and rely on paper logs as their normal method. That’s a different situation from reconstruction, but it explains why paper logs still show up in fleets that are otherwise fully electronic.

If your fleet includes drivers who move between company trucks or rental equipment, it’s worth checking how our local drivers ELD guide addresses short-notice vehicle changes, since a swap between devices can sometimes leave a gap that needs to be filled the same way.

How Does Your Driver Reconstruct Records During an ELD Malfunction?

Your driver reconstructs records by first noting the malfunction, switching to paper logs for the affected period, and then filling in duty status changes using accurate supporting information rather than estimates. The paper log has to follow the same graph-grid format used for any non-ELD record of duty status.

Here’s how it typically works, as soon as your driver notices the ELD isn’t functioning correctly, they note the malfunction and the time it started, then keep a manual record of duty status going forward on graph-grid paper logs from that point on. For the portion of the reconstruction window that isn’t already documented, your driver fills it in using whatever accurate source material is available: dispatch logs, fuel stops, toll receipts, or their own detailed recollection of the day.

Two deadlines run in parallel once a malfunction happens, one for your driver and one for your fleet: your driver’s window to notify the carrier, and the carrier’s window to fix the device. Both are covered under 49 CFR 395.34, with the specific timeframes and citation numbers detailed in the buyer guide section further down. If your team needs help sorting out a malfunction on the road, reaching out to our support team the same day keeps things moving and gives your driver a clear answer on how long they’ll need to keep paper logs, since our support line runs 24 hours a day, 7 days a week and doesn’t have to wait for business hours.

What Time Period Must Be Reconstructed?

The standard reconstruction window covers the current 24-hour period plus the previous 7 consecutive days, the same lookback period officers use to check compliance with the 60-hour and 70-hour on-duty limits under 49 CFR 395.3.

If part of that window is already documented, either through an unaffected portion of the ELD record or a properly completed prior paper log, your driver doesn’t need to redo that section. The reconstruction only needs to fill the actual gap, so in practice the amount of paper logging your driver has to do depends entirely on how much of the 7-day window the malfunction actually affected.

Once the ELD is repaired or replaced, your driver goes back to normal electronic logging. The paper logs from the reconstruction period don’t get deleted or replaced, since they become the official record for those days and get filed the same way any other supporting document would be.

What Happens If Your Driver Cannot Reconstruct Accurate Records?

If a reconstructed record is missing, incomplete, or doesn’t hold up against supporting documents, your driver can be cited for a no-record-of-duty-status violation under 49 CFR 395.8(a)(1), the same citation used when a driver has no log at all. That puts the driver at risk of being placed out of service during an inspection.

There’s a sharper risk beyond a simple missing-record citation. If an officer believes the reconstructed log was deliberately falsified rather than honestly rebuilt from incomplete memory, that falls under knowing falsification, covered by 49 CFR 395.8(e)(1), which carries a steeper penalty than a routine missing-record citation. Maximum civil penalty amounts for violations like this are adjusted annually for inflation under the FMCSA penalty schedule, so the exact fine can shift from year to year. This is one reason reconstruction has to lean on actual supporting documents wherever possible, not just a driver’s best guess at what a normal day looked like.

CVSA’s 2026 International Roadcheck placed a specific focus on log integrity and tampering, and 58,382 falsification violations were recorded across the industry in 2024 according to CVSA annual data. Inspectors are trained to compare a reconstructed paper log against fuel receipts, GPS pings from other systems, and dispatch records, so a reconstruction that’s rushed or inconsistent tends to get noticed.

How Long Must Reconstructed Records Be Kept?

Reconstructed paper logs have to be kept for 6 months, the same retention period that applies to standard records of duty status under 49 CFR 395.8(k)(1), and they don’t get a shorter window just because they were created by hand instead of by the ELD.

Supporting documents used to build the reconstruction, receipts, dispatch notes, toll records, fall under the supporting documents requirement in 49 CFR 395.8(k) and should be kept alongside the reconstructed log itself. If your dispatch team already tracks maintenance and inspection paperwork through our ELD and DVIR integration, it’s worth keeping reconstruction-related documents in that same organized system so they’re easy to pull if a compliance review ever asks for them.

Reconstructed Paper Logs vs Normal ELD Logs: What’s the Difference?

Both formats are treated as legitimate records when completed correctly. The difference is that a paper reconstruction puts more weight on your driver’s supporting documents, since there’s no automatic data trail backing it up the way there is with an ELD.

Questions to Ask Before Choosing an ELD Provider

Does the provider’s ELD run on a device built for vehicle conditions, not just a consumer tablet?

A tablet that isn’t rated for vibration, heat, or power fluctuation is more likely to malfunction on the road. Ask whether the hardware carries any independent certification for vehicle use, not just a claim of durability. Our tablet, for example, is SAE J1455 certified specifically for commercial vehicle conditions.

What happens to stored data if the device loses power or connection?

Ask whether the platform keeps a local backup so a temporary connection drop doesn’t turn into a full reconstruction. A device with a backup battery and local storage reduces how often your drivers need to fall back on paper.

How fast can your driver reach support if a malfunction happens mid-route?

A malfunction at 2 a.m. on an interstate isn’t the time to find out support only answers during business hours, so confirm the provider offers live support around the clock rather than just email tickets.

Is the device currently listed on the FMCSA registered ELD list?

Devices get removed from the FMCSA registered ELD list regularly, and using a delisted device is treated the same as having no ELD at all. Check the list directly rather than relying on a vendor’s claim, and confirm the vendor itself is FMCSA registered as a company, not just the device.

How does the platform document a malfunction start time for your records?

Your driver’s notification clock starts the moment a malfunction is discovered, so it helps if the system timestamps that moment automatically instead of leaving your driver to remember and log it manually under pressure. Ask a prospective vendor how their platform handles this step.

How quickly does the provider typically ship a repair or replacement device?

Your carrier is working against a fixed clock once a malfunction is reported, so a vendor’s actual turnaround time matters more than a general promise to help. Ask for a specific timeframe, not just a policy statement.

Does the provider offer any guidance for drivers who need to complete a paper log?

Even reliable equipment fails occasionally. A provider that gives drivers a straightforward reference for paper log requirements, rather than leaving them to figure it out mid-shift, makes reconstruction less stressful when it does happen.

What does the money-back guarantee or satisfaction policy actually cover?

If a device turns out to be unreliable, know upfront what your options are for a refund or replacement, and over what time window, before you commit a whole fleet to one system. We back our hardware with a 30-day money-back guarantee for this reason.

Common Questions

About ELD Malfunctions and Record Reconstruction

What counts as an ELD malfunction that triggers a reconstruction?

Anything that stops the device from recording or transferring accurate hours of service data counts, including power failures, engine connection loss, timing errors, or data recording failures under 49 CFR 395.34. Your driver doesn’t need to diagnose the exact cause to know reconstruction is required, just that the data isn’t reliable.

How many days of records does your driver actually need to reconstruct?

Generally the current 24-hour period plus the previous 7 consecutive days, unless part of that window is already documented elsewhere. The exact amount depends on how long the malfunction has been affecting the ELD before it was caught.

Can your driver reconstruct a log purely from memory?

Memory alone is weak support if the record is ever questioned, so your driver should use receipts, dispatch communications, or any other timestamped record available, and treat memory as a last resort for filling small gaps only.

Does a malfunction automatically put your driver out of service?

Not on its own. A driver can continue operating using paper logs while the malfunction is addressed, as long as they’re properly reconstructing and maintaining records during that period. What can lead to an out-of-service order is a missing or clearly inadequate record, not the malfunction itself.

What if the malfunction happens in the middle of a multi-day trip?

Your driver switches to paper logs at the point the malfunction is discovered and continues that way until the device is repaired or replaced. The reconstruction only needs to cover the gap, not days that were already properly recorded before the malfunction started.

Are reconstructed paper records treated differently at a roadside inspection?

Officers know paper reconstructions happen and don’t treat them as inherently suspicious. What they check closely is whether the record lines up with other available information, so having supporting documents on hand matters more with a reconstructed log than with a standard ELD pull.

About Choosing the Right ELD Provider

Does our hardware reduce how often reconstruction is needed?

Our tablet is SAE J1455 certified for vehicle conditions and connects through J1939, J1708, or OBD-II, which is built to handle the vibration and power variability that causes malfunctions in less durable devices. It also includes a backup battery so a temporary power loss doesn’t interrupt logging.

How quickly can a driver get help if something goes wrong on the road?

Support is available 24 hours a day, 7 days a week, so a malfunction at any hour gets a real response rather than a queue.

Do all ELD platforms require the same reconstruction process?

Yes, the reconstruction requirement comes from federal regulation, not from any individual vendor’s policy. What differs between platforms is how much support and guidance they give your driver while it’s happening.

What connection types does our ELD support?

It connects via J1939, J1708, or OBD-II, covering most commercial vehicle engine types without needing separate adapters for different truck models in your fleet.

Is there a way to try the device before committing a whole fleet to it?

There’s a 30-day money-back guarantee, so you can test the device on actual routes before deciding it’s the right fit for your operation.

What should a fleet manager check before assuming a device is fully compliant?

Confirm the device appears on the current FMCSA registered ELD list and ask the vendor directly about their malfunction notification and repair process, since both affect how often your drivers end up on paper logs.

Conclusion

A reconstruction of records of duty status isn’t a sign that your driver did anything wrong. It’s a required response to equipment that failed to do its job, and it exists specifically so a device malfunction doesn’t turn into a compliance gap. What matters is that your driver knows the trigger, understands the 7-day lookback window, and leans on real supporting documents instead of guesswork when filling in the paper log.

Enforcement in 2026 hasn’t gotten more forgiving on this point. Inspectors are actively checking reconstructed logs against supporting documents, and a record that doesn’t hold up can lead to the same citation as having no record at all. The best defense is equipment that malfunctions less often in the first place, paired with a driver who knows exactly what to do in the hours after a malfunction is discovered. As an FMCSA-registered ELD provider based in Tucson, our compliance team hears these questions from fleets of every size, and we’re glad to walk through your specific setup.

Call us at (800) 261-4361 to talk through your fleet’s specific situation, or check your price calculator to see what a hardware refresh would look like.