How to Read a PSP Report: Crash and Inspection History, Decoded

A PSP report is the only pre-employment document that shows a CDL driver's federal safety footprint - the crashes and roadside inspections recorded against them in FMCSA's own database, regardless of which state they were licensed in or which carrier they were driving for. The MVR tells you what one state's DMV knows; the Pre-Employment Screening Program tells you what the federal government saw at the roadside. Most fleet managers order it as part of the pre-hire stack and then read only the summary line. This guide is the section-by-section read.

What PSP is - and where the data comes from

The Pre-Employment Screening Program was mandated by Congress in SAFETEA-LU (49 U.S.C. §31150) and is operated for FMCSA by a contractor. The record draws from the Motor Carrier Management Information System (MCMIS) - the federal database that stores crash reports and roadside inspection results uploaded by state enforcement agencies. That source matters for three reasons:

• MCMIS is federal, so the record follows the driver across state lines and across employers.
• MCMIS stores events (crashes, inspections), not adjudications - there are no convictions, court outcomes, or license actions on a PSP record. That is MVR territory.
• The PSP system loads a fresh MCMIS snapshot approximately once per month, and the current snapshot date is posted on the PSP homepage. A crash from three weeks ago may simply not be on the report yet.

A PSP record contains the driver's most recent 5 years of crash data and most recent 3 years of roadside inspection data. It contains no score of any kind - reading it is the carrier's job, which is the rest of this guide.

Is PSP required?

No. PSP is a voluntary program for both carriers and drivers - nothing in the FMCSRs requires a PSP pull before hiring, and it does not substitute for any required step in the DOT pre-employment checklist. Carriers buy it anyway because the safety math favors it: FMCSA's published program data shows companies that screen with PSP lower their crash rate by 8% and their driver out-of-service rate by 17% on average, compared to non-users.

How to get one

Carriers enroll at psp.fmcsa.dot.gov (or order through an enrolled screening provider) and may request records solely for pre-employment screening, only with the driver's written authorization - and not on a generic consent form. The program requires the FMCSA-prescribed disclosure and authorization language included in the account-holder agreement. Each record costs $10.

Drivers can pull their own record anytime for the same $10, or free of charge via a Privacy Act request to FMCSA, and can subscribe to the free PSP Monitoring service to get an email whenever their record changes - worth recommending to any driver who disputes what a previous employer's report shows.

Reading the report, section by section

Section 1: Driver identification

Name, date of birth, and license information as recorded in MCMIS at each event. Check this block first: drivers with common names occasionally find another driver's event on their record, and an identity mismatch is the fastest DataQs win there is.

Section 2: Crash activity (5 years)

Each crash entry shows the date and location of the crash, the motor carrier the driver was operating for at the time, and the federal severity markers from the §390.15(b)(1) data elements - injuries, fatalities, and whether a vehicle was towed from the scene.

The critical reading rule: a PSP crash listing is an involvement record, not a fault finding. A driver who was rear-ended at a red light appears in MCMIS exactly like the driver who caused the wreck. Two consequences follow. First, never treat raw crash count as a disqualifier without context - ask the driver for the narrative and check it against the §391.21 application's accident disclosures. Second, look for the preventability notation: following a data review, a record may be updated to reflect a determination that a crash was not preventable. A not-preventable marker materially changes what the entry means.

Section 3: Inspection activity (3 years)

Each roadside inspection entry shows the date, location, inspection level, the carrier at the time, any violations cited, and whether the driver or vehicle was placed out of service. Patterns matter more than singles:

• Repeated driver out-of-service events (hours-of-service, license, medical card) are the strongest negative signal on the report - they are the federal version of a failed spot-check.
• Clean inspections count too: a driver with twenty inspections and two violations is a known quantity in a way a driver with zero inspections is not.
• Violation entries can change after the fact - a citation reduced in court to a different charge can be updated on the record through the data-review process.

What is *not* on a PSP report

• License status, class, endorsements, points, convictions, suspensions - pull the MVR (line-by-line guide).
• Drug and alcohol program violations - run the §382.701(a) Clearinghouse query; PSP never shows test results.
• States of CDL licensure - that is the CDLIS check.
• Employment history or gaps - that is the §391.21 application and the §391.23 investigation.

The three-report comparison is covered in PSP vs MVR vs CDLIS.

Consent, FCRA, and saying no

Because a PSP record is obtained for employment purposes through a consumer-reporting pipeline, treat it with the same discipline as any screening report: written authorization before the pull, and if the report drives a no-hire decision, the full FCRA pre-adverse-action sequence - report copy, Summary of Rights, dispute window - before the final no. The mechanics are in how to handle a failed pre-employment screening.

Disputing errors: DataQs, not the DMV

PSP data is corrected through FMCSA's DataQs system - a request for data review filed against the underlying MCMIS record. State DMVs cannot fix a PSP record, and the PSP contractor does not adjudicate disputes. Successful DataQs outcomes that change PSP records include removing an event recorded against the wrong driver, marking a crash not preventable, and updating a violation that a court reduced to a different charge. Drivers should file with documentation (court disposition, police report) and watch for the next monthly snapshot to confirm the change landed.

Frequently asked questions

How far back does a PSP report go?

Five years for crash data and three years for roadside inspection data, measured from the most recent monthly MCMIS snapshot loaded into the PSP system.

Does a PSP report show drug or alcohol test results?

No. Drug and alcohol program violations live in the FMCSA Clearinghouse and are reached only through a §382.701 query with the driver's consent. PSP shows crashes and inspections only.

Is a PSP report required to hire a CDL driver?

No. PSP is voluntary for carriers and drivers alike. It is widely used because it is the only source of federal crash and inspection history, but no FMCSA regulation requires it and it does not replace the MVR, Clearinghouse query, or any other mandatory step.

How much does a PSP report cost?

$10 per record through the federal PSP service, for carriers and drivers alike. Drivers can alternatively obtain their own information free of charge through a Privacy Act request to FMCSA, which is slower.

How do I dispute something on a PSP record?

File a request for data review through FMCSA's DataQs system at dataqs.fmcsa.dot.gov with supporting documentation. If the review succeeds, the underlying MCMIS record is corrected and the change appears on PSP after a subsequent monthly snapshot.

Where PSP fits in the order flow

FastDriverScreening includes the PSP report in the $80 DOT Hire-Ready package (MVR + CDLIS + PSP) and the $100 DOT Pre-Employment package (adds the §382.701(a) Clearinghouse query), with the FMCSA-required driver disclosure and authorization handled in the same consent flow as the MVR pull - one signature collection, same-day digital delivery, and the report PDF filed ready for the DQ file.