Can a Carrier Edit Driver Logs? Where a Legal Edit Ends and Falsification Begins

Published September 11, 2026 | TruckerNavi Inc | 20 min read

By the TruckerNavi compliance team, led by Dmitry Borovoy, a New Jersey-licensed insurance producer and author of Safety Manager: From Zero to Expert.

The short answer: a carrier can propose an edit. It cannot impose one. Under 49 CFR 395.30(d)(1) the carrier may request edits to a driver's records of duty status only after the driver has submitted them, and the driver must confirm or reject the proposed change, implement the edit, then recertify and resubmit before anything takes effect. Paragraph (d)(2) bars the carrier from requesting edits before submission at all. Paragraph (d)(3) says an edit requested by any system or by any person other than the driver requires the driver's electronic confirmation or rejection.

Three limits close the loop. Automatically recorded driving time can never be shortened by anyone. Every change needs an annotation. And the original record survives every edit, so the before-and-after stays visible to an inspector. Everything a compliance department legitimately needs to do fits inside those rules. Everything outside them has a name: falsification, one of the heaviest findings in a DOT investigation.

Separate from all of that is the category people confuse it with: form and manner, a real log filled in badly. It is a violation, but in FMCSA's own scoring it weighs 1 out of 10 where a false log weighs 7. Below is that line drawn precisely, with the section numbers and the numbers.

Who is allowed to do what to a log?

Start with the division of powers, because most of the fear in a dispatch office comes from not knowing it. 49 CFR 395.30 assigns responsibility to both sides: paragraph (a) says a driver and the motor carrier must ensure that the driver's ELD records are accurate. Not the driver alone. Not the carrier alone.

Read that table as one sentence: the carrier owns the question, the driver owns the answer. A compliance manager who spots a problem writes a proposal with a reason attached. The driver decides. That is the entire legal architecture of a log edit. The underlying limits those records have to fit inside are in the hours-of-service rules explained, and the device-side duties in ELD compliance requirements for 2026.

Why can't the carrier touch a log before the driver submits it?

Because the certification would be meaningless. Under 395.30(b)(2) the driver certifies by selecting "Agree" right after a statement that reads, word for word, "I hereby certify that my data entries and my record of duty status for this 24-hour period are true and correct." The driver must certify immediately after the final required entry has been made or corrected for the 24-hour period. If the office could rewrite the day first, the driver would be certifying somebody else's version of it.

The sequence is fixed and it matters at audit:

1. The driver reviews the day, fixes what is wrong, adds what is missing, annotates each change.
2. The driver certifies the 24-hour period.
3. The driver submits the record to the carrier. Under 395.8(a)(2)(ii) that must happen within 13 days of the period the record covers.
4. Only now may the carrier review and propose edits, with an annotation explaining why.
5. The driver confirms or rejects. If confirmed, the driver implements the edit and, under 395.30(b)(4), recertifies the record and resubmits it.

Skipping step 2 or step 5 is where carriers get written up: FMCSA carries discrete roadside codes 395.30B1 (failed to certify the accuracy of ELD information) and 395.30B4 (failed to recertify after edits).

Can driving time that the ELD recorded automatically be edited or removed?

No, and the device itself is built to refuse. Section 4.3.2.8.2(b) of Appendix A to Subpart B of Part 395 states that an ELD must not allow automatically recorded driving time to be shortened, and must not allow the ELD username attached to a record to be edited or reassigned, with two narrow exceptions written into the same paragraph.

Two companion rules make this stick:

• 4.3.2.8.1(a): if a driver edits or annotates a record or enters missing information, the act must not overwrite the original record.
• 395.30(f): a motor carrier must not alter or erase, or permit or require alteration or erasure of, the original hours-of-service information, the source data streams behind it, or any information in an ELD that uses that original data.

So the inspector does not see the version you settled on. He sees the version the truck recorded, every proposed change on top of it, who asked for each change, when, and what reason was typed. FMCSA is explicit that the record must retain what was originally recorded plus the date, time, and identity of the individual entering the correction. There is no clean way to make driving disappear, and that is the design intent.

When is editing automatically recorded driving time actually allowed?

