Who this is for: carrier
Using PSP in the Driver Hiring Process
PSP report data must be used carefully within the broader driver qualification framework. This page covers how to integrate PSP into pre-hire screening, what to look for in the results, and how PSP fits with other Part 391 requirements.
Checklist
Checkboxes reset on page reload. This is a reference tool only — not a saved record.
PSP as Part of Pre-Employment Screening
Under 49 CFR Part 391, carriers must verify several driver qualifications before allowing a driver to operate in interstate commerce. The required pre-employment steps include obtaining an application, checking MVR, verifying prior employment, and reviewing road test results. PSP is a voluntary addition to this framework — but one that adds federal safety data not available from any other pre-employment source.
The Required Consent Step
Before running PSP, the driver must sign a written authorization specifically for the PSP inquiry — a general background check release bundled into the employment application does not satisfy this requirement. The PSP consent is separate from the Clearinghouse consent; both must be obtained independently for the respective queries. The authorization must identify PSP specifically and must be signed before the inquiry is submitted. Retain the signed form with the PSP report in the DQ file. Carriers who run PSP without documented written consent violate the PSP User Agreement. If the driver refuses to sign the PSP consent, the carrier cannot run the report and must decide how to handle the refusal under its own hiring policy.
What to Look for in PSP Results
When reviewing a PSP report, consider: - **Pattern of crashes:** Multiple at-fault crashes within a short window are a more significant concern than a single incident years ago - **Out-of-service violations:** Repeated OOS orders suggest the driver routinely operated with serious mechanical or hours-of-service violations - **Violation severity:** Some inspection violations carry higher CSA severity weights than others - **Recency:** Recent events (last 12–24 months) are generally more relevant than older ones near the edge of the look-back window There are no federal bright-line rules on what PSP results must disqualify a driver — carriers set their own standards in their safety policies.
Documentation and Retention
Retain the PSP report and the driver's signed consent form in the DQ file for the duration of employment and at least 3 years after separation. Keep both documents together — a PSP report without the consent form raises questions about whether proper authorization was obtained, and a consent form without the report leaves no evidence the review actually happened. In accident litigation, the DQ file is a primary exhibit. A carrier that ran PSP and retained the results is in a stronger evidentiary position than one that ran it but can't produce the documentation, and both are in a better position than a carrier that didn't run it at all when the driver's federal safety history was directly relevant.
Adverse Action Requirements
If PSP data is used to make an adverse employment decision (denying hire or terminating employment), be aware that the Fair Credit Reporting Act (FCRA) may apply if PSP data was obtained through a Consumer Reporting Agency (CRA). When carriers access PSP directly through FMCSA's portal rather than through a CRA, standard FMCSA PSP program rules apply rather than FCRA adverse action requirements — but carriers should consult legal counsel on their specific situation.
Applying PSP results consistently
Carriers should have a written policy for how PSP results are evaluated — what patterns or specific findings will result in denial, what is reviewed on a case-by-case basis, and how results are documented. Applying PSP inconsistently across candidates with similar records creates legal exposure. Document the review and the decision for every PSP report obtained. If two candidates have similar PSP histories and one is hired and one is not, the records should reflect what drove the different outcomes.
Building PSP evaluation into a written hiring policy
A written PSP policy protects the carrier on two fronts. First, it ensures consistency — documented standards that apply the same way to every candidate prevent the appearance of selective enforcement. Second, it demonstrates deliberate safety management. A one-page policy defining trigger criteria (e.g., two at-fault crashes in three years, any OOS order in the past 12 months) and requiring documentation of every PSP-based decision is sufficient. More important than the specific thresholds is applying them uniformly and keeping a record that the evaluation happened.
Frequently Asked Questions
Is there a PSP score or threshold that automatically disqualifies a driver?
No. FMCSA does not publish disqualification thresholds for PSP data — that is a carrier policy decision. Carriers that use PSP should have a written policy stating what findings trigger denial, what triggers case-by-case review, and how decisions are documented. The policy protects the carrier from discrimination claims by ensuring consistent application across all candidates.
What if PSP shows a crash the driver didn't mention on the application?
A PSP crash that wasn't disclosed on the application is a material discrepancy. Document the finding and discuss it with the candidate. Some carriers treat any incomplete disclosure as an independent disqualifying factor, separate from the safety history itself. If you proceed with the hire, document your reasoning. If you don't, document that too.
Should PSP be run before or after extending a conditional offer?
Both approaches are used. Some carriers run PSP as part of initial screening before extending any offer. Others run it only after a conditional offer is in place to control the per-inquiry cost. Neither approach is mandated. What matters is that the report is reviewed and documented before the driver's first dispatch.
If a driver was involved in a crash but wasn't cited, does it still appear on PSP?
Yes. PSP records crashes based on enforcement-level documentation, not on whether a citation was issued. The report indicates whether the driver received a citation, which provides context — but an uncited crash still appears in the data. This is one area where PSP shows information that an MVR would not.