FMCSA PSP Report: How Carriers Use It

Pulling the FMCSA PSP report is the easy part. The hard part is reading it — deciding whether a page of roadside violations is a real liability or just the normal wear-and-tear of a driver who runs hard miles. Pull ten PSPs and most won’t be spotless. The skill isn’t finding a clean record; it’s knowing how to weigh a messy one. Here’s how a carrier actually reads, scores, and uses an FMCSA PSP report in a hire/no-hire call — without letting it become the whole decision.

Key takeaways

• The FMCSA PSP report (Pre-Employment Screening Program, run by the Federal Motor Carrier Safety Administration) is a federal file showing a CDL driver’s 5 years of DOT-recordable crashes and 3 years of roadside inspection history, drawn from the MCMIS database.
• Read it for pattern, severity, and recency — not a raw violation count. A single out-of-service (OOS) event is a bad day; a cluster of recent hours-of-service (HOS) violations is a habit.
• Separate red flags (repeat OOS, clustered fatigue violations, at-fault crashes) from noise (a paperwork error, a non-fault crash, an old reflector-light citation).
• FMCSA-cited data shows carriers that screen with PSP regularly saw about an 8% lower crash rate and a 17.2% lower driver OOS rate — but FMCSA and the program’s own materials are clear that a PSP must not be the sole basis for a hiring decision.
• A PSP scores a driver’s federal safety record. It says nothing about reliability, no-shows, or rehire-worthiness — the behavior layer a peer driver-review database adds alongside it.

What the FMCSA PSP report actually contains (briefly)

A PSP report is FMCSA’s pre-employment safety file on a commercial driver, pulled straight from the Motor Carrier Management Information System (MCMIS) — the federal database of crashes and roadside inspections. It has two halves: the driver’s most recent 5 years of DOT-recordable crashes and 3 years of roadside inspection history, including every cited violation and any out-of-service order.

This article is about using that file, not defining it line by line. If you need the full breakdown of every field, what’s excluded, and what it costs, start with what is a PSP report, then come back here for the read. One thing worth re-stating up front, because it drives how you score the document: a PSP lists violations cited at roadside even if the driver was never convicted and never paid a fine. That’s a lower bar than a court conviction, which is exactly why a driver can carry a clean state MVR (Motor Vehicle Record) and a busy PSP at the same time.

How to read and score a PSP report

A PSP is not pass/fail, and treating it that way will cost you good drivers. A hard-running over-the-road (OTR) driver who covers 130,000 miles a year will collect citations — that’s physics, not character. What you’re scoring is the driver’s risk profile: the shape of the record, not the size of it.

Read the document along four axes. Here’s the framework most experienced recruiters apply, whether they’ve ever written it down or not:

Work the two sections separately. On the inspection side, scan for out-of-service orders first — these are the events serious enough that a DOT officer shut the driver or the truck down on the spot. Then look at the violation mix: a run of HOS (hours-of-service, the federal limits on driving time) and logbook violations clustered together is one of the strongest signals on the page. It suggests a driver who pushes past legal limits to hit delivery windows — a genuine liability, not a clerical slip.

On the crash side, the count matters less than the story. The PSP notes injuries, fatalities, tow-aways, and number of vehicles, but it does not adjudicate fault. So a crash entry is a question, not an answer: was the driver rear-ended at a light, or did they cause it? You’ll often need to ask the driver directly and weigh their account against the record. Read the whole thing like a forensic accountant, not a star-rating shopper — you’re building a picture of risk, not hunting for a reason to disqualify.

Red flags vs. noise: what to actually worry about

The single most common scoring mistake is treating every line as equal weight. It isn’t. Some entries should move a decision; most shouldn’t move it much at all. Here’s the split.

Red flags — these should give you pause:

• Repeat out-of-service events, especially for the same defect. A pattern of OOS orders means problems that weren’t fixed the first time.
• Clustered HOS and logbook violations. Fatigue-related violations correlate with the crashes that hurt people. A run of them is the clearest “this driver cuts corners on safety” signal a PSP offers.
• A recent at-fault or serious crash — particularly one with an injury or a tow-away — paired with related violations from the same window.
• An upward trend. Violations getting more frequent or more serious over the last 12–18 months matters more than a thick file that’s been quiet lately.

Noise — context, not disqualifiers:

• A non-fault crash. Getting rear-ended is not a driving deficiency. The entry exists; the blame may not.
• Paperwork and administrative violations — a form filled out wrong, a missing document, an expired sticker. Real, but low-severity.
• A single old citation that hasn’t repeated. One reflector-light violation from three years ago tells you almost nothing.
• Volume that’s proportional to miles. A busy PSP on a high-mileage OTR driver can still be a low-rate PSP once you account for exposure.

The honest read: a driver with a couple of minor, dated, paperwork-flavored entries and no OOS history is usually a cleaner hire than the rare applicant whose PSP is blank because they’ve barely driven. Empty isn’t the same as proven.

Why a PSP can’t be the sole basis for the call

Here’s the guardrail, and it’s both a legal one and a practical one. FMCSA restricts the PSP to pre-employment screening only, and only with the driver’s written authorization — that consent isn’t optional, must be kept on file, and is subject to audit. The mandatory FMCSA disclosure-and-authorization language every account holder must use makes the purpose limitation explicit. For the step-by-step on obtaining consent and what the pull costs, see how to pull a PSP report and the cost, consent, and dispute breakdown.

