Hours-of-Service Audit: What FMCSA Checks in Driver Logs
By Justin Seyl, NATMI Certified Director of Safety
A DOT auditor going through driver logs is checking four things: did the driver stay inside hours-of-service limits, are the records accurate and not falsified, do the supporting documents actually back up what the logs say, and does the ELD data — edits, unassigned driving time, all of it — hold together without gaps. Get any one of those wrong across enough files and a compliance review stops being a paperwork exercise. It starts affecting your Safety Fitness Determination.
I've sat across the table from carriers after the auditor already pulled the files. By that point your options are thin. Waypoint True exists so that review happens before FMCSA shows up, not after. Our Verity log audit goes through records of duty status the same way an investigator does: hours limits, supporting documents, ELD edit history, unassigned driving segments. The mistake most fleets make is waiting for a letter to show up before they look hard at their own logs. By then you're explaining problems instead of fixing them.
What Hours-of-Service Limits Does an Auditor Check First?
The baseline is 49 CFR 395.3. A driver needs 10 consecutive hours off duty before driving, can't drive past the 14th consecutive hour after coming on duty following that break, and is capped at 11 hours of actual driving time inside that 14-hour window. On the weekly side, a driver can't drive after piling up 60 hours on duty in 7 consecutive days, or 70 hours in 8 consecutive days for carriers running every day of the week. A 34-hour or longer off-duty stretch resets either clock.
An auditor isn't just checking one bad day on one log sheet. They're looking for a pattern — drivers routinely right up against the 14-hour wall, a 60/70 clock that never seems to hit a real reset, dispatch patterns that make the math look suspicious even when the individual logs look clean on paper.
How Does an Auditor Spot a False Log?
Under 49 CFR 395.8(e)(1), no driver or carrier can make a false report connected to a duty status. That's the rule in plain language: logs have to be true, period. Auditors cross-reference the record of duty status against everything else that exists for that trip — fuel receipts, toll records, dispatch notes, GPS pings from the fleet management system, even weigh station timestamps.
When those sources don't match what the log says, that's a false log finding, and it's one of the more serious things an auditor can write up. It can carry out-of-service consequences, and it's exactly the kind of violation that drags your Hours-of-Service Compliance BASIC score the wrong direction on CSA. A related falsification rule sits at 49 CFR 390.35, covering carriers and drivers who falsify applications, certificates, or logs tied to qualification records. So falsification exposure doesn't stop at the RODS — it follows you into the driver qualification file too.
What Supporting Documents Does FMCSA Require?
This is where a lot of fleets lose ground without ever touching a false-log violation. Under 49 CFR 395.11, a driver has to turn in supporting documents within 13 days of the 24-hour period they relate to, or within 13 days of getting the document, whichever is later. Required categories include dispatch records, trip records, expense receipts tied to on-duty-not-driving time, electronic mobile communication records from the fleet management system, and payroll or settlement records.
You don't have to keep an endless pile of paper on every driver. A carrier only needs up to eight supporting documents per driver per 24-hour period, and if more than eight exist, you keep the ones with the earliest and latest time indications. But "we don't have to keep everything" isn't the same as "we don't have to keep enough to verify the log." An auditor pulling a week of logs and finding zero supporting documents behind them isn't going to take the RODS at face value. That's exactly the gap a hours of service audit should catch before FMCSA does.
How Does ELD Data Get Reviewed During an Audit?
Carriers running ELDs have specific obligations under 49 CFR 395.22 over who can access ELD records and who's authorized to suggest or make edits. On the driver side, 49 CFR 395.30 requires the driver to review their own ELD records, fix inaccuracies, add missing information, and certify accuracy by actively selecting "Agree" on a statement confirming the data entries and record of duty status for that 24-hour period are true and correct.
Here's what fleet owners get wrong most often: automatically recorded drive time — the time the ELD captured while the vehicle was actually moving — can't just get edited into non-driving time. There are narrow exceptions, like a team-driver reassignment, but outside of that, drive time is drive time. A carrier can propose an edit, but it can't pressure a driver into a false certification, and it can't alter or erase the original ELD data. Auditors pull edit histories specifically to see whether changes line up with legitimate corrections or look like an attempt to make a log compliant after the fact.
If your fleet has never run its own ELD log audit software or review process against that edit history, now's the time — not after a compliance review notice lands on your desk. Get your logs in front of Waypoint True's Verity log audit and we'll flag the same edit patterns and unassigned-driving gaps an FMCSA investigator is trained to catch.
What Happens With Unassigned Driving Time?
Under 49 CFR 395.32, an ELD has to dump any driving time with nobody logged in into a single "Unidentified Driver" account the second the vehicle starts moving. When a driver logs in afterward, they have to review any unassigned driving time the system flags and either claim it or confirm it isn't theirs.
Unresolved unassigned driving segments are a red flag auditors watch closely. It can mean a driver just forgot to log in — sloppy, but fixable. It can also mean someone's driving on another driver's credentials, or hours are going unrecorded on purpose. Either way, a stack of unassigned driving time nobody ever claimed or disclaimed tells an investigator the carrier isn't managing its ELD data, and that invites a harder look at everything else in the file.
Do Vehicle Maintenance Records Factor Into a Logs Review?
Auditors often pull maintenance files alongside RODS because the two tell a connected story about whether a carrier runs a controlled operation. Under 49 CFR 396.3, carriers have to keep a record for each vehicle under their control showing identification, a schedule of due inspection and maintenance work, and a record of repairs and maintenance performed — retained for one year where the vehicle is housed or maintained and for six months after it leaves the carrier's control. Driver vehicle inspection reports fall under 49 CFR 396.11 and need to be kept for three months from the date the report was written.
It's not that bad maintenance records cause a false-log finding. It's that an auditor who finds sloppy recordkeeping in one corner of your operation starts looking harder everywhere else. A clean logs file sitting next to a messy maintenance file doesn't read as clean for long.
How Waypoint True Helps With a Logs Audit
When a file comes to us, we start the same way an FMCSA investigator does. We pull the records of duty status and check them against the hours limits in 49 CFR 395.3, then check whether the data was reported the way 49 CFR 395.8 and 395.11 require, including whether supporting documents actually exist behind the logs that need them. We go through the ELD edit history looking for anything that looks like an after-the-fact fix instead of a legitimate correction, and we check unassigned driving segments for gaps nobody resolved under 49 CFR 395.32.
Where we find a real dispute — the data looks wrong, incomplete, or doesn't match what actually happened — we tell you exactly what it is and what your options are for fixing it before it shows up in a compliance review. We don't file paperwork on your behalf and we don't promise an outcome. What we give you is a clear, documented read on where your logs stand, built by someone who's overseen more than 650,000 citations and directed over 10,000 Safety Fitness Determination upgrades.
If you've already got an audit notice in hand, don't wait on this. Get your records in front of us through the Verity log audit now, while there's still time to find and fix a problem 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.3
- 49 CFR Part 395.8
- 49 CFR Part 390.35
- 49 CFR Part 395.11
- 49 CFR Part 395.22
- 49 CFR Part 395.30
- 49 CFR Part 395.32
- 49 CFR Part 396.3
- 49 CFR Part 396.11
FAQ
What triggers a DOT compliance review of driver logs?
Compliance reviews get triggered by crash history, complaints, CSA BASIC scores crossing intervention thresholds, or random selection by FMCSA and state partners.
Can a false log violation put a carrier out of service?
It can. Roadside inspectors apply the CVSA out-of-service criteria, and a driver found with a false log can be placed out of service under them. Whether a specific finding qualifies depends on the current criteria, so check them before assuming either way.
How many supporting documents does a carrier need to keep per driver?
Under 49 CFR 395.11, a carrier doesn't need more than eight supporting documents per driver per 24-hour period. If more than eight exist, you keep the ones with the earliest and latest time indications. Fewer than the required documents behind a log invites an auditor to question whether the log itself is accurate.
Can a carrier edit a driver's ELD record to fix a mistake?
A carrier can propose an edit under 49 CFR 395.30, but it can't alter or erase the original ELD data and can't pressure a driver into a false certification. Automatically recorded drive time while the vehicle was in motion generally can't get edited into non-driving time, aside from narrow exceptions like team-driver reassignment.
What does unassigned driving time mean on an ELD report?
Unassigned driving time is driving the ELD recorded with no driver logged in, automatically bucketed under an "Unidentified Driver" account per 49 CFR 395.32. Drivers have to review and claim or disclaim that time at their next login. Unresolved segments are a common flag in compliance reviews.
Should a fleet audit its own logs before FMCSA does?
Yes. Going through records of duty status, supporting documents, and ELD edit history on your own schedule means you find and fix problems before an investigator does. Waiting until a compliance review notice arrives leaves you reacting to findings instead of correcting them ahead of time.