Supporting Documents Under 49 CFR 395.11: Full Guide
By Justin Seyl, NATMI Certified Director of Safety
A carrier has to keep supporting documents that verify a driver's on-duty, not-driving time — up to eight per driver per 24-hour period — and hold onto them for six months alongside the driver's records of duty status. That's the whole rule in one sentence. Actually doing it right, day after day, across every truck in your fleet, is the hard part. In 25+ years running safety departments and overseeing more than 650,000 citations, I've watched this exact recordkeeping gap sink more compliance reviews than any single HOS violation on a log.
At Waypoint True, we built Verity because we kept seeing the same failure pattern: carriers with clean-looking logs get hit hard at audit because the paperwork behind those logs doesn't match up, or doesn't exist at all. The mistake most fleets make is waiting until a DOT notice shows up to go looking for bills of lading, dispatch records, and fuel receipts from three months back. By then it's too late to fix a gap. Supporting documents only protect you if you're collecting and matching them against logs in real time, not scrambling to reconstruct them under deadline pressure.
What Counts as a Supporting Document Under 49 CFR 395.11?
A supporting document is anything your business generates or receives in the normal course of operations that can verify a driver's record of duty status is accurate. That definition comes straight from 49 CFR 395.2, which defines the term broadly: any document, in any medium, that you or an enforcement officer could use to check a driver's RODS against what actually happened that day.
That's intentionally broad. It's not limited to paper logs or a specific form. It covers electronic records, scanned receipts, dispatch software exports, and anything your fleet management system spits out, as long as it ties back to verifying on-duty time.
What Are the Five Categories of Supporting Documents?
FMCSA's official guidance breaks supporting documents into five categories, all described under 49 CFR 395.11(c):
- Bills of lading, itineraries, schedules, or equivalent documents showing the origin and destination of each trip
- Dispatch records, trip records, or equivalent documents
- Expense receipts tied to any on-duty, not-driving time
- Electronic mobile communication records reflecting messages sent through a fleet management system
- Payroll records, settlement sheets, or equivalent documents showing payment to a driver
Think fuel receipts, scale tickets, toll records, lumper receipts, and dispatch texts. If it shows where a driver was and when, it probably falls into one of these five buckets.
What Must Each Document Show, and What's the Eight-Document Rule?
Under 49 CFR 395.11(c)(2)(i), a qualifying supporting document needs four elements: the driver's name or carrier-assigned ID number, the date, the location (city, town, or village), and the time. Miss one of those and the document can still count in a pinch: if a driver has fewer than eight documents with all four elements for a given 24-hour period, a document missing only the "time" element still qualifies as a supporting document under 395.11(c)(2)(ii).
Here's the number every safety manager needs memorized: eight. A carrier only has to retain up to eight supporting documents per driver per 24-hour period. If a driver generates more than eight that day, 395.11(d)(3) says the eight you keep must include the ones with the earliest and the latest times. One wrinkle worth flagging: under 395.11(d)(2), the electronic mobile communication records for a driver's 24-hour period count as a single document, no matter how many messages went back and forth.
Don't make the mistake of only grabbing a start-of-day and end-of-day document and calling it compliant. Documents collected throughout the day are what verify on-duty time, so a carrier that only captures the bookends is leaving gaps an auditor will find.
How Long Do Drivers Have to Submit Supporting Documents?
A driver has 13 days to submit supporting documents to the employer, counted from either the end of the 24-hour period the documents cover or the day the driver got the document, whichever comes later. That's the text of 49 CFR 395.11(b), and it runs on the same clock as the record of duty status itself. 49 CFR 395.8(a)(2)(ii) sets the matching deadline for the log itself: the driver must submit the record of duty status to the carrier within 13 days of the 24-hour period it covers.
How Long Must a Carrier Retain These Records?
Six months. 49 CFR 395.8(k)(1) requires a motor carrier to maintain records of duty status and all supporting documents for each driver for six months from the date of receipt. The driver side of that rule matters too: 395.8(k)(2) requires drivers to keep a copy of each RODS for the previous seven consecutive days in their possession and available for inspection.
Worth noting that this six-month clock runs separately from vehicle maintenance recordkeeping. Under 49 CFR 396.3, inspection and repair records have to be kept for one year while the vehicle is in the carrier's possession, plus six months after it leaves. Auditors frequently pull both file types in the same review, so don't assume your HOS retention schedule covers your maintenance files, or vice versa.
This is the point where most fleets realize their filing system wasn't built for this. If you're sitting on boxes of receipts and a patchwork of ELD exports with no process tying them back to specific drivers and dates, now's the moment to get ahead of it, not after a data request letter arrives. Verity, Waypoint True's log-auditing tool, checks your electronic logs against the supporting documents you already have on file so you can see the gaps before an auditor does.
How Do Auditors Actually Use Supporting Documents?
Auditors use supporting documents to check whether a driver's logged on-duty and driving time matches what really happened: where the truck was, when, and what the driver was doing. This verification function is the stated purpose of 395.11 in FMCSA's own guidance. A bill of lading that puts a driver at a shipper two states away from where the log says he was logging off-duty is the kind of mismatch that turns a routine compliance review into a bigger problem.
Hours-of-Service Compliance is one of seven Behavior Analysis and Safety Improvement Categories FMCSA tracks in its Safety Measurement System, covering operation of commercial vehicles by drivers who are fatigued or out of compliance with HOS rules, according to FMCSA's Driver SMS Methodology. Supporting documents are the raw material an investigator uses to decide whether your logs reflect reality or just reflect what a driver typed into an ELD. A clean log with no paperwork behind it doesn't hold up the way carriers assume it will.
How Waypoint True Helps Carriers Stay Ahead of Supporting Document Gaps
When a file comes to us, the first thing we do is review the audit notice itself and confirm what period and what records are actually in scope. From there we check whether violations got reported correctly against the carrier's actual logs and supporting documents, because reporting errors happen more often than most safety managers expect. We identify where a dispute is legitimate — a missing data element, a mismatched document count, a retention gap that predates current staff. Then we walk you through the next step, whether that's a DataQ challenge, a corrective action plan, or just tightening your document collection process going forward.
If you've got an audit notice sitting on your desk right now, don't wait on this. Get your file in front of us for a Verity log audit so you know exactly where your supporting documents stand before an investigator tells 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.11
- 49 CFR Part 395.2
- 49 CFR Part 395.8
- 49 CFR Part 396.3
FAQ
How many supporting documents does a carrier need per day?
A carrier needs to retain up to eight supporting documents per driver per 24-hour period. If more than eight exist, the eight you keep must include the earliest and the latest, per 49 CFR 395.11(d).
What happens if a driver doesn't submit documents within 13 days?
The regulation sets the 13-day window under 49 CFR 395.11(b), but it doesn't spell out an automatic penalty for a late submission. The real risk is a carrier missing documents when a safety review happens, which can make it harder to verify a log's accuracy.
Does an electronic message count as one document or several?
One. Under 49 CFR 395.11(d)(2), the electronic mobile communication records for a driver's 24-hour period count as a single document, no matter how many individual messages went through the fleet management system that day.
How long must a carrier keep supporting documents on file?
Six months from the date of receipt, as set out in 49 CFR 395.8(k)(1). That retention period applies alongside the driver's record of duty status, not as a separate or shorter timeline.
Can a document missing the time element still qualify?
Sometimes. Under 49 CFR 395.11(c)(2)(ii), if a driver has fewer than eight qualifying documents for a 24-hour period, a document with the other three required elements but missing only the time can still count as a supporting document.
Are vehicle maintenance records the same as HOS supporting documents?
No. Maintenance records fall under 49 CFR 396.3 and carry their own one-year-plus-six-month retention rule, separate from the six-month HOS supporting document requirement. Auditors often review both, but they're distinct recordkeeping obligations.