FMCSA DataQs Appeal Deadlines Take Effect for Safety Records

New DataQs requirements begin today

Motor carriers and commercial drivers disputing state-reported safety data now have a more defined path for review. As of September 18, 2026, revised Federal Motor Carrier Safety Administration requirements for the DataQs system are in effect for state Requests for Data Review, or RDRs.

The changes establish deadlines, require a three-stage review structure when a case is escalated, and call for more detailed explanations when a state decides not to correct a record. DataQs is FMCSA's system for challenging Federal and state data that a driver, carrier, or other user believes is incomplete or incorrect.

For trucking businesses, the development matters because inspection, crash and violation records can affect safety monitoring, hiring decisions, customer vetting, insurance discussions and internal compliance work. For drivers, it provides a more structured process for seeking correction of inaccurate information connected to an inspection or crash.

The new process does not guarantee that a challenged record will be changed. Requestors still need to present a valid, well-documented case. But it does create clearer expectations for who reviews a request, when a decision should arrive and what happens if a requestor seeks another review.

What changed on September 18

FMCSA's revised DataQs requirements apply to states receiving Motor Carrier Safety Assistance Program, or MCSAP, funding. The requirements are tied to those states' participation in the federal safety-assistance program.

The most visible change is the required three-stage process for eligible state data reviews:

1. **Initial Review:** The state reviews the initial request. A denial cannot be decided solely by the officer who issued the underlying inspection finding. 2. **Reconsideration Review:** If the requestor seeks reconsideration, the matter moves to an independent reviewer or group with subject-matter expertise that was not involved in the first decision. 3. **Final Review:** A further escalation goes to a senior decision-maker or an independent panel for a final determination.

The process is meant to separate later review decisions from the people directly involved in the initial enforcement event or first denial. States also must provide detailed explanations and identify the evidence considered when they close a request without making a correction.

FMCSA says DataQs processed more than 71,000 requests in 2024, including more than 8,300 crash-data requests. That volume shows why a consistent system for routing, documenting and resolving challenges matters to carriers and drivers across state lines.

The deadlines carriers and drivers should know

The revised process adds concrete timelines for state handling of RDRs:

• States must open an Initial Review request within **seven days** of submission.
• States must issue and communicate an Initial Review decision within **21 days** of submission.
• A Reconsideration Review decision is due within **21 days** after the matter is escalated.
• A Final Review decision is due within **45 days** after escalation.
• Requestors have **30 days** after a decision at one stage to seek Reconsideration or Final Review.

There is an important qualification: if a state requests more information, its decision clock is paused while the requestor has up to 14 days to respond. That makes fast, complete responses important.

FMCSA also advises requestors to submit all relevant facts and records with the Initial Review whenever possible. If entirely new information is introduced during Reconsideration or Final Review, the request can be sent back to the Initial Review stage rather than continuing on the appeal path.

What records can be challenged

DataQs is not a tool for relitigating every enforcement outcome. It is the channel for requesting review of FMCSA or state data believed to be incomplete or incorrect.

Common examples can include information associated with:

• Roadside inspection reports and violations;
• Crash records;
• Safety audits or investigations;
• Carrier, vehicle or driver identification errors;
• Incorrect assignment of a crash or inspection to a motor carrier; and
• Other state-reported safety information in FMCSA systems.

The state where the event occurred generally handles state-related requests. That means a carrier based in one state but inspected in another should make sure the event state and report number are correct when creating the request. Entering the wrong state can send the case to the wrong agency and add delay.

FMCSA's DataQs Help Center notes that Crash Preventability Determination Program requests and Drug and Alcohol Clearinghouse petitions follow their own processes and timelines. Users should not assume the new state RDR timetable automatically applies to those separate programs.

Why documentation now matters even more

The new deadlines should not be mistaken for a shortcut. A quick submission with limited proof may be harder to resolve and can trigger a request for additional information.

Drivers and carrier compliance teams should preserve the records tied to an event as soon as possible. Depending on the issue, useful documentation may include:

• The inspection report number and a complete copy of the inspection;
• Crash reports, photographs, dash-camera footage or location data where available;
• Shipping papers, bills of lading and lease documents when carrier responsibility is disputed;
• Vehicle, driver or unit records that establish identity or assignment; and
• Court or administrative disposition documents when relevant to the record at issue.

The right documentation depends on the type of RDR. The practical point is to explain precisely what data is believed to be wrong, identify the requested correction and upload evidence that directly supports that position.

A generic complaint about a citation or an inspection outcome may not give the reviewer enough to evaluate a data-quality issue. Clear event details, report numbers, dates and supporting records can reduce follow-up questions and avoid an avoidable pause in the review timeline.

What fleets should do now

Carriers should update their safety-data workflows rather than treating DataQs as an occasional administrative task. The new system gives fleet teams measurable dates to track, which makes ownership and follow-up more important.

A practical compliance checklist

• Assign a person or team to monitor new inspection and crash records promptly.
• Establish an internal deadline for deciding whether a DataQs request is warranted.
• Keep a file of event records before memories, electronic logs or documents become harder to obtain.
• Record the DataQs request ID, submission date, state agency and stage of review.
• Calendar the 30-day window for reconsideration or final review after each decision.
• Respond quickly if the state asks for additional documentation.
• Review a denial carefully before escalating, including the evidence reviewed and the agency's explanation.

Recruiters and staffing agencies may also benefit from understanding the change. Safety-record questions can arise during driver qualification and placement, but an inspection or crash record under review is not the same as a corrected record. Organizations should maintain accurate status notes and avoid representing that a DataQs request has changed a driver's or carrier's official safety data before a determination is completed.

What to watch next

The first test of the revised system will be implementation by the states. FMCSA requires state agencies to maintain DataQs implementation plans, and approved plans are available through the DataQs Help Center. Those plans should help carriers understand how an individual state assigns reviewers and administers its process.

Fleet compliance teams should also watch whether states meet the new opening and decision timelines in practice, particularly on complex crash disputes and requests requiring documents from local agencies. FMCSA has said it will review state compliance as part of its MCSAP oversight.

For now, September 18 marks a meaningful operational change: disputes over many state-reported safety records now come with a clearer escalation route, defined response targets and stronger documentation expectations. Drivers and carriers that act quickly, preserve evidence and track their case through every stage will be in the best position to use the revised DataQs process effectively.