Imagine this: A roadside inspection appears in your company’s FMCSA safety data, but something does not look right. Perhaps a violation was assigned to the wrong driver. Maybe the same inspection appeared twice, or some important information was missing, or a citation connected to the inspection was later dismissed in court... but the outcome was not reflected in the federal record.
The Federal Motor Carrier Safety Administration (FMCSA) uses "DataQs" to give motor carriers, drivers, and other eligible users a formal way to request review of federal or state safety data they believe is incorrect or incomplete. If you work in a DOT-regulated industry, here's what you need to know about this recourse.
Key Takeaways
- File a DataQs request when safety data is inaccurate, incomplete, duplicated, or attributed to the wrong carrier or driver.
- Correcting a legitimate violation after an inspection does not make the original violation inaccurate.
- Citation adjudication and DataQs review are separate processes. After a citation is adjudicated, the result may be submitted through DataQs with appropriate documentation.
- States subject to the enhanced requirements effective September 18, 2026, must review qualifying inspection-related RDRs submitted within three years of the inspection, and qualifying crash-related RDRs submitted within five years of the crash.
- A strong request identifies the error, explains what the record should show, and provides supporting evidence.
- If a qualifying state-reviewed request is denied, the submitter may seek reconsideration and final review under FMCSA’s updated requirements.
Glossary of Key Terms
-
DataQs: FMCSA’s online system for requesting and tracking reviews of federal and state crash, inspection, and other safety data believed to be incomplete or incorrect.
-
Request for Data Review (RDR): The formal request submitted through DataQs asking the responsible agency to review specific information.
-
CSA: Compliance, Safety, Accountability, FMCSA’s safety compliance and enforcement program.
-
Adjudicated citation: A citation that has been contested and resolved through a state, local, or administrative due-process proceeding.
-
PSP: The Pre-Employment Screening Program, which provides certain commercial driver safety history information to authorized users.
What Is FMCSA DataQs?
The Federal Motor Carrier Safety Administration (FMCSA) DataQs system allows users (most commonly motor carriers and drivers) to request and track reviews of federal and state data reported to FMCSA when they believe the information is incomplete or incorrect.
A carrier might use DataQs when a roadside inspection violation is recorded incorrectly, an inspection has been duplicated, or a violation has been attributed to the wrong carrier or driver. A carrier may also request correction of inaccurate crash facts.
What Is a Request for Data Review?
A Request for Data Review, or RDR, is the formal request submitted through DataQs; the latter then routes the request to the responsible agency for review. For state inspection records, the state reviews the facts and supporting documentation.
Importantly, filing an RDR does not, by itself, remove a violation.
When to File a DataQs Request
DataQs is intended to address inaccurate, incomplete, or incorrectly attributed data. A strong request identifies a specific factual error and provides evidence showing what the record should reflect.
The Violation Is Incorrect
Suppose an inspection record states that a required piece of equipment was missing, but documentation from the inspection shows that the equipment was present and compliant.
The discrepancy, supported by evidence, provides a basis for a DataQs request.
The Same Violation or Inspection Appears More Than Once
Duplicate information can also be challenged.
However, before filing, you should confirm that the entries are actually duplicates: Some data downloads may appear repetitive because individual violations are displayed on separate rows even though they belong to the same inspection.
The Record Was Assigned to the Wrong Carrier or Driver
An RDR may be appropriate when an inspection contains the wrong company name, USDOT number, driver name, license information, or other responsible-party information.
For a request like this, provide documentation that clearly identifies the correct carrier, driver, vehicle, or other responsible entity.
A Crash Is Incorrectly Recorded as a Tow-Away Crash
A tow by itself does not establish that a vehicle sustained disabling damage in a crash. For example, a carrier may have grounds to request review if a vehicle was towed at the owner’s request but the evidence shows it was not disabled by crash damage. Under 49 C.F.R. § 390.5, the tow-away criterion requires crash-related disabling damage that makes transport from the scene necessary; disabling damage has a specific regulatory definition, and whether the vehicle could move is not, by itself, the test.
The request should identify the crash record and disputed field, explain the proposed correction, and provide scene photos, a tow invoice or operator’s statement, the incident report, and inspection or repair records where available. The reviewing agency weighs that evidence.
Crash Record Accuracy and Crash Preventability Are Different Reviews
DataQs is the system used to submit requests; FMCSA’s Crash Preventability Determination Program (CPDP) is a specific program accessed through it. An accuracy RDR determines whether the crash record contains a factual error, such as the wrong carrier, date, vehicle, or tow-away designation. CPDP, on the other hand, investigates whether an eligible, accurately recorded crash was preventable by the carrier.
For CPDP, submit evidence showing why the driver or carrier could not reasonably have prevented the crash. Note that a CPDP decision does not correct the underlying crash report or decide legal fault. A “Not Preventable” finding receives the treatment FMCSA specifies in its Safety Measurement System and is noted in the Pre-Employment Screening Program (PSP); the crash still appears in the record.
A Citation Was Dismissed, Reduced, or Otherwise Adjudicated
A DataQs request may also be appropriate after a citation associated with a roadside inspection violation has been resolved through the proper court or administrative process. A dismissal or reduction may support an update request, but it does not automatically remove the inspection violation.
Employers need to challenge the citation itself through the applicable state, local, or administrative system. Once that process is complete, the documented outcome can support a DataQs request to update the related federal safety record where applicable.
Important Information Is Missing or Incomplete
A DataQs request does not always involve removing a violation: It can also address missing or incomplete information.
Vehicle information, inspection details, location data, carrier information, or other record elements may be inaccurate or incomplete. If you can establish what the correct information should be, an RDR may be appropriate.
What Should You Not Challenge Through DataQs?
Some issues fall outside the purpose of the DataQs process.
A Valid Violation That Has Since Been Fixed
Suppose an inspector identifies a broken light during a roadside inspection and the carrier repairs it immediately afterward.
The repair is appropriate, but it does not mean the light was working when the inspection occurred.
Fixing a violation is not the same as showing that the original violation was incorrect; if the violation was valid at the time of inspection, a later repair does not make the record inaccurate.
A Valid Violation With No Evidence of an Error
Disagreement by itself is not evidence.
Before filing, make sure you can identify both the alleged error and the documentation supporting your position. Broad or speculative requests are unlikely to succeed.
A Citation That Has Not Gone Through the Proper Process
DataQs does not replace the court or administrative process for contesting a citation.
If you dispute whether the citation itself was legally valid, follow the process in the jurisdiction that issued it. After the citation is resolved through the appropriate court or administrative process, the documented outcome may support a DataQs request to update the related FMCSA safety record where applicable.
How Long Do You Have to Submit a DataQs Challenge?
FMCSA announced major changes to the DataQs program in April 2026, and the enhanced state review requirements took effect on September 18, 2026. The revised process applies to requests submitted on or after September 18, 2026. Earlier requests follow the prior process.
Under the enhanced requirements effective September 18, 2026, states subject to those requirements must review qualifying inspection-related RDRs submitted within three years of the inspection and qualifying crash-related RDRs submitted within five years of the crash.
How Long Does a DataQs Review Take?
For qualifying state-reviewed requests subject to FMCSA’s revised requirements, the process includes three stages with these review timelines:
- Initial review: within 21 calendar days
- Reconsideration: within 21 calendar days
- Final review: within 45 calendar days
Reconsideration involves independent subject-matter experts who did not participate in the initial decision. Final review involves a senior decision-maker or independent panel.
What Documentation Should You Include With a DataQs Request?
A well-supported request should make both the disputed issue and the evidence easy to identify.
Match your supporting records to the disputed issue. Identify the error, explain the requested correction, and show how each attachment supports your request.
Supporting Records for Common DataQs Disputes
Data table
| Disputed issue |
Relevant supporting records |
What the records should establish |
|
Incorrect roadside inspection violation
|
Inspection report, photographs from the inspection, vehicle records, relevant maintenance records
|
The vehicle’s condition at the time of inspection and evidence contradicting the recorded violation
|
|
Duplicate inspection or violation
|
Copies of the disputed entries, original inspection report, report numbers, dates, vehicle identifiers
|
Both entries represent the same event or violation, rather than separate violations within one inspection
|
|
Wrong carrier or USDOT number
|
Inspection report, lease agreement, ownership records, documents identifying the responsible carrier
|
Which carrier was responsible for the vehicle or operation during the inspection
|
|
Wrong driver or driver information
|
Inspection report, driver records, license information
|
The correct driver’s identity and the specific information requiring correction
|
|
Citation dismissed, reduced, or otherwise adjudicated
|
Citation or ticket, certified court disposition, related inspection report
|
The final adjudication outcome and its connection to the specific inspection violation
|
|
Crash incorrectly recorded as tow-away
|
Crash report, scene photos, tow invoice or operator’s statement, incident report, post-crash inspection or repair records
|
Whether crash-related damage met the regulatory definition of disabling damage and whether the tow-away field should be corrected
|
|
Missing or inaccurate record details
|
Inspection report, vehicle records, carrier or driver records, event timeline, relevant photographs
|
The correct vehicle, location, date, identity, or other disputed detail
|
FMCSA describes supporting documentation broadly as attachments containing detailed information related to the carrier, driver, vehicle, or event being disputed. DataQs allows additional documents after submission, but submit a complete set with the initial request whenever possible.
How to File an FMCSA DataQs Request
Step 1: Access DataQs
Motor carriers access DataQs through their FMCSA Portal account. If the appropriate DataQs role has not been added, the user may need to request secure access through the Portal profile.
Step 2: Start a New Request
Users can begin an RDR from the DataQs homepage or from the “Start a New Request” area within My DataQs.
Step 3: Locate the Correct Record
Depending on the request type, DataQs may ask you to search for the inspection, crash, investigation, or audit record involved. Confirm the state where the event occurred and use the correct inspection or crash report number.
Be careful not to confuse the inspection report number with the citation number. They are not the same.
Step 4: Select the Correct Request Type
Choose the category that best describes the problem, such as an incorrect violation, duplicate information, incorrect responsible-party information, or a citation associated with an inspection violation.
Selecting the correct category helps route the request and clearly identifies the issue under review.
Step 5: Explain the Error and Upload Your Evidence
State the issue as specifically as possible. Identify the following:
- which part of the record is wrong
- what the record should show
- why the existing information is inaccurate
- which attached document supports the requested correction
Keep the explanation factual and tied to the evidence.
Step 6: Monitor the Request
After submission, monitor the request in DataQs. As a user, you can track its status, review updates, and provide additional information when requested.
How to Appeal a Denied DataQs Request?
Under FMCSA’s enhanced requirements, a denial does not necessarily end the review process.
For qualifying state-reviewed requests subject to FMCSA’s revised requirements, the review process has three stages:
- Initial review
- Reconsideration
- Final review
Request reconsideration or final review within 30 calendar days of the preceding decision. Explain the factual or legal error in the decision. When the state requests more information, respond within 14 days. The state review clock pauses during this response period.
DataQs Reviews as Part of CSA Compliance
DataQs works best as part of a carrier’s regular safety-data review process, with periodic reviews of inspections, violations, crashes, and related records.
A carrier can
- review inspection information on a routine schedule;
- identify new inspections, violations, and crashes;
- confirm that records belong to the correct carrier and driver;
- review violation descriptions for factual accuracy;
- track associated citations through adjudication;
- preserve inspection and court documents;
- submit justified DataQs requests promptly; and
- monitor decisions and confirm that accepted corrections appear in FMCSA systems.
Tools such as continuous driver monitoring can help carriers identify changes in driver risk, while maintenance, training, qualification, and recordkeeping practices can help reduce repeat violations.
How DISA Can Help
Regular review, documentation, submission, monitoring, and verification help carriers keep their safety records accurate. DISA can support the broader compliance processes that produce and maintain those records.
DISA provides DOT compliance services covering driver file management, motor vehicle record checks, drug and alcohol testing, physical exams, and related transportation compliance needs.
If you need help strengthening your DOT compliance program, contact us to explore our transportation compliance solutions for your operation today.
Frequently Asked Questions About FMCSA DataQs
DataQs is FMCSA’s online safety-data review system. It allows eligible users to request review of federal or state information they believe is incomplete or incorrect.
Users with appropriate DataQs access can submit Requests for Data Review. This includes motor carriers and drivers. FMCSA and state partners also use the system to review and manage requests.
A roadside inspection violation can be challenged when there is a factual basis for claiming that the information is incorrect, duplicated, incomplete, or otherwise recorded in error. A negative effect on safety data is not, by itself, a reason for correction.
Not simply because it was fixed. FMCSA states that correcting a legitimate violation after an inspection does not make the original violation inaccurate.
DataQs reviews the underlying federal or state data. Review the records behind the measurement to determine whether a specific inspection, violation, crash, or other data element is inaccurate.
Under the enhanced requirements effective September 18, 2026, states subject to the requirements must review qualifying inspection-related RDRs submitted within three years of the inspection. This is a required state review window for those requests, not a universal DataQs filing deadline.
For qualifying crash-related RDRs, states subject to the revised requirements must review requests submitted within five years of the crash. Other DataQs requests may have different rules.
If a citation associated with a roadside violation is dismissed or results in a not-guilty outcome, the adjudication can be submitted through DataQs. The documented outcome may support a request to update the related FMCSA record where applicable; it does not automatically remove the inspection violation.
No. The court or administrative process determines the citation outcome. DataQs addresses the FMCSA safety-data record. If a citation is changed or dismissed through the proper proceeding, certified documentation of the result can then support an RDR.
Regular reviews can help carriers identify questionable information earlier, preserve supporting evidence, and identify legitimate violation trends that require operational attention.
November 02, 2026
