A roadside inspection follows you. The moment an officer writes it up, that inspection — and every violation on it — flows into FMCSA's data systems, lands on your public Safety Measurement System profile, and feeds the matching CSA BASIC. A wrong line or a violation that shouldn't be yours doesn't just sit there quietly. It inflates your score, it changes the Inspection Selection System read that tells the next officer how hard to look at you, and it can show up when an insurer or a broker pulls your record. The good news: if the data is wrong, you can challenge it. This lesson is the how-to.
Two different buttons: RDR vs IRR.
Before anything else, get one distinction straight, because it trips up almost everyone. DataQs has two separate actions, and people reach for the wrong one all the time.
The first is the Request for Data Review, or RDR. That's the challenge — the formal request asking FMCSA and the issuing state to review data you believe is incomplete or incorrect, and fix it. That's what this lesson is about.
The second is the Inspection Report Request, or IRR. That one simply gets you a copy of an inspection report you've misplaced. It does not change anything; it just hands you the paperwork. If all you need is the report itself, you file an IRR. If you believe the report is wrong and you want it corrected, you file an RDR. Same portal, two different jobs.
Request for Data Review
Challenge the data. Ask FMCSA and the state to review a record you believe is incorrect or incomplete — and correct it.
Inspection Report Request
Get a copy. Obtain the paperwork for an inspection report you've misplaced. Does not change anything on your record.
And one expectation to set now: DataQs corrects the data based on evidence. It is not an appeals court for the underlying ticket. You're not re-trying the citation here — you're proving the record is factually wrong, or that a court already decided it in your favor.
The four strong grounds.
There are four situations where a Request for Data Review has real teeth. If your dispute fits one of these, it's usually worth filing.
Wrong driver
The inspection lists a driver's name or license number that isn't who was actually behind the wheel — or the violation got attached to the wrong driver entirely.
Wrong carrier
Your USDOT number is on an inspection that belongs to another carrier — a common headache after a lease change, or when two carriers share equipment. The rule lets you challenge an inspection where your DOT number is listed incorrectly.
Factual or clerical error
The violation didn't exist, was recorded in error, was listed multiple times by mistake, or the inspection has the wrong vehicle, wrong level, or wrong location.
Adjudicated citation
A ticket that went through a court or administrative tribunal and came back in your favor. A court disposition is hard evidence — but the outcome matters in a specific way most people don't expect.
The adjudication outcome matrix
The fourth ground is one of the strongest plays you have, but the outcome matters in a specific way most people don't expect. If you were found not guilty, or the citation was dismissed without a fine or court costs, the violation comes out of both your SMS calculation and your PSP report. If the citation was dismissed but you paid a fine or punitive court costs, FMCSA treats that as a conviction, and the violation stays. If you were convicted of a lesser charge, the violation isn't removed, but it gets re-coded to show the reduced result and its severity weight drops to the lowest level. And if you were convicted of the original charge, nothing changes.
“I beat the ticket” only helps if you beat it cleanly — paying a fine to make it go away usually does not move the record.
— The adjudication rule that trips people up
So "I beat the ticket" only helps if you beat it cleanly — paying a fine to make it go away usually does not move the record.
Is it worth filing? The gut check.
A quick gut check before you file: was the record actually wrong, or were you correctly cited and you just don't like it? If you can point to a specific factual error or a court paper that contradicts the record, file. If you're hoping to argue your way out of a violation that genuinely happened, that's not what DataQs is for.
And don't sit on it. States are required to accept and review an inspection-related challenge for three years from the date of the inspection, and a crash challenge for five years from the date of the crash. Outside those windows a state can still look, but it no longer has to — so a wrong line is easiest to fix while it's fresh.
Filing the RDR, step by step.
Here's the path through the portal, start to finish.
Register or log in
At the DataQs site. New users pick a role — motor carrier, driver, or representative — and set up access; logging in now runs through multifactor authentication using Login.gov or FMCSA Portal credentials.
Start a new request and find the inspection
Search for the specific inspection record by its report number or details, and select it. This anchors your challenge to the exact event.
Choose the data element
Point to what's wrong — a specific violation, the carrier or driver identity, a duplicate, or another field on the report. Be precise; you're telling the reviewer exactly where to look.
State the basis
Explain plainly which of the four grounds applies and why the record is incorrect. Clear, specific, documentation-backed reasoning gets a better outcome than a vague complaint.
Attach your evidence
Upload the supporting documents that prove your case — a court disposition for an adjudicated citation, a lease agreement for a misattribution, the inspection report itself, photos, or logs. Different grounds need different proof; our evidence lesson is the full guide to what wins for each.
Submit and track it
You'll get a request ID. Use the portal's monitoring tool to watch the status as the state works it.
For a deeper look at exactly what evidence wins for each ground, see the evidence that wins a DataQs case lesson. And for a full read on what a DOT inspection report contains before you pick a data element, how to read a DOT inspection report walks through every field.
The new 21/21/45-day review clock.
As of 2026, inspection and violation challenges run through a three-step independent review, and there are deadlines attached.
Initial Review
decision to deny cannot be made solely by the citing officer
Reconsideration
independent subject-matter experts not part of the first decision
Final Review
senior decision-maker or independent panel
Those clocks are per stage, not one combined countdown — but each is a hard deadline the state has to meet, which is new. The whole independent structure directly answers the old criticism that the citing agency got to grade its own homework.
The deadlines run from each request, so you control when the later clocks start. You file. The 21-day Initial clock runs. If you're denied and you want to push, you request Reconsideration, and that 21-day clock starts. If you're denied again and you escalate, the 45-day Final clock starts.
For more on the new three-step review, its origin, and how states are implementing it, see the 2026 DataQs overhaul lesson.
When NOT to file.
Be honest with yourself, because a weak filing wastes your time and clutters your record with a denial.
- You were correctly cited
DataQs corrects errors — it doesn't forgive valid violations. If the violation genuinely happened, a DataQs challenge won't remove it.
- Cosmetic gripes
Disagreeing with how strict the officer was is not a ground for an RDR. If nothing on the report is factually wrong, there's nothing to correct.
- A fixed-but-valid violation
Repairing a brake at the roadside doesn't make the brake violation disputable. The fixed-is-not-incorrect rule applies firmly here.
- Outside the filing window
Inspection challenges are accepted for 3 years from the inspection date; crash challenges for 5 years from the crash. A state may still review older events, but it no longer has to.
Save your effort for the records that are actually wrong — those are the ones that win. For everything else about the CPDP crash-preventability path, see the Crash Preventability Determination Program lesson.
The full filing checklist.
Every step from knowing which button to press through tracking your request, with the filing window and review clock included.
Bad data on your record costs real money.
A wrong inspection drags your CSA score the same way a real one does — and it's the kind of thing an auditor and an insurer both see. We review your roadside data for disputable lines, build the evidence, and file the RDR so the record reflects what actually happened.