How to Use FMCSA DataQs
Dispute DOT Violations and Correct Your Safety Records
Updated November 2026 to reflect FMCSA’s revised DataQs review and appeal procedures.
How FMCSA DataQs Helps Trucking Companies Dispute DOT Violations and Correct Safety Records
An incorrect DOT violation or crash report can create problems for a trucking company long after the original incident. It can affect your safety record, raise questions with customers, and potentially influence your Compliance, Safety, Accountability (CSA) performance.
But what happens when the information reported to FMCSA is wrong?
That’s where the FMCSA DataQs system comes in.
DataQs gives motor carriers and commercial drivers a way to challenge inaccurate safety information and request corrections to federal or state records. Whether you’re dealing with an incorrectly assigned violation, a duplicate inspection, or a crash that doesn’t belong on your company’s record, understanding the process can help you protect the accuracy of your safety history.
And with important changes to the DataQs review process taking effect September 18, 2026, carriers now have clearer deadlines and additional opportunities to challenge unfavorable decisions.
This guide explains how the system works, what evidence you’ll need, and how to navigate the updated review process.
What Is the FMCSA DataQs System?
The Federal Motor Carrier Safety Administration (FMCSA) created DataQs to give drivers, trucking companies, and other stakeholders a formal way to request corrections to inaccurate safety information.
The system allows users to submit a Request for Data Review (RDR) when they believe federal or state safety records contain errors.
These requests are routed to the agency responsible for the original information. That agency reviews the evidence and determines whether a correction is appropriate.
Common reasons for filing include:
- An incorrect violation listed on a roadside inspection
- A duplicate inspection or crash record
- A crash assigned to the wrong motor carrier
- Incorrect driver identification or USDOT information
- An adjudicated citation that needs to be reflected in the safety record
The important distinction is that DataQs is designed to correct inaccurate information. It is not a shortcut for removing legitimate violations simply because they negatively affect a company’s safety performance.
Why Accurate DOT Safety Records Matter
Trucking companies depend on accurate safety records for more than regulatory compliance.
Roadside inspection and crash data can influence FMCSA’s Safety Measurement System (SMS), which evaluates carriers across several Behavior Analysis and Safety Improvement Categories, commonly called BASICs.
When incorrect information enters the system, it may affect how a carrier’s performance is represented.
Customers, insurers, and other business partners may also consider a company’s safety history when evaluating risk.
For example, imagine a roadside inspection violation is mistakenly assigned to your fleet. If that violation remains in the system, it may influence the relevant BASIC calculation even though your company was not responsible.
Correcting the record helps ensure your safety history reflects what actually happened.
However, an approved correction does not guarantee a specific improvement in a CSA percentile. Those calculations depend on several factors, including the carrier’s other inspections, violations, and safety events.
For additional strategies, read our guide on how to improve CSA scores.
Download the additional 17 crash checklist that will help you be better informed when it comes to what you can DataQ challenge.
What’s Changed With FMCSA DataQs in 2026?
One of the most important developments in recent years is FMCSA’s revised process for reviewing disputed safety data.
Effective September 18, 2026, State agencies must follow enhanced review requirements for covered DataQs requests submitted on or after that date.
Previously, carriers and drivers often faced inconsistent review procedures, limited reconsideration opportunities, and uncertainty about when a decision would be issued.
The updated requirements establish a more consistent process with three potential stages of review.
Stage 1: Initial Review
The responsible State agency reviews the original request and supporting evidence.
States must open an initial Request for Data Review within seven days of submission and issue a decision within 21 days.
The review process includes requirements intended to prevent an issuing officer from being the sole decision-maker when a correction is denied.
If the agency determines that the information is incorrect, the appropriate record correction can be made.
If the request is denied, the applicant may be eligible to request reconsideration.
Stage 2: Reconsideration
If you disagree with the initial decision, you can generally request reconsideration within 30 days of receiving it.
This stage provides an additional review by qualified personnel who were not responsible for the initial determination.
The State generally has 21 days from escalation to issue its reconsideration decision.
When requesting reconsideration, explain why you believe the original decision was incorrect and identify the evidence supporting your position.
Stage 3: Final Review
If reconsideration does not resolve the dispute, an eligible request can advance to Final Review.
This stage involves a senior decision-maker or independent review panel.
The State generally has 45 days from escalation to issue a final determination.
Applicants generally have 30 days after the reconsideration decision to request this stage.
Important exceptions and deadlines
The standard review deadlines are:
| Review stage | Agency deadline |
|---|---|
| Open initial request | Within 7 days |
| Initial decision | Within 21 days |
| Reconsideration decision | Within 21 days |
| Final review decision | Within 45 days |
When an agency requests additional information, the review clock may pause. Applicants generally have 14 days to respond.
These rules do not automatically apply to every type of DataQs submission. The Crash Preventability Determination Program and Drug and Alcohol Clearinghouse petitions follow separate procedures.
The September 2026 changes are also not retroactive to requests submitted before the effective date.
For complete details, consult the FMCSA DataQs Help Center.
How to File a DataQs Request: Step by Step
Filing a request is relatively straightforward. The part that requires the most attention is gathering the right documentation and explaining the problem clearly.
Step 1: Review the original safety record
Before submitting anything, examine the inspection report, crash record, or other information you believe is incorrect.
Identify the specific error and determine what correction you are requesting.
For example, are you challenging the violation itself, an incorrect driver identification, or a crash record assigned to your USDOT number?
Being specific from the beginning can help the reviewing agency understand your request.
Step 2: Gather supporting documentation
Your request should include evidence that directly addresses the disputed information.
Depending on the situation, useful documentation may include inspection reports, photographs, dashcam footage, police accident reports, maintenance records, or electronic logging device information.
Court records may also be important when reporting the outcome of an adjudicated citation.
Avoid submitting large amounts of unrelated material. The goal is to provide clear evidence supporting the particular correction you are requesting.
Step 3: Access the DataQs system
Visit dataqs.fmcsa.dot.gov and sign in.
Motor carriers generally access DataQs through the FMCSA Portal. Drivers and other public users can access the system through the appropriate Login.gov registration process.
Once your account is ready, select the option to submit a new Request for Data Review.
Step 4: Choose the correct request category
DataQs offers different categories based on the type of information being challenged.
Select the category that most accurately describes your concern.
For example, an incorrect violation should not automatically be submitted as a crash dispute.
Similarly, a request involving the outcome of a court citation may require a different category than a request claiming that a violation was recorded incorrectly.
Choosing the correct category helps route the request to the appropriate reviewers.
Step 5: Explain the problem clearly
Provide the inspection or report number, event date, State, and other identifying information requested by the system.
Then explain the error in plain language.
A useful explanation answers three questions:
- What information is currently incorrect?
- Why do you believe it is incorrect?
- What specific correction are you requesting?
Keep your explanation factual and professional.
A clear request supported by appropriate documentation is more useful than a lengthy argument about how unfair the original violation feels.
Step 6: Submit and monitor your request
After submitting, save your request number and monitor the status through your DataQs account.
The reviewing agency may ask for additional information.
Respond promptly because missed deadlines can delay or close the review.
You can track submitted requests through the Monitor an Existing Request section of DataQs.
What Makes a Strong DataQs Request?
The strongest requests focus on verifiable facts.
For example, suppose a roadside inspection lists a violation involving a vehicle that was not operating under your company’s authority at the time of the inspection.
A useful submission might include documents showing the vehicle’s ownership, lease status, operating authority, and other information relevant to the disputed assignment.
The key is connecting the evidence directly to the correction being requested.
The same principle applies to vehicle defects and Hours-of-Service disputes.
If you’re challenging an inspection finding, you need evidence that addresses the condition or information recorded at the time of inspection.
Simply repairing a defect after the inspection does not mean the original violation was incorrect.
This is one of the most important distinctions for safety managers to understand.
Can You Use DataQs to Remove a DOT Violation?
Sometimes, but not simply because the violation has been corrected.
DataQs may allow an inspection violation to be removed or modified when evidence demonstrates that the information was inaccurate, duplicated, or otherwise eligible for correction.
For example, a violation might be assigned to the wrong carrier or recorded with incorrect information.
On the other hand, a legitimate brake defect does not disappear from the inspection record simply because the maintenance department repaired the truck later that afternoon.
The original inspection documents the condition identified at that time.
If the issue involved a citation that was subsequently adjudicated, the outcome may be handled differently under FMCSA’s citation adjudication policies.
Understanding that difference can save companies considerable time when preparing requests.
For more information about serious inspection deficiencies, see our DOT Out of Service Violations List.
What Happens If a Traffic Citation Is Dismissed?
A dismissed citation may affect how an associated inspection violation is treated in FMCSA’s safety systems.
However, a court dismissal does not necessarily delete the original inspection record.
Under FMCSA’s adjudicated citation policy, different outcomes have different effects.
Not guilty or dismissed: The associated violation is excluded from SMS calculations and the driver’s Pre-Employment Screening Program (PSP) report.
Convicted of a different charge: The violation’s severity weight is generally reduced to one for SMS calculations, and the different conviction is reflected on the PSP report.
Convicted of the original charge: The violation generally retains its original treatment.
The original inspection information and adjudication result may remain accessible to authorized users.
If your citation has been adjudicated, use the appropriate DataQs category and provide documentation of the final outcome.
Can DataQs Help With a Crash That Wasn’t Your Driver’s Fault?
Yes, although you need to understand the difference between correcting inaccurate crash information and requesting a crash preventability determination.
If a crash report incorrectly identifies your company, lists inaccurate vehicle information, or contains another reporting error, a standard DataQs request may be appropriate.
But what if the crash was accurately reported and your driver could not have prevented it?
That situation may qualify for FMCSA’s Crash Preventability Determination Program (CPDP).
How the Crash Preventability Determination Program works
FMCSA expanded the program on December 1, 2024, to cover 21 eligible crash types.
Examples include certain situations where a commercial vehicle is struck from behind, another motorist drives in the wrong direction, or a vehicle is struck while legally stopped.
Other qualifying scenarios involve specific actions by another motorist or circumstances outside the commercial driver’s control.
To request a review, the carrier submits the appropriate request through DataQs along with the required police accident report and other supporting evidence.
FMCSA reviews the circumstances and determines whether the crash was preventable, not preventable, or whether the evidence is insufficient to reach a decision.
A crash determined to be Not Preventable remains visible in FMCSA’s records but is excluded from the carrier’s Crash Indicator BASIC calculation.
The driver’s PSP record also reflects the determination.
The standard 2026 State DataQs review deadlines do not govern CPDP requests.
Learn more through FMCSA’s Crash Preventability Determination Program.
How Long Does It Take for a DataQs Correction to Appear?
Even after a request is approved, the correction may not appear immediately in every federal system.
FMCSA maintains several systems with different update schedules.
The Safety Measurement System and Pre-Employment Screening Program generally update monthly.
The SAFER Company Snapshot updates daily but displays a more limited set of carrier information.
Consequently, there can be a delay between an approved correction and the date it becomes visible in public-facing safety data.
Keep the decision documentation and monitor the appropriate federal system to confirm that the updated information appears.
If the correction is still missing after the applicable update cycle, follow up with the responsible agency.
Common DataQs Mistakes to Avoid
A DataQs request can become more difficult than necessary when the original submission does not clearly establish the problem.
Some common mistakes include submitting a request without sufficient evidence, choosing an incorrect category, or attempting to challenge a legitimate violation that was simply repaired after the inspection.
Another mistake is overlooking agency correspondence.
If a reviewer requests additional information, the company needs to respond before the applicable deadline.
Safety managers should also understand that DataQs is not the appropriate system for changing routine carrier registration details. Changes to company registration information are generally handled through FMCSA’s registration procedures.
Before submitting, review the entire request for accuracy and make sure the supporting documents match the event being challenged.
DataQs Is Important, but Prevention Matters More
Correcting inaccurate safety records is an important part of effective fleet management.
But DataQs should not become the primary strategy for improving safety performance.
The stronger approach is preventing legitimate violations in the first place.
That starts with qualified drivers, properly maintained equipment, consistent inspections, and ongoing education.
When companies review inspection data and identify recurring violations, they can use those findings to improve their training programs.
For example, repeated Hours-of-Service violations may indicate that drivers need additional instruction on ELD procedures, logging requirements, or company expectations.
Recurring vehicle maintenance violations may suggest problems with inspection practices, maintenance scheduling, or driver reporting.
A strong fleet safety training program gives companies a consistent way to address these concerns before they produce additional violations.
INFINITI helps organizations deliver recurring driver training, track participation, and document completion. Companies can also use custom training programs to reinforce their own inspection procedures and regulatory requirements.
Training cannot eliminate every violation, but it can help companies build stronger habits and identify preventable safety problems earlier.
DataQs Is Important, but Prevention Matters More
Correcting inaccurate safety records is an important part of effective fleet management.
But DataQs should not become the primary strategy for improving safety performance.
The stronger approach is preventing legitimate violations in the first place.
That starts with qualified drivers, properly maintained equipment, consistent inspections, and ongoing education.
When companies review inspection data and identify recurring violations, they can use those findings to improve their training programs.
For example, repeated Hours-of-Service violations may indicate that drivers need additional instruction on ELD procedures, logging requirements, or company expectations.
Recurring vehicle maintenance violations may suggest problems with inspection practices, maintenance scheduling, or driver reporting.
A strong fleet safety training program gives companies a consistent way to address these concerns before they produce additional violations.
INFINITI helps organizations deliver recurring driver training, track participation, and document completion. Companies can also use custom training programs to reinforce their own inspection procedures and regulatory requirements.
Training cannot eliminate every violation, but it can help companies build stronger habits and identify preventable safety problems earlier.
FAQs
What is FMCSA DataQs used for?
FMCSA DataQs is an online system that allows motor carriers, commercial drivers, and other stakeholders to request a review of federal or state safety data they believe is incorrect or incomplete.
Common requests involve roadside inspections, inaccurate violations, duplicate records, and crash reporting errors.
The system routes requests to the agency responsible for the original information. That agency reviews the submitted evidence and determines whether a correction is appropriate.
DataQs can be valuable when incorrect information affects a carrier’s safety history, but it does not automatically remove legitimate violations.
Who can submit a DataQs request?
Motor carriers, commercial drivers, owner-operators, and other eligible stakeholders can submit requests through the system.
Users must create an account and follow the applicable sign-in process.
Motor carriers typically access DataQs through the FMCSA Portal, while drivers and public users can register through Login.gov.
The person submitting the request should have enough information about the disputed event to identify the record and explain why a correction is needed.
Representatives may also submit requests when appropriately authorized.
Is there a fee to file a DataQ?
No. FMCSA does not charge a fee to create a DataQs account or submit a standard Request for Data Review.
Companies can prepare and submit requests themselves.
Some organizations choose to work with consultants or legal professionals when dealing with complicated disputes, but those outside services are separate from FMCSA’s system.
Regardless of who prepares the request, providing accurate records and relevant supporting documentation remains essential.
A paid third-party service cannot guarantee that FMCSA or a State agency will approve a correction.
How long do DataQs appeals take in 2026?
Under the revised State review process effective September 18, 2026, covered requests generally have an initial decision deadline of 21 days.
Reconsideration decisions must generally be issued within 21 days of escalation, while Final Reviews have a 45-day deadline.
Applicants generally have 30 days after a decision to request the next available review stage.
Timelines may pause when additional information is requested.
These requirements apply to eligible State reviews submitted on or after the effective date. Crash preventability requests and certain other programs follow separate timelines.
What happens if my DataQs request is denied?
A denial does not always end the process.
Under the updated requirements for covered State requests, applicants can generally seek Reconsideration and then Final Review if they disagree with the previous decision.
Each stage provides an additional opportunity for independent evaluation.
Before requesting another review, read the agency’s explanation carefully and identify why you believe the determination was incorrect.
Reconsideration requests should be submitted within the applicable deadline. Simply repeating the original complaint without addressing the decision may not strengthen your position.
What documentation is needed to dispute a DOT violation?
The supporting documentation depends on the specific error being challenged.
Useful records may include roadside inspection reports, photographs, dashcam footage, maintenance documentation, ELD records, lease agreements, or court documents.
The evidence should relate directly to the information you believe is incorrect.
For example, if an inspection was assigned to the wrong motor carrier, documentation identifying the correct responsible carrier may be important.
Provide a concise explanation of the problem and identify the correction being requested.
The goal is to make the reviewing agency’s job easier by presenting clear, relevant evidence.
Can DataQs remove an out-of-service violation?
DataQs may result in an out-of-service violation being corrected or removed when the underlying information is inaccurate and the responsible agency approves the change.
However, repairing a vehicle after an inspection does not automatically invalidate the original violation.
An out-of-service order documents a qualifying condition identified during enforcement.
If that condition actually existed, the original record generally remains even after repairs are completed.
A successful request needs evidence demonstrating that the recorded information was incorrect or otherwise eligible for correction.
Will correcting a DataQ improve my CSA score?
It may, depending on the information corrected and how that data affects the carrier’s Safety Measurement System results.
Removing an incorrectly assigned inspection violation, for example, could influence the applicable BASIC calculation.
However, FMCSA does not assign every carrier one overall CSA score. It evaluates performance within individual categories using multiple data points.
An approved correction does not guarantee a particular percentile change.
Carriers should monitor their updated SMS data while continuing to address legitimate safety risks.
Can a dismissed citation be removed from FMCSA records?
A dismissed citation can affect how the associated inspection violation is treated in FMCSA’s safety systems.
Under FMCSA’s adjudicated citation policy, a not-guilty or dismissed outcome generally results in the associated violation being excluded from SMS calculations and the driver’s PSP report.
However, the original inspection record may remain available in other federal systems.
The appropriate DataQs request should include documentation showing the final adjudicated outcome.
A citation dismissal does not necessarily mean every historical record of the inspection disappears.
Can I dispute a crash that was not my driver’s fault?
Potentially. If the crash information itself is incorrect, a standard DataQs correction request may be appropriate.
If the reported crash is accurate but the driver could not have prevented it, the Crash Preventability Determination Program may be the appropriate option.
FMCSA reviews 21 eligible crash types under the expanded program for crashes occurring on or after December 1, 2024.
A Not Preventable determination removes the crash from the carrier’s Crash Indicator BASIC calculation, but the crash remains listed in FMCSA records.
Why can’t I find my inspection report in DataQs?
A report may not appear because it has not yet been entered into the federal system, the wrong State was selected, or the report number was entered incorrectly.
FMCSA recommends starting with a limited search using the State where the event occurred and another identifying field.
For inspection reports, users should follow the system’s instructions regarding report number formatting and State abbreviations.
If the report still cannot be found, DataQs provides an option indicating that the record is not visible in the search results.
Keep the original inspection documentation available when submitting the request.
How long does an approved DataQs correction take to appear?
Approved corrections may take time to appear because FMCSA systems follow different update schedules.
SMS and PSP generally update monthly, so a correction may not be visible immediately after an agency approves it.
The SAFER Company Snapshot follows a different schedule and displays a more limited set of information.
Companies should retain the approval documentation and monitor the system where the disputed record originally appeared.
If the correction remains missing after the applicable update cycle, contact the responsible agency.
Can driver training help reduce DOT violations?
Yes. Ongoing driver training can reinforce the procedures and regulatory knowledge needed to reduce preventable violations.
Topics such as Hours-of-Service compliance, vehicle inspections, driver qualifications, and maintenance reporting are important for commercial motor vehicle operations.
Safety managers can review inspection trends to identify recurring issues and assign training that addresses those specific concerns.
Training alone cannot guarantee compliance, but consistent education combined with preventive maintenance and management oversight can support safer operations.
A structured training program also gives organizations better documentation of the educational steps taken to address recurring problems.








