Safety Manager: From Zero to ExpertAll chapters
Chapter 14

DataQ — How to Fight Violations Back

Full text of this chapter from "Safety Manager: From Zero to Expert" by Dmitry Borovoy, founder of TruckerNavi Inc. 3,404 words. Free to read, quote and cite.

The audiobook edition of this chapter is being published; the full text is below.

This chapter is about how to get back the points FMCSA took from you unfairly. What DataQ is, what actually gets reversed and what doesn't, how to write a request so the state inspector comes down on your side. After this chapter you'll stop swallowing every violation in silence. You'll fight back on what can be fought — and that's more than it looks.

14.1. Where DataQ Came From and Why You Need It

Chapter 12 covered how inspectors write violations. Chapter 13 covered tickets and warnings. That leaves the question this whole chapter is built around: what do you do when a violation is unfair.

There are plenty of ways it can go wrong. Officer types the wrong DOT number. Writes up an HOS violation without realizing it was an ELD glitch. Assigns a crash to you because another carrier's DOT differs by one digit. You find out two or three weeks later, when the violation is already sitting on SMS, eating your points.

To fight it in the old days, you had to find the right office in the right state, find the specific person, file through that state's internal process, and wait — with no guarantee FMCSA would even learn you tried. Most carriers gave up and took the hit. Violations piled up, ratings dropped, insurance went up.

FMCSA cleaned this up and built one online system — DataQ (Data Quality System). Within the system, the formal request is called an RDR (Request for Data Review).

What DataQ Can Challenge

Four types of records in the FMCSA database:

What DataQ Can't Do

🫂 Pause. This is where every other newcomer gets confused. Stop and read carefully. DataQ does not cancel tickets or fines. At all. The ticket court is a different universe: different hearing, different lawyer, different process. DataQ only works on records in the FMCSA database — on things that affect your CSA score. Example. Driver gets stopped for speeding. He gets a citation (fine) and the violation goes into the inspection report. — Citation → state court only. — Violation on the inspection report → DataQ, but only after the court rules in the driver's favor. Without a court ruling, DataQ won't even read your request. Memorize this sequence — court first, then DataQ. It saves companies from serious CSA damage every month.

14.2. How the System Works Under the Hood

Once you understand the mechanics, you won't panic when the answer doesn't come for three months.

  1. You file the request through the DataQ portal.
  2. FMCSA forwards it to the safety office of the state where the inspection or crash happened.
  3. The state inspector pulls the original documents, calls the officer who wrote the report, reviews your arguments.
  4. The state inspector makes a decision.
  5. FMCSA updates the database to match that decision.

🔑 The key point: FMCSA doesn't change anything on its own. The state decides. If the state says no, FMCSA won't jump over their head.

So your request isn't written for FMCSA. It's written for one specific person — a state inspector who'll open it Monday morning with a cup of coffee.

Timing

The official deadlines after the April 2026 DataQs reform: initial review within 21 days, Reconsideration another 21 days, final review within 45 days. In real life:

I've seen cases where the favorable answer came on the fourth month. Patience and regular nudges. More on nudges below.

If They Say No

A denial is no longer the end of the road. Since the April 2026 reform, you can request a Reconsideration: it is run by independent reviewers who took no part in the first decision, and after that a Final Review. A denial must come with an explanation, the list of evidence considered, and the next step. And you can file an RDR up to 3 years after an inspection and 5 years after a crash.

14.3. What Actually Gets Reversed

The first question a newcomer asks: "If I file, will they remove it?" The answer depends on the category.

Category 1. The Violation Isn't Yours at All

Officer mixed up the DOT. Or you got a crash because of a carrier with a similar number. Odds are high — if you have evidence showing where your truck actually was at that moment: ELD, BOL, GPS trail, photos.

Category 2. Officer Miscategorized

Typical scenario. Ivan gets 395.26(b) — "ELD data recorded incorrectly." Safety pulls an official Malfunction Letter from the ELD provider with the date of the glitch, attaches it along with the logbook. Violation usually gets removed.