FMCSA and the program’s own materials are consistent on one point: the PSP is informational and should not be the sole basis for a hire/no-hire decision. It isn’t a replacement for an interview, reference checks, a road test, or the rest of your safety-history investigation. There are two reasons that matters in practice.

First, scope. The PSP is silent on license status, employment history, drug-and-alcohol violations (those live in the FMCSA Clearinghouse), and court outcomes — a driver who fought a roadside ticket and won still shows the original violation. Decide off the PSP alone and you’re deciding off a fraction of the picture. That’s why most carriers pair it with the MVR, the Clearinghouse, and often a DAC report (Drive-A-Check employment history); the PSP vs. DAC vs. MVR comparison shows exactly which record closes which gap.

Second, the law. Because a PSP is used to make a hiring decision, the Fair Credit Reporting Act (FCRA) treats it as a consumer report. If you decline a candidate based in whole or in part on what’s in it, you owe them the adverse-action process: a pre-adverse-action notice with a copy of the report and a summary of their FCRA rights, time to respond, then a final notice. None of this is legal advice — if you’re unsure, talk to an attorney who knows transportation hiring. The takeaway is structural: the PSP is one weighted input in a decision, never the verdict on its own.

It’s worth knowing the data cuts in PSP’s favor when you use it consistently. In an FMCSA-cited study of more than 5,000 carriers, those that screened with PSP saw roughly an 8% reduction in crash rate and a 17.2% reduction in driver out-of-service rate versus non-users — an estimated 863 crashes and over 3,500 driver OOS events avoided across the study window. Those gains come from systematic screening, not from any single dramatic catch. Run it on everybody, read it the same way every time, and the average improves.

What the PSP can’t see — and how to close it

Here’s the limit of even a perfectly-read PSP. It is excellent at one thing — federal safety events — and blind to almost everything else about how a person actually works a job. It will tell you a driver picked up an HOS violation in Ohio in 2024. It will not tell you that the same driver no-showed for orientation at two carriers, ghosted a dispatcher mid-load, or abandoned a truck after a pay dispute — walked off and left the equipment hundreds of miles from the yard. None of that is a federal safety event, so none of it lands on a PSP. A clean PSP, a clean MVR, and a clean Clearinghouse can still describe the most unreliable hire you’ll make this year.

That behavioral record — reliability, no-shows, abandoned loads, whether past carriers would take the driver back — lives only in the heads of the recruiters and dispatchers who dealt with them. A peer driver-review database like cdlscan.com is built to surface exactly that: you search a driver by name and read what past carriers said about showing up, finishing loads, and being worth rehiring. Search is free; a full report runs from $2.75, against a bad hire that costs a fleet anywhere from $8,000 to $50,000. It doesn’t replace your PSP, MVR, Clearinghouse, or DAC checks — it adds the reputation read those records structurally miss. The smart play is both: score the PSP for the federal safety record, then check the peer reviews for the behavior the safety record can’t see.

Frequently asked questions

How do carriers use a PSP report in a hiring decision? As one weighted input, not a verdict. Carriers read the 5-year crash and 3-year inspection history for severity, pattern, recency, and miles-driven exposure — then combine it with the MVR, Clearinghouse, DAC, an interview, and a road test before deciding. FMCSA materials are clear the PSP should not be the sole basis for the call.

What’s a red flag on a PSP report vs. just noise? Red flags: repeat out-of-service events, clustered hours-of-service and logbook violations, and recent at-fault or serious crashes — especially if the trend is climbing. Noise: a non-fault crash, paperwork or administrative violations, and a single old citation that never repeated. Weight severity and recency, not raw count.

Is a high violation count on a PSP automatically disqualifying? No. A high-mileage OTR driver naturally accumulates more citations than a local driver, so count has to be read against exposure. A busy PSP can still be a low-rate PSP. What matters is the mix of serious vs. cosmetic violations and whether the pattern is recent and repeating.

Can I reject a driver based only on their PSP report? You shouldn’t, and FMCSA’s own guidance says the PSP isn’t meant to be the sole basis for a decision. Legally, because it’s used for hiring, the PSP is an FCRA consumer report — if you decline based in whole or part on it, you must follow the adverse-action process (pre-adverse notice with a copy and rights summary, time to respond, final notice). This isn’t legal advice; consult counsel.

Does a PSP show whether a driver was at fault in a crash? No. The PSP lists DOT-recordable crashes with details like injuries, fatalities, tow-aways, and vehicle count, but it does not assign fault. Treat each crash entry as a question to ask the driver and corroborate, not a settled conclusion.

Do roadside violations on a PSP mean the driver was convicted? No. A violation posts to the PSP the moment an officer writes it up — conviction or not, fine paid or not. That’s a lower bar than a court conviction, which is why a driver can have a clean MVR but a PSP with violations on it. Read PSP entries as cited events, not adjudicated outcomes.

Does using PSP actually lower crash rates? FMCSA-cited data from a study of more than 5,000 carriers found those that screened with PSP regularly saw about an 8% lower crash rate and a 17.2% lower driver out-of-service rate than non-users. The benefit comes from screening every applicant consistently, not from a single pull — it’s a correlation tied to process, not a guarantee on any one hire.

What does a PSP report not tell me about a driver? License status, employment history, drug-and-alcohol violations (those are in the FMCSA Clearinghouse), and court outcomes — plus everything behavioral: no-shows, ghosting, abandoned trucks, and whether past carriers would rehire. For license and conviction data, pull the MVR; for the behavior layer, check peer driver reviews alongside the PSP, never instead of it.