FMCSA Background-Check Requirements: A Carrier Hiring Workflow

Your new driver has finished orientation, but a former employer hasn’t answered the records request. Dispatch wants to assign a brokered load. The hiring folder says “background check complete,” yet nobody can explain which records were reviewed or who approved the driver.

Build the process around separate decisions: what information you requested, what evidence you received, what your reviewer concluded, and what practical training remains. Don’t use one checkbox for all four. This guide focuses on hiring investigations under 49 CFR 391.23 and a suggested workflow for managing them.

1. Decide what your screening process actually covers

Start by giving each screening task a specific name. “Background check” is too broad for a hiring tracker. Use separate entries for licensing records, previous-employer investigations, drug-and-alcohol history review, and any additional company screening. Then name the person responsible for each entry.

For criminal screening, keep the federal claim narrow: Section 391.23 does not prescribe a universal criminal-record search. Don’t present a vendor’s criminal-screening package as the requirement established by this section. (ecfr.gov↗ (opens in a new tab))

Before ordering additional criminal screening, ask employment counsel to approve its scope and process for the jurisdictions involved. Bring counsel the proposed forms, vendor package, decision criteria, and intended use of results. Don’t ask a dispatcher to make a hiring decision from an unexplained report flag.

Keep drug-and-alcohol history work distinct, too. Under §391.23(e)(4), covered employers use the Clearinghouse for FMCSA-regulated employment history beginning January 6, 2023. Direct requests remain necessary for applicable other-DOT-mode history and unfinished follow-up testing plans. FMCSA’s guidance explains that the Clearinghouse change does not eliminate employment-verification and crash-history inquiries. (ecfr.gov↗ (opens in a new tab))

For your workflow, assign that review to someone who can distinguish those records rather than treating every former employer the same. Use the FMCSA Clearinghouse checklist as a separate planning resource. Keep this article’s tracker focused on which investigation tasks remain open.

Before recruiting starts, write a short scope memo for your reviewer. Identify the proposed equipment, work, driver role, and operating jurisdictions. Ask the reviewer to identify applicable requirements and exceptions. Avoid building the whole process around an informal label such as “hotshot driver” or “part-time help.”

2. Turn the hiring packet into a request-and-evidence tracker

Give the hiring coordinator a record-by-record work queue, not just a folder. A folder tells you where something belongs. Your queue should show what has been requested, what came back, and what still needs a decision.

Subject to applicability and exceptions, §391.23 requires three-year licensing-history inquiries and three-year DOT-employer safety-history investigations. Licensing inquiries and placement of returned MVRs in the driver qualification file have a 30-day employment-start deadline. Investigation replies or documented good-faith efforts belong in the investigation history file within that period. (ecfr.gov↗ (opens in a new tab))

Use those requirements as inputs to a reviewed procedure, not as permission to dispatch. Have your compliance lead identify every prerequisite for the proposed assignment separately. Your internal tracker should distinguish a filing deadline from the fleet’s release decision.

For each request, capture the driver identifier, record category, recipient, date sent, response location, responsible employee, and next follow-up date. Add separate fields for receipt and review. A file uploaded this morning should not automatically appear as reviewed this morning.

Start with the driver’s information and reconcile it before sending requests. Ask about unclear employer names, overlapping dates, and changes in licensing jurisdiction. Record the clarification without overwriting the original entry. That gives the reviewer both the initial information and the explanation.

Use statuses that describe the work

A practical status sequence is “not requested,” “requested,” “received,” “review needed,” and “review completed.” Add an exception status when the ordinary sequence breaks. Keep the final hiring or assignment decision in a different field so a completed document review doesn’t become an accidental dispatch approval.

Here’s an illustrative example: a driver lists two former carriers. One responds; the other request goes to an inactive address. Mark the first response received and awaiting review. Mark the second request as an exception, assign a coordinator to locate a working contact, and set a follow-up date. Don’t combine both into “employment verified.”

When using a screening vendor, ask it to demonstrate a completed sample packet. Can your coordinator distinguish an order confirmation from the actual response? Can the reviewer see the source, covered period, and unresolved exceptions? Treat those questions as purchasing criteria, not assumptions about what a package includes.

Use the broader driver qualification file checklist to plan the surrounding file. Keep this investigation tracker focused on requests, evidence, and decisions rather than duplicating every qualification document.

3. Handle missing responses and disputed information deliberately

For unanswered requests, §391.23 requires documentation of good-faith efforts. For drivers without DOT-regulated employment during the preceding three years, document that no investigation was possible. (ecfr.gov↗ (opens in a new tab))

Build a practical follow-up procedure around those situations. Save the request, delivery failure if available, subsequent contact attempts, and responses together. Give each open item a named owner. “Waiting on employer” should describe the situation, not excuse the absence of a next action.

