How FMCSA's Pre-Employment Screening Program (PSP) Works for Carriers

Carriers running informal background checks and calling it due diligence are operating on borrowed time. FMCSA’s Pre-Employment Screening Program gives motor carriers direct access to five years of roadside inspection data and three years of crash records for any prospective driver — and the enforcement record is clear: carriers that skip or misuse PSP are exposed to both negligent entrustment liability and driver qualification file violations that survive audits.

This post breaks down exactly how the PSP system works, what the data contains, where carriers make critical errors, and how PSP fits into the broader pre-employment compliance architecture.

What the FMCSA PSP Report Contains and Why It Matters for Driver Hiring Pre-Employment

The FMCSA Pre-Employment Screening Program pulls from the Motor Carrier Management Information System (MCMIS) — the same federal database that drives SMS scores, intervention targeting, and carrier safety ratings. Each PSP report delivers two distinct data windows:

Five years of roadside inspection records, including all inspection levels, violation codes, and out-of-service orders
Three years of DOT-reportable crash records, including crash severity, fault indicators, and whether the driver was cited

This is not a motor vehicle record. An MVR from a state DMV captures license status, convictions, and suspensions. PSP captures federal enforcement activity — violations cited under 49 CFR Parts 382, 383, 390–397, and 399 — that never appear on an MVR but are directly relevant to how a driver performs under federal safety standards.

How to Read PSP Inspection Violation Codes

Every PSP report presents violations by their inspection code and regulatory citation. Common high-weight violations a carrier should flag immediately include:

391.11 — Driver qualifications (operating without a valid CDL or required endorsements)
382.301 — Pre-employment controlled substance testing not completed
395.3 — Hours of service operating rules violations
396.7 — Unsafe equipment (driver-related violations noted during inspection)
392.2 — Reckless driving or improper operation

A pattern of 395.3 violations across multiple inspections — particularly with prior employers — signals a driver who has historically operated outside HOS parameters. That pattern, documented in MCMIS, is now on your desk before you hand over the keys.

Written Driver Authorization Is Non-Negotiable

Under the Driver Privacy Protection Act (DPPA) and FMCSA program rules, carriers cannot pull a PSP report without the driver’s written consent. FMCSA provides a standardized Pre-Employment Screening Authorization Form. Carriers must:

Obtain signed consent before ordering the report
Provide the driver a clear disclosure that a PSP report will be requested
Retain the authorization in the driver qualification file

Failure to obtain authorization before ordering a PSP report is both a program violation and a potential federal privacy claim. This is not a bureaucratic formality — it has legal exposure attached to it.

Where PSP Fits in the Full Pre-Employment Stack

PSP is one layer in a multi-component pre-employment process. The complete DOT pre-employment requirements framework includes MVR checks, road testing or road test certificate verification, employment history verification, and controlled substance testing. PSP does not replace any of those — it augments them with federal enforcement history that no other single source provides.

Carriers maintaining driver qualification files under 49 CFR 391.51 should document PSP pulls as part of the file alongside the authorization form, the report itself, and any adverse action documentation if a hiring decision is affected.

PSP and the FMCSA Drug and Alcohol Clearinghouse: Parallel Obligations

Two Separate Queries, Two Separate Compliance Obligations

A mistake carriers make repeatedly is conflating PSP with Clearinghouse obligations. They are distinct programs with distinct regulatory hooks.

PSP reflects crash and inspection history from MCMIS. The FMCSA Drug and Alcohol Clearinghouse reflects drug and alcohol program violations under 49 CFR Part 382 — including positive tests, refusals, and return-to-duty status. Both are required pre-employment. Both require separate driver consent processes.

Understanding the difference between a full Clearinghouse query and a limited query matters here: pre-employment requires a full query, which demands explicit driver electronic consent through the Clearinghouse portal. A limited query does not satisfy the pre-employment requirement under 382.301(b).

A PSP report showing prior 382.301 violations — failure to complete pre-employment testing — paired with a Clearinghouse full query showing unresolved violations creates a clear picture of a high-risk hire. Both data points are accessible before the driver ever sits in your truck.

How PSP Data Intersects With Post-Hire Enforcement Risk

Inspection History Predicts Ongoing Violation Patterns

FMCSA’s safety data and statistics consistently show that drivers with prior out-of-service orders and multi-inspection violation patterns contribute disproportionately to carrier SMS percentile degradation. When a carrier hires a driver with a documented HOS or equipment violation history and that driver generates another violation post-hire, the enforcement exposure is compounded — not just for the driver, but for the carrier’s BASIC scores.

From a reasonable suspicion testing documentation standpoint, a driver’s prior inspection record showing behavioral indicators at roadside doesn’t directly trigger reasonable suspicion — but it informs supervisory awareness and protocol when those behaviors appear post-hire.

Similarly, for post-accident testing decisions, carriers with a driver’s crash history in hand pre-hire are in a stronger documentation position if a post-hire accident requires a thorough internal review.

Operational Checklist: Running PSP Correctly

Carriers that run PSP correctly treat it as a structured intelligence process, not a checkbox. Executed properly, the sequence looks like this:

Obtain signed FMCSA PSP authorization form before pulling any report
Order PSP through the FMCSA PSP portal (psp.fmcsa.dot.gov) — cost is currently $10 per report
Review inspection violations by CFR citation, flagging out-of-service orders and Part 382/395/396 patterns
Run a full Clearinghouse query simultaneously — both are required under 382.301 before a driver operates a CMV
Retain the PSP report and authorization in the DQ file alongside MVR, road test certificate, and employment verification documentation

The report is valid for the hiring decision in progress. It does not serve as a substitute for annual MVR checks or ongoing Clearinghouse limited queries required under 382.701.

Enforcement Takeaway

PSP is not optional infrastructure. It is a carrier’s most direct window into how a prospective driver has performed under federal safety enforcement — and FMCSA auditors and plaintiffs’ attorneys both know how to determine whether you pulled it and what you did with it. Carriers that integrate PSP into a documented, consent-compliant, file-retention-complete pre-employment process are in a fundamentally different legal and operational position than those treating it as a supplemental step.

The data exists. Use it before the hire, not after the incident.

Data sourced from FMCSA Pre-Employment Screening Program and FMCSA public records. Verify current enforcement thresholds at fmcsa.dot.gov.

Written on April 19, 2026