Understanding Your Driver PSP Report

What Is the PSP Report?

The Pre-Employment Screening Program (PSP) is an FMCSA system that allows motor carriers and individual drivers to access a driver's safety performance history from the federal Motor Carrier Management Information System (MCMIS). The PSP report includes crash and inspection records from the most recent five years of crash data and three years of roadside inspection data. It is one of the primary tools carriers use during the hiring process to evaluate a driver's safety track record.

What Information Is on the Report?

A PSP report contains two main sections:

Crash Records (5 Years)

• Date, location, and type of each reportable crash
• Number of fatalities and injuries
• Whether hazardous materials were released
• Whether the crash was designated as DOT-recordable

Important: A crash appearing on your PSP report does not necessarily mean you were at fault. The FMCSA records all DOT-reportable crashes involving CMVs regardless of fault determination.

Inspection Records (3 Years)

• Date, location, and level of each roadside inspection
• Violations discovered, including violation codes and descriptions
• Whether any out-of-service (OOS) orders were issued
• The inspection result -- clean or with findings

Each violation is listed with its specific regulatory citation, making it possible to identify patterns such as repeated HOS issues or brake-related defects.

How Carriers Use PSP Reports

Most large carriers pull PSP reports as part of their pre-employment background check. A report with multiple OOS violations or preventable-crash indicators may lead to a conditional offer, higher insurance rates applied to the driver, or in some cases a declined application. Carriers weigh PSP data alongside your MVR (Motor Vehicle Record), DAC report, drug-and-alcohol testing history, and interview performance.

Understanding how your report looks to a hiring manager gives you a significant advantage during the application process. Drivers who can explain their inspection history and demonstrate corrective action present a stronger case.

How to Access Your Own Report

Drivers can request their own PSP report through the FMCSA's PSP website. The process requires:

1. Creating an account on the PSP portal
2. Verifying your identity with your CDL number and personal information
3. Paying a small fee per report request

Review your report before applying to new carriers so you are prepared to discuss any items that appear.

Correcting Errors on Your PSP

If you find inaccurate information on your PSP report, you can submit a DataQs challenge through the FMCSA's DataQs system. Common reasons for challenges include:

• Crashes attributed to the wrong driver
• Inspection violations that were corrected on-site but still show as cited
• Duplicate records from the same incident
• Incorrect vehicle or driver identification

The DataQs process involves submitting your challenge online with supporting documentation. The state agency that entered the original record reviews the request and either modifies or upholds the data. Processing times vary, so submit challenges well before any planned job search.

PSP vs. DAC Report

Drivers often confuse the PSP with the DAC (Drive-A-Check) report. The key difference: PSP data comes from federal FMCSA records (inspections and crashes), while the DAC report is compiled by a private company and includes information reported by previous employers, such as reason for separation, rehire eligibility, and contract fulfillment. Both are important to monitor, but they serve different purposes and require different correction processes.

Building a Stronger Record

The best strategy for a clean PSP report is consistent, proactive safety performance:

• Perform a thorough pre-trip inspection daily to catch vehicle defects before an inspector does.
• Maintain accurate HOS records to avoid logbook violations.
• Drive defensively and document any incidents thoroughly.
• Review your report annually, even when you are not job hunting, to catch and correct errors early.