The Trucking Violations Hiding Inside Discovery
Discovery requests for trucking cases routinely pull driver qualification files and FMCSA logs, but the review often stops at whether the file exists rather than whether it satisfies the regulation. The gap between compliant paperwork and compliant conduct is where the strongest liability arguments sit unclaimed.
What Does a Trucking Discovery Review Actually Check?
Most discovery requests in a trucking case ask for the driver qualification file, the electronic logging device (ELD) data, and the CDL record. Most reviews confirm those documents exist and stop there. The federal standard those documents are supposed to meet is a separate question, and it's the one that turns a routine file into a liability finding.
The File That Passes and Still Fails
A driver qualification file (DQF) can look complete on a first pass: application present, license copy present, medical card present. Nothing missing, nothing to flag.
But "present" and "compliant" are not the same test. Under 49 CFR § 391.51, a motor carrier must maintain a DQF for every driver containing specific required items, not just a general employment record. A file that has an employment application skipping the three-year accident history required by § 391.21, or a medical certificate with no way to confirm the examiner is listed on FMCSA's National Registry of Certified Medical Examiners under § 391.41, still counts as incomplete under the regulation, even though it would pass a glance.
That gap, between a file that exists and a file that satisfies the standard, is where discovery review usually stops looking.
What the CDL Manual Actually Requires
The commercial driver's license itself is governed by 49 CFR Part 383. The document most attorneys mean when they say "the CDL manual" isn't itself the source of the substantive licensing rules. Under § 383.131(a)(1), it's the state-issued study and testing guide FMCSA requires to be comparable to the American Association of Motor Vehicle Administrators' Model Commercial Driver Manual. The actual requirements the manual is built to teach, which vehicle groups and endorsements apply to which combinations of vehicle and cargo, come from other sections of Part 383 itself.
That distinction still matters in litigation. A driver's licensed vehicle group and endorsements are checkable against the vehicle and cargo actually involved in the crash. A driver hauling a tanker without a tank vehicle endorsement, or operating a vehicle class outside what their license covers, is a documented licensing fact that can materially narrow the scope of factual dispute, independent of what the CDL manual says about how to pass the test for it.
Where Driver Qualification Files Fall Short
The regulation spells out what belongs in the file. Under § 391.51(b), the required contents include:
The employment application under § 391.21, including a three-year accident record and three-year driving history
A motor vehicle record (MVR) from each state where the driver was licensed, obtained at hire under § 391.23(a)(1) and reviewed annually under § 391.25
The medical examiner's certificate required under § 391.41(a), issued by an examiner listed on the National Registry of Certified Medical Examiners
Road test certification or a copy of an accepted equivalent
Annual driver certification of violations and the carrier's annual review of the driving record
Each of those has a failure mode that shows up in discovery. A missing annual MVR review means the carrier had no current picture of a driver's record for up to a year.
A medical certification gap needs to be read carefully right now. FMCSA has an active nationwide exemption, in effect April 11 through October 11, 2026, letting carriers rely on a paper medical examiner's certificate for up to 60 days after issuance while five states finish transitioning to the electronic National Registry II system. A driver relying on a paper certificate inside that window isn't automatically out of compliance, even if the file looks incomplete next to a fully electronic record. What's still worth checking is whether the certificate itself has actually expired, or whether the examiner who issued it is listed on the National Registry of Certified Medical Examiners under § 391.41(a). Those are documentation gaps regardless of the NRII transition; the paper-versus-electronic format on its own isn't.
Under § 391.51(d), the file itself has to be retained for the length of employment plus three years, so a file that's missing a document isn't necessarily one that was never created; it may be one the carrier failed to preserve, which is a separate question worth asking in a spoliation letter.
Hours of Service Violations Hiding in Plain Sight
Hours of service (HOS) rules limit how long a driver can be behind the wheel before a fatigue risk becomes a regulatory violation. Under 49 CFR § 395.3, a property-carrying driver may drive a maximum of 11 hours following 10 consecutive hours off duty, and may not drive at all after 14 consecutive hours have passed since coming on duty, regardless of how many of those hours were spent actually driving.
Here's what that looks like worked out, as a hypothetical: a driver comes on duty at 6:00 a.m. Under the 14-hour rule, that driver cannot be driving after 8:00 p.m. that same day, even if actual drive time hasn't hit 11 hours yet, because the clock started at sign-on, not at first movement. If the ELD record shows the vehicle still moving at 8:14 p.m., that's not a rounding issue. It's a documented departure from the regulation's own bright line, the kind of gap worth building the rest of the liability argument around.
The weekly limit compounds the daily one: § 395.3(b) caps a driver at 60 hours on duty across 7 consecutive days, or 70 hours across 8 days, depending on the carrier's operating schedule. A driver who's clean on any single day's 11-hour and 14-hour limits can still be in violation of the weekly cap, which only shows up when someone pulls seven days of logs side by side rather than reviewing one day at a time.
Cross-Referencing Regs Against the Case File
None of this requires guessing at what "reasonable" driver management looks like. It requires matching two sets of documents against each other: what the regulation specifies, and what the file actually contains. That's a matching problem, and it's the kind of problem that gets harder, not easier, as the file grows. A single crash can generate a DQF, months of ELD data, maintenance logs, and dispatch records, and a manual review has to hold the § 391.51 checklist and the § 395.3 hours limits in mind at once while paging through all of it.
Here's a second hypothetical to make that concrete: a carrier produces 400 pages of dispatch logs and driver certification forms in response to a discovery request. Somewhere in page 60 is an annual driver certification of violations dated fourteen months after the previous one, a four-month gap past the annual requirement in § 391.25. Nothing about that page looks unusual on its own. It's a routine form with a date on it. The violation only becomes visible when someone lines that date up against the date on the form before it, across hundreds of pages that were never filed in chronological order to begin with. That's the kind of gap a reviewer working page by page is statistically likely to miss on a first pass, not because the fact is hidden, but because the two dates that expose it are 60 pages apart.
The same matching approach isn't limited to driver files and hours logs. Vehicle inspection and maintenance records, cargo securement documentation, and driver training records all carry their own federal requirements, and the same discrepancy-hunting applies: does the maintenance log match the inspection schedule required for the vehicle class, does the cargo documentation match what the bill of lading says was loaded. Treating trucking discovery as one regulatory cross-reference problem, rather than a DQF problem or an HOS problem in isolation, is what keeps a review from stopping at the first file that looks complete.
Anytime AI's Discovery Response tool is built for that kind of cross-referencing: reviewing high-volume discovery documents and flagging where driver records, HR files, and compliance documentation are inconsistent with each other or with the underlying federal standard. Talk to Teddy can then surface the specific regulation a flagged document falls short of, with the citation attached, rather than leaving an attorney to track it down separately. For a fuller look at how that applies across truck accident litigation generally, the practice area page covers the broader workflow this fits into. It's a tool for finding where to look closer, not a replacement for looking.
What AI Review Still Can't Tell You
A regulation citation tells you a requirement wasn't met. It doesn't tell you why, and it doesn't tell you what that failure meant to the specific crash. A missing annual MVR review is a violation regardless of context, but whether it's central to the case depends on whether the driver's record, had it been reviewed, would have shown a disqualifying pattern. That's a judgment call for the attorney, not something a document match settles on its own.
The same goes for intent and credibility. A carrier that missed one medical certificate renewal because of an administrative error is a different case than one with a pattern of expired certificates across multiple drivers, and that pattern only means something once someone asks why it happened, not just that it happened. Flagging the gap is the easy part. Deciding what the gap is worth to the case still takes a lawyer who knows the file.
Turning a Regulation Citation Into Leverage
A general negligence theory asks a jury to agree that a carrier should have done better. A cited regulation asks them to agree that a carrier broke a specific, written rule, one the carrier had every ability to know about, because it applied to every driver on their fleet. The second argument is harder to talk around in a deposition, because there's no room to debate what "reasonable" meant. The rule says what it says.
That's the case for treating discovery review as a matching exercise against the actual text of 49 CFR Parts 383, 391, and 395, rather than a checklist of whether documents exist. The file that passes a glance and the file that meets the standard are not the same thing, and the difference between them is usually where the strongest fact in the case was sitting the whole time.
FAQs
What documents does 49 CFR § 391.51 require in a driver qualification file?
The regulation requires the employment application, motor vehicle records from each licensing state, the medical examiner's certificate, road test documentation, and annual reviews of the driver's certification and driving record.
How long must a carrier keep a driver qualification file?
Under § 391.51(d), the file must be kept for as long as the driver is employed, plus three years after that employment ends.
What is the 14-hour rule for truck drivers?
Under 49 CFR § 395.3(a)(2), a driver cannot drive after 14 consecutive hours have passed since coming on duty, whether or not the driver was actively driving for all of that time.
Is the CDL manual a federal regulation?
Not directly. Federal rule 49 CFR § 383.131 requires states to provide applicants a manual comparable to AAMVA's Model Commercial Driver Manual, so the manual's content reflects a federally mandated standard even though states publish their own versions of it.
Can an expired medical certificate be used as evidence of negligence?
An expired or missing medical certificate is a documented regulatory violation under § 391.41, and it can support a negligent hiring or retention theory, though whether it's central to a given case still depends on the facts connecting it to the crash.
Get Started
Ready to go deeper — and safer?
See how Anytime AI gives plaintiff firms the strategic edge
and the security their clients deserve.