Every §391.51 document. One driver profile.

49 CFR §391.51 is the federal rule that defines a Driver Qualification file. The text is short. The operational tail is long.

Every motor carrier must hold a single file per driver containing eight categories: the employment application from §391.21, the road test certificate from §391.31, MVRs from every state of license issuance over the prior 3 years, previous-employer inquiries from §391.23, the annual driving record review from §391.25, the annual violation list from §391.27, the current medical examiner's certificate from §391.43, and the Safety Performance History records request. For CDL holders trained on or after February 7, 2022, the entry-level driver training (ELDT) certificate sits alongside.

The retention rule: while the driver is employed, plus 3 years after separation. Medical certificates carry a separate clock, 3 years from the date of the exam. Several documents (MVR, annual review, violation list) reset on a rolling 12-month window while the driver is active. Miss the window on one driver and the violation is per-driver, not per-fleet.

That's where the math turns ugly. Under the FMCSA civil-penalty schedule in 49 CFR Part 386 — adjusted annually for inflation — a DQ-file recordkeeping violation runs into five figures per driver per violation (on the order of $12,000 per the 2026 adjustment table). A 20-driver fleet that lets the annual MVR slip across the board is staring at a six-figure exposure ceiling before a single citation is even issued. And the operational damage cuts deeper than the fines: a DQ-file gap surfaced at a compliance review can downgrade your carrier safety rating from Satisfactory to Conditional or Unsatisfactory, which kills you on every load board that screens by safety rating.

DQ files break first under audit because they're the easiest kind of compliance to fake your way through day-to-day. You don't get a roadside citation for a missing previous-employer inquiry the way you do for an expired plate. The gap stays invisible until FMCSA actually opens the file. Then it's a week of binder-flipping, vendor-emailing, and praying the medical cert your driver renewed last March was actually scanned to the shared drive.

Dockex's approach is to make each §391.51 category an explicit, named slot on the driver profile, with a known content type, a known retention rule, and known expiration logic. The compliance dashboard scores every driver on those eight categories continuously, so a missing document is visible the moment it's missing (not the morning FMCSA knocks).

Expiration alerts fire at 30, 15, and 7 days for every document with a clock: medical certificates, annual MVR pulls, the 12-month violation list, Clearinghouse queries. Out-of-compliance drivers get flagged on the dispatch board so a dispatcher can't accidentally put a driver with an expired med card on a load.

The audit-export piece is where this earns its keep. FMCSA gives you 48 hours to produce DQ files on request. From paper, that window evaporates. In Dockex, you select drivers and click export. A single indexed PDF assembles with a table of contents that carries a §-reference entry per §391.51 category, last-updated timestamp and expiration date on every entry, and an immutable audit log showing every view, upload, and modification on the underlying record. That's the document FMCSA wants. You produce it in the time it takes the printer to warm up.

For the broader picture of how DQ files sit inside the federal compliance stack, the fleet compliance checklist covers what runs alongside (Clearinghouse, D&A results, MCS-150, insurance), and the spreadsheet failure piece walks through why a shared Google Sheet is the most common reason DQ files fall apart at audit time.