The system that lets you fix wrong data.
Start with the thing nobody tells a new owner-operator: the safety record the federal government keeps on you is not always right, and when it's wrong, you can do something about it. The tool for that is called DataQs. It's an FMCSA system, free to use, that lets you ask the government to review a piece of data you believe is incomplete or incorrect — and correct it.
That's the whole idea. DataQs is the official channel for saying "this record is wrong, here's why, please fix it." A motor carrier can use it. A driver can use it. So can someone filing on their behalf. FMCSA's own position is that no one should be turned away from filing.
Before we get into what you can challenge, two things will save you a lot of wasted effort: knowing the two different requests DataQs offers, and knowing what DataQs is not for.
Two requests, not one: RDR vs IRR.
People mix these up constantly, so get it straight now.
The one you'll usually want is the Request for Data Review — the RDR. That's the challenge. You're asking FMCSA and the state that reported the data to review it and correct it. Every "fix my record" action in this whole series is an RDR, and the DataQs system accepts RDRs for every state.
The other is the Inspection Report Request — the IRR. That one doesn't change anything. It just gets you a copy of an inspection report you've lost or never received. Most states let you pull a report this way through DataQs; a few handle it their own way. If all you need is the paperwork, file an IRR. If you think the paperwork is wrong, file an RDR.
Request for Data Review
Challenges the data and asks for a correction. Accepted for every state. This is the "fix my record" action.
Inspection Report Request
Gets you a copy of a report you've lost or never received. Most states; doesn't change anything.
One request fixes data. The other just hands you a document. Same website, two different buttons.
The nine kinds of data you can challenge.
Here's what an RDR can actually touch. FMCSA reviews a defined set of data, and it helps to think of it as nine kinds of records:
Roadside inspections and their violations
The most common challenge by far — a violation on an inspection report that's wrong, misattributed, duplicated, or pinned to the wrong driver or carrier.
Crashes
A crash on your record that isn't yours, isn't actually a reportable crash, got entered twice, or has wrong details like the fatality count. (And, through a related program, a crash you genuinely couldn't have prevented.)
Compliance reviews and investigations
Data an FMCSA safety specialist recorded during a compliance review or investigation that's inaccurate or incomplete.
Safety audits
Data captured during a new-entrant safety audit that's wrong. (Careful here — challenging the data is DataQs; appealing the rating is a different process, which we'll get to.)
Enforcement actions
A fine tied to a Notice of Claim or Notice of Violation where the underlying data is wrong.
Registration data
Your MCS-150 carrier-identification information not matching what you actually filed.
Operating authority
Your authority status — the OP-1 or OP-2 record — misreported.
Insurance
Your financial-responsibility or insurance filing not reflecting correctly.
Complaints
A household-goods complaint sitting in the national complaint database that's fraudulent or a duplicate.
In the live DataQs "Start a New Request" tool, these nine kinds map onto four top-level request groups: (1) Crash / Inspection / Investigation / Audit; (2) Registration (MCS-150) / Licensing & Insurance / Operating Authority (OP-1, OP-2); (3) Household Goods (HHG) Complaints; and (4) Drug and Alcohol Clearinghouse Violation Petition. That fourth group is a distinct, narrow §382.717 petition that challenges the accuracy of what was reported to the Clearinghouse — not a standard RDR — and it's covered in the driver-data lesson.
Each of these has its own lesson later in the series with the exact grounds and the evidence that wins. The job right now is just to find your problem on this list — if it's here, DataQs is your channel.
What DataQs is NOT for.
This is where people waste filings. DataQs corrects data. It is not an all-purpose complaint box, and three things in particular belong somewhere else.
1. Disagreeing with a safety rating
If you got a conditional or unsatisfactory rating and you think it's wrong, that's an administrative review, a separate process — not a DataQs request. You can use DataQs to fix the wrong data a rating was built on, but the rating itself is appealed elsewhere.
2. Arguing about CSA or SMS itself
Questions or complaints about how the scoring works, or about the interventions process, go to FMCSA's CSA feedback channel, not DataQs.
3. Re-trying your ticket
This is the big one. DataQs is not an appeals court for the underlying citation. You're not arguing that you shouldn't have been stopped, or that the officer was too strict. You're proving the record is factually wrong, or that a court already decided the matter in your favor. If the violation genuinely happened and the record describes it correctly, DataQs can't help you — and "I fixed the problem at the roadside" doesn't make a valid violation disappear.
DataQs corrects data. It is not an appeals court for the underlying citation.
— The distinction that saves wasted filings
Get this distinction and you'll never burn a filing on something DataQs was never going to do.
It runs on evidence — and there's a clock.
Two practical realities to carry into every filing.
First, DataQs runs on evidence, not argument. The reviewer decides on the documents you attach, not on how unfair the record feels. A letter that just says the data is wrong, with nothing attached, gets denied for insufficient evidence. The evidence lesson later in the series is the full playbook on what actually wins.
Second, don't sit on it. States are required to review an inspection challenge for three years from the date of the inspection, and a crash challenge for five years from the date of the crash. After those windows, a state can still look, but it no longer has to. A wrong line is easiest to fix while it's fresh.
Inspection challenge
from the date of the inspection
Crash challenge
from the date of the crash
Where to start.
If you already know which kind of record you're fighting, jump straight to its lesson — an inspection or violation, a crash you couldn't prevent, a crash-record error, registration and authority and insurance, or driver-side data. If you're not yet sure it's worth the effort, the next lesson is the case for caring: it follows one wrong line from the side of the road into the score that costs you money. And if you ever get stuck in the system itself, FMCSA staffs a DataQs help line.
Not sure which of your records are even wrong? A DOT-audit review reads your SAFER/SMS profile line by line, flags the data worth challenging, and helps you file the right request the right way — so you spend your effort only on the corrections that move your score. You can also start with the DataQs hub to map the whole topic.
And if you want to understand the new 2026 review protections before you file, the lesson on the 2026 DataQs overhaul explains the new three-step independent review and the 21/21/45-day clocks you can now hold a state to.
Bad data on your record costs real money.
A DOT-audit review reads your SAFER/SMS profile line by line, flags the data worth challenging, and helps you file the right request the right way — so you spend your effort only on the corrections that move your score.