Explore the sections in this guide
The short answer
DataQs lets users request and track review of FMCSA-issued federal and state data believed incomplete or incorrect. Identify the record, the specific concern, and the evidence supporting the change.
Follow the current DataQs process for the request type. A request is not a promise that a violation will be removed.
A practical example
A report appears to identify the wrong unit. Gather the report and records that connect the event to the correct equipment; explain the discrepancy precisely.
Your next steps
- Preserve the original report and supporting records.
- Describe the disputed information and requested correction.
- Track the request and respond to follow-up questions.
A factual request needs a defined issue
| Record or decision | What it addresses | What to check |
|---|---|---|
| Reported information | The specific event or field disputed | Identify the record being reviewed. |
| Requested correction | What the evidence supports changing | Avoid an undefined request to remove everything. |
| Supporting evidence | Records relevant to that issue | Explain the link between each attachment and the concern. |
| Request history | Submission, follow-up, and determination | Preserve the original record and responses. |
Separate an incorrect record from an unfavorable record
A violation can be unfavorable to the carrier without the data being inaccurate. State what is believed incomplete or incorrect and why. A disputed equipment identifier, duplicate entry, or other documented discrepancy needs evidence relevant to that discrepancy. The reviewing authority determines the request; a consultant cannot promise a score change.
Example: several attachments do not address the disputed field
The carrier supplies a policy manual, training roster, repair invoice, and driver statement for a request about the vehicle identifier. Some documents may be unrelated. Organize the request around the record showing which equipment was involved, identify how the supporting documents connect, and explain the correction being sought. More pages do not necessarily make the request clearer.
Keep correction of the underlying condition separate
If the event identified an actual equipment or operating concern, the carrier still needs to manage that concern. A data review is not a substitute for repairs, employee instruction, or required reporting. Document the operating action and the data-review request as separate activities.
State the disputed fact precisely
Identify the report and the specific field or finding you believe is incorrect. Explain what the record says, what correction you request and which evidence supports that correction. For a unit-identification issue, connect the VIN, plate, unit number and relevant document date. For another dispute, use evidence that addresses that actual finding. A large attachment bundle without an explanation makes the relevant evidence difficult to evaluate.
A successful repair and an inaccurate report are separate questions
Repair records establish what the carrier did after an inspection. They do not automatically show that the original finding was wrong. An RDR should address the disputed data and the review process appropriate to it. Continue required repairs, certifications and deadline management while the review proceeds. Keep the submission, correspondence and disposition available so staff can distinguish requested changes from changes the reviewing agency actually made.
Official source
Confirm applicability, exceptions, and current requirements for your operation. This is a focused summary.
