By Justin Seyl, Certified Director of Safety, CDL Manager, with 25+ years in CDL compliance.
Justin has personally overseen more than 650,000 citations and directed more than 10,000 Safety Fitness Determination upgrades.
Two reports can describe the same driver’s history and still answer different questions. A state motor vehicle record, often called an MVR or driving abstract, is the starting point for questions about licensing history and status. A Pre-Employment Screening Program (PSP) report shows a different part of your commercial-driving history. Choosing the right record helps you avoid sending the wrong document when a carrier, agency or adviser asks what happened.
Start with the question you need answered. Are you checking a license action, reviewing an inspection entry, or preparing documents after a court decision? Write that question down before ordering reports. It will guide what you request, what you compare and where an apparent error belongs.
Start with the licensing state for license questions
States administer CDL programs within federal minimum standards. Use your licensing agency’s current record instructions rather than assuming that another state’s record names, fees or correction process apply to you.
New York illustrates why the record type matters. Its DMV offers Standard, Lifetime and CDL abstracts, and directs drivers who suspect an abstract error to its call center. Those are New York instructions, not a nationwide ordering procedure.
When you receive a record, check the identifying details and the date it represents. Save the original download with its source and retrieval date. If the question concerns your present authority to drive, confirm it with the responsible licensing agency and your carrier’s safety team. An old copy in a personal folder is not a current clearance decision.
Use PSP for crash and inspection history
FMCSA’s DataQs Help Center says a commercial driver’s PSP report covers five years of FMCSA-reportable crash history and three years of inspection records, based on the latest monthly update. (FAQ last updated September 11, 2023.)
That scope makes PSP useful when you want to understand which crash or inspection entries a report contains. It does not make PSP interchangeable with a state abstract. Keep the reports separately labeled and read each according to its purpose. Do not combine the entries into a homemade point total or assume that an item absent from one report must be absent from every other system.
A useful personal review is straightforward: identify the event, find the original document and write down the exact discrepancy. “This inspection lists a vehicle I did not operate” is a question that can be investigated. “My report looks bad” does not identify what needs to be checked.
Compare events by identifiers and dates
Create a simple event list with the jurisdiction, event date, report or case number, document source and unresolved question. Keep a citation, inspection report and court disposition as separate documents even when they relate to the same stop. Naming each file clearly reduces the chance that a reviewer will mistake one document for another.
For example, imagine that a driver sees an inspection entry after resolving a traffic case. The first task is to match the case paperwork to the inspection, not to assume that every entry should have disappeared. Compare the dates and identifying numbers, preserve the final disposition, and ask which system and record the outcome affects. This is a hypothetical review method, not a promise about the result of a particular case.
Record timing also matters. FMCSA’s DataQs update FAQ (updated July 3, 2025) says SMS and PSP data are updated monthly (a data snapshot is taken on the third or last Friday of each month, and processing takes about 10 days before results are posted). A later decision and an earlier report can therefore reflect different points in time. Save both dates before concluding that an update failed.
Send the question to the right place
For a suspected state-record error, use the issuing agency’s process. For federal or state safety data that may be incomplete or incorrect, DataQs provides a request-for-review route. Under FMCSA’s revised MCSAP grant requirements and current DataQs instructions, states have been required since September 18, 2026 to use a staged review (Initial Review, Reconsideration, Final Review) for Requests for Data Review, so older descriptions of the process may be out of date. A review request should identify the disputed entry and the evidence supporting a correction. The responsible agency determines the outcome.
Before submitting anything, make a short evidence index. List what each document establishes, note any missing item and keep an untouched copy of the originals. Share personal records only through an appropriate channel with the people who need them. Avoid posting a license number, birth date or complete report in a public comment or social-media message.
If an agency asks for more information, respond to the specific question and retain the correspondence. A submission receipt shows that a request was made; it does not establish that your record or licensing status has changed.
Keep the review useful after the first answer
Save the response, the date and any follow-up instruction. When an update is expected, obtain the appropriate current record and compare the specific entry again. Ask for clarification if the result does not answer the original question. Do not treat one corrected report as proof that every related system has updated.
Bring your current records, original incident documents and a short list of questions to a CDL Consultants case review. That preparation helps focus the conversation on the record concern and the next appropriate step.
Request a review.
This article provides general educational information. It does not determine whether an individual driver may operate a vehicle or promise that a record will be changed.