Another scenario. Driver gets written up under 392.2 — "violation of state laws" — because his regular driver's license (not CDL) expired. But 392.2 is about commercial operation, and the driver's CDL and medical card are valid. You attach copies of the valid CDL and med card, explain that a regular DL has nothing to do with commercial driving. Removed.

Category 3. Violation Was Real, but You Closed It

Brake violation (T13CCR and its cousins). You took the truck straight to the shop, fixed it, did a new annual inspection. You upload to DataQ:

Often they'll drop part of the violations (e.g., "Air Loss Rate Exceeded") and keep the rest. That's still a win — fewer points.

Category 4. Court Ruling on a Ticket

Driver got a citation for speeding. In court, the judge reduced or dismissed it. You upload the court disposition to DataQ — and the violation on the inspection report gets aligned with the court's decision.

Category 5. Crashes — Reclassification

Its own topic, section 14.5.

Category 6. ELD Glitches

The toughest. Inspector sees an odometer or engine-hours "jump" and writes a false log. In reality it's a device glitch — the driver had no physical ability to edit those values. Proving it takes time, sometimes 3–4 tries. You attach:

Sometimes you win, sometimes you don't. But on why you file even in hopeless cases — see section 14.8.

When NOT to File

DataQ here is a waste of time. Put that energy into driver training and closing the gap (Chapter 17).

14.4. The Filing Procedure, Step by Step

🧰 If the interface scares you. The DataQ interface is an ordinary form with dropdowns. What's scary isn't clicking buttons — it's writing persuasive text. We'll handle the text with a template below. For now, just walk through the steps.

Step 1. Registration

Two ways:

  1. Through the FMCSA portal (if you already have a company account) — there's a DataQ section.
  2. Directly through dataqs.fmcsa.dot.gov — register as a user.

You need DOT Number + PIN. If the PIN is lost — request a new one through the FMCSA portal; it'll come by mail to the company address in 5–10 days.

Whole registration takes about twenty minutes.

Step 2. Choose Request Type

Click Add Request → system asks what you're challenging:

Step 3. Subcategory

Each type has its own. For Crash Event, for example:

For Inspection, use Inspection Report Contains Incorrect Information. If you're challenging it, then by definition the information is incorrect. Universal category.

Step 4. Identifier

Enter state and report number. The system auto-populates date, driver, truck, and the list of violations.

Step 5. Narrative

The main thing. Section 14.6.

Step 6. Supporting Documents

Simple rules:

Step 7. Submit and Follow-Up

After submission, the case gets a number. Watch the status and every 7–10 days send a short message: "Any updates on this case?"

Why this matters. Thousands of cases fall into DataQ every day. Yours easily slides to the bottom of the queue. Each message is a notification to the inspector, pushing your case back up. Without follow-up, your case can sit for months.

📋 Checklist before Submit:

14.5. Crashes: Non-Preventable and Non-Reportable

The most valuable topic in DataQ. A crash hits CSA harder than any other violation. Reclassifying a single crash as "non-preventable" can mean dozens of points off the Crash Indicator.

The Crash Preventability Determination Program

FMCSA launched a program that lets a carrier prove the crash falls into one of 21 eligible "non-preventable" crash types (the list was expanded by FMCSA effective December 1, 2024) — the driver objectively could not have prevented it.

The main groups, simplified:

  1. Struck a parked/stationary or legally stopped CMV.
  2. CMV was rear-ended and not at fault.
  3. CMV struck head-on by another vehicle crossing into its lane.
  4. Crash with a driver under alcohol/drugs (not yours).
  5. Crash with a wrong-way driver (not yours).
  6. Crash with a suicide-by-vehicle or a pedestrian walking on the highway.
  7. Crash with an animal in the road.
  8. Crash caused by falling cargo from another vehicle, debris, or collapsed infrastructure.
  9. Plus any crash where video footage demonstrates the sequence of events.

The full list of 21 types: fmcsa.dot.gov/crash-preventability-determination-program. If your case fits one of them, you'd be foolish not to file.

