DataQs
FMCSA's online data quality challenge system that carriers and drivers use to dispute inaccurate crash reports or roadside inspection violations in the MCMIS database.
A successful DataQs challenge corrects the underlying MCMIS record, which then reduces the CSA BASIC score at the next monthly SMS update. Challenges are reviewed by the state agency that submitted the original record. Only factual errors can be challenged — disputes over correct records or fault determinations are not valid DataQs grounds. Access the system at dataqs.fmcsa.dot.gov.
What can (and cannot) be challenged in DataQs
DataQs challenges work for factual errors: a crash attributed to the wrong carrier; a violation citing the wrong regulation; a violation corrected at the scene that should be annotated; or an inspection record linked to the wrong vehicle. DataQs cannot remove technically correct violations — if the brake adjustment was actually out of spec, the violation stands regardless of how good the carrier's maintenance record otherwise is. The reviewing agency evaluates only whether the submitted record is accurate, not whether the violation was appropriate given context.
DataQs challenge process and timeline
Log into dataqs.fmcsa.dot.gov to file a challenge. Submit with supporting documentation: the inspection report, repair records, vehicle registration, or other evidence relevant to the specific error. The reviewing state agency has 30 days to respond. Successful challenges correct the MCMIS record, and the correction flows into the next monthly SMS update. Track open challenges through the DataQs portal and follow up if responses are overdue. Each violation on an inspection report can be challenged separately — challenge only the specific violations that are factually wrong.
Last updated: May 29, 2026
When this definition matters
This term usually matters when a driver, owner-operator, or small carrier is deciding whether a federal rule applies, preparing a compliance file, or checking a state CDL step. Use this definition as a starting point, then confirm the controlling requirement in the official source listed below before making a licensing, hiring, dispatch, or recordkeeping decision.
The related terms above are included because they often appear in the same compliance workflow. Reviewing them together can prevent common mix-ups, such as treating a state licensing step as a federal carrier obligation or confusing a driver record with a separate employer record.