Safety records
DataQs: Handle a Disputed Carrier Safety Record Without Erasing the Evidence
By VerifyCarrier · · 3 min read
DataQs lets users request and track reviews of FMCSA safety information believed to be incomplete or incorrect. A submitted request is a dispute, not a correction. Brokers should preserve the original observation, the carrier’s evidence and the review status until the responsible authority reaches an outcome.
Identify the record and the alleged error
Ask for the USDOT number, inspection or crash report identifier, date, state and disputed field. “Our record is wrong” does not identify what an analyst must examine. The request should state the proposed correction and which document supports it.
Separate factual accuracy from crash preventability. A crash can be correctly assigned to a carrier while the carrier disputes whether it could have prevented it. FMCSA provides a distinct Crash Preventability Determination Program process through DataQs. Choosing that route does not mean the incident never occurred.
Sources: DataQs; DataQs help center
Submit evidence that addresses the disputed fact
FMCSA lists inspection reports, crash reports, shipping papers and lease agreements among possible supporting documents. Choose evidence relevant to the claim. For a fictional wrong-carrier assignment, records connecting the involved vehicle and operation to the correct carrier matter more than a general statement about the company’s safety practices.
Supporting material can be uploaded with the request or added later. Keep a copy of what was submitted and use the request’s correspondence history to respond to further questions. Avoid repeated disconnected requests for the same issue; track the existing request and its instructions.
Sources: DataQs help center
Use the current account and review process
DataQs currently uses Login.gov for users who previously signed in with a DataQs username and password; the account email must match. Motor carriers can also use the FMCSA Portal to reach requests associated with their USDOT numbers. Follow the current registration guidance rather than relying on an old screenshot of the login form.
The DataQs homepage states that revised requirements for state reviews took effect September 18, 2026. That is a reason to use current instructions and notices for an active request. Do not promise a universal outcome or turnaround from an older guide; the relevant agency must assess the evidence.
Sources: DataQs
Track request status separately from carrier approval
DataQs allows users to find requests by ID or status and inspect their details. A broker’s internal review should reference the request, the disputed source record and any verified outcome. “Carrier says a DataQs request is open” and “official record corrected” must remain different states.
Apply your approval policy to the evidence available while the request is unresolved. Do not delete an adverse record solely because it was challenged, or treat the existence of a challenge as evidence of misconduct. State which fact remains disputed and what would resolve the booking question.
Sources: DataQs help center
Verify the correction downstream
When an outcome arrives, read what it actually changed. A correction to one field does not erase every other observation in the report. Preserve the decision or response and recheck the relevant public source after its next applicable update.
SAFER, SMS and raw agency exports do not all refresh on the same schedule. If a service still shows an earlier value, compare its source date with the correction rather than assuming the request failed. Update the broker’s review with both the official outcome and the downstream observation date so the same resolved discrepancy does not trigger another investigation.
Sources checked . Procedures are VerifyCarrier’s recommendations; examples are illustrative. How we prepare and correct these guides.