Guide

The same inspection listed twice: what DataQs reviews

When one roadside inspection appears more than once on your USDOT number, the DataQs request type is "Inspection—Duplicate (Same Inspection Listed Multiple Times)". This guide quotes what FMCSA's Analyst Guide tells the State analyst to check.

On this page

Prepare your request: evidence checklist

  • Identify the inspection report number, State and date, and the exact field or violation you dispute.
  • Identify both records of the same inspection, including their report numbers, dates, vehicle and State. Explain what demonstrates that they describe one event and which duplicate entry should be corrected. Repeating a violation code within one report is a different issue from duplicate inspection records.
  • Suggested supporting records: the original inspection report and copies of both disputed database entries. The Guide requires the analyst to compare the original State report and the submitted evidence (§6.10, p. 57).

RoadsideProof's upload checklist is an intake condition for its optional automated completeness check. An inspection report that lets the software start is not proof that an RDR should be granted. The reviewing agency decides whether the evidence supports the correction. A record-error request does not require a court disposition merely because it is an RDR.

Next: submit the evidence with your own DataQs request, then track it and answer requests for more information. For State requests, use the deadlines guide to check the applicable review stage and response window.

The request type

FMCSA's DataQs Analyst Guide describes the situation as a filer "asserting that the motor carrier's MCMIS inspection file contains duplicate inspection records (i.e., the same inspection is listed more than once)." (§6.10, p. 57).

What the analyst checks first

"The DataQs analyst should review the original State report (crash or inspection) and SAFETYNET to verify the carrier assigned to the vehicle record in question." (p. 57).

"In addition, it is recommended that the vehicle in question be verified against the original State report." (p. 57).

Your documents and the inspector

"Second, review all documentation (if any) submitted by the filer to justify his/her request to modify the inspection file in MCMIS. If the DataQs analyst finds that the filer's documentation is inadequate, the analyst should contact the filer via the DataQs website and request additional information. Upon receipt of additional documentation, he/she should contact the MCSAP inspector responsible for the inspection report to discuss the issue at hand." (p. 57).

The burden of proof

The revised State DataQs process applies to requests submitted on or after September 18, 2026. It is not retroactive and does not establish deadlines for Federal reviews. The requestor bears the burden of proof at all three stages. A request to remove or modify information must explain the factual or legal basis for why it is incorrect or incomplete, with necessary supporting documents (91 FR 20567).

If the State agrees

"If the documentation confirms the existence of duplicate inspection records in the motor carrier's MCMIS inspection file, the DataQs analyst should take the steps necessary (according to his/her State's protocol) to update the inspection file. Corrections to MCMIS data should be uploaded within 7 days from the date that the State concluded an error occurred." (p. 57).

How long a review can be requested

The revised State DataQs process applies to requests submitted on or after September 18, 2026. It is not retroactive and does not establish deadlines for Federal reviews. The 2026 notice requires States to accept and conduct a good-faith review of inspection RDRs submitted within 3 years of the inspection and crash RDRs within 5 years of the crash (91 FR 20566).

How RoadsideProof handles this category

For this category the paid check looks for one document: the inspection report. The check is about whether the first filing is complete.

We do not file for you. You file from your own account and you sign it, and that signature carries 18 U.S.C. 1001.

We do not promise an outcome. The burden of proof is on the filer. The revised State DataQs process applies to requests submitted on or after September 18, 2026. It is not retroactive and does not establish deadlines for Federal reviews. Its stages are Initial Review, Reconsideration, and Final Review. FMCSA considers the State's RDR decision final after Final Review is completed; this is separate from a court's disposition of a citation.

Sources

FMCSA, DataQs Analyst Guide: Best Practices for Federal and State Agency Users, 2nd edition, December 2014, section 6.10, as hosted on the DataQs site and archived on 2026-05-26. Page numbers are the guide's own. Burden of proof: Federal Register, 91 FR 20567, FR Doc. 2026-07429.

Sources and factual review

Editorial source check: .

Document dates and data snapshot dates are separate from this editorial review. This review does not validate production calculations, document processing or storage controls.

More in Errors in an inspection record

See what it did to your score

Live lookup in the app for the USDOT you enter. Illustrative examples are separate from your results.

Unsafe Driving, HM Compliance and Crash Indicator are not included in this lookup.

What this lookup supports

What this lookup supports

Vehicle Maintenance

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Hours-of-Service Compliance

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Controlled Substances/Alcohol

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Driver Fitness

Reference codes: Available

Listed violations: When data and checks allow

Weighted numerator contribution: When data and checks allow

BASIC measure: When data and checks allow

Estimated position and range: When data and checks allow

Unsafe Driving

Reference codes: Available

Listed violations: Not offered

Weighted numerator contribution: Internal calculation only; not in lookup

BASIC measure: Not offered

Estimated position and range: Not offered

HM Compliance

Reference codes: Available

Listed violations: Not offered

Weighted numerator contribution: Not offered

BASIC measure: Not offered

Estimated position and range: Not offered

Crash Indicator

Reference codes: Not offered

Listed violations: Not offered

Weighted numerator contribution: Not offered

BASIC measure: Not offered

Estimated position and range: Not offered

The four supported BASICs require readable snapshot data and a computed measure to list violations or open a report. Estimated positions also require sufficient carrier data and passed publication checks; calibration failure can withhold a position or retain a dated previous estimate. Controlled Substances/Alcohol is subject to these checks too. Missing carrier data, no relevant inspections, no applicable violations and an unavailable calculation are different states. An unavailable result is not a zero or a claim that there are no violations. HM Compliance and Crash Indicator have no report calculation in this product.

Unsafe Driving’s SMS denominator is average power units × utilization factor, which depends on vehicle miles traveled (VMT) and carrier segment (Equation 3–1). Our product lacks the historical power-unit inputs needed to reconstruct and validate that full calculation. It calculates numerator points internally only; Unsafe Driving records, measure and estimated position are not offered in this lookup.

Severity weight is an input. Weighted numerator contribution accounts for time weighting and the inspection cap. The marginal change in a named BASIC measure also depends on its denominator. An estimated percentile compares carriers within a safety event group and must be read with its range. Do not add points across BASICs. SMS calculations are separate from an official safety rating. This is our estimate from public FMCSA data, not an official FMCSA percentile.

FMCSA SMS Methodology v3.21, Chapter 3 Safety rating: 49 CFR 385.3