Safety record
DataQs: how to challenge a violation on your safety record
DataQs is the only route for correcting a violation, an inspection or a crash that FMCSA has recorded against your USDOT number. It is also the step carriers skip after winning a ticket in court, which is why a dismissed citation so often keeps scoring against a carrier for two more years.
By Evan Reid, Founder of Haul Handbook · Updated Sep 11, 2026
What DataQs is
An FMCSA system for requesting and tracking a review of Federal and State data believed to be incomplete or incorrect. The submission is called a Request for Data Review (RDR), and it is open to carriers, drivers and their representatives.
The claim it accepts is narrow on purpose. A request argues that the record is incomplete or incorrect, which is a question of fact about what was written. It is not a place to argue that a correctly recorded violation was harsh.
The court result that most carriers never file
A citation and a safety violation travel separately. Beating the citation changes the court record and leaves the violation scoring in the Safety Measurement System until you tell FMCSA about it.
| Citation result | What happens to the violation |
|---|---|
| Dismissed or found not guilty | The violation is removed. |
| Convicted of a different charge | Severity weight is set to 1 and the violation is not subject to the out-of-service weight. |
Filing a request
- Pull the inspection report and read what was actually written. Work from the report rather than from memory. The violation code, the date, the inspection number and the state that recorded it are the fields a reviewer matches against, and a challenge that misidentifies any of them fails on the paperwork rather than the merits.
- Decide which claim you are making. A Request for Data Review argues the data is incomplete or incorrect. That is a narrower claim than unfair. A violation correctly recorded against the regulation stands even when the circumstances were sympathetic, so identify the specific field that is wrong before filing.
- Gather evidence a reviewer can check. Repair invoices with dates, driver qualification documents, the electronic logging record, photographs, or the certified court disposition. State partners review most roadside challenges, so documents that stand on their own do more than argument.
- File the request and keep the tracking number. Submit through https://dataqs.fmcsa.dot.gov/. An FMCSA system for requesting and tracking a review of Federal and State data believed to be incomplete or incorrect. Each request is tracked, and the reply tells you which office reviewed it and why the outcome went the way it did.
- Watch the record change, or challenge the reasoning. A successful request removes the violation or reduces its weight, and the effect flows into the next monthly run rather than appearing the same day. A denial names its reasoning, which is what a second request has to answer.
Crashes go through a different program
A crash found not preventable is listed on the SMS website as reviewed and not preventable, and excluded from the carrier's measure and percentile in the Crash Indicator BASIC.
Two things follow from that wording. The crash is not erased: it stays on your record carrying the review outcome, so anyone reading your history still sees it. And the exclusion applies to the Crash Indicator category, which FMCSA does not publish anyway, so the benefit shows up in how the agency prioritizes you rather than in a number a broker can see. CSA scores covers which categories are public.
What a correction is worth
It depends almost entirely on the age of the violation. Weight falls as a violation ages and stops counting after 24 months, so removing something written last month is worth three times removing the same violation from eighteen months ago. CSA points by violation lists what each violation group carries, which is the fastest way to see whether a challenge is worth the paperwork.