--- title: Carrier vs driver roles in driver qualification files description: Who submits Part 391 documents versus who reviews them, and how you record carrier status when drivers upload licenses and medical records from the road. date: 2026-09-05 lastReviewed: 2026-10-22 canonical: /blog/carrier-and-driver-dq-file-responsibilities --- Your driver snaps a photo of a new medical certificate at a truck stop. By the time they reach the terminal, dispatch sees an upload notification and assumes the file is “green.” But [49 CFR 391.51](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-F/section-391.51) places **maintenance** of the qualification file on the motor carrier—not on the driver’s camera roll. Mobile tools speed collection. They do not replace reviewer names, inquiry dates, or the carrier’s decision that a file is complete enough for your policy. When roles blur, audits find self-certified files that look modern and fail anyway. Picture a safety manager reviewing three hires while terminals push for Friday departures. Drivers did their part—photos uploaded, applications signed electronically. The carrier still owes MVR requests, inquiry letters, Clearinghouse queries, and dated review notes before your policy treats the file as complete. Clarity about that split keeps weekends calmer and files defensible. Write the split into onboarding scripts dispatchers hear, not only into safety SOPs. When terminal staff repeat the same carrier-versus-driver language, drivers stop treating upload notifications as clearance to roll. Consistency across shifts matters as much as the policy PDF. ## Key takeaways - Drivers provide applications, licenses, medical certificates, and updates you request; **carriers** file MVRs, road test evidence, annual review notes, and medical documentation in the qualification file. - Only staff involved in hiring decisions should access the **investigation history file** under [§ 391.53](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-F/section-391.53). - Status flags in software reflect **carrier review**, not driver uploads alone. - Same-day onboarding still requires carrier-side sequencing—see [same-day onboarding records](/blog/same-day-driver-onboarding-records) alongside driver tasks. > A driver upload is an input; a dated carrier review is the record auditors expect. ## What drivers submit versus what carriers must file Drivers complete applications under [§ 391.21](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-C/section-391.21), provide employment history, and submit licenses and medical documents your packet requests. They should know how to send updates when credentials change. They should not browse previous-employer drug and alcohol replies unless your policy explicitly puts them in that role. The [driver app](/features/driver-app) routes uploads to **reviewer queues**, not to dispatch chat as unofficial approval. Train drivers that “uploaded” means waiting for carrier review. Carriers request MVRs under [§ 391.23](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-C/section-391.23) and [§ 391.25](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-C/section-391.25), file road test or equivalent documentation, maintain medical evidence under [§ 391.43](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-E/section-391.43), and decide when a driver meets qualification standards for your operation. Terminal windows may collect paper, but safety staff index documents under the correct driver and date reviews. When unreadable scans arrive from the road, reject them quickly and request rescans—storing unusable PDFs fails audits and trains drivers to treat uploads as optional. Walk through a generic hire: the driver completes the application and uploads a CDL photo. The carrier still must request MVRs from each licensing state in scope, send previous-employer inquiries, obtain road test documentation if required, run Clearinghouse pre-employment queries, and file medical evidence that matches registry or CDLIS status. Each step has a **carrier owner** and a due behavior—drivers cannot substitute for inquiry letters sitting unsent. Dispatch should see “awaiting carrier review” until safety dates the file, not “ready” because the phone buzzed. ## Investigation files, Part 382 records, and hire pressure Previous-employer inquiries and replies belong in the **investigation history file** under [§ 391.53](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-F/section-391.53). Qualification reviewers who are not hiring decision makers should not casually read those replies. [Clearinghouse consent and receipts](/blog/clearinghouse-annual-query-cycle) are Part 382 records—drivers may sign consent digitally, but carriers retain receipts and control access. Same-day hiring compresses time. MVR requests must still go out within regulatory windows under § 391.23; Clearinghouse pre-employment queries must complete before safety-sensitive functions under [§ 382.701](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-382/subpart-G/section-382.701). Whether you may allow a driver to operate before every previous-employer reply arrives depends on § 391.23 conditions and counsel’s reading—do not treat dispatch approval as automatic qualification. Document who authorized road use when inquiry tasks remain open. Owner-operators and leased drivers under your USDOT number still need carrier-maintained files. Contracts should state who maintains the qualification packet you present in audits. Third-party administrators may operate MVR or Clearinghouse portals, but **your carrier** remains responsible for files presented under your USDOT number. Contracts should require deliverables you can file—receipts and inquiry responses—not only dashboard screenshots. ELP Training and ELP Testing App features record training status; they do not replace carrier qualification decisions under [§ 391.11](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-B/section-391.11). Annual MVR reviews remain carrier work even when drivers upload license renewals from the road. The driver supplies the new card image; safety requests the MVR, reads it against policy, and writes the [§ 391.25](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-C/section-391.25) note. Blurring that step—treating a photo upload as the annual review—shows up in audits as missing reviewer names. Software should make the distinction obvious in status labels drivers see in the app. ## Role confusion and fixes you can apply this week Dispatch marks drivers active when uploads arrive. HR stores I-9 folders beside MVRs without labels. Third-party apps let drivers self-report “ready” outside your system of record. Fix with one workflow diagram, a published RACI in the same portal drivers use, and stand-up metrics: drivers under review and oldest open hire packet. Audit five recent hires: who uploaded each document, who reviewed it, and review dates. Blank reviewer fields get an owner before the next hire batch. Link staff to [driver qualification file basics](/resources/guides/driver-qualification-file-basics) for definitions. When roles stay fuzzy, drivers get blamed for carrier delays—“your file is not done”—even when the missing item is an MVR the carrier never ordered. That erodes trust and encourages workarounds, like texting photos to dispatch instead of the review queue. Clarify in driver orientation that **compliance is a partnership**: drivers supply truthful applications and timely updates; carriers supply inquiries, reviews, and filing. Terminal staff who hear complaints should route them to safety with the driver name and document type, not promise clearance on the spot. ## Clarify roles before the next hire wave Clean roles make modern tools worth the cost. Drivers collect; carriers review and file; investigation data stays restricted. Implement that split in software and SOPs together—start with the [driver app](/features/driver-app) workflow, then align dispatch rules so uploads never imply automatic compliance. Review the split after every audit sample. If investigators asked for reviewer names you could not produce, the fix is carrier-side dating and indexing—not another driver reminder to photograph licenses. Roles that match Part 391 reduce friction for drivers and shrink the compliance surprises that land on safety managers’ desks. Update the RACI when you add a terminal or vendor so new hires inherit clear owners, not improvised email chains. ## Sources - [49 CFR 391.51 — General requirements for driver qualification files](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-F/section-391.51) - [49 CFR 391.21 — Application for employment](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-C/section-391.21) - [49 CFR 391.53 — Driver investigation history file](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-F/section-391.53) - [FMCSA — Driver qualification regulations (Part 391)](https://www.fmcsa.dot.gov/regulations/title49/part/391)