$0
Cost to file an RDR
~10 days
FMCSA response target (a goal)
16
Crash types eligible for preventability review
24 mo
Window the violation affects your score
In This Guide
What DataQs Is and Why It Matters
DataQs is the Federal Motor Carrier Safety Administration's online system for challenging the accuracy of the safety data it holds about you. Anyone — a motor carrier, a commercial driver, a state agency, or a member of the public — can submit a free Request for Data Review (RDR) to dispute a crash report, a roadside inspection record, a specific violation, or other safety information that appears to be wrong or improperly associated.
The reason it matters is that this data is not just sitting in a government database. Roadside inspection violations and crashes feed FMCSA's Safety Measurement System (SMS), which produces the percentile rankings across the seven BASICs that drive interventions, influence whether you get a CSA alert, and are visible to insurers and brokers through tools like the Pre-Employment Screening Program (PSP). An erroneous violation does not just look bad — it can raise your insurance, cost you freight, and trigger enforcement attention. DataQs is the mechanism to get genuinely incorrect data corrected.
FMCSA itself notes that thousands of records with incorrect information are corrected through DataQs every year. That is the opportunity. The constraint — and the rest of this guide is largely about this constraint — is that DataQs corrects inaccuracy. It is not a forgiveness program for accurate violations you wish had not happened.
The mental model: accuracy, not appeal
Think of DataQs as a tool to make your record true, not to make it kinder. If the record is factually wrong, you have a strong case. If the record is accurate but unwelcome, DataQs is the wrong tool. Getting this distinction right before you file saves you from spending effort on challenges that are designed to lose.
What You Can and Cannot Challenge
The single most common reason a DataQs challenge fails is that it targets something the system was never meant to change. Sort your situation into the right column before you spend time on it.
Challengeable (factual errors)
- Violation attributed to the wrong carrier or USDOT number
- Inspection or crash listing the wrong driver
- Duplicate inspection or crash record
- A violation that does not actually meet the cited regulation
- A crash that does not meet FMCSA reportability standards
- Post-crash equipment damage counted as a maintenance violation
- A citation overturned in court (with certified court documents)
- An eligible crash that was not preventable (via the CPDP)
Not challengeable
- A real, accurately recorded violation you simply disagree with
- A violation you later fixed — correcting it does not erase it
- Verbal or written warnings (they are not in FMCSA's data)
- The severity weight FMCSA assigns to a valid violation
- Drug and alcohol test results themselves (only reported-data accuracy)
- A preventability claim outside the 16 eligible crash types
- Dissatisfaction with how SMS math works generally
Two entries deserve emphasis because they trip up so many carriers. First, fixing a defect is not grounds for removal. If your truck was cited for a brake out of adjustment and you repaired it the next day, the violation still happened and still counts — the repair belongs in your maintenance file, not in a DataQs challenge. Second, a court outcome can matter, but only with proof. FMCSA policy allows removal, or reduction to the lowest severity, when a citation underlying a violation was dismissed or you were found not guilty — but you must submit the certified court documents through DataQs to get it.
Are Your Fleet's Docs Current?
Free 3-minute check shows exactly which medical cards, CDLs, and DQF docs are expired or at risk. No signup. No email. Just answers.
Who Actually Reviews Your Request
Understanding who decides your challenge explains a lot about how to win one. The DataQs system is national, but the adjudication is largely local. Most Requests for Data Review are handled by state DataQs analysts, and the request goes to the state where the event happened — the inspection state or the crash location — not the state where your company is based. The same officer or agency that generated the record is, in many cases, the one reviewing the challenge to it.
FMCSA reviews certain specialized matters directly. The Crash Preventability Determination Program and Drug and Alcohol Clearinghouse petitions are handled at the federal level, as are some administrative requests. If you file in the wrong place, the system can route the request to the correct office rather than simply rejecting it.
Why this makes your evidence decisive
Because outcomes are decided by state analysts applying judgment to the record in front of them, the difference between a granted and denied challenge is frequently the quality and completeness of what you attach. A bare assertion that "the violation is wrong" gives the reviewer nothing to act on. The police report, the inspection form, the repair invoice, a dated photo, the certified court disposition — these are what let a reviewer say yes. As of mid-2026, there is no formal federal appeal path for a state-denied RDR, which raises the stakes on filing a complete, well-documented request the first time.
How to File a Request for Data Review, Step by Step
Filing is straightforward; winning takes preparation. The workflow below front-loads the part that actually determines the outcome — the evidence.
Identify the exact error
Pull the specific record from your SMS data or PSP report and pinpoint precisely what is wrong: wrong USDOT number, wrong driver, duplicate, a violation code that does not match what actually happened, or a crash that should not be counted. Vague challenges lose; specific ones win.
Gather the supporting records
Assemble the documentation that proves the error: the roadside inspection form (DVER), the police accident report, repair invoices and work orders, dated photographs, dispatch or ELD records, the driver's CDL, or certified court documents for an overturned citation. This is the heart of the request.
Submit the RDR through DataQs
Create or log into your account at the DataQs portal (dataqs.fmcsa.dot.gov), open a Request for Data Review, select the record type (inspection, crash, violation, and so on), describe the error clearly and factually, and upload your supporting documents. There is no filing fee.
Respond and track to resolution
Monitor the request; the agency targets roughly 10 business days for standard reviews. If the reviewer asks for more information, respond promptly — you generally have up to 60 days. After a decision, you can typically provide additional information once through a reconsideration.
The evidence is the case
A reviewer cannot independently investigate your truck or your trip. They decide on the documents in the request. The carriers that win DataQs challenges are not better arguers — they are better record keepers. If the proof is organized and ready the moment a questionable violation appears, you can file inside the window with a complete package instead of scrambling to reconstruct what happened weeks later.
The Crash Preventability Determination Program
Crashes are different from violations, and they have their own dedicated path. The Crash Preventability Determination Program (CPDP), which FMCSA made permanent on May 1, 2020, lets carriers ask FMCSA to review certain crashes and determine whether they were preventable. It reviews crashes in 16 eligible crash types that occurred on or after August 1, 2019.
The eligible types are situations where the commercial vehicle was largely a victim of circumstance — for example, the CMV was struck by a motorist driving under the influence, struck by a vehicle traveling the wrong direction, struck in the rear, or struck while legally stopped or parked. You submit the police accident report and any supporting evidence through DataQs, and FMCSA — not a state — makes the determination.
The payoff is meaningful: a crash determined Not Preventable is removed from the SMS Crash Indicator measure and percentile calculation. The crash still appears in your SMS record, but it is listed separately and no longer counted against your Crash Indicator score. Historically, the large majority of eligible crashes submitted have been found not preventable, which makes the program worth using whenever a crash plausibly fits one of the 16 types.
Examples of eligible "not preventable" crash scenarios
These are illustrative of the 16 eligible categories. Confirm the current eligible crash types and required documentation in FMCSA's CPDP Eligibility Guide before filing.
How audit-ready are you for keeping crash reports and inspection evidence ready for a DataQs filing?
Free 3-minute FMCSA audit readiness check. No signup, no credit card. See exactly which documents are expired or at risk.
The Effect on Your CSA/SMS Score
A successful challenge changes your record in one of a few ways, depending on what you challenged. An erroneous violation that is removed or corrected stops contributing to its BASIC percentile. A citation overturned in court can be removed or reduced to the lowest severity weight. A crash found not preventable is pulled out of the Crash Indicator calculation. In each case, the correction flows back into the SMS data and, at the next monthly refresh, can move your percentile.
Timing is the catch that decides whether any of this helps you today. Violations and crashes influence your SMS percentile for 24 months. Winning a challenge on a violation that has already aged out of the calculation cleans up your historical record but does little for your current score and intervention status. That is why the carriers who get the most out of DataQs are the ones reviewing every new inspection and crash as it posts and filing while the record is still doing damage — not discovering a bad violation when an insurer flags it eighteen months later.
DataQs is not a substitute for compliance
The cleanest way to keep your scores down is to not earn the violations in the first place. DataQs is a correction tool for genuine data errors, and it is powerful when used that way — but a carrier relying on challenges to offset a stream of real violations is treating the symptom. Use DataQs to keep your record accurate, and use a disciplined compliance and maintenance program to keep your record clean.
How FileFlo Builds the Evidence Behind a DataQs Challenge
FileFlo is not a DataQs-filing service and it does not submit challenges on your behalf — you file the RDR, because you are the carrier and the determination is yours to pursue. What FileFlo does is the part that actually decides DataQs outcomes: it is the records and proof layer that keeps your roadside inspection reports, repair documentation, crash reports, and supporting evidence organized and instantly retrievable, so that when a questionable violation or a non-preventable crash appears, you can file a complete, well-documented request inside the window instead of reconstructing it from memory.
You file the challenge; FileFlo holds the proof
- Every inspection report in one place: Store each Driver Vehicle Examination Report against the right vehicle and driver, so when a violation looks wrong you have the underlying record in seconds — not buried in a glovebox or an email thread.
- Repair and correction documentation: Keep the work orders, invoices, and dated evidence tied to each defect. For post-crash equipment damage or a mis-cited condition, that documentation is what demonstrates the error to the reviewer.
- Crash records ready for the CPDP: Hold the police accident reports and supporting evidence organized by event, so an eligible crash can be submitted to the Crash Preventability Determination Program while it is still affecting your Crash Indicator.
- File while it still counts: Because everything is retrievable on demand, you can review new inspections and crashes as they post and assemble the evidence package inside the 24-month window — when a successful challenge actually moves your score.
Key Takeaways
- DataQs corrects inaccuracy, not accurate-but-unwelcome violations. A free Request for Data Review fixes wrong-carrier, wrong-driver, duplicate, mis-cited, or non-reportable records.
- Fixing a defect does not erase the violation, and warnings cannot be challenged because they are never recorded in the first place.
- State analysts decide most challenges based on where the event occurred, so the completeness of your attached evidence usually decides the outcome.
- The Crash Preventability Program (permanent since May 1, 2020; 16 crash types; crashes on/after Aug 1, 2019) removes not-preventable crashes from the Crash Indicator percentile.
- File within the 24-month window. A challenge only helps your current score while the violation or crash is still in the SMS calculation.
Challenging a DOT Violation with DataQs: FAQ
Common questions about filing a Request for Data Review, what can be challenged, and how it affects your CSA score.
DataQs is FMCSA's free online system for challenging the accuracy of federal safety data. Through it, commercial drivers, motor carriers, state agencies, and the public can submit a Request for Data Review (RDR) to dispute crash reports, roadside inspection records, violations, and other safety information held by FMCSA. There is no cost to file. The system routes each request to the office responsible for the underlying record — usually the state where the inspection or crash occurred — for resolution.
You can challenge records that are factually wrong: a violation attributed to the wrong carrier or driver, a duplicate inspection, a violation that does not meet the cited regulation, a crash recorded against the wrong USDOT number, a crash that does not meet reportability standards, or post-crash equipment damage being counted against you. You cannot use DataQs to remove a violation simply because you later fixed the defect — correcting a problem does not erase that it occurred. You also cannot challenge verbal or written warnings, because warnings are not recorded in FMCSA's data in the first place.
Most Requests for Data Review are reviewed by state DataQs analysts, based on where the event occurred — the crash location or the inspection state, not your domicile. FMCSA staff handle specialized programs directly, including the Crash Preventability Determination Program and Drug and Alcohol Clearinghouse petitions. If a request is routed to the wrong agency, the system can forward it to the correct office. Because a state reviews most challenges, outcomes can vary by state, and the quality of the supporting records you attach is often what decides a close call.
FMCSA's stated target is a response within roughly 10 business days for standard Requests for Data Review, though the agency describes this as a goal rather than a binding deadline, and complex cases take longer. The Crash Preventability Determination Program and Clearinghouse petitions follow their own separate timelines. If the reviewing agency asks you for more information, you generally have up to 60 calendar days to respond, and you can typically provide additional information once through a reconsideration after an initial decision.
Through the Crash Preventability Determination Program (CPDP), yes — for eligible crash types found not preventable. FMCSA made the CPDP permanent on May 1, 2020, and it reviews crashes in 16 eligible crash types that occurred on or after August 1, 2019 (for example, being struck by a driver under the influence, struck in the rear, or struck by a vehicle traveling the wrong direction). A crash determined Not Preventable is removed from the SMS Crash Indicator measure and percentile — though it still appears in your SMS record, flagged separately. You submit the police report and supporting evidence through DataQs.
FMCSA does not publish a strict filing deadline for most data reviews, but timing still matters because violations and crashes affect your Safety Measurement System percentile for 24 months. Filing within that two-year window is what makes a successful challenge actually move your score — winning a challenge on a violation that has already aged out of the calculation does little for your current percentile. The practical rule is to review every new inspection and crash promptly and file while the record is still influencing your data.
Win DataQs Challenges With Evidence That Is Always Ready
DataQs is decided by the records you attach. FileFlo keeps your inspection reports, repair proof, and crash documentation organized and retrievable, so you can file a complete Request for Data Review inside the window that actually moves your score. You file the challenge; FileFlo holds the proof — it is the records layer, not a DataQs-filing service.
Plans from $89/month — No credit card required — 5-day free trial