Can a Carrier Edit a Driver's ELD Log Without Consent?
By Justin Seyl, NATMI Certified Director of Safety
No. A carrier can ask for an edit to a driver's ELD log, but it can't make that edit on its own. The driver has to review the request, confirm it or reject it, and the change only sticks once the driver recertifies the record. That's not a gray area — it's written straight into 49 CFR 395.30.
I've gone through enough FMCSA compliance review files to know exactly where this breaks down. Safety managers treat the edit-request feature in their ELD software like a correction tool they control. It isn't. It's a proposal tool. The driver owns the certification. When a carrier forgets that, or worse, pressures a driver to accept edits without actually reading them, that's precisely the pattern an auditor is trained to catch. At Waypoint True, we pull the edit history and annotation trail on a fleet's logs before FMCSA does, through our Verity log-auditing process, because by the time a Compliance Review flags a pattern of unexplained edits, you're already explaining yourself instead of getting ahead of it. Waiting until the audit letter shows up is the single biggest mistake we see fleets make.
Can a Carrier Edit a Driver's ELD Log Without the Driver's Approval?
No. Under 49 CFR 395.30, a motor carrier can only request edits to a driver's record of duty status after the driver has already submitted it. The carrier can't touch the record before submission, and it can't push a change through on its own say-so. The driver has to confirm or reject the proposed edit, put it into effect if accepted, then recertify the record before it's final. If the driver rejects it, it doesn't happen. Full stop.
This two-step setup — request, then driver confirmation — exists for one reason: to keep the record of duty status under the driver's control, since that record is the driver's sworn word about their own hours. A carrier that edits around that process, or treats a driver's silence as a yes, has stepped outside the rule.
What Does 49 CFR 395.30 Actually Require for Log Edits?
49 CFR 395.30 lays out the whole edit workflow, and it's worth knowing cold if you're running a safety department. The driver reviews their own ELD records, fixes mistakes, fills in missing pieces, and certifies the record is true and correct. That certification happens through an affirmative action in the software, not some default checkbox.
From there, a driver can edit and annotate their own records, but every change needs an annotation explaining it. A carrier reviewing submitted records can propose edits too, but again, the driver has to confirm or reject each one and recertify afterward. The rule also flatly bans coercion: a carrier can't pressure a driver into a false certification. That's not a side note. FMCSA built it into the rule specifically to keep the record safe from manipulation by either side.
Separately, 49 CFR 395.8 sets the submission deadline this whole edit cycle depends on. A driver has to turn in their record of duty status to the carrier within 13 days of the end of the 24-hour period it covers. That matters because a carrier can't propose an edit to a record that hasn't been submitted yet. If your dispatch team is leaning on drivers for "corrections" before the log ever reaches their queue, you're outside the sequence the rule actually requires.
What Happens to the Original Record When an Edit Is Made?
It stays. That's the part a lot of safety managers never fully grasp. The ELD technical specs in Appendix A to Subpart B of 49 CFR Part 395 require that an ELD can't allow alteration or erasure of the original data, and any edit or annotation a driver makes can't overwrite that original. The system keeps both versions: what the device first captured, and whatever edit got layered on top with its annotation.
That same obligation falls on the carrier. A motor carrier is independently required to leave the original ELD data alone, and has to keep a back-up copy of records for six months on a device separate from where the original data lives. In practice, an auditor pulling a file doesn't just see the "final" log. They see the whole edit history: what got recorded, what got proposed, what got accepted or rejected, and the annotation on each step. There's no version of this where an inconvenient original entry just disappears.
Can Automatically Recorded Driving Time Be Shortened?
No, and this is the line that trips up the most carriers. Automatically recorded driving time — the time the ELD captured while the vehicle was actually moving — isn't something a driver or carrier can edit down into off-duty, sleeper berth, or on-duty-not-driving. FMCSA's own ELD guidance is blunt about it: the Appendix A specs don't allow automatically recorded drive time to get reclassified as non-driving time, whether the edit comes from the driver or the carrier's side.
The narrow exceptions that do exist are specific and limited. Team drivers can reassign driving time that got logged under the wrong co-driver's account, but only if both drivers had flagged each other as co-drivers and both confirm the change. Unidentified-driver records can get corrected to assign hours to the right driver under 49 CFR 395.32, which requires a carrier to review unassigned driving time and either annotate why it's unassigned or attribute it correctly. Outside those lanes, driving time is driving time. No annotation fixes that.
What Does a Pattern of Edits Look Like to an Auditor?
An auditor isn't looking at one edit. They're looking at what a stack of them says about how your operation runs. A few things catch attention fast. Logs that look too clean, with duty status changes lining up suspiciously close to the regulatory limits every single day, read differently than logs with the normal variation you'd expect from real operations. Edits with no annotation, or the same boilerplate annotation copied across dozens of records, look like a workaround, not a correction. And cross-checking against toll records, fuel receipts, or scale tickets that put a driver somewhere the edited log says they weren't is one of the fastest ways an edit turns into a falsification finding.
Auditors also pull specific back-office reports built for exactly this: unassigned driving miles, the edit history report, odometer jump reports, and violation summaries. If your fleet has a cluster of carrier-proposed edits that all move hours off-duty right before a driver would've busted the 11-hour or 14-hour limit, that's not a coincidence an auditor's going to overlook.
FMCSA's own method for rating a carrier's safety fitness tells you how seriously the agency treats repetition over a one-off mistake. Under the Safety Fitness Rating Methodology in Appendix B to 49 CFR Part 385, a pattern of noncompliance with a critical regulation needs more than a single violation and has to hit a set threshold of the records sampled. One bad edit on one log is a mistake you can usually explain. A recurring pattern is what pulls a carrier into a deeper look.
This is the point where most fleets figure out they don't actually know what their edit history looks like until someone goes digging. If you're not sure what an auditor would find in your carrier-proposed edit log today, find out on your own schedule, not theirs. A Verity log audit from Waypoint True runs through that edit and annotation trail before a DOT auditor ever has a reason to ask for it.
What's the Difference Between an Edit and Falsification?
An edit is a correction made through the process the regulation spells out: proposed, confirmed or rejected by the driver, annotated, and recertified. Falsification is an intentionally false entry or statement on a required record, and it's banned on its own under 49 CFR 390.35, which covers fraudulent or intentionally false statements on any application, certificate, report, or record a carrier has to keep.
The line between the two isn't whether an edit happened. Edits happen constantly, and legally. The line is intent and process. A driver fixing a mistyped duty status with an honest annotation is doing exactly what the rule allows. A carrier pressuring a driver to reclassify real driving time as off-duty to dodge an hours-of-service violation is falsification, and it puts both the driver and the carrier in front of enforcement action that goes well past a routine log-edit finding.
How Waypoint True Helps Fleets Manage ELD Edit Risk
We review the edit history on a fleet's ELD records the same way an FMCSA auditor would: every carrier-proposed edit, every driver annotation, and whether recertification actually happened the way 49 CFR 395.30 requires. We check whether records got submitted and reviewed on the timeline 49 CFR 395.8 sets, and whether unassigned driving time got handled correctly under 49 CFR 395.32 instead of getting quietly reclassified.
When we find a cluster of edits that would read as a pattern to an auditor, we flag it before it turns into a Compliance Review finding, and we walk the safety manager through what's defensible and what isn't. If there's a dispute between what the ELD originally captured and what the current record shows, we identify it and lay out your next step — whether that's fixing your internal edit-approval process, retraining dispatch on what they can and can't ask for, or getting documentation ready ahead of an audit. We don't promise an audit outcome. We give you the same view an investigator will have, while you've still got time to act on it. If your fleet hasn't had its edit history reviewed, get your records in front of us through Verity before FMCSA requests them for you.
Don't wait for a Compliance Review to find out what your edit history says about your fleet. Get your ELD records in front of Waypoint True through a Verity log audit now, while you've still got time to fix what it finds.
Justin Seyl is a NATMI Certified Director of Safety and NATMI Certified Audit Specialist with more than 25 years in CDL compliance. He has personally overseen more than 650,000 citations and directed more than 10,000 Safety Fitness Determination upgrades. He is the founder of CDL Consultants, CDL360 and CDL Manager.
Sources
- 49 CFR Part 395.30
- 49 CFR Part 395.8
- 49 CFR Part 395
- 49 CFR Part 395.32
- 49 CFR Part 385
- 49 CFR Part 390.35
FAQ
Can a dispatcher edit a driver's ELD log directly?
No. Only the carrier's authorized edit-request function can propose a change, and only the driver can confirm it. A dispatcher making changes outside that confirmed workflow, or pushing a driver to accept an edit without reading it, violates the process 49 CFR 395.30 requires.
Does a driver have to accept every carrier-proposed edit?
No. The driver can reject a proposed edit. Under 49 CFR 395.30, a carrier's proposed change only takes effect once the driver confirms it, implements it, and recertifies the record. A rejected edit doesn't change the driver's record of duty status.
Is the original ELD record deleted once an edit is made?
No. The technical specs in Appendix A to Subpart B of 49 CFR Part 395 require the original data stay intact, and edits can't overwrite it. Both the original entry and the edit, with its annotation, remain part of the record carriers have to keep.
Can automatically recorded driving time be edited into off-duty time?
No, outside two narrow exceptions. Automatically recorded drive time can't be reclassified as non-driving time by either the driver or the carrier, per FMCSA's ELD guidance on Appendix A. The only corrections allowed are confirmed team-driver reassignment or fixing unidentified-driver records under 49 CFR 395.32.
What triggers an FMCSA review of a carrier's edit history?
There's no fixed edit count that automatically triggers a review, but auditors look for patterns, not isolated corrections. Investigators pull edit-history reports, odometer jump reports, and unassigned driving data, and a recurring pattern of unexplained or unannotated edits is a common reason a Compliance Review goes deeper.
Can a carrier be cited for a driver's false ELD entry?
Yes, if the carrier caused, coerced, or knowingly allowed it. 49 CFR 390.35 bans fraudulent or intentionally false statements on required records, and FMCSA can hold a carrier accountable where its practices, pressure, or lack of oversight contributed to the false entry.