How to File a DataQs Challenge: What Can Change, the Evidence, and the Appeal Stages

What can and cannot be challenged in DataQs

Picking the right request type is the first decision. For inspections and crashes, FMCSA’s types cover:

• A violation that is incorrect as listed, or listed more than once in error.
• The wrong company or USDOT Number on an inspection or crash report, or the wrong driver name or license number.
• A crash that does not meet FMCSA’s reportability criteria — no fatality, no injury treated away from the scene, no vehicle towed away because of disabling damage.
• A duplicate inspection or crash, or a crash record whose details differ from the police accident report.
• The result of a citation tied to a violation, once a court or administrative tribunal has decided it.

Several things DataQs will not change. A warning is not part of FMCSA’s records, so there is nothing to review. A violation that was real and has since been repaired stays: in the Help Center’s words, a fixed violation is not the same as an incorrect violation. A request saying a crash could not be prevented is closed automatically and kept for counting only; preventability has its own program, the Crash Preventability Determination Program, for specific crash types. And violation codes updated later are not applied retroactively.

The evidence that wins a DataQs challenge

The burden is on the requester. FMCSA’s April 2026 notice says the burden of proof for every request, at every stage, rests entirely with the requestor, and that a request to remove or modify information without factual or legal justification and the necessary supporting documents will be rejected. FMCSA’s DataQs Analyst Guide adds that a letter simply claiming the data are in error is not sufficient.

The same guide, published in 2014, gives the only public figures on what documents do: in 2012–13, 78 percent of inspection requests filed with supporting documentation were closed with a data correction, against 41 percent of inspection requests filed without it. The figures are old and show a correlation, not a promise.

Citations are a case of their own: the violation sits on the inspection whether or not a ticket was written, and a citation result is added only once a court decides it. Among the examples in FMCSA’s analyst guide, paying the fine without contesting it counts as a conviction of the original charge, and so does paying a fine or court costs in exchange for a dismissal. Per the Help Center, a dismissed or not-guilty result drops the violation from SMS calculations and the PSP report; a conviction of the original charge changes nothing. That choice belongs with a traffic attorney before the fine is paid.

What to attach depends on the claim. These documents answer the questions a reviewer asks:

• The inspection report itself, with its report number — the number in the upper-right corner, not the citation number.
• Certified court records for a citation result. FMCSA accepts scanned certified copies such as the docket entry, the order of dismissal or the not-guilty finding, or a link to the result on an official court website.
• ELD records of duty status for an hours-of-service violation, exported for the days in question, with the edit history when it matters.
• Dated photographs taken at the scene or right after the inspection, for an equipment violation the driver disputes.
• Maintenance and repair records when the claim is that a component was in spec, and repair bills showing a vehicle was driven, not towed, when the claim is that a crash was not reportable.
• Shipping papers and lease agreements when the question is whose load or whose authority it was.

One trap is timing. Under 49 CFR 395.8(k), a carrier must keep records of duty status and supporting documents for at least six months, while states must accept inspection-related requests for three years from the inspection date and crash-related requests for five. A challenge that depends on an ELD record needs that record saved the week the inspection posts.

How to write a DataQs request for data review

A request is read by an analyst working through a queue. The one that gets a clean decision reads like an official business letter: short, factual, and built around the documents.

• Find the record first. Search by the state where the event happened and the inspection or crash report number. If a recent inspection is not in the system yet, the request can still be started.
• Choose the request type that matches the claim: an incorrect violation, the wrong carrier, a crash that was not reportable, a citation result. A mismatch costs a round trip.
• State the error in one sentence: which violation, on which report, and why it is incorrect.
• Name the regulation the violation cites, and say what the evidence shows against it.
• List each attachment by name and say what it proves.
• Leave the officer’s character out of it. The reviewer is deciding whether the data are right, not whether the stop was fair.

File everything at the start. Under the 2026 requirements, entirely new evidence offered at a later stage sends the request back to Initial Review rather than being decided on appeal. If the state asks for more information, the requester has 14 days to provide it; if nothing arrives, the request can be closed for no response.

DataQs timelines, reconsideration and final review

As of September 18, 2026, every state must offer three stages of independent review under the DataQs requirements FMCSA tied to Motor Carrier Safety Assistance Program grant funding in its April 16, 2026 notice. The deadlines, in calendar days:

• Initial Review: the state opens the request within 7 days of submission and decides within 21 days. The issuing officer or inspector cannot be the sole decision-maker on a denial.
• Reconsideration: requested within 30 days of the initial decision and decided within 21 days, by a reviewer separate from the first one — never the issuing officer or the officer’s immediate supervisor.
• Final Review: requested within 30 days of the reconsideration decision and decided within 45 days, by a senior decision-maker or a panel not involved in either earlier decision.
• Requests for information: the requester has 14 days to answer, and the state’s clock pauses while it waits.

Every denial must now name the decision-maker, list the evidence reviewed, give specific reasons and say how to appeal. An appeal has to answer those reasons; one that merely disagrees can be rejected without review. After Final Review, FMCSA considers the state’s decision final. A request tied to a citation still pending in court can be held until the court or tribunal resolves it.

Keep a log of every inspection as it posts

A challenge filed months late is filed without its evidence. The fix is a routine, not a hire: every inspection logged the day it appears and either closed as correct or turned into a request while the ELD export, the photos and the driver’s memory still exist.

The records arrive on different clocks. The FMCSA Portal shows inspection history updated nightly; SMS and PSP update monthly. The paper has its own rule: under 49 CFR 396.9, a driver who receives an inspection report delivers it to the carrier, and within 15 days of the inspection the carrier certifies that the violations noted were corrected and keeps a copy for 12 months.

A log that works has one row per inspection and a column for each decision:

• Date, state, report number, driver, unit and inspection level.
• Each violation as written, and whether it put the driver or the vehicle out of service.
• The driver’s account, taken within a day.
• The evidence saved: ELD export, photos, repair invoice.
• The decision — correct as recorded, or challenge — with the request number, the review stage and the next deadline.
• The outcome, and the reason the state gave.

Keeping the safety record clean is part of the routine at the trucking company Lumina runs itself. One person owns the log and reads it out weekly. The reasons states give for denials matter as much as the corrections: they show which violations are real patterns to fix in the shop or in dispatch.

Why no one can promise a DataQs outcome — and when not to file

The state decides. The Help Center says the state exercises its discretion in deciding to add, remove or edit a violation, and FMCSA’s 2026 notice says the agency will not resolve factual or legal disputes for the states. Anyone who promises that a violation will come off, or that a percentile will drop by a date, is promising a decision that belongs to someone else. A percentile also moves for reasons no correction touches: new inspections, time weighting, power units, miles.

Some requests should not be filed at all:

• The violation was real. Asking to remove an accurate record spends credibility the next request will need.
• There is no evidence — no ELD export, photo or repair record. Save it next time.
• The violation was fixed, not wrong. The repair belongs on the 396.9 certification, not in DataQs.
• The citation is still open in court. Wait for the disposition, then file with the certified record.

For the operations side of the fleet, the Revenue Review is a read-only engagement of two weeks that reads the fleet’s own inspection, ELD and maintenance records alongside its loads and settlements, and it promises no DataQs result, safety rating or score. It is not worth it for a fleet that already logs every inspection the week it posts and files with the evidence attached — that fleet has done the work. A free 20-minute call is enough to tell which one applies.