There is a published, closed list. FMCSA guidance FMCSA-HOS-ELD-395-FAQ51, reissued July 31, 2023, sets out four situations where such an edit is acceptable, plus one it expressly rules out. Everything not on this list is off limits.

That last row is where a large share of real disputes live. You cannot look back at yesterday's unassigned driving and decide it was Personal Conveyance or a yard move. FMCSA notes that the time should be annotated instead, because enforcement personnel weigh annotations and GPS coordinates together when deciding whether a violation exists. Claiming and declining that time is covered in unassigned driving time on an ELD; what qualifies as a yard move in the first place is in yard moves and the ELD.

What is an annotation, and why does every edit need one?

FMCSA draws the distinction cleanly: an edit is a change to a record that does not overwrite the original; an annotation is a note attached to a record, update or edit that a driver or authorized support personnel types into the ELD. They are not alternatives. Under 395.30(c)(2) every change or addition must be annotated, and under Appendix A 4.3.2.8.1(c) the ELD is required to prompt for it.

FMCSA's own example of a good annotation, on a carrier-proposed change from Off Duty to On-duty not driving: "Driver logged training time incorrectly as off-duty." Short, factual, states the reason. Then it goes to the driver for approval.

Annotations are also how a driver documents what the grid cannot express: the start and end of authorized personal use or a yard move, or a claim to the adverse driving conditions exception under 395.1(b), which is far easier to defend when a contemporaneous note names the storm or closure that caused it. The practical rule: an unexplained edit is worse than no edit. A column of blank annotations reads as a pattern rather than an accident.

What exactly counts as log falsification?

Two regulations, and they overlap on purpose.

• 49 CFR 395.8(e)(1): "No driver or motor carrier may make a false report in connection with a duty status." Paragraphs (e)(2) and (e)(3) add the hardware side: no one may disable, deactivate, disengage, jam, block, degrade, reengineer, reprogram or otherwise tamper with an ELD so that it does not accurately record and retain required data, or permit or require another person to do so.
• 49 CFR 390.35: no motor carrier, its agents, officers, representatives or employees may make or cause to make a fraudulent or intentionally false statement or entry on any application, certificate, report or record required by the safety regulations, or reproduce any such record for fraudulent purposes.

Note who is named in 390.35: not just the driver, but agents, officers and representatives. A dispatcher who proposes an edit knowing it is untrue is inside the text of the rule, and so is the owner who told him to.

What it looks like in practice:

• Driving time relabeled as On-duty not driving or Off Duty so the day fits inside the limits.
• A status change back-dated so a rest period looks longer than it was.
• A driver operating under someone else's ELD account, or a second account created for the same person.
• Real driving reclassified as Personal Conveyance after the fact to hide a limit violation.
• An edit proposed with an annotation that the office knows is false.
• Supporting documents altered so they stop contradicting the log. 395.11(f) covers altering, defacing, destroying, mutilating or obscuring a supporting document, and 390.35 covers fraudulent alteration of one.

Falsification is almost never discovered from the log alone. It surfaces when the log stops matching something else: fuel receipts, toll records, gate times, bills of lading, dispatch messages, ELD power events, or GPS coordinates on a status change hundreds of miles from where the driver claims to have been.

What is a form and manner violation, and why is it not falsification?

A form and manner violation means the record is true but badly kept. Nothing is hidden. Something is missing or in the wrong place.

For paper logs, 395.8(f) lists what must be there: entries kept current to the last change of duty status, legible entries made by the driver, date, total miles driven today, vehicle identification, carrier name, signature, time base, main office address, total hours in each status, and shipping document number or shipper and commodity. For ELDs, 395.24(c) lists what the driver must type in or verify: annotations when applicable, location description when prompted, output file comment when a safety officer asks, plus power unit number, trailer numbers and shipping document number.

FMCSA's own examples of form and manner issues are as ordinary as they sound: the log does not include miles traveled, the log does not include locations. Missing paperwork in the cab lands in a neighboring bucket: under 395.22(h) the carrier must ensure the driver carries an ELD information packet with a data transfer instruction sheet, a malfunction reporting instruction sheet, and a supply of blank graph-grids sufficient for at least 8 days. Those are the three items in the current text: the SMS list still carries a fourth code, 395.22H1 for the ELD user's manual, but that requirement was removed from 395.22(h) by the final rule at 91 FR 37053, published June 22, 2026 and effective July 22, 2026.

The difference is not rhetorical. It is scored differently at the roadside and classified differently at the audit, and the gap is roughly sevenfold. What a roadside HOS violation costs and how to attack the ones that are wrong is in how to fix HOS violations.

What does each action actually cost?

Two scoring systems run in parallel and people mix them up constantly. At the roadside, a violation enters the HOS Compliance BASIC with a severity weight from 1 to 10, per the SMS Methodology and its Appendix A violations list (Appendix A version 3.21, methodology revised May 2026). At an investigation, the same conduct is classified acute or critical under Appendix B to Part 385 and drives your safety rating. Here is the whole map in one table.

Two things to read carefully. First, weight 1 versus weight 7: a missing trailer number and a false log are not the same species of problem, and FMCSA does not treat them as one. Second, severity weights compare only within a BASIC, because they were calibrated separately for each category, and the sum of all weights on one inspection in one BASIC is capped at 30. How a weighted violation turns into a percentile is broken down in HOS violations and what they cost in CSA; the thresholds are in what is a good CSA score.

Why is falsification one of the heaviest findings in a DOT audit?

Because of how the safety rating arithmetic works. Under Appendix B to Part 385, an investigator assigns points inside six factors:

• One point for each instance of noncompliance with an acute regulation.
• One point for each pattern of noncompliance with a critical regulation. A pattern is more than one violation; when a set of documents is reviewed, the number needed equals at least 10 percent of those examined.
• Two points for each pattern of noncompliance with a critical regulation relative to Part 395. Hours of service is the only part that gets doubled.

Then the factor rating is mechanical: 0 points is Satisfactory, 1 point is Conditional, 2 or more points is Unsatisfactory. The factors are Factor 1 General (Parts 387 and 390), Factor 2 Driver (Parts 382, 383, 391), Factor 3 Operational (Parts 392 and 395), Factor 4 Vehicle (Parts 393 and 396), Factor 5 Hazardous Materials, and Factor 6 Accident.

Put those pieces together and the exposure is obvious:

A single pattern of falsified logs is therefore enough to put an entire factor at Unsatisfactory in one step, and a second Unsatisfactory factor takes the overall rating there too. "Pattern" is also a low bar: on a document review it can be as few as 10 percent of the records examined. Ten falsified days out of a hundred pulled is a pattern.

Meanwhile, a hundred form and manner citations carry zero rating points, because none of them appears on the acute and critical list. They still stack up in your percentile, but they do not touch your rating. What a rating is and how it differs from a percentile is untangled in safety rating vs CSA score. What the investigator will actually ask for is listed in the DOT audit preparation checklist and the DOT audit document checklist.

What if the driver refuses to confirm the carrier's proposed edit?

Then the record of duty status does not change. That is the design. But the proposal does not vanish either: FMCSA states that if the driver is unavailable or unwilling to recertify the record, the carrier's proposed edit and annotation remain part of the record. Both sides of the disagreement stay visible.

This protects the carrier as much as the driver. If the office spotted a genuine error, proposed the fix with a reason, and the driver declined, the file shows the carrier acted. If the office proposed something untrue and the driver refused, the file shows that too. FMCSA is direct that driver and carrier share responsibility for accuracy, and that the certification exists in part to protect the driver from unilateral changes.

What if a dispatcher pressures a driver to change a log?

There are two named federal concepts and both give the driver a route that does not depend on the employer.

• 395.30(e), coercion into false certification: "A motor carrier may not coerce a driver to make a false certification of the driver's data entries or record of duty status." FMCSA's SMS list carries this as a roadside code with a severity weight of 7, the same as a false log.
• 390.36, harassment: FMCSA explicitly prohibits a motor carrier from harassing a driver through the ELD. A driver may file a written complaint under 49 CFR 386.12(b) no later than 90 days after the event, through the National Consumer Complaint Database at nccdb.fmcsa.dot.gov or the FMCSA Division Administrator for the state where the driver is employed. Information on filing is available at 1-888-DOT-SAFT (1-888-368-7238).

