Hours of Service Audit: Common Log Violations Explained
By Justin Seyl, NATMI Certified Director of Safety
A log audit almost always turns up the same two problems: drivers running past the hard limits in 49 CFR 395.3, and recordkeeping defects under 49 CFR 395.8 that auditors call "form and manner" violations. I've personally reviewed more than 650,000 citations over my career, and the pattern doesn't change much from fleet to fleet. False reports of duty status under 49 CFR 395.8(e) and having no record of duty status under 49 CFR 395.8(a) regularly show up among the most-cited driver violations in FMCSA's published roadside inspection data.
At Waypoint True, we built our Verity log-auditing product because fleets kept finding these problems the hard way — during a DOT audit, after the damage to their CSA score was already done. The mistake almost every fleet owner makes is waiting until a letter shows up before they take a hard look at their logs. By then you're not fixing a pattern, you're explaining one to an investigator. Run a self-audit before FMCSA ever knocks, and you're in control of the story instead of reacting to it.
What Does 49 CFR 395.3 Actually Limit?
49 CFR 395.3 sets the core driving-time rules for property-carrying CMVs, and it's where most hard violations get flagged. A driver can't drive without first taking 10 consecutive hours off duty. Once on duty, they can't drive past the 14-hour window that starts the moment they come on duty after that break. Inside that window, total driving time can't top 11 hours. None of this bends for weather, traffic, or a late dock. The clock runs regardless.
The section also sets the 30-minute break rule. After 8 cumulative hours of driving time, a driver needs a break of at least 30 consecutive minutes before driving again. FMCSA changed this in its 2020 final rule so the break ties to driving time instead of on-duty time, and it now allows an on-duty, not-driving period to satisfy it. That change took effect September 29, 2020. It gave drivers more flexibility, but it also created a new kind of audit finding: drivers and dispatchers who never updated their habits and keep getting flagged for missing or late breaks.
On top of the daily limits, 395.3(b) sets the 60-hour/7-day and 70-hour/8-day caps, depending on the carrier's operating schedule. A driver can restart that clock with 34 consecutive hours off duty. We regularly catch drivers who miscount their restart window or run two carriers' logs against each other without reconciling total on-duty hours across both.
What Counts as a "Form and Manner" Violation Under 49 CFR 395.8?
395.8 governs how a driver's record of duty status has to be built and kept, and that's a different problem than running over a driving limit. A driver can sit perfectly within the 11-hour and 14-hour limits and still get cited because the log itself is wrong, incomplete, or unsigned. Since December 18, 2017, carriers have had to install and require ELD use under this section, with narrow exceptions for drivers who complete a record of duty status on 8 or fewer days in any 30-day period, or driveaway-towaway operations.
False logs sit inside this same section. 395.8(e) bars a driver or carrier from making a false report of duty status, and that one subsection drives a huge share of the falsification citations I see on audit files. Retention matters too. Carriers have to keep records of duty status and supporting documents for 6 months from the date of receipt, and the driver has to carry the last 7 consecutive days of logs while on duty. Missing supporting documents, incomplete grids, logs that don't show miles or location — all of it falls under this section, and all of it shows up constantly in the audits we run through Verity.
What ELD-Specific Violations Show Up Most in Log Audits?
49 CFR 395.24 spells out what a driver has to do when the ELD prompts them. The device requires the driver to pick among Off Duty, Sleeper Berth, Driving, or On-Duty Not Driving, and 49 CFR 395.28 has the driver flag special categories such as personal conveyance or a yard move and add an annotation. Drivers skip that annotation step constantly, and an auditor reading an unexplained gap, or a status that doesn't match dispatch records, is going to flag it every time.
49 CFR 395.22 puts a separate duty on the carrier. Under 395.22(h), the motor carrier has to make sure each driver has in the truck a supply of blank record of duty status graph-grids, enough for at least 8 days, so the driver can keep logging by hand if the ELD malfunctions. Fleets that run lean on backup supplies get caught here, and it's an easy, preventable finding that has nothing to do with driver behavior and everything to do with fleet-level prep.
This is usually the point where a fleet owner realizes a once-a-year glance at logs isn't enough. If you're carrying any of these gaps right now, don't wait for a compliance review to find them for you. Run your logs through Waypoint True's Verity log-auditing service and get a clear picture of where your fleet actually stands before FMCSA builds that picture for you.
Do Maintenance Violations Ever Show Up Alongside HOS Findings?
They do, and it's worth knowing why. A full compliance audit doesn't stop at hours-of-service records. Auditors reviewing a driver's file commonly check maintenance compliance in the same pass, because a carrier loose on one set of records is often loose on the other. 49 CFR 396.17(c), operating a CMV without proof of a periodic inspection, is another frequently cited violation. 49 CFR 396.9 governs out-of-service declarations, and it bars a carrier from putting a vehicle marked out of service back on the road until every required repair is done. Fleets that treat HOS compliance and maintenance compliance as separate problems tend to miss how closely an auditor connects the two.
Why Does This Matter for Your CSA Score?
Every one of these violations, hard limit or form and manner, feeds into your Hours-of-Service Compliance BASIC under CSA. A pattern of 395.3 violations signals fatigue risk to FMCSA. A pattern of 395.8 or 395.24 recordkeeping problems signals a fleet that isn't managing its records, and that raises the credibility question on every other log in the file. Neither pattern helps your Safety Fitness Determination, and both are the kind of thing a DOT auditor digs into the second they spot the first red flag. Run an internal hours of service audit before that happens and you get the chance to correct the pattern instead of defending it.
How Waypoint True Helps With Hours-of-Service Log Audits
When you send us a file, we start by checking the actual logs against the 395.3 limits — driving time, the 14-hour window, the 30-minute break, the 60/70-hour caps — driver by driver, day by day. We cross-check that against 395.8 and 395.24 to confirm each record was built and annotated the way FMCSA expects. We spot where a violation was reported correctly versus where the record itself has a gap, a missing annotation, or a retention problem that could read as a bigger issue than it is. From there, we flag disputes worth raising and lay out your next move, whether that's correcting driver habits, fixing a dispatch process, or getting documentation ready ahead of a compliance review. You get a clear, ranked picture of where your fleet actually stands, not a guess.
If you've read this far and you're already wondering what your own logs would show, that's the right instinct. Get your file in front of us through Verity and find out before an auditor does. We don't promise a particular outcome on any file, but a fleet that knows its own problems ahead of time is always in a stronger spot than one that doesn't.
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.3
- 49 CFR Part 395.8
- 49 CFR Part 395.24
- 49 CFR Part 395.22
- 49 CFR Part 396.17
- 49 CFR Part 396.9
FAQ
What's the most common hours-of-service violation found in a log audit?
Audits most often turn up violations clustered around 49 CFR 395.3 driving-time limits and 49 CFR 395.8 recordkeeping defects. False records of duty status and missing records of duty status regularly appear among the most-cited driver violations in FMCSA's roadside inspection data.
Can a driver violate hours-of-service rules even with an ELD installed?
Yes. An ELD records duty status automatically, but it doesn't stop a driver from going over the 11-hour or 14-hour limits under 49 CFR 395.3, and it doesn't fix a missing annotation required under 49 CFR 395.24. The device logs the problem; it doesn't prevent it.
How long does a carrier have to keep hours-of-service records?
Under 49 CFR 395.8(k), a motor carrier has to keep records of duty status and supporting documents for at least 6 months from the date of receipt. The driver separately has to carry the previous 7 consecutive days of logs while on duty and have them ready for inspection.
What's the difference between a "form and manner" violation and a driving-limit violation?
A driving-limit violation under 49 CFR 395.3 means a driver actually went over the 11-hour, 14-hour, or 60/70-hour limits. A form-and-manner violation under 49 CFR 395.8 means the record itself is wrong, missing, or incomplete, even if the driver never actually drove over the limit.
Does a maintenance violation count against hours-of-service compliance?
Not directly, but auditors often review them together. 49 CFR 396.17(c) covers operating without proof of a periodic inspection, and 49 CFR 396.9 covers out-of-service orders. A carrier weak on one set of records frequently draws closer scrutiny on the other during a full audit.
How often should a fleet run its own hours-of-service log audit?
There's no FMCSA-mandated frequency, but waiting for a compliance review to find your problems is the costliest option. Running a driver log auditing service like Verity on a regular schedule catches 395.3 and 395.8 issues while they're still cheap to fix.