Editing your logs: what can change, what can't

← All guides

“Can you edit an ELD log?” is one of the most asked questions in trucking, and it draws two wrong answers. One camp says nothing can ever be changed, so a small mistake is a permanent stain. The other camp whispers that anything can be fixed if you know the trick. The rule says neither. It says records can be corrected — openly, with a reason attached, and with the original kept — and it draws one hard line: driving time the device recorded cannot be shortened or removed by an edit.

This guide walks the whole picture: whose job accuracy is, what the driver certifies each day, what can be fixed and how, what can never change, and the protection that stops the office from changing a driver's record behind his back.

Accuracy is a shared job, and the day ends with a signature

Start with the duty itself. Under 49 CFR 395.30(a), the driver and the carrier must both ensure the driver's ELD records are accurate. Not the driver alone, not the office alone — both. The office cannot treat a wrong record as purely the driver's problem, and the driver cannot treat checking the record as optional paperwork.

The driver's part of that duty has a daily rhythm. The driver reviews his records, edits and corrects inaccuracies, enters missing information, and then certifies the day — selecting “Agree” after the statement: “I hereby certify that my data entries and my record of duty status for this 24-hour period are true and correct,” under 49 CFR 395.30(b).

Read that statement slowly once, because you agree to it every day. It says the entries are true and correct — which is exactly why the review comes before it, not after. The honest order is: look at the day, fix what is wrong, add what is missing, then sign. And if edits happen after you have already submitted the records, you recertify after the edits. The signature always covers the final version of the day, never an earlier one you have since changed.

What can be fixed

The fixable list covers the mistakes real days are made of:

• A wrong duty status chosen by mistake. You tapped on duty when the work was done and you meant off duty, or the reverse. The record can be corrected to the status the work actually was.
• A status change you forgot to make. The forgotten log-out is the classic: the day ended, the driver went home, and the device sat on duty because nobody told it the day was over. The correction restores the change that should have been made at the time.
• Missing entries, added. Information the day should carry and does not can be entered.
• Locations and shipping information, corrected. A wrong place name or wrong shipping detail can be put right.

Every one of these changes carries the same condition, and it is not fine print. Under 49 CFR 395.30(c)(2), every change or addition must be annotated — the reason rides with the record. An annotation is a short, plain explanation written at the time of the edit: what was wrong, and what actually happened. “Forgot to log out at the yard; day ended at 6 p.m.” is an annotation. It takes ten seconds, and it is what separates a correction from a suspicion. An edit with a clear reason reads, to any officer or auditor who ever looks, as a driver keeping an honest record. The same edit with no reason reads as a question nobody can answer.

The original never disappears

Here is the design underneath all of it. When you edit a record, the ELD keeps the original record, and every edit stands next to it with who made it, when, and why. Under 49 CFR 395.30(f), the carrier must not alter or erase the original information collected.

That can sound like a trap until you see what it protects. Because the original stays, you never have to fear that fixing a mistake looks like hiding one: the record itself shows the before, the after, and your reason, all in the open. Editing under this rule is not rewriting history. It is adding a correction to history, signed and dated. Drivers who understand that stop fearing the edit button and start using it the way it was built to be used — promptly, honestly, and with the reason attached.

What can never change: driving time

Against that open door stands one locked one. Driving time the ELD recorded cannot be shortened or removed by an edit. Not by the driver, not by the office, not for a good reason, not for a small amount. The device watched the truck drive; that time stands.

The rule allows exactly one movement of driving time, and it is narrow enough to state in full. Under 49 CFR 395.30(c)(3), if a mistake put driving time on the wrong driver, and both drivers were shown as co-drivers of each other for that period, the time may be reassigned between those team drivers. The pair's total does not change — not one minute is created or destroyed. The time simply moves to the partner who actually drove, inside a team that the record already showed as a team. Outside that one case, driving time does not move at all.

This line is the whole reason the system can be trusted at a roadside. A record where driving could be edited away would be worth nothing to an officer, and the rule knows it. Everything around the driving — statuses chosen by hand, forgotten changes, missing details — can be corrected because hands make mistakes. The driving itself was recorded by the device, and the device does not make that kind of mistake.

The office proposes; the driver disposes

Now the protection drivers ask about most. Can the office change your record while you are out on the road? Under 49 CFR 395.30(d), no — not without you.

The pattern works like this. On review, the carrier may request edits to a submitted record. A request is all it is. The driver must confirm or reject the proposed change, and only after the driver implements it, recertifies, and resubmits do carrier-proposed changes take effect. Any edit suggested by a system or by another person requires the driver's own electronic confirmation or rejection. And the carrier may not request edits before the driver has submitted the records in the first place — the office cannot reach into a day the driver has not yet signed and sent.

Hold onto what this means in practice. If a proposed edit is right, confirm it, recertify, and move on; the system is working as designed, with the office's eyes helping yours. If a proposed edit is wrong — if it asks your record to say something that did not happen — you can reject it, and your rejection is the end of it. Your signature at certification is yours. Which brings in the last rule of this section, stated plainly in 49 CFR 395.30(e): a carrier may not coerce a driver into a false certification. A record you certified must be a record you believe is true. The rule does not treat pressure to sign a false day as a grey area; it prohibits it.

Unidentified time follows the same pattern

One neighbour topic belongs here because drivers meet them together. When driving happened with nobody logged in, it sits on an Unidentified Driver account until it is dealt with, and its assignment to a driver goes through the driver review at login — the driver sees the time, and claims what is his or says it is not attributable to him. The full picture, including the office's duty to assign or annotate what is left, is in our guide to unidentified driving records. The spirit matches everything above: time reaches a record openly, through the person it belongs to, with the reasoning kept.

The two-minute habit

All of this reduces to a small daily habit. Before you certify, look at the day the way an officer will look at it during a roadside inspection: does the grid match the work, are the locations right, is there a status still running that should have ended? Fix what is wrong while you still remember why it is wrong, write the reason in plain words, and then sign. Corrections made the same evening are easy and believable. Corrections attempted a week later, from fading memory, are neither. The edit rules give you a fair deal — an honest record you can repair in the open, a hard line that protects the repair's worth, and a signature nobody can take from you. Use the deal daily and it stays fair.

Rules checked October 2026. Rule sources: 49 CFR 395.30.