Some records ride with the driver, not the truck.
Most of this series has been about the carrier's record — the inspections and crashes attached to a DOT number. But there's a second kind of safety data, and it doesn't stay with the company. It rides with the driver, from one employer to the next, and a single wrong line on it can cost a good driver a job they were about to get.
That's the thing nobody explains to a new driver. When you apply somewhere, the carrier doesn't just take your word for your record. They can pull a federal screening report on you — your roadside-inspection and crash history — and decide whether to hire based on what it says. If a violation on that report belongs to someone else, or a crash on it was never yours, the carrier sees it before you ever get a chance to explain. The hiring decision can be made and gone before you know the data was wrong.
So this lesson is about the records that follow the driver — what they are, why they matter at hiring time, and exactly how to fix each one. And there's one trap built into this that sends people to the wrong office for months, so we'll mark it clearly when we get there.
PSP — the report a carrier pulls before they hire you.
The big one is PSP, the Pre-Employment Screening Program. It's a screening tool that lets a carrier — or you — buy a driver's safety record straight out of FMCSA's national database.
Here's what's in a PSP report: the most recent five years of crash data and three years of roadside-inspection data, including the serious safety violations. It lists every reportable crash you've been in. And this part matters — a PSP report shows your crash involvement only. It makes no determination about who was responsible. A crash where you were rear-ended at a red light shows up on your PSP looking exactly like a crash you caused. The report doesn't sort fault; it just lists that the crash happened and that you were in it.
A carrier can only pull your PSP for pre-employment screening, and only with your written consent — they have to ask, and you have to sign off. You, on the other hand, can buy your own PSP anytime for a small fee, and you should — especially before you go job-hunting. You want to see what a prospective employer is going to see, before they see it.
PSP doesn't hold any data of its own. It's a mirror. Every line on a PSP report was uploaded to FMCSA's national database by a state or by FMCSA, from a roadside inspection or a crash report.
— The key point about PSP
Which means there is no "fix my PSP" button, and you don't need one. If a line on your PSP is wrong, you correct it by correcting the underlying inspection or crash through DataQs — the same Request for Data Review you'd file for any roadside record. Fix the source, and the PSP line changes when the database changes, because the report is only ever showing you what the database holds.
How you actually fix a wrong PSP line.
A wrong PSP line is really an inspection problem or a crash problem wearing a different hat. The fix is the same Request for Data Review — the RDR — you'd file for any roadside record, and the evidence is the same too.
If the bad line is a violation or inspection — it's not your inspection, it's misattributed to you, or it states a fact that isn't true — that's an inspection dispute. The inspection-dispute lesson walks the whole filing, and the evidence lesson lays out the proof that wins: identity documents showing the inspection belonged to a different driver, repair records or photos for a factual error, the certified court disposition for a charge that was later thrown out.
Inspection dispute lesson →If the bad line is a crash — it's not your crash, it isn't actually a reportable crash, or it got entered twice — that's a crash-record dispute. The crash-record-errors lesson is the one to follow. The proof there is the police report and your trip records showing the crash wasn't yours, or the records showing it never met the recordable definition.
Crash-record dispute lesson →Owner-operators and the “independent contractor” question
One detail worth knowing when the dispute is about which driver an inspection belongs to: under the federal rules, "employee" includes an independent contractor. A leased owner-operator running under a carrier's authority counts as that carrier's employee for this purpose. So "I'm a contractor, not their employee" is not a reason a misattributed inspection can't be sorted out — the directing carrier and the driver of record are still the questions that get answered with identity and dispatch evidence.
The point to hold onto: there's no special driver-side DataQs process. You're filing an ordinary RDR against the underlying inspection or crash. Win that, and the PSP line clears with it.
CDLIS — the licensing record is a different office.
There's a second record that follows the driver, and it's a different animal from PSP: CDLIS, the Commercial Driver's License Information System.
CDLIS exists because of a problem from the 1980s — drivers holding licenses in several states at once and dodging suspensions by jumping between them. The Commercial Motor Vehicle Safety Act of 1986 fixed that by mandating a nationwide system where one driver equals one license and one record. Under the hood it works through a master pointer: the state where someone asks about your record gets "pointed" to the state that actually holds it. You don't see any of this — CDLIS isn't public. Only authorized state and federal licensing people can look.
Keep the two straight: PSP is safety data (inspections and crashes) and rides the DataQs path; CDLIS is licensing data and rides the state-licensing-agency path. Same driver, two different records, two different offices.
Your own record — and how to read it before someone else does.
A driver isn't stuck waiting to find out what's on these records secondhand. You can pull your own, and you should.
Your PSP you can buy yourself anytime from FMCSA's PSP site for a small fee. Do it before you apply anywhere. If something on it is wrong, now you have months to fix the source data through DataQs instead of discovering the problem the day a carrier declines you.
There's also a quieter record worth knowing about: the National Driver Register, and its Problem Driver Pointer System. These hold pointers to drivers whose licenses have been revoked or suspended, or who have serious convictions on file. You can request your own NDR file at no charge through a Privacy Act request — a notarized letter to the NDR in Washington, DC. And if a conviction or a license withdrawal needs to move between states, the states are required to transfer that information within 31 days, so a record that's lagging shouldn't lag forever.
Pull your own PSP before you go looking for a job. Read it the way a hiring carrier will, and fix anything wrong at the source while you still have time.
— The habit every driver should build
The Clearinghouse — same DataQs front door, but a different and narrower petition.
There is one driver-side record that trips people up here, and the trap is subtler than it used to seem.
It's the Drug and Alcohol Clearinghouse. The Clearinghouse is the federal database of drug- and alcohol-program violations, return-to-duty status, and the query results carriers run on drivers. It follows the driver hard — a violation in there can keep a driver out of a safety-sensitive seat entirely until the return-to-duty process is complete.
The §382.717 petition is narrow: it challenges only the accuracy of what was reported to the Clearinghouse — for example, an employer's actual-knowledge report that was based on a traffic citation that never resulted in a conviction, or a report that didn't comply with the federal reporting requirements. You cannot use it to re-litigate the underlying violation or challenge the refusal itself.
The clean way to remember it: if the wrong data is an inspection or a crash, file a standard DataQs RDR (and it'll show up on PSP). If the wrong data is a drug- or alcohol-program record, go to DataQs and choose the Clearinghouse Violation Petition category. Same front door, different and narrower petition type — filing a standard inspection RDR for a Clearinghouse problem sends it to the wrong queue just as surely as going to a different website.
If you need help standing up the Clearinghouse correctly so a Clearinghouse reporting error gets caught and directed to the right petition from the start, that's exactly what our Clearinghouse setup service is built for.
Where to go from here.
If a wrong line on your PSP is an inspection or violation, the inspection-dispute lesson is your next stop; if it's a crash, the crash-record-errors lesson is. Either way, the evidence lesson is the one to read before you file — a driver-side RDR wins or loses on the same proof as any other. If your problem is licensing, it's your state's driver-licensing agency, not DataQs. And if it's a Clearinghouse record, go to DataQs and choose the "Drug and Alcohol Clearinghouse Violation Petition" category — the same front door, but a distinct §382.717 petition, not a standard RDR.
The records that follow your drivers — PSP, CDLIS, and the Clearinghouse — only help you hire well if they're clean. Our Driver Qualification File service pulls these the right way, with written consent on record, so a wrong line gets caught before it costs you a hire.
And the DataQs hub maps the whole topic if you're starting from zero.
Bad data on your record costs real money.
PSP, CDLIS, and the Clearinghouse each have their own correction path — and walking through the wrong one costs you time. We build and maintain the driver-qualification file that pulls these the right way, with written consent on record, so a wrong line gets caught before it costs you a hire — and we'll point a Clearinghouse error to the petition process it actually needs.