Screening
How to Read a PSP Report and Make the Hire Call
By Editorial Team · Updated July 9, 2026 · 12 min read · Editorial standards
On this page 7 sections
You just pulled a driver’s PSP report and the screen is full of crash entries, inspection lines, and violation codes. Now what? A single not-at-fault fender-bender can look scarier than a string of hours-of-service violations that should actually worry you far more. Reading a PSP report wrong costs you both ways: you pass on a safe driver over a cosmetic ding, or you seat a real risk because the serious stuff was buried in the noise. Here is how to read a PSP report line by line and turn it into a defensible hire or no-hire decision.
What does a PSP report actually contain?
A PSP report is a commercial driver’s federal safety history, and it has exactly two halves: a 5-year crash section and a 3-year roadside-inspection section. Both come straight from FMCSA’s Motor Carrier Management Information System (MCMIS), the central database where every DOT-recordable crash and every roadside inspection in the country gets logged. There are no employer comments, no “eligible for rehire” flag, and no reason-for-leaving. It is government data about what happened on the road, and nothing else. If you want the full primer on the record itself, our explainer on what a PSP report is covers the ground; this guide is about reading one you already have in front of you.
Two facts shape how you read every FMCSA PSP report. First, roadside violations land on the report the moment an officer writes them up, whether or not the driver was ever convicted or paid a fine. Second, crashes are listed regardless of fault. Keep both in mind and half the rookie misreads disappear.
Here’s the at-a-glance on what each half covers and how far back it looks:
| Section | Lookback window | What it shows | What it does NOT show |
|---|---|---|---|
| Crash history | Last 5 years | DOT-recordable crashes: date, location, injuries/fatalities, tow-away, vehicles involved | Who was at fault |
| Inspection history | Last 3 years | Every roadside inspection, each violation cited, severity, OOS status | License status, endorsements |
| Violations (inside inspections) | Last 3 years | HOS, logbook, equipment, moving violations at the scene | Court convictions or dismissals |
| Source | FMCSA MCMIS | Federal crash and inspection data | Employment history, drug tests, behavior at past jobs |
How do you read a PSP report section by section?
Read a PSP report top to bottom in four passes: crashes first, then inspections, then the violations inside those inspections, then out-of-service events last so the heaviest signals stay front of mind. The point of a structured read is that a psp trucking report isn’t pass/fail; a hard-running over-the-road (OTR) driver will always collect some entries, so you’re hunting for a pattern, not a single blemish. Below is how to read a PSP report the way an experienced safety manager does, one step at a time, with the trap that bites recruiters at each stage.
Read the crash history first
What you do: Start with the 5-year crash section. For each entry, note the date, location, whether anyone was injured or killed, how many vehicles were involved, and whether a truck was towed. Then ask the only question that matters here: is there a pattern? Two not-at-fault rear-end hits over five years tell you almost nothing. A cluster of backing incidents, lane-change crashes, or fatigue-flavored events tells you a lot.
Required or smart? Pulling the report at all is federally consent-gated, but reading crashes for fault is smart practice, not something FMCSA does for you. The report will never label a crash preventable or non-preventable on its own.
The gotcha: PSP lists crashes regardless of fault, so counting a not-at-fault crash against a driver is the single most common misread. FMCSA runs a Crash Preventability Determination Program that can flag qualifying crashes as “not preventable,” and a driver who took the trouble to get one reviewed shows initiative worth noting. Never treat a raw crash count as a strike sheet.
Work through the inspection history
What you do: Move to the 3-year inspection section and read it as a ratio, not a tally. Count the total inspections, then count how many came back clean versus how many drew violations. A driver with 40 inspections and 2 minor violations is a different animal from one with 5 inspections and 4 violations, even though the second driver has fewer total dings.
Required or smart? Smart. Nothing in 49 CFR forces you to compute a clean-inspection ratio, but it’s the honest way to read exposure and it’s exactly how a plaintiff’s attorney will read it later if a crash ever goes to court.
The gotcha: Clean inspections are the denominator recruiters forget. A busy PSP report on a high-mileage driver can look alarming until you notice most of those inspections were spotless. Read the whole section before you react to any one line.
Decode the violations
What you do: Inside the inspection section, read the actual violation codes. Group them: hours-of-service (HOS) and logbook violations in one bucket, equipment and vehicle-maintenance defects in another, moving violations (speeding, following too close) in a third. HOS and logbook falsification are governed by 49 CFR Part 395 and are the ones that most directly signal a driver who pushes past legal limits to hit a delivery window.
Required or smart? Smart, and heavily so. The federal rule you must honor kicks in later, at the decision stage under FCRA. Grouping violations is your own diligence.
The gotcha: A roadside violation is not a conviction. It appears on the psp report even if the driver fought the ticket and won, or the citation was dismissed. That’s why a driver can carry a clean state Motor Vehicle Record (MVR) and still show a busy PSP, and it’s a core reason the two records don’t interchange, as our PSP vs DAC vs MVR breakdown lays out.
Flag every out-of-service event
What you do: Last pass, scan specifically for out-of-service (OOS) events and mark each one. An OOS means the driver or the vehicle was pulled off the road on the spot until the problem was fixed, judged against the Commercial Vehicle Safety Alliance (CVSA) out-of-service criteria. These carry more weight than an ordinary violation because an inspector decided the situation was unsafe to continue.
Required or smart? Smart. Weighting OOS events heavier than paperwork dings is judgment, not regulation, but it’s the judgment that separates a careful hire from a lucky one.
The gotcha: Distinguish a driver OOS (for example, an HOS violation that put the person out of service) from a vehicle OOS (a brake or tire defect on equipment the driver may not have owned). A leased owner-operator dinged for a company trailer’s bad light is not the same risk as a driver shut down for driving over hours. Read which is which before you weigh it.
How do you weigh severity into green, yellow, and red?
Convert your four-pass read into a simple green / yellow / red framework, because “some violations” is not a decision and hiring managers need one. The mechanism is straightforward: severity times frequency times recency. A serious violation counts more than a cosmetic one; a repeated violation counts more than a single one; and a violation last quarter counts more than one four years ago, because recent behavior predicts future behavior better than old behavior does. Run every psp report for trucking through the same rubric so your decisions are consistent and defensible.
| Signal | 🟢 Green (proceed) | 🟡 Yellow (dig deeper) | 🔴 Red (strong caution) |
|---|---|---|---|
| Crashes | 0–1 not-at-fault over 5 yrs | 2+ crashes, fault unclear | Cluster of at-fault or fatigue-coded crashes |
| HOS / logbook | None, or one old minor | A few over 3 yrs | Repeated or recent, or logbook falsification |
| Out-of-service | None | One driver or vehicle OOS | Multiple OOS, especially driver OOS |
| Trend | Violations tapering off | Flat | Piling up in the last 12 months |
| Clean-inspection ratio | High (mostly clean) | Mixed | Low (most inspections drew violations) |
A yellow isn’t a rejection; it’s a prompt for a conversation. Ask the driver directly about a clustered stretch of HOS violations or a recent OOS, and listen to whether the answer shows accountability or excuses. A red flag rarely stands alone either. The strongest disqualifiers show up as combinations: recent, repeated, at-fault, and out-of-service all pointing the same way. That’s the profile a negligent-hiring claim is built on, which is why pairing the PSP with a broader truck driver background check matters. And remember the whole exercise assumes you pulled the report correctly in the first place, which our step-by-step on how to pull a PSP report walks through.
Do you need consent to pull and use a PSP report?
Yes, and it works on two layers you can’t skip. FMCSA contractually requires the driver’s written or electronic authorization on its exact stand-alone Disclosure and Authorization form before you pull a single record, and you must retain that signed consent for at least five years. There is no verbal-consent shortcut for a PSP the way there sometimes is for other checks.
The second layer is federal law. Because a PSP report is used to make a hiring decision, the Fair Credit Reporting Act treats it as a consumer report, which means the consent disclosure has to stand on its own and can’t be buried in your general application. More important for reading the report: if you decide not to hire someone based in whole or in part on what the PSP shows, you owe them the FCRA adverse-action process. Send a pre-adverse-action notice with a copy of the report and a summary of their rights, give them time to respond and dispute, then send a final adverse-action notice. If a driver says an entry is wrong, they don’t fix it through you; the challenge goes through FMCSA’s DataQs system, which routes it to the state that reported the crash or inspection. None of this is legal advice, and a transportation attorney should vet your exact notices.
What a PSP report structurally can’t show you
Here’s the honest limit, and it’s the one that quietly costs recruiters the most. A PSP report is built entirely from roadside events and crashes, meaning what happened when a commercial motor vehicle met a scale house or an inspector. It is genuinely excellent at that. But a perfectly clean PSP tells you nothing about how a driver actually behaved at their last three carriers. No-shows after orientation. A truck abandoned mid-load three states from the yard after a pay dispute. Quitting on dispatch. Chronic 30-day job-hopping. Trashed equipment turned back in. None of that is a federal safety event, so none of it ever touches an FMCSA PSP report, an MVR, or the Clearinghouse.
That behavioral record lives only in the memories of the recruiters and dispatchers who dealt with the driver, until a peer-sourced database surfaces it. That’s the exact gap a driver-review platform like cdlscan.com is built to close. Instead of guessing what a clean report leaves out, you can search a driver by name and read what past carriers reported about attendance, finishing loads, and rehire-worthiness, the reputation layer the safety records can’t see. Think of it as the added behavior check that sits on top of your required records, never a replacement for them. CDLScan lists more than 1 million driver reviews and runs north of 20,000 searches a week; the search itself is free, with a full report starting at $2.75.
The smart play is to run both: read the PSP for the safety record using the four passes above, then check the peer driver-review database for the on-the-job behavior the PSP is structurally blind to.
Frequently asked questions
How do I read a PSP report? Read it in four passes: crashes first (5-year window, remembering fault isn’t shown), then the 3-year inspection history as a clean-versus-violation ratio, then the individual violation codes grouped by type, and finally every out-of-service event, which carries the most weight. You’re looking for a pattern of recent, repeated, serious events, not a single old ding.
What is a red flag on a PSP report? The strongest red flags are combinations: repeated or recent hours-of-service violations, multiple out-of-service events (especially driver OOS), logbook falsification, and a cluster of at-fault or fatigue-coded crashes, particularly if they’re piling up in the last 12 months rather than tapering off.
Does a PSP report show who was at fault in a crash? No. A PSP report lists every DOT-recordable crash regardless of fault, so a driver rear-ended at a light shows the same entry as one who caused the wreck. Read crashes for pattern and check whether any were reviewed under FMCSA’s Crash Preventability Determination Program before you weigh them.
How much does a PSP report cost and do I need the driver’s consent? A PSP report costs about $10 per record through the official FMCSA portal, plus a small annual subscription. You must have the driver’s signed FMCSA Disclosure and Authorization form before pulling it, and keep that consent on file for at least five years.
Is a violation on a PSP report the same as a conviction? No. Roadside violations appear on a PSP report the moment an officer writes them up, even if the driver later beat the ticket in court or the citation was dismissed. That’s why a driver can have a clean MVR and still show violations on their PSP.
What’s the difference between a driver out-of-service and a vehicle out-of-service? A driver OOS means the person was pulled off the road (for example, an hours-of-service violation), while a vehicle OOS means the equipment failed inspection (such as a brake or tire defect). Driver OOS events point more directly at the driver’s own behavior, so weigh them more heavily.
Can I reject a driver based on their PSP report? Yes, but because the PSP is an FCRA consumer report used for a hiring decision, you must follow the adverse-action process: send a pre-adverse-action notice with a copy of the report and a summary of rights, allow time to dispute, then send a final notice. Consider talking to a transportation attorney about your exact procedure.
What does a PSP report not tell me about a driver? It won’t show license status, employment history, drug-test results, or, most importantly, how a driver behaved at past carriers, such as no-shows, abandoned trucks, or quitting on dispatch. Those behavioral signals never become roadside citations, so you need a peer driver-review database to see them.