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: .
- FMCSA RDR Request Type Definitions · March 2025 · p. 2 Archived copy of the checked edition
- FMCSA DataQs Analyst Guide · 2nd edition, December 2014 · Chapters 4–6 (requests, adjudicated citations and record errors) · §§4.13–4.14, 6.10 Archived copy of the checked edition
- FMCSA State DataQs review requirements · 91 FR 20561–20568, April 16, 2026 · pp. 20563–20568
- FMCSA DataQs Update Fact Sheet · document dated September 15, 2026 · p. 1 (requests submitted from September 18, 2026; system updates)
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