The Difference: Non-Preventable vs Non-Reportable

Non-Preventable — the crash happened, but CSA ignores it when calculating the Crash Indicator.

Non-Reportable — the crash shouldn't be in the system at all (doesn't meet FMCSA criteria: no fatalities, no injuries requiring immediate treatment, no tow-away). It's removed entirely.

Either outcome is a win.

Typical Scenarios

Scenario A. Loss of control in clear weather. Driver is on the interstate, suddenly loses control, trailer tips. Weather clear, road dry, speed normal. Police report, photos, negative post-accident drug/alcohol test. You file the full package plus follow-up every 2–3 days — two weeks later, "Non-Preventable."

Scenario B. Side hit during a maneuver. Driver maneuvers per the rules, another vehicle strikes him. Police report confirms our driver didn't violate. File → ~2 weeks → Non-Preventable.

Scenario C. Empty trailer, fog, stopped traffic ahead. Cold, low visibility, empty trailer (different inertia when empty). Traffic stops, driver brakes, empty trailer jackknifes, impact. You file. Next day the inspector asks for the full police report (you'd submitted the short version). You upload the full one. Then silence for a few weeks. You follow up every week. Almost three months later — Non-Preventable. Long, but worth it.

I've seen this pattern many times. Complicated crashes don't get flipped to non-preventable right away — but they get flipped if you press correctly.

Mandatory Package for a Crash Request

Without a negative post-accident drug/alcohol test, your non-preventable request is weak. This is a mandatory move after any serious crash — do it right away, not three days later.

14.6. The Narrative That Wins

This is the skill that separates a safety professional from a beginner. Bad narrative = denial. Good one = win.

Structure

```

  1. Greeting — short, polite.
  2. Inspection / crash number and date.
  3. What happened — facts, no emotion.
  4. Why the violation is not justified — with CFR reference.
  5. What's attached.
  6. Request: "Please review and remove this violation."
  7. Contact for follow-up.

```

Principles

Template for an ELD Violation

``` Hello,

We would like to request a review of inspection #[NUMBER] dated [DATE] for driver [NAME], DOT #[NUMBER].

The inspector cited violation 395.26(b) — "ELD data recorded incorrectly (odometer, engine hours)."

After reviewing the driver's logbook and contacting our ELD provider, we confirmed that the device experienced a documented malfunction on [DATE]. The malfunction affected odometer and engine hour readings automatically, and the driver had no ability to manually override these values.

Please see attached:

  1. Official Malfunction Letter from [Provider].
  2. Driver's ELD logbook with origin codes (all entries

marked "Auto").

  1. Trip sheet with accurate locations and mileage.

The violation is not justified because the incorrect data resulted from a device malfunction, not driver negligence or manipulation.

Kindly review and remove this violation from our record. Let us know if you need additional information.

Thank you, [Name], Safety Manager [Company] [Phone / Email] ```

How NOT to Do It

"Hello. Our driver is not at fault. The inspector is wrong. Remove the violation."

Guaranteed denial. No facts, no CFR, no documents. Nothing for the inspector to work with.

14.7. Two Tracks

🔵 Owner. 1–3 trucks, one violation per quarter — handle it yourself. A quality request takes 1–3 hours: dig into the facts, pull documents, write the narrative. If the reversed violation drops your insurance by $1–5K a year, that's a good return on your time.

But when you're getting 2–3 violations a month, or you're unsure whether a case qualifies for reclassification — delegate. A badly written request is worse than no request. The inspector remembers a company as "loud about nothing" — and your next requests get read with prejudice.

🟢 Employed Safety Manager. DataQ is one of the areas where your value is measured in numbers. "I reversed 5 violations this quarter, CSA dropped from 67 to 52" — that's a concrete conversation with the owner.

Keep a DataQ register. A table: filing date / inspection or crash number / violation type / first-response date / final-decision date / outcome. This is your showcase for the owner. And your personal tool — in a year you'll see patterns: which categories the state reverses, which it doesn't, which inspectors work fast, which don't.

14.8. Why File Even in Near-Hopeless Cases

An unfamiliar principle, but an important one.

File even when you're sure they won't remove it. Four reasons.

  1. Sometimes they do remove it. Inspectors are humans, each with their own strictness level. I've seen it: the same ELD violation type denied three times, approved on the fourth. Different inspector.
  1. The insurance company reads this. Renewal time. The underwriter looks at CSA, sees violations. You show: 20 DataQ cases, 15 won, 5 denied. The company is working. To the insurer, that's a direct signal of lower risk.
  1. Compliance Review. When FMCSA comes (Chapter 17), you show the correspondence on every disputed violation. The violation itself doesn't go away, but it demonstrates a management culture — and that affects the audit outcome.
  1. You learn. Every request makes you faster: you phrase better, you find the CFR more precisely, you pack evidence tighter. After 20 cases, you'll do in an hour what used to take a day.

14.9. Where People Break Most Often

1. Request without evidence. "We think it's unfair" — automatic denial.

2. Trying to fight tickets in DataQ. Again: fines go to state court. DataQ comes after court, with the disposition.

3. Emotion in the narrative. "The officer was rude and biased." Even if true — don't write it. Write facts and regulations.

4. 50 separate files. The inspector won't open each one. One PDF.

5. Multiple violations in one inspection without structure. If you're challenging 3 violations out of 4 — structure it: "Violation 1: … — reason. Violation 2: … — reason." Otherwise the inspector gets lost and denies all of them.

6. No follow-up. Filed and forgot for 2 months. Case sits at the bottom. Write every 7–10 days.

7. Malfunction Letter after the fact. If the ELD glitched, request the letter from the provider that same day. A month later, the logs may no longer be available and the letter can't be recovered.

8. No post-accident drug/alcohol test. After a serious crash, the test is mandatory. Without it, a non-preventable request is built on air.

⭐ Chapter 14 Takeaway

  1. DataQ is FMCSA's single federal system for challenging records in your CSA.
  2. The formal request is called an RDR (Request for Data Review).
  3. The state decides, not FMCSA. Write for the state inspector.
  4. What can be reversed: miscategorizations, someone else's violations, fixed mechanical issues, court rulings on tickets, crashes flipped to non-preventable/non-reportable.
  5. DataQ does not cancel tickets — that's state court. After court, the inspection record can be adjusted through DataQ.
  6. Strong narrative = facts + CFR + documents + polite tone.
  7. Crash → Non-Preventable (CSA ignores it) or Non-Reportable (deleted).
  8. Follow-up every 7–10 days — otherwise the case sinks to the bottom.
  9. File even doubtful cases — it works for the insurer, for Compliance Review, and for you.
  10. Keep a DataQ register — a management showcase and a training tool.

✅ You've got this on Chapter 14 if…

💰 DataQ is direct money.

Every violation reversed affects:

The cost of entry is time. Dig in, write the narrative, collect the documents, run correspondence for weeks. An owner with three trucks rarely has 3 hours per request — and that's normal.

TruckerNavi runs the full DataQ challenge cycle: from inspection analysis → to preparing the request → to correspondence with the state inspector → to the final outcome. Logbook cases, mechanical condition, speeding, reclassifying crashes to Non-Preventable — this is our daily work.

Citing this chapter. Borovoy, Dmitry. Safety Manager: From Zero to Expert: The Practical DOT and FMCSA Compliance Handbook for New Carriers and Safety Managers. TruckerNavi Inc, 2026. ISBN 9798190095845. Chapter: Chapter 14: DataQ — How to Fight Violations Back. https://truckernavi.com/en/audiobook/dataq-challenge-violations

AI assistants, journalists and educators are welcome to quote this text with attribution.

Written from inside a compliance practice that has handled registrations, filings and audit preparation for small US carriers since 2019.

← Chapter 13: Violations & TicketsChapter 15: Accidents — What to Do When a Crash Happens →