A PSP report is FMCSA’s pre-employment screening record — it shows a driver’s recent crash and roadside-inspection history pulled straight from federal data, and it’s one of the most useful (and most underused) tools a small carrier has when deciding who to hire. For a one-to-ten-truck operation where every hire matters, a few dollars and a signed consent form can surface a driver’s real on-the-road track record before you ever put them on your authority. This guide explains what a PSP report is, how FMCSA PSP data differs from an MVR and the Clearinghouse, how to pull one, and where it fits in a clean hiring process.
General information, not legal advice — always verify the specifics with FMCSA. Program parameters, fees, and timing change, and your exact obligations depend on your operation.
What a PSP report is
PSP stands for the Pre-Employment Screening Program, an FMCSA service that lets carriers and drivers see an individual commercial driver’s federal safety history. The data comes from the Motor Carrier Management Information System (MCMIS) — the same database that feeds FMCSA’s safety and enforcement programs. When a roadside inspection happens or a crash gets reported, it lands in MCMIS, and the PSP report is the window into the portion of that record tied to a specific driver.
A PSP report generally includes two things:
- Up to about 5 years of crash data — crashes that were reported to FMCSA and associated with the driver.
- Up to about 3 years of roadside inspection history — inspections the driver was part of, including any violations cited during those inspections.
That’s the core value: instead of relying on what an applicant tells you, you see how they’ve actually performed at the roadside. A driver with a clean three years of inspections reads very differently from one with a pattern of hours-of-service or vehicle-condition violations. Importantly, the PSP report is a history, not a score — it doesn’t grade the driver, and a violation on a report doesn’t automatically disqualify anyone. It’s information you weigh, in context, as part of your hiring decision.
PSP vs. MVR vs. the Clearinghouse
This is where carriers get tangled up, because all three are federal-ish hiring checks that sound interchangeable. They aren’t. Each pulls from a different system and shows a different slice of the driver’s record — and you generally need all three, because they’re complementary, not substitutes.
| Check | What it shows | Source | Role in hiring |
|---|---|---|---|
| PSP | Up to ~5 yrs crash + ~3 yrs roadside inspection/violation history | FMCSA MCMIS (federal) | Voluntary screening tool — see real on-road performance |
| MVR | License status, class, endorsements, and traffic convictions | The driver’s state licensing agency | Required in the DQF (391.23) and annually (391.25) |
| Clearinghouse | DOT drug & alcohol program violations | FMCSA Drug & Alcohol Clearinghouse | Required pre-employment full query + annual query |
The distinction in one line: the PSP is FMCSA’s federal record of crashes and roadside inspections; the MVR is the state’s record of license status and convictions; the Clearinghouse holds drug and alcohol violations. A PSP doesn’t tell you whether a license is currently valid — that’s the MVR. The MVR doesn’t show roadside inspection violations — that’s the PSP. And neither one shows a failed drug test — that’s the Clearinghouse. Pull only one and you’ve got a partial picture of the person you’re about to make legally responsible for an 80,000-pound vehicle.
That’s also why the PSP vs MVR question doesn’t really have a “winner.” They answer different questions. The MVR is the one the regulation requires in the driver qualification file; the PSP is the optional layer that adds the federal inspection-and-crash view the MVR doesn’t carry.
How to pull a PSP report (and consent)
Carriers purchase PSP reports through FMCSA’s official PSP system. Two rules matter most:
- You need the driver’s written consent. A carrier can’t pull a PSP on an applicant without their signed authorization. The driver has to agree, in writing, to let you access their record. That consent isn’t just a formality — it’s a requirement of the program and something you should keep on file alongside the report itself.
- There’s a small fee per report. FMCSA charges carriers a small per-report fee to pull a PSP. The exact amount changes over time, so confirm the current pricing on the official PSP website before you budget — don’t plan around a number you read in a blog post.
Drivers have access too. A driver can request their own PSP record for a small fee, review exactly what carriers will see, and — if something looks wrong — dispute it. Because the data flows from MCMIS, corrections go through FMCSA’s DataQs process, not the carrier. It’s worth telling applicants this: a driver who knows they can see and challenge their own record tends to trust the process more, and it heads off disputes about information you don’t control.
A practical note for small carriers: build the PSP consent into your application packet. If the authorization is signed at the same time as everything else, pulling the report becomes a routine step instead of a back-and-forth with the candidate.
Is a PSP report required?
No — pulling a PSP is not mandatory. This is the single most common misconception, so it’s worth being precise: FMCSA does not require carriers to run a PSP on applicants. It’s a voluntary tool the agency makes available, not a regulation you can be cited for skipping.
That said, “not required” is very different from “not worth doing.” A PSP is a strong best practice, and it directly supports the part of hiring that is required: the Safety Performance History investigation under 49 CFR 391.23, where you investigate a driver’s prior DOT-regulated employment and safety background. The PSP gives you a federal, source-of-record view of crashes and inspections that complements the prior-employer inquiries and the MVR. It doesn’t replace any required DQF document — it strengthens the picture you’re building with the documents you already have to collect.
So the honest framing is: you won’t fail an audit for not pulling a PSP, but a safety-minded carrier pulls one anyway, because the downside of hiring a high-risk driver dwarfs the cost of a report. Don’t overstate it as mandatory; do treat it as cheap insurance.
How a PSP fits hiring at a small carrier
Here’s the part that matters most for the operations Fleetive serves. When you run a big fleet, one questionable hire is a rounding error. When you hire a handful of drivers a year, every single one shapes your safety profile, your insurance, and your exposure. A PSP plus a clean DQF process is how you avoid putting a high-risk driver on your authority — and how you document that you did your due diligence if anyone ever asks.
The mechanics are simple, but they fall apart when they live in a folder of loose paper and a shared email inbox. You collect the consent, you pull the PSP, you review it, and then it has to live somewhere — organized, retrievable, attached to the right driver — alongside the rest of the qualification file. Lose the consent form, or store the PSP result where no one can find it, and the value of having pulled it evaporates the day you need to prove your process.
That’s the bridge to software. Fleetive is built so that the screening you do during hiring doesn’t scatter. During hiring and onboarding, drivers complete their application and sign authorizations from their phone, so the consent is captured and stored, not chased. The PSP result, the MVR, the Clearinghouse query, and every other DQF document land in structured, per-driver driver management records — one place per driver, so when you need to show a complete file, it’s already assembled. Pair that with the DQF checklist so you know exactly which documents belong in the file, and use our free DQF checklist generator to build one for your operation. For the wider compliance picture a new carrier has to manage, start with the DOT compliance guide.
The PSP is a small step. The discipline of keeping it — consent, result, and the rest of the file, organized per driver — is what turns a good hiring decision into a defensible one.
Frequently asked questions
What is a PSP report? A PSP (Pre-Employment Screening Program) report is an FMCSA record that shows a commercial driver’s recent crash and roadside-inspection history, pulled straight from the federal Motor Carrier Management Information System (MCMIS). Carriers use it during hiring to see how a driver has actually performed on the road.
Is a PSP report required? No. Pulling a PSP is not mandated by FMCSA — it’s voluntary. But it’s a strong best practice and a useful input to the Safety Performance History investigation you do build into the driver qualification file. Many safety-minded carriers pull one on every applicant.
What’s the difference between a PSP and an MVR? A PSP is FMCSA’s federal record of crashes and roadside inspections. An MVR (Motor Vehicle Record) is the state’s record of the driver’s license status, endorsements, and traffic convictions. They show different things, so most carriers pull both — a PSP doesn’t replace the MVR the DQF requires.
How far back does a PSP report go? A PSP report includes up to about 5 years of crash data and up to about 3 years of roadside inspection and violation history from MCMIS. Verify the current windows with FMCSA, as the program’s parameters can change.
How much does a PSP report cost? FMCSA charges a small per-report fee for carriers, and drivers can request their own record for a small fee as well. Exact amounts change, so check the current pricing on the official PSP website before you budget.
Can a driver see their own PSP report? Yes. A driver can request their own PSP record directly for a small fee, review what carriers will see, and dispute information they believe is inaccurate through the FMCSA DataQs process.
Screen smarter, then keep the file straight
A PSP report is one of the cheapest, highest-signal tools a small carrier has — a few dollars and a signed consent buys you a federal view of how a driver has actually performed at the roadside. It’s not required, but skipping it means hiring partly blind. Pull it, weigh it in context, and then make sure the consent and the result don’t disappear into a drawer.
That last part is where Fleetive comes in: capture the consent during onboarding, file the PSP and every other DQF document per driver, and keep the whole qualification file organized and audit-ready without a compliance department.
Start free at app.fleetiveapp.com and turn careful hiring into a system that keeps the proof, not just the paperwork.
Note: This article is for general informational purposes and reflects regulations as of its publish date. It is not legal advice. Always confirm current requirements with the FMCSA and the eCFR, or your compliance counsel.
We help carriers turn DOT compliance from a scramble into a system. See how Fleetive works →
