Pre-employment inquiries and investigation files

Hiring a driver feels like a sprint: applications, road tests, dispatch asking for plates. Federal qualification rules still expect a parallel investigation track—previous employers contacted, motor vehicle records requested, and sensitive replies stored where only hiring decision-makers can read them. 49 CFR 391.23 sets inquiry timing; replies from previous employers belong in the driver investigation history file under § 391.53, not in the open qualification packet on the counter.

When those two files blur, auditors see drug and alcohol history mixed with dispatch paperwork. When inquiries go out late, the motor carrier cannot show it pursued records within regulatory windows. Getting both right is less about volume and more about dated requests, secure storage, and visible open tasks while replies are pending.

Key takeaways

• Send required pre-employment inquiries within 30 days of hire and document send dates on the workflow.
• File previous-employer safety performance replies in the investigation history file, not the open qualification folder.
• Request motor vehicle records from applicable states within the same hire window under § 391.23(a).
• Run Clearinghouse pre-employment full queries with consent before safety-sensitive work under § 382.701.

What § 391.23 requires when employment starts

Motor carriers must investigate employment history and driving records before relying on a new driver. § 391.23(d) requires contacting DOT-regulated employers from the past three years for safety performance history, including accidents and controlled substances and alcohol violations former employers may share under the rule’s limits. Motor vehicle record requests must go to each state that issued a license or permit during the past three years, within 30 days of the driver’s start date.

Track each jurisdiction separately when drivers moved between states mid-career. Standardize inquiry letters so terminal staff cannot omit required history windows or DOT employer contacts—include send method, tracking number when mailed, and the staff member who placed the call. Our driver qualification file basics guide lists how qualification documents differ from investigation records on the driver qualification file itself. The 30-day clock in § 391.23 starts with employment; same-day dispatch pressure is not a reason to delay sending employer letters until someone remembers Friday afternoon.

A sent inquiry log without a filed reply still shows you started; silence on both send and receive tells a different story.

Investigation history file access under § 391.53

Previous-employer responses often include sensitive details. § 391.53 limits access to people who decide whether to hire or retain a driver. Qualification reviewers who need license class or medical status should not browse replies casually. Use workflow statuses on the qualification side to show outstanding inquiries—sent date, follow-up date, reply received—while storing the actual reply in the secure file.

That pattern keeps dispatch informed about open tasks without exposing restricted content. When previous employers do not respond, document good-faith efforts on the investigation file; the qualification workflow should show escalating follow-ups rather than a single attempt lost in voicemail. § 391.53 exists because safety performance history and drug or alcohol details are not dispatch bulletin material—they are hiring decision material with restricted access.

MVR requests in the same 30-day hire window

Initial MVR pulls share the hire window and multi-state logic described in MVR pull schedules and expiration tracking. File responses with request dates and source states. Do not mark hire tasks complete when only one state replied if others remain outstanding. Annual reviews come later under § 391.25; hire investigations are the foundation those anniversaries build on.

Drivers who return after a break may look like easy hires, but inquiry obligations restart with the new employment relationship under your counsel’s reading of § 391.23. Treat rehires with the same send-date logging as external hires, and note on the file why prior responses were or were not reused. Initial MVR requests belong in the same hire window—marking the qualification side complete when one state responds while another jurisdiction remains outstanding is the multi-state mistake hire samples surface first.

Clearinghouse pre-employment queries before safety-sensitive work

Before a driver performs safety-sensitive functions, carriers must conduct a full query of the Drug and Alcohol Clearinghouse with the driver’s consent, per § 382.701. Retain consent and query results with Part 382 records while qualification workflows track whether the step is complete. Do not treat a limited query or annual cycle as a substitute for pre-employment full queries on new hires.

Drivers sometimes sign application packets before they authorize Clearinghouse queries. Sequence consent so Part 382 records show a clear timestamp before safety-sensitive assignment, and tie that timestamp to your hire checklist. Align timing with same-day driver onboarding records when dispatch pressure is high—inquiries and queries can run in parallel once consent exists; what matters is dated proof both tracks started promptly. A pre-employment full query under § 382.701 is not interchangeable with the annual limited query cycle for an existing employee.

Operating before every employer reply and proving send dates

§ 391.23 includes conditions under which a driver may begin operating before every previous-employer response is in hand. Those conditions are legal text, not dispatch defaults. Work with counsel on how your policy interprets the rule, and document sends, follow-ups, and any decision to assign loads while replies remain pending.

Investigators sampling hire files look for proof inquiries went out on time and replies landed in the correct secure location. Export bundles described in auditor requests for driver qualification files should reference investigation files separately when customers are authorized to see them—provide qualification exports first and offer investigation access only under confidentiality terms counsel approves. § 391.23 also addresses when driving may begin before every employer reply is in hand; that analysis belongs in policy and counsel guidance, with sends and follow-ups documented—not in dispatch assuming replies are optional. A qualification export that shows “inquiry complete” without a send date on the investigation side is worse than showing pending— it suggests the carrier cannot prove the rule’s clock started.

What to do this week

Pick two recent hires and trace each inquiry from send to filing location. Confirm previous-employer replies sit in the investigation history file with restricted access. Storing employer replies in shared qualification folders, missing send dates on outgoing inquiries, and confusing Clearinghouse pre-employment queries with annual limited queries are the mistakes that show up in hire samples first.

Test inquiry templates with a terminal admin who did not write them—if they cannot send a complete packet without calling safety, simplify the template. Rebuild hire checklists from the driver qualification file basics guide so sends, replies, and queries each carry dates investigators can follow. Storing employer replies in open qualification folders, omitting send dates on outgoing letters, and treating annual Clearinghouse limited queries as hire clearance are the investigation mistakes that turn a fast onboarding sprint into a hire sample failure.

Sources

• 49 CFR 391.23 — Investigation and inquiries
• 49 CFR 391.53 — Driver investigation history file
• 49 CFR 382.701 — Database queries
• FMCSA — Driver qualification regulations overview