Ask your compliance lead to approve the escalation schedule and decide how unresolved cases will be evaluated. Don’t invent a company rule that a fixed number of emails automatically proves adequate effort. Instead, preserve the actual sequence and bring the unresolved facts to the reviewer.

Use clear notes. “Request sent to former carrier’s listed records address; delivery failed; coordinator seeking an updated contact” is useful. “Background pending” leaves the next employee starting over. Keep speculation about the former employer or driver out of the record.

For covered applicants, written notice of rights to review, correction, and rebuttal must precede the hiring decision. Section 391.23(i)–(j) governs those procedures. (ecfr.gov↗ (opens in a new tab))

Give corrections their own work queue

Ask your reviewer to supply the approved notice and response procedure. Then designate an inbox owner and backup. Put an incoming records-review or correction request into that queue immediately rather than leaving it in the recruiter’s personal email.

As an internal recordkeeping practice, retain the original response alongside later correspondence and corrected versions. Label each version clearly. Have the reviewer document which information supported the decision and whether a later correction requires the decision to be reconsidered.

For an illustrative dispute, suppose a driver challenges the employment dates in a former carrier’s response. Record the disagreement accurately, route it through the approved procedure, and identify the unresolved question. Don’t silently edit the employer’s response or treat the driver’s challenge as proof that either account is correct.

Use a narrow operational update for dispatch: review pending, responsible manager, and next update time. As a suggested privacy practice, keep detailed investigative material out of load notes and group chats.

4. Keep screening evidence separate from onboarding training

Design your records so an orientation sign-off cannot close a screening task. Equally, don’t let a completed records review close practical training. Give each workstream its own owner, evidence, and completion decision.

For the administrative side, organize the record request, returned information, reviewer’s notes, and decision trail. For onboarding, document the company procedures taught, the exercise used, the trainer’s observations, and any follow-up practice. Cross-reference the driver identifier without merging the two meanings of “complete.”

Consider an illustrative wedge-trailer hire. The trainer can walk through appointment communications, a sample condition report, and the process for reporting a gate-release problem. Record those exercises as training. Leave the background-investigation statuses unchanged unless the assigned reviewer separately completes that work.

Keep training descriptions specific. “Reviewed paperwork” is weak. “Practiced reporting a missing gate release and identifying the person to contact” tells the next supervisor what was covered. For practical safety training, use procedures approved for your equipment and operation rather than improvising from this administrative guide.

Avoid making this a contest between safety staff and operations. Agree on the handoff before a truck becomes available. The hiring coordinator owns collection, the designated reviewer owns the screening decision, and the trainer owns the assigned onboarding work. Name one manager to resolve conflicting statuses.

Use the first-week driver onboarding plan to develop the training side. Keep the hiring investigation procedure separate so changes to dispatch training don’t accidentally change the records-review process.

If your onboarding packet also explains driver settlements, put that material in a separate pay-policy section. This article does not determine whether a deduction is permissible. Send deduction-policy questions for jurisdiction-specific employment review instead of trying to resolve them through a background-check form.

5. Give dispatch a clear decision, then test the process

Create a short internal handoff that identifies the driver, decision owner, decision date, approved assignment scope, and unresolved restrictions or follow-up. Have your compliance lead approve its meaning. Dispatch should not need to interpret investigative records to understand the manager’s instruction.

For this workflow, require an explicit management decision before changing the internal assignment status. Keep any remaining record follow-up visible with its owner and deadline. Do not let an upload, orientation attendance entry, or vendor order receipt trigger that decision automatically.

Before rolling out the procedure, work through one sample hiring file from start to finish. Use fictional driver information for a demonstration. Ask someone who didn’t build the tracker to explain what was requested, what returned, what remains unresolved, and who made the decision.

Then test an exception: an unanswered former-employer request, a disputed response, or a document placed in the wrong category. Check whether your backup employee can find the next action without calling the original coordinator. Revise any status that requires an oral explanation.

Set a recurring review of open hiring cases. Review the work queue rather than counting uploaded files. Ask which items are approaching their reviewed deadlines, which responses await interpretation, and which decisions need escalation. Close each meeting with an owner and next action for every unresolved case.

TruckTA’s driver documents and qualification tracking can support record organization. Keep the intended use limited to organizing the work; this draft does not claim automated background checks, Clearinghouse integration, or legal approval. (truckta.com)

Explore driver record organization by bringing one sample hiring packet and your proposed status list to a workflow review. Demonstrate how your team would distinguish requested, received, reviewed, and unresolved records. If those distinctions aren’t clear, fix them before expanding the process to the next group of hires.