Guide

How to file a DataQs Request for Data Review

DataQs is the system where a carrier files a Request for Data Review about FMCSA data. Corrections to FMCSA data go through the Request for Data Review process.

On this page

File the request yourself: a short checklist

  • Sign in for your role. Motor carriers first access DataQs through their FMCSA Portal account: select DataQs under Available FMCSA Systems, then Go. Drivers and Public/Industry users follow the DataQs registration path through Login.gov; do not assume every role uses the carrier path.
  • From My DataQs, choose Add a Request, then Inspection and the request type that matches your situation. The category mapping below uses the March 2025 official definitions.
  • Identify the inspection by report number, State and inspection date; identify the disputed violation or field. Explain what is wrong, why, and the correction you request.
  • Attach relevant evidence for that request type. For a citation outcome, identify the citation number and associated violations and provide verifiable court-disposition records or a direct official court-results link. A record-error request needs evidence of that error, not an unrelated court document.
  • Review the information and attachments in Ready to Submit, read the certification, and submit from your own account. Save the acknowledgement and request number; return to My DataQs and Response History to track the response. Use Take Action when responding or requesting the next review stage.
  • If you disagree with a State decision, use the applicable next review stage and explain why its stated reasons are incorrect. Read the deadlines guide for the effective date, response periods and appeal requirements.

Optional self-serve RoadsideProof software

You can complete these steps without buying RoadsideProof. The following sections explain the optional automated document-completeness check and fixed-template draft; those are separate from DataQs registration and submission.

Review the inspection and the record

Start with the inspection report and the violation being reviewed. The free RoadsideProof report shows the code, the description, whether it was an out-of-service violation, and the inspection it came from.

Identify the Inspection category

A Request for Data Review states a request type. RoadsideProof supports a subset of the Inspection group, using shorter product labels. The category guide maps those labels to the official March 2025 request types; it is not a list of every DataQs option.

Prepare the documents for that category

For an inspection request, upload the inspection report and supporting documents. For a CPDP crash request, upload the police accident report (PAR) and supporting evidence. Check each required value against its source and confirm it.

The product's category list requires the inspection report for inspection-record corrections. The carrier-identity category also requires proof the inspection was not yours; the driver-information category also requires the driver's record. The citation-outcome category requires the citation itself and the court disposition.

Review and confirm the draft fields

Nothing reaches your draft until you confirm it. A field you did not confirm cannot appear in the text — that is enforced in code, not by review.

RoadsideProof software assembles a draft from a fixed template and only fields you confirmed. Its automated check covers completeness against the documents you upload.

File from your own account and sign it yourself

We do not file for you. You file from your own account and you sign it, and that signature carries 18 U.S.C. 1001.

Any Request for Data Review you submit is your filing. You sign it, and that signature is made under penalty of 18 U.S.C. 1001. You are responsible for the accuracy of every statement in it, including statements assembled from fields you confirmed in this software.

We never ask for your FMCSA Portal, DataQs, or Login.gov credentials. There is no step in the flow where you would hand them over.

The agency decision

We do not promise an outcome. The burden of proof is on the filer. The revised State DataQs process applies to requests submitted on or after September 18, 2026. It is not retroactive and does not establish deadlines for Federal reviews. Its stages are Initial Review, Reconsideration, and Final Review. FMCSA considers the State's RDR decision final after Final Review is completed; this is separate from a court's disposition of a citation.

Sources and factual review

Editorial source check: .

Document dates and data snapshot dates are separate from this editorial review. This review does not validate production calculations, document processing or storage controls.

More in Filing and deadlines

See what it did to your score

Live lookup in the app for the USDOT you enter. Illustrative examples are separate from your results.

Unsafe Driving, HM Compliance and Crash Indicator are not included in this lookup.

What this lookup supports

What this lookup supports

Vehicle Maintenance

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Hours-of-Service Compliance

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Controlled Substances/Alcohol

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Driver Fitness

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Unsafe Driving

Reference codes: Available

Listed violations: Not offered

Weighted numerator contribution: Internal calculation only; not in lookup

BASIC measure: Not offered

Estimated position and range: Not offered

HM Compliance

Reference codes: Available

Listed violations: Not offered

Weighted numerator contribution: Not offered

BASIC measure: Not offered

Estimated position and range: Not offered

Crash Indicator

Reference codes: Not offered

Listed violations: Not offered

Weighted numerator contribution: Not offered

BASIC measure: Not offered

Estimated position and range: Not offered

The four supported BASICs require readable snapshot data and a computed measure to list violations or open a report. Estimated positions also require sufficient carrier data and passed publication checks; calibration failure can withhold a position or retain a dated previous estimate. Controlled Substances/Alcohol is subject to these checks too. Missing carrier data, no relevant inspections, no applicable violations and an unavailable calculation are different states. An unavailable result is not a zero or a claim that there are no violations. HM Compliance and Crash Indicator have no report calculation in this product.

Unsafe Driving’s SMS denominator is average power units × utilization factor, which depends on vehicle miles traveled (VMT) and carrier segment (Equation 3–1). Our product lacks the historical power-unit inputs needed to reconstruct and validate that full calculation. It calculates numerator points internally only; Unsafe Driving records, measure and estimated position are not offered in this lookup.

Severity weight is an input. Weighted numerator contribution accounts for time weighting and the inspection cap. The marginal change in a named BASIC measure also depends on its denominator. An estimated percentile compares carriers within a safety event group and must be read with its range. Do not add points across BASICs. SMS calculations are separate from an official safety rating. This is our estimate from public FMCSA data, not an official FMCSA percentile.

FMCSA SMS Methodology v3.21, Chapter 3 Safety rating: 49 CFR 385.3