Two details worth knowing. Harassment is defined by reference to an underlying violation: under 390.36(a) it means carrier action using information available through the ELD that the carrier knew, or should have known, would result in the driver violating 392.3 or Part 395. And because prosecuting harassment requires disclosing the driver's identity, FMCSA states it will take every practical means to ensure the driver is not subjected to intimidation, discipline or financial loss for filing, and notes that 49 U.S.C. 31105 carries broad employee protections enforced by OSHA.

Can the carrier delete records, reset the ELD, or switch providers to start clean?

No, and each attempt has its own citation.

• 395.30(f) forbids altering or erasing the original information, the source data streams, or anything derived from them. At investigation this is acute.
• 395.8(k) requires the carrier to keep records of duty status and supporting documents for each driver not less than 6 months from receipt; the driver separately keeps the previous 7 consecutive days available while on duty.
• 395.22(i)(1) requires a back-up copy retained for 6 months on a separate device. Losing the primary system is not a defense.
• 395.32(c) requires unidentified driving records to be annotated with an explanation or assigned to the right driver, and retained at least 6 months.
• On a replaced or reset ELD, the current 24-hour period and previous 7 days must still be produced, uploaded into the new device or kept on paper.

Drivers have the mirror-image right under 49 CFR 395.36: by 395.36(a) a carrier must not introduce a process that forces a driver to go through the company for copies of his own ELD records when those records exist on or are automatically retrievable through the ELD he operates, and by 395.36(b) the carrier must, on request, provide access to and copies of those of his records that are not available to him through the ELD itself, during the retention period set by 395.8(k).

If the ticket is dismissed, does the false log come off my CSA record?

Sometimes, and only on documented adjudication. Per the SMS Methodology, a violation is used at its listed severity weight unless the citation result is adjudicated and documented as "dismissed / not guilty." When the result is documented as "convicted of a different charge," the severity weight is set to 1 and the additional out of service weight of 2 does not apply.

Three practical consequences:

• Paying the ticket does not help. Neither does a plea that ends in a conviction on the original charge.
• To get any of this recorded, the driver or carrier must submit certified documentation of the judicial proceeding through a Request for Data Review in DataQs.
• The process applies only to inspections conducted on or after August 23, 2014.

None of this touches the investigation side. An acute or critical finding is a finding about your management controls, not a courtroom outcome, and it is corrected by fixing the process and requesting a rating change, not by contesting a citation. The mechanics of the challenge itself, including what evidence actually moves an RDR, are in how to dispute violations through DataQs; the adjudication rule quoted above is in the SMS Methodology.

How to run log edits so they survive an audit

1. Never edit a driver's log for him. Propose, annotate, send; the driver confirms and recertifies. Make that the only workflow your office knows.
2. Wait for submission, and do not let the driver sit on records past the 13-day limit in 395.8(a)(2)(ii).
3. Annotate every change with a reason a stranger could follow. "Corrected" is not a reason. "Loaded at consignee, status entered late" is.
4. Treat automatic drive time as immovable. If an edit would reduce it, the answer is no. If your ELD permits it anyway, that is a compliance emergency.
5. Clear unassigned driving weekly, assigning or annotating it. Under 395.32(c) the carrier must do one or the other.
6. Match logs against supporting documents before FMCSA does. Fuel, tolls, gate times and bills of lading are where falsification surfaces.
7. Keep the paper trail complete: 6 months of records and supporting documents, a separate back-up copy, and the in-cab ELD packet with 8 days of blank graph-grids.
8. Write the procedure down and have drivers sign it. A documented process with confirmations attached is the difference between an isolated error and a pattern.

FAQ

Related articles

• Unassigned Driving Time: Who Has to Claim It and When
• Yard Moves on an ELD: What Actually Counts
• The Adverse Driving Conditions Exception, Line by Line
• HOS Violations and What They Cost in CSA
• What Is a Good CSA Score? Intervention Thresholds by BASIC
• Safety Rating vs CSA Score: Not the Same Thing
• How to Check Your CSA Score for Free
• How to Fix HOS Violations: DataQ Removal
• ELD Compliance Requirements for 2026
• DataQ Challenge: How to Dispute Violations
• DOT Audit Preparation Checklist
• DOT Audit Document Checklist
• Hours of Service Rules Explained