The weekly HOS audit: find the pattern before FMCSA does
Hours-of-service problems rarely start as one bad log. They start as a habit that repeats for weeks until a roadside inspection or an investigator finds it.
The HOS audit in numbers
A weekly HOS audit is a carrier's own review of last week's driver logs: check each day against the driving limits, clear unidentified driving, test personal conveyance, yard moves, and edits, and match logs to supporting documents. Then coach the driver, fix the cause, and record what you did.
Hours-of-service violations are rarely one-time mistakes. More often they are the same missed break or the same personal conveyance trip, repeated until it becomes a pattern on paper.
I have led operations at Simplex for nearly eight years, and I treat log review the way I treat any recurring control: same day, same checks, same record of what we found. Below is the routine we recommend, built on the same rules an investigator uses.
The full briefing, read aloud
7 chapters. Select one to jump to it.
Generated with AI text-to-speech from this article's key insights, in order, rather than reading it word for word. Chapter times come from a transcript of the audio. The article itself was written and reviewed by Inely Baez.
Key takeaways
One HOS pattern can fail a whole factor
In a compliance review, violations in at least 10% of the records examined form a pattern, and each hours-of-service pattern counts two points: enough for an Unsatisfactory Operational factor.
Clear unidentified driving first
Unassigned driving can hide hours. The carrier must assign it to a driver or annotate why it is unassigned, and keep those records for 6 months.
Personal conveyance is where false logs hide
Off-duty driving that served the business is cited as a false log at roadside, with the same severity weight as driving over hours.
Logs must match supporting documents
Bills of lading, dispatch records, receipts, fleet messages, and payroll records show where a driver really was. Keep them so they can be matched to each log.
Edits go through the driver
A carrier can propose an edit only after the driver submits the log, the driver must accept or reject it, and edits can never shorten recorded driving time.
In this articleContents
Why run a weekly HOS audit?
A weekly HOS audit catches a habit while it is still a few logs. The rules leave room for it: drivers have 13 days to submit each day's record, and you keep logs and supporting documents for at least 6 months, under 49 CFR 395.8.
Investigators read the same records. In a compliance review, a pattern is more than one violation and at least 10% of the records examined. Each pattern of a critical hours-of-service violation counts two points, and two points make the Operational factor Unsatisfactory. Our guide to what to expect in a DOT compliance audit covers how investigators sample.
At roadside, the same violations feed the Hours-of-Service Compliance BASIC, where FMCSA prioritizes most property carriers at the 65th percentile. Violations from the last six months weigh three times as much as those more than a year old, so last month's habits count most.
| Finding | Roadside severity weight | In a compliance review |
|---|---|---|
| Driving past the 11-hour, 14-hour, 30-minute, or 60/70-hour limit | 7, plus 2 if out of service | Critical regulation |
| False log, including improper personal conveyance | 7 | Critical regulation |
| Log not current to the last change of duty status | 5 | Not on the acute or critical list |
| Driver did not review unassigned driving time | 5 | Not on the acute or critical list |
| Log not certified, or a missing annotation | 1 | Not on the acute or critical list |
What should you check in last week's logs?
Check every driver's week against the limits first, then the entries that can hide driving time. If you need a refresher on how the device records each event, see how an ELD logs the day.
| Check | What to look for | Rule |
|---|---|---|
| Driving limits | 11 hours of driving within the 14-hour window after 10 hours off; a 30-minute break after 8 hours of driving; the 60- or 70-hour limit; 34-hour restarts | 49 CFR 395.3 |
| Unidentified driving | Every segment assigned to the right driver or annotated with the reason | 49 CFR 395.32 |
| Personal conveyance | Off-duty driving that served the business: reaching the terminal, getting closer to the next pickup, or fetching a load | FMCSA guidance |
| Yard moves | Periods that look like ordinary driving: long, fast, or far from the yard | 49 CFR 395.28 |
| Edits | An annotation on every change, driver approval of office edits, nothing that shortens recorded driving | 49 CFR 395.30 |
| Certification | Every 24-hour period certified, and recertified after edits | 49 CFR 395.30 |
| Malfunctions | Any open malfunction and its 8-day repair clock | 49 CFR 395.34 |
| Short-haul time records | Report time, on-duty hours, and release time; back within 14 hours and 150 air miles | 49 CFR 395.1(e)(1) |
Why clear unidentified driving first?
Unassigned driving is time that belongs to someone's clock. Under 49 CFR 395.32, the carrier must review it and either assign it to the right driver or annotate why it is unassigned, then keep the records for 6 months.
It also shows at roadside. According to FMCSA's ELD FAQs, more than 30 minutes of unidentified driving in a 24-hour period turns on the ELD's data diagnostic indicator for that day and the next 7. It clears only when the total for the current day and previous 7 drops to 15 minutes or less.
Where does personal conveyance go wrong?
Personal conveyance is off-duty only when the carrier has relieved the driver of all work, under FMCSA guidance. The truck can be loaded. These moves do not qualify:
- Bypassing available rest locations to get closer to the next pickup or delivery
- Driving to the carrier's terminal after loading or unloading
- Bobtailing or pulling an empty trailer to get another load
- Taking the truck to a shop for maintenance
- Driving to rest after being placed out of service for hours, unless an officer directs it
You can set stricter limits, such as a mileage cap or no personal conveyance while loaded. A driver who forgets to select personal conveyance or a yard move cannot turn that driving into off-duty or on-duty time later; FMCSA says to annotate the record instead.
How do you catch a false log?
You catch a false log by comparing it with documents the driver did not write in the ELD. Under 49 CFR 395.11, you must keep these supporting documents for each driver and day:
- Bills of lading, itineraries, or schedules showing each trip's origin and destination
- Dispatch or trip records
- Expense receipts for on-duty, not-driving time, such as fuel receipts
- Messages sent through your fleet management system
- Payroll records or settlement sheets
Each one needs a driver name, ID, or unit number, a date, a location, and a time. You need not keep more than eight per driver per day, but if you have more, keep the earliest and the latest. Drivers must turn them in within 13 days, and you must store them so they can be matched to the log.
Then compare. A fuel receipt timed during a sleeper-berth period, a shipper check-in while the log shows off duty, or a dispatch message sent mid-break are the gaps an investigator looks for.
How to run a weekly HOS audit, step by step
No rule sets the frequency. A fixed weekly slot keeps every log inside the driver's 13-day window and well inside your 6-month retention.
Step 1: Pull the week on the same day
Export last week's logs, the unidentified driving report, the edit history, personal conveyance and yard-move events, and open malfunctions. Pull the supporting documents for the same days.
Step 2: Resolve unidentified driving
Assign or annotate every segment before you check hours. Time you assign can change a driver's totals.
Step 3: Check limits and near misses
Flag every violation, then the days that finished within minutes of a limit. Near misses usually point to the same appointment or lane.
Step 4: Test the entries that hide driving
Read each personal conveyance trip, yard move, and edit. Office edits are proposals: the driver must accept or reject them and recertify, and the original record stays, under 49 CFR 395.30.
Step 5: Match a sample to supporting documents
In a small fleet, check every driver. In a larger one, check every flagged log plus a random sample, and widen the sample when you find a gap.
Step 6: Coach, fix the cause, and write it down
Talk to each driver with a finding, and look for the cause in dispatch: tight appointments, long dock waits, or loads that do not fit the clock. Never push a driver to change a log; our ELD mandate compliance checklist explains where edits become coercion. Record what you checked, found, and changed.
Which numbers show the audit is working?
Track a few numbers from week to week, not a single score. These are internal measures; FMCSA does not set targets for them.
| Metric | Why it matters |
|---|---|
| HOS violations per 100 driving days | Compares weeks and drivers fairly as the fleet changes |
| Unidentified driving minutes per truck | Over 30 minutes in a day turns on the diagnostic indicator |
| Days certified late or not at all | Uncertified logs are an easy roadside citation |
| Personal conveyance miles per driver | Unusual totals point to the trips worth reading |
| Logs matched to supporting documents | Shows the false-log check actually ran |
| Clean driver inspections | Inspections without violations also count in your HOS measure |
That last point matters. FMCSA's HOS measure divides weighted violations by the time-weighted count of all relevant driver inspections, clean ones included, so each clean inspection helps. If you want a team to run this review every week, HOS management is part of our compliance programs. For the device side, such as malfunctions and backups, see our ELD compliance guide.
How Simplex helps you audit hours of service
The ELD records the data. Someone still has to read it every week and act on it.
HOS management, every week
Our compliance programs include HOS management, CSA monitoring, and mock audits, so the review runs even when your team is busy.
ELD solutions for fleets
Simplex offers ELD solutions, and we help set up the process around the device, from unidentified driving to edits.
Audit and safety support
Our DOT safety compliance team covers hours of service, driver qualification files, and audit preparation.
Frequently asked questions
How often should a carrier audit driver logs?+
Can a carrier edit a driver's ELD log?+
What should a carrier do with unidentified driving time?+
Is personal conveyance a violation?+
How long must a carrier keep HOS records?+
Where this information comes from
The requirements below come from federal regulation and FMCSA guidance and data documents, checked on October 19, 2026.
-
1
eCFR — 49 CFR Part 395
Driving limits (395.3), 13-day submission and 6-month retention (395.8), short-haul time records (395.1), unidentified driving (395.32).
-
2
eCFR — 49 CFR 395.11
Supporting document categories, data elements, the eight-document limit, and matching to the log.
-
3
eCFR — 49 CFR 395.30
Driver certification, carrier-proposed edits, annotations, and coercion.
-
4
eCFR — Appendix B to 49 CFR Part 385
The 10% pattern rule, two points for HOS patterns, factor ratings, and the critical regulations.
-
5
FMCSA — Personal Conveyance
When driving may be logged off duty, and the uses that do not qualify.
-
6
FMCSA — ELD Frequently Asked Questions
Unidentified driving indicator thresholds, special driving categories, and edit limits.
-
7
FMCSA — SMS Methodology (June 2026)
HOS Compliance BASIC measure, time weights, and intervention thresholds.
-
8
FMCSA — SMS Appendix A Violation List (May 2026)
Severity weights for hours, false log, and form-and-manner violations.
Written by
Inely Baez
Chief Operating Officer, Simplex Group
Chief Operating Officer at Simplex Group, with nearly eight years at the company leading operational strategy and execution across compliance, technology, logistics, and performance systems. She is a Certified Public Accountant with a background spanning operations and finance, including leadership roles within Simplex's Freight 4 U division and Velox Transport Solutions. Her work focuses on building scalable, disciplined systems that support long-term performance and growth.
Published · Updated
Related articles and services
Read last week's logs before anyone else does
An investigator or a roadside officer will read your drivers' logs eventually. A weekly audit means you have already seen what they will see, fixed the cause, and written it down.
If you want help setting up the routine or running it for you, talk to our team.
