False Driver Logs Under 49 CFR 395.8(e) Explained
By Justin Seyl, NATMI Certified Director of Safety
A false driver log under 49 CFR 395.8(e) is any record of duty status that doesn't match what actually happened on the road: hours marked off-duty that were really drive time, a status logged under the wrong name, or a device that's been messed with to hide what the vehicle actually did. I've personally overseen the review of more than 650,000 citations and directed over 10,000 Safety Fitness Determination upgrades, and false logs show up in nearly every file where a carrier's CSA scores took a hit nobody saw coming.
At Waypoint True, we built Verity because carriers kept finding out about log problems the hard way, during a DOT audit or after a crash, when it's too late to fix anything. The mistake most fleet owners make is waiting for FMCSA to find the discrepancy first. By the time an investigator flags a false report, the penalty exposure and the Hours-of-Service BASIC damage are already locked in. Run the audit on your own schedule, matched against the supporting documents the rule already makes you keep, and you catch the problem while you still have options.
What Is a False Report of Duty Status?
A false report of duty status is a record that doesn't reflect what the driver actually did. The regulation at 49 CFR 395.8(e) is blunt about it: no driver or carrier may make a false report connected to a duty status. The text doesn't spell out an intent test, and an investigator decides from the evidence whether a mismatch is an honest mistake or a false log. That's exactly why a good audit treats every discrepancy as worth checking, not just the obvious ones.
The baseline duty that makes a false report possible sits in 49 CFR 395.8(a), which requires every driver to record duty status for each 24-hour period using the method the carrier has in place. Every status change, driving, on-duty not driving, off-duty, sleeper berth, has to get logged, and it has to be accurate. A false log is simply a failure of that duty: a record that doesn't capture reality.
How Does Driving End Up Logged as Off-Duty?
This is the pattern I see most in audit files: the ELD or engine data shows the vehicle moving, and the driver's log shows off-duty or on-duty-not-driving for that same window. Under 49 CFR 395.26, ELDs automatically record vehicle motion data independent of what the driver types in. That automatic record is exactly what exposes the mismatch. A driver can enter whatever status they want in the log. The engine data doesn't care what they typed.
Some of this comes from habit, drivers who ran paper logs for twenty years and never fully trusted the device. Some of it comes from dispatch pressure to keep rolling past a legal limit. Either way, once the vehicle-motion data and the manual entry disagree, you've got a 395.8(e) problem sitting in your own ELD records, waiting for an investigator to pull it.
What Counts as Misusing Personal Conveyance?
Personal conveyance misuse happens when a driver marks off-duty time while still actually serving a business purpose, continuing toward a delivery, repositioning for dispatch convenience, or advancing a load under cover of a personal-use status. Personal conveyance itself isn't a numbered CFR provision. It's FMCSA guidance interpreting what counts as legitimate off-duty use of a commercial vehicle under 395.8. That guidance is what sets the line between a real personal trip and a disguised business one.
A supporting-document check is what usually catches this. If a driver clocks off-duty for personal conveyance but the dispatch record, fuel receipt location, and timestamp all point toward a delivery route instead of a personal errand, that's a mismatch you need to resolve. When the facts show the vehicle was still working under a business purpose, the off-duty entry becomes a false report under 395.8(e), guidance label or not.
What Happens When a Driver Logs Under Someone Else's Profile?
Every duty status entry has to match the person who actually did the work. Assigning hours to another driver's name, a co-driver who wasn't really there, or a fictitious profile set up to spread hours around, is a false report under 395.8(e) no matter how clean the paperwork looks. On the ELD side, 49 CFR 395.32 governs how the device handles driving that isn't tied to an authenticated profile, routing it into an unidentified-driver record instead of letting it disappear. That mechanism exists specifically to catch misattributed hours.
I've worked files where a carrier had two drivers trading log-ins to stretch available hours across a team run. The unidentified-driver data on the ELD told a completely different story than the paper logs the drivers submitted. That gap is exactly what an audit is built to find, and it's exactly what an investigator will find too if you don't find it first.
Does Tampering with the ELD Count as a False Log?
Yes. 49 CFR 395.8(e) covers both the false-report prohibition and a separate ban on disabling, jamming, reprogramming, or otherwise interfering with an ELD's signal or data. Disconnecting a device to suppress drive time, reflashing firmware to alter recorded hours, or blocking a transmission so drive time doesn't register are all tampering violations under that same subsection. This is the most serious version of a false log because it's not a labeling mistake. It's an attempt to beat the recording system itself.
If you're a safety manager and you suspect a device has been tampered with, that's the point to stop guessing and get the file reviewed. Waypoint True's Verity platform runs your ELD data against supporting documents and flags exactly this kind of inconsistency before it turns into a finding on an audit report.
How Does a Log Audit Catch These Problems?
A log audit works by pulling the record of duty status and the supporting documents from the same period and lining them up side by side. The rule that makes this possible is 49 CFR 395.11, which defines a supporting document, per the definitions in 49 CFR 395.2, as anything the carrier generates or receives in the normal course of business that can verify the accuracy of a duty status. Fuel receipts, toll records, bills of lading, dispatch and trip records, and electronic mobile communication records all qualify.
The retention rule in 49 CFR 395.8(k) requires carriers to keep records of duty status and supporting documents for at least six months, and requires drivers to keep the prior seven days with them while on duty. That retention window is what makes a retrospective audit possible at all. Without it, there's nothing left to check the log against. An auditor looks for odometer and time entries that don't line up with fuel or toll timestamps, automatically recorded ELD data that conflicts with a manual entry, and unidentified-driver or malfunction records that reveal gaps nobody explained. One mismatch might be a clerical error. A pattern of mismatches is a compliance problem, and patterns are exactly what a structured audit is built to surface before FMCSA finds them for you.
How Waypoint True Helps Fleets Catch False Logs Before an Auditor Does
When a file lands on my desk, step one is a straight read of the record of duty status against every supporting document the carrier has on hand: fuel, tolls, dispatch, bills of lading, electronic communications. We check whether the duty status for each 24-hour period was recorded and reported the way 49 CFR 395.8(a) requires, and whether anything in that record looks off against the automatically recorded ELD data under 395.26.
If we find a mismatch, we pin down exactly where the dispute is: a labeling error, a personal conveyance question, an unidentified-driver gap, or something that points toward tampering. Then we lay out the next step, whether that's a corrected log, a retraining conversation, or getting ahead of a CSA score hit before it shows up in your Hours-of-Service BASIC. Get your logs in front of us through Verity and find out what's actually sitting in your records before an investigator does it for you.
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.8
- 49 CFR Part 395.26
- 49 CFR Part 395.30
- 49 CFR Part 395.11
- 49 CFR Part 395.2
FAQ
Does a log have to be intentionally false to violate 49 CFR 395.8(e)?
The rule's text doesn't spell out an intent test: it bars making a false report in connection with a duty status. In practice an investigator looks at the evidence to tell an honest mistake from a false log, so fix and annotate errors as soon as you find them.
How long does a carrier have to keep supporting documents?
Under 49 CFR 395.8(k), carriers must keep records of duty status and supporting documents for at least six months from the date of receipt. Drivers must keep the prior seven consecutive days' records with them and available for inspection while on duty.
What counts as a supporting document under the rule?
49 CFR 395.11, read with the definitions in 49 CFR 395.2, defines a supporting document as anything the carrier generates or receives in the normal course of business that can verify a duty status record. That includes fuel receipts, toll records, dispatch logs, bills of lading, and electronic mobile communication records.
Is personal conveyance misuse the same thing as a false log?
It becomes one when the facts show the driver was still serving a business purpose while marked off-duty. Personal conveyance is FMCSA guidance, not a numbered rule, but an off-duty entry that doesn't match the actual activity still violates the false-report prohibition in 49 CFR 395.8(e).
Can an ELD itself catch a false log?
Partially. Automatically recorded data under 49 CFR 395.26, like vehicle motion, and the unidentified-driver handling under 49 CFR 395.32 both create a record independent of what the driver types in. An audit that checks that automatic data against the manual entries is what actually catches the discrepancy.
What should a safety manager do first after finding a possible false log?
Pull the supporting documents for that period and compare them against the record of duty status before taking any action against the driver. Getting the file reviewed through a structured audit, like Waypoint True's Verity, tells you whether you're looking at a clerical mistake or something that needs a bigger fix.