For most of its existence, DataQs has been the part of the Federal Motor Carrier Safety Administration's compliance system that fleets loved to hate. You could challenge an incorrect violation, but the challenge went back to the same agency, sometimes the same officer, that wrote it. Outcomes varied from state to state, and reviews could take months. Many carriers stopped bothering.
That changes this month! In April 2026, as part of the Department of Transportation's Pro Trucker Package, FMCSA overhauled the DataQs requirements for every state that receives federal Motor Carrier Safety Assistance Program (MCSAP) enforcement funding and the new rules take effect in mid-September. For the first time, states must run a three-stage independent review on strict deadlines and explain, in writing, what evidence they considered and why they decided the way they did.
It's a meaningful change, although a narrower one than some of the headlines suggest. Here's what's different, what stays the same, and what fleets should do about it.
What DataQs is
DataQs is FMCSA's system for requesting a review of federal and state crash and inspection data that a carrier, driver or other party believes is incorrect or incomplete. The requester files a Request for Data Review (RDR) explaining what's wrong and attaching supporting documentation. The request is routed to the agency responsible for the underlying record, usually the state that performed the inspection.
The volume was large, but still only a fraction of total violations. In 2024, DataQs received 63,548 requests concerning inspections and violations and another 8,314 involving crash data. Against roughly 3 million inspections, 5 million violations and more than 180,000 vehicles in reportable crashes each year, that works out to challenges on about 4.6% of crashes and well under 1.3% of violations.
Inspection data feeds the carrier's safety record and FMCSA's Safety Measurement System, the system FMCSA uses to identify and prioritize motor carriers for safety interventions. The same data also lands on the driver's Pre-Employment Screening Program (PSP) record, which prospective employers can use when evaluating a driver. A violation that shouldn't be there can affect both the carrier and the driver.
How it used to work
On paper, the old process was reasonable: file the request, the state reviews it, the record is corrected or the request is denied, and you could ask for reconsideration. In practice, carriers ran into three problems.
For one, the reviewer was often the issuer. Requests went back to the agency whose inspector wrote the violation, and in some states to the officer personally. In 2019 testimony before the Small Business Administration, OOIDA described a member who was cited for violating a federal regulation that “does not even exist.” His DataQ was denied by the same trooper who issued the citation. According to OOIDA, it ultimately took a lawsuit and thousands of dollars in legal fees, to get the violation removed.
There were no deadlines. A request could sit for weeks or months, and during that time the violation stayed on the record. Denials didn't always explain much either. Carriers complained that some reviewers wouldn't engage with the evidence, and a one-line denial gave them little indication of what had been considered or what to do next. Outcomes varied widely by state.
What changes in 2026
FMCSA Administrator Derek Barrs framed the reform as a matter of due process: anyone who challenges an inspection or crash record should get an independent, unbiased and completed review in a timely manner. The specifics:
Three stages, with independence built in. The initial review can't be decided solely by the officer who wrote the violation. Reconsideration must be handled by subject matter experts who weren't involved in the first decision. A final review goes to a senior decision-maker or independent panel.
Deadlines. Initial and reconsideration reviews each get 21 days. Final reviews must be completed within 45 days. If the reviewer asks the requester for more information, the requester has up to 14 days to respond.
Written explanations. Every decision, and especially a denial, must state what evidence was reviewed, why the decision was reached and what options remain.
Look-back windows. States must review requests filed within three years of an inspection or five years of a crash.
Accountability. States must designate points of contact and submit implementation plans for meeting the deadlines and clearing backlogs. FMCSA will publish state-by-state performance data, including average review times and completion rates.
What doesn't change
For all the changes to how requests are reviewed, the basic standard for challenging a violation hasn't changed.
A fixed violation is still not an incorrect violation and FMCSA is explicit on this. If the defect existed when the inspector looked at the truck, repairing it that afternoon doesn't make the record wrong. The cases that belong in DataQs are ones where there is a legitimate basis to believe the underlying record is inaccurate: a violation assigned to the wrong carrier, a defect recorded twice, damage caused by the crash that triggered the inspection, a citation later dismissed in court, or a violation the fleet can show wasn't there.
The requester still has to make the case that the record is inaccurate. The state doesn't build that case for you. Under the new process, however, the request goes through defined stages of review, with independence requirements, deadlines and a written response.
The data also remains public while the challenge is pending. Industry groups asked FMCSA to suppress disputed records until a decision is made, but that didn't make it into the final rule.
The reform only binds states. The federal-level appeal and FMCSA's own reviews were already structured; the new requirements target the state agencies that handle the overwhelming majority of inspection challenges.
How fleets should approach DataQs
The changes make it worth revisiting how your fleet handles DataQs. A few things should change.
Pick your battles, but pick more of them. Don't dispute violations you simply don't like. At the same time, plenty of carriers stopped filing legitimate challenges because they concluded the process wasn't worth the effort. With independent review, deadlines and written explanations now required, there is more reason to pursue a challenge when you have a legitimate basis for one.
Know which cases are easiest to document. Wrong carrier or wrong vehicle, duplicate entries, adjudicated citations, and crash-caused damage recorded as pre-existing defects tend to have a clearer documentary trail. A disagreement over whether a brake or light was working at the time of an inspection depends heavily on timestamped records from that day.
Check your data regularly. SMS updates monthly. A violation you don't see until an insurance renewal or a customer audit is a violation you've had less time to investigate. The three-year and five-year windows are generous, but evidence gets harder to assemble the longer you wait.
Give the reviewer the full story. FMCSA's guidance has always asked for a detailed explanation with documents attached. Under the new rules, the reviewer has to state what evidence was considered. Lay out what the record says, what happened, and which document supports each part of your account.
Be ready for the 14 day request. If the reviewer asks for more information, you have two weeks. That's plenty of time when the DVIR, repair order, photo and inspection report are already connected to the asset but gets much harder when someone has to reconstruct the day from a text thread and an email inbox.
Use the three stages. An initial denial doesn't necessarily settle the matter anymore. Reconsideration goes to different people, and the written denial should tell you what they found unpersuasive. That gives you an opportunity to address the specific issue rather than simply resubmitting the same package.
Involve the driver. Drivers can file their own RDRs, and the PSP consequences fall on them. A driver's pre-trip inspection, photos and account of the stop may also be some of the most contemporaneous evidence available.
Watch the state data. Once FMCSA starts publishing review times and completion rates by state, fleets will be able to see which agencies are meeting the new standards and which are falling behind. That will be useful context for setting expectations and, where necessary, escalating a request that isn't being handled according to the new requirements.
How maintenance fits
A surprising amount of the evidence comes from maintenance records created long before anyone knows they'll be needed.
Consider a roadside violation for an inoperative brake light at 3:40 p.m. on a truck whose lamp was replaced that morning. A useful record might include the driver's defect report, the repair order, the technician's photo and sign-off, and timestamps showing when each event occurred. No single item establishes the condition of the lamp at 3:40. Taken together, they give the reviewer a contemporaneous account of the truck's condition and what happened earlier that day.
After a crash, the sequence can matter even more. A tire damaged in the collision may appear as a defect when an officer inspects the truck afterward. Photos from the scene, the morning's pre-trip, dashcam footage, telematics events and repair history can help establish when the damage occurred.
The problem for many fleets is that these records are scattered. The DVIR is in one system, the work order in another, the photo is on someone's phone, and the inspection PDF is sitting on a desktop. Months later, someone has to reconstruct the history.
Keeping those records connected as part of the asset's history makes that reconstruction much easier. The original defect report can stay linked to the repair that closed it. Photos and technician sign-offs can stay with the repair. Vendor paperwork can be tied to the same event, and roadside inspections can become part of the asset record.
There are plenty of reasons to do this even if the fleet never files a DataQ. The same history is useful during audits, repeat-failure investigations, vendor disputes and accident reviews. If a DataQs challenge does come up, much of the evidence is already organized.
The bottom line
The new DataQs rules don't make every challenge successful, and they don't make a legitimate violation disappear. They put more structure and accountability around the review: independent reviewers, deadlines, and a written explanation of what was considered.
For years, fleets could reasonably ask whether a challenge was worth the effort. The new rules are meant to make the answer less dependent on how a particular state handles DataQs and more dependent on the evidence a fleet can produce.That's a better problem to have, and it's one a fleet can actually prepare for.
Axle Mobility automates the paperwork-heavy work behind fleet maintenance, so fleets and service providers spend less time chasing records and more time keeping equipment moving