Executive Summary
DataQs is FMCSA's system for requesting and tracking review of crash and inspection data believed to be incomplete or incorrect.
FMCSA reported 8,314 crash-data requests and 63,548 inspection or violation requests in 2024, against a system publishing roughly three million inspections and five million violations each year.
A strong request identifies the exact record, states the narrow error, and supplies organized supporting documents rather than a broad fairness argument.
Data quality is an operating process
FMCSA describes DataQs as the channel for motor carriers, drivers, and other interested parties to review federal and state crash or inspection data and request correction of incomplete or incorrect records.
The system is only the last step. The real process begins when the driver receives the inspection report or a crash occurs. Missing reports, unlabeled photos, late citations, and scattered repair invoices weaken the later request.
EvidenceRevised DataQs Requirements for Motor Carrier Safety Assistance Program Grant Funding DataQs Help Center
Build the evidence package around a precise claim
A useful request says exactly which field, violation, assignment, crash classification, or disposition is wrong and what the record should show. The evidence should let a reviewer follow the same chain without guessing.
FMCSA's help material names common supporting documents such as state inspection reports, state crash reports, shipping papers, and lease agreements. The right package depends on the error.
| Issue | Useful evidence | Weak substitute |
|---|---|---|
| Wrong carrier assignment | Lease, trip document, shipping paper, unit and driver records | Statement that the truck was not ours |
| Citation disposition | Court disposition tied to the cited inspection item | Screenshot without case number or final status |
| Inspection detail error | Inspection report, repair record, dated photos, officer or agency correspondence | General maintenance policy |
| Crash record error | Official crash report, vehicle and carrier identity records, adjudication when relevant | Narrative written months later |
| Duplicate or incomplete record | Both record identifiers and a clear reconciliation | Request to clean up the profile |
EvidenceDataQs Help Center
Preserve evidence before the score changes
SMS gives more weight to recent events, so a new incorrect violation can materially affect the profile. Waiting for a monthly review can allow the error to influence internal carrier decisions or enforcement prioritization.
Create a same-day inspection intake. The driver sends the complete report, photos, citation, unit details, repair actions, and a factual note. Compliance then decides whether the record is accurate, needs corrective action, or needs a DataQs review.
- 1
Collect the complete inspection or crash record on the day of the event.
- 2
Assign the driver, vehicle, carrier, and shipment identifiers.
- 3
Separate facts from opinion.
- 4
Complete repairs or corrective action and retain proof.
- 5
Track citation or court disposition when one exists.
- 6
Compare the published record to the source documents.
- 7
Submit a narrow request with labeled attachments.
- 8
Monitor correspondence and add requested evidence promptly.
- 9
Confirm the final record after closure.
EvidenceDataQs Help Center Safety Measurement System Methodology: BASIC Prioritization Status, Version 3.21
A correction workflow should not erase the safety lesson
A disputed record can still reveal a process gap. Even when a violation is assigned to the wrong carrier or later changed, the event may expose weak document control, unclear leases, delayed repairs, or poor communication.
Close the DataQs request and the operational corrective action separately. One fixes the public record. The other reduces the chance of a repeat.
- Record correction owner and deadline.
- Root cause owner and deadline.
- Evidence retention location.
- Final DataQs disposition.
- SMS or public-record verification after the next update.
EvidenceRevised DataQs Requirements for Motor Carrier Safety Assistance Program Grant Funding
Recommended actions
- Create a same-day roadside inspection evidence intake.
- Write DataQs requests around one precise factual issue with labeled attachments.
- Track public-record correction and internal corrective action as separate closures.
Questions worth asking next
- How quickly does an inspection report reach compliance today?
- Can your team tie every uploaded document to a specific record identifier?