Driver Resources · Inspection Follow-Up

Post-Inspection & DataQs Action Kit

Organize a roadside inspection report, corrections, citations, supporting evidence, DataQs requests, decisions, and follow-up actions in one printable kit.

Start Action Kit
Clear To Roll

Your entries stay in this browser session. This public kit does not save, upload, or send the information you enter.

July 22, 2026 rule change: FMCSA’s completed-inspection-report rule takes effect July 22, 2026. The signed completed roadside inspection form must be returned to the issuing State only if that State requests its return. The carrier must still retain a copy for 12 months. Always follow the current report instructions and regulation.

DataQs is for data believed incomplete or incorrect. Repairing a defect does not automatically make the original inspection finding incorrect. This kit helps organize a review; it does not submit a request or determine whether a correction should be granted.

Using the public kit? This action kit is for planning and recordkeeping only. It is not legal, court, citation, DOT, FMCSA, DataQs, safety, insurance, carrier, employment, tax, accounting, or compliance advice. It does not determine whether an inspection finding, violation, citation, crash, carrier assignment, driver assignment, vehicle assignment, or other data is correct or incorrect. It does not determine whether a DataQs request should be filed or whether a correction will be made. Clear To Roll does not investigate, verify, approve, certify, screen, qualify, represent, appeal, file, submit, or guarantee any inspection, citation, repair, carrier, driver, vehicle, request, correction, decision, or outcome. Use current official sources, the inspection report, applicable regulations, agency instructions, court requirements, and appropriate professional guidance.

Privacy note: This public page does not upload, store, or send your entries. Avoid entering passwords, full bank information, full Social Security numbers, or other unnecessary sensitive information.

01

Handle the inspection first

Document safety corrections, out-of-service conditions, report instructions, repairs, and retention.

02

Review the data carefully

Compare every violation, driver, carrier, vehicle, citation, and event detail with source records.

03

Build a focused record

Organize supporting evidence, DataQs correspondence, decisions, and later SMS or PSP follow-up.

Public KitPost-Inspection Action Worksheet

Select the items that apply, record their status, and use the logs for each violation, evidence item, DataQs request update, and follow-up action.

1Inspection & File Details
Enter only the information needed for this inspection file. Do not enter Social Security numbers or unrelated sensitive information.
2Current Action Status
This is an internal planning status only. It is not an FMCSA, State, court, or DataQs decision.
3Filters
Inspection Report & Event Details›
Start with the official inspection report. Record the report number, State, inspection level, driver, carrier, vehicle, citations, and out-of-service information exactly as shown.
Use the full report — not a cropped photo or partial page — so every violation, unit, note, and instruction can be reviewed.
ReportCore
Not selected
DataQs generally uses the numeric inspection report number; the report number is not the same as a citation number.
ReportDataQs
Not selected
Use the State where the inspection occurred when searching for the record.
ReportSearch
Not selected
These details can help distinguish similar events and support a factual timeline.
ReportTimeline
Not selected
Note the level shown on the report, such as driver-only, walk-around, or full inspection.
ReportInspection
Not selected
Compare the report with the carrier that was actually operating the vehicle.
CarrierIdentity
Not selected
Check spelling, license number, State, and whether the correct driver is associated with the inspection.
DriverIdentity
Not selected
Review unit numbers, VINs, plates, plate States, makes, and vehicle types.
VehicleIdentity
Not selected
Use the exact report wording before deciding whether a data issue may exist.
ViolationCore
Not selected
Separate driver OOS, vehicle OOS, and non-OOS findings.
OOSSafety
Not selected
The inspection report number and citation number serve different purposes.
CitationRecord
Not selected
Keep the issuing agency information with the inspection file.
AgencyRecord
Not selected
Immediate Post-Inspection Actions›
Safety corrections and report-handling duties are separate from a DataQs challenge. Correcting a violation does not by itself prove that the original inspection data was incorrect.
Make sure the carrier or safety manager receives the report promptly and can begin the required review.
CarrierImmediate
Not selected
Do not return an OOS vehicle to service until the applicable condition has been corrected and operation is permitted.
OOSCritical
Not selected
Document when and how the driver became eligible to resume operation, if applicable.
OOSDriver
Not selected
Use an appropriate shop, technician, or service provider for the defect involved.
RepairSafety
Not selected
Capture the condition before work begins without interfering with enforcement or safe operations.
EvidencePhoto
Not selected
Keep dispatch records, tow bills, service tickets, and location details.
EvidenceExpense
Not selected
The form may include a return address, certification block, State-specific instruction, or due date.
ReportInstruction
Not selected
Effective July 22, 2026, federal rules require return to the issuing State only when that State requests it; always follow the current form and rule.
Report2026 Rule
Not selected
Use the report instructions and current 49 CFR 396.9; do not assume every State uses the same return process.
ReportDeadline
Not selected
Current federal rules retain the 12-month record requirement even when the State does not request return.
Recordkeeping12 Months
Not selected
Review contracts, policies, and company procedures for any separate notice obligation.
NoticeOperation
Not selected
Keep the report, repairs, photos, citations, DataQs materials, correspondence, and final disposition together.
OrganizationCore
Not selected
Violation-by-Violation Accuracy Review›
Review each finding separately. A repaired condition is not automatically an incorrect violation. DataQs is intended for Federal or State data believed to be incomplete or incorrect.
Confirm the code, regulation, unit, and narrative appear internally consistent.
ViolationAccuracy
Not selected
Document any mismatch precisely.
AttributionAccuracy
Not selected
Do not confuse multiple data rows in an SMS download with a duplicated inspection finding.
DuplicateDataQs
Not selected
Gather operating authority, lease, dispatch, and shipping evidence if carrier attribution is disputed.
CarrierDataQs
Not selected
Use identification and assignment records that relate to the inspection event.
DriverDataQs
Not selected
Identify the exact field believed to be incorrect or incomplete.
VehicleDataQs
Not selected
Separate minor clerical differences from facts that materially identify the event.
ReportDataQs
Not selected
Preserve interchange, lease, shipping, and equipment-control records.
IEPShipper
Not selected
Citation adjudication uses a specific DataQs request reason and supporting documentation.
CitationDataQs
Not selected
DataQs is not a general appeal of enforcement discretion, severity, or the effect of accurate data.
ScopeDataQs
Not selected
FMCSA states that fixing a violation is not the same as proving the violation was incorrect.
RepairDataQs
Not selected
Examples: remove duplicate, correct USDOT number, correct driver, correct vehicle, append adjudicated citation result.
RequestPrecision
Not selected
Repair & Correction Evidence›
Build a factual repair record. Repair documentation can prove that corrective action occurred, but it does not necessarily establish that the original violation was recorded incorrectly.
The record should identify the date, unit, condition, work performed, and service provider.
RepairDocument
Not selected
Retain itemized charges, parts, labor, and payment records.
RepairInvoice
Not selected
Connect replaced components to the inspected unit where possible.
PartsEvidence
Not selected
Create a clear sequence between inspection, repair, and return to service.
TimelineRepair
Not selected
Keep qualifications or certifications when the work requires them.
ProviderRepair
Not selected
Label photos with the unit, area, date, and what the image shows.
PhotoEvidence
Not selected
Keep follow-up inspection, diagnostic, measurement, or road-test records.
ReinspectionEvidence
Not selected
Record who authorized release and what records were reviewed.
ReleaseSafety
Not selected
Add the roadside report, repair evidence, and follow-up maintenance information.
MaintenanceRecord
Not selected
Keep transmission confirmation, certified mail, portal receipt, email, or other delivery evidence.
ReportProof
Not selected
Use qualified, factual documentation rather than a conclusory note.
RepairDecision
Not selected
Use the event to identify repeated component, inspection, or maintenance issues.
PreventionMaintenance
Not selected
Driver, HOS & ELD Evidence›
Use only records that relate to the inspection and the exact issue being reviewed. Do not alter, recreate, or backdate logs or supporting documents.
Keep the records that were available at the inspection and any later exported copy.
ELDEvidence
Not selected
Roadside ELD review generally covers the current 24-hour period and previous seven consecutive days.
HOSRODS
Not selected
Do not overwrite or conceal original events.
ELDAudit Trail
Not selected
Keep dates, written notices, reconstruction records, and repair information.
ELDMalfunction
Not selected
Use source records that help establish locations, times, load activity, and assignments.
SupportingTrip
Not selected
Use objective records that relate to the disputed time or location.
SupportingReceipt
Not selected
Document assignment, rejection, or acceptance decisions in the ELD system.
ELDUnidentified
Not selected
Preserve the facts and company policy used at the time.
ELDSpecial Driving
Not selected
Examples may include CDL, medical certification, endorsements, or employer records.
DriverQualification
Not selected
Use the driver’s own words, dates, locations, and observations without coaching an admission or legal conclusion.
StatementDriver
Not selected
Keep original messages, call notes, and timestamps.
CommunicationEvidence
Not selected
Avoid submitting evidence that appears inconsistent because of time-zone differences.
HOSAccuracy
Not selected
Citation & Adjudication Records›
An inspection violation and a citation are related but separate records. Certified adjudication documents may be submitted through DataQs to append the citation result to the inspection.
Use the correct identifier when contacting the court or submitting DataQs documentation.
CitationIdentifier
Not selected
Keep the official contact information and case location.
CourtRecord
Not selected
Use official notices rather than relying on memory.
CourtDeadline
Not selected
Preserve every page, charge, code, and instruction.
CitationDocument
Not selected
Payment may have legal consequences; do not treat it as a DataQs correction by itself.
CourtProof
Not selected
FMCSA policy uses certified adjudication documentation for citation-result requests.
CertifiedDataQs
Not selected
DataQs may append this result and FMCSA systems may treat the associated violation differently.
OutcomeDismissed
Not selected
Keep the final charge, statute, and certified disposition.
OutcomeDifferent Charge
Not selected
Do not request removal when the official outcome confirms the original charge.
OutcomeOriginal Charge
Not selected
Use the precise certified wording and current DataQs options.
OutcomeOther
Not selected
Do not submit the adjudication under an unrelated request type.
CitationRDR
Not selected
The public toolkit does not provide legal advice or direct a court strategy.
LegalBoundary
Not selected
DataQs Request-Type Review›
Choose the request type that matches the problem. An Inspection Report Request (IRR) requests a copy; a Request for Data Review (RDR) asks the responsible agency to review data believed incomplete or incorrect.
Use an Inspection Report Request when the purpose is only to obtain the report.
IRRReport Copy
Not selected
Use an RDR only when a specific data issue can be identified.
RDRScope
Not selected
Match the DataQs request reason to the disputed violation issue.
RDRViolation
Not selected
Identify the correct motor carrier and provide event-specific evidence.
RDRCarrier
Not selected
Identify the correct driver information and supporting records.
RDRDriver
Not selected
Check Portal, SMS display settings, and update timing first.
RDRMissing
Not selected
Multiple violation rows in a download do not necessarily mean the inspection is duplicated.
RDRDuplicate
Not selected
Examples include vehicle, inspection level, location, date, or similar fields.
RDRReport Data
Not selected
Attach the required certified disposition.
RDRCitation
Not selected
FMCSA states that its records do not contain State warnings for DataQs review.
RDRNot Reviewable
Not selected
FMCSA’s 2026 requirements direct States to review inspection RDRs submitted within three years of the inspection.
RDRTiming
Not selected
Drivers, carriers, representatives, and public users may have different access and visibility.
RDROwner
Not selected
RDR Narrative & Supporting Evidence›
A strong request identifies the exact record, explains the specific alleged error, states the requested correction, and attaches relevant evidence. More documents are not always better — use focused evidence.
Make the event easy to identify.
NarrativeIdentifier
Not selected
Avoid broad statements that do not identify the alleged error.
NarrativePrecision
Not selected
Use a factual timeline and direct comparison to source records.
NarrativeReason
Not selected
Examples include correct a field, remove a duplicate, or append an adjudicated citation result.
NarrativeRequest
Not selected
Include every relevant page and instruction.
EvidenceReport
Not selected
Use official, legible documents that show the final result.
EvidenceCertified
Not selected
Use documents that connect the correct carrier, driver, vehicle, or equipment provider to the event.
EvidenceOperation
Not selected
Limit the submission to the dates and issue involved.
EvidenceHOS
Not selected
Label what each item shows and when it was created.
EvidenceVisual
Not selected
Repairs may show corrective action but do not alone prove that a violation did not exist.
EvidenceRepair
Not selected
Do not submit Social Security numbers, unrelated medical information, financial account numbers, or other unnecessary data.
PrivacyEvidence
Not selected
FMCSA’s Help Center recommends prompt supporting documentation and notes that combined PDFs can improve handling.
FileOrganization
Not selected
DataQs Submission & Monitoring›
Keep the request ID, correspondence, uploads, agency questions, status changes, and final PDF together. DataQs uses email notifications, but the requestor should also monitor the account.
Current DataQs login uses enhanced authentication; keep the account email current.
AccountAccess
Not selected
Inspection, crash, audit, and other request paths use different screens.
SubmissionType
Not selected
Do not default to the carrier’s home State.
SearchState
Not selected
DataQs notes that report numbers are typically ten digits even when a State abbreviation appears on the paper report.
SearchReport Number
Not selected
Document the search and continue only with accurate event information.
SearchMissing Record
Not selected
Use the request ID in every follow-up.
Request IDRecord
Not selected
Late or incomplete evidence can delay review.
UploadEvidence
Not selected
Watch for agency questions, officer comments, or a requestor-response status.
MonitorStatus
Not selected
DataQs states the requestor may have up to 60 calendar days; use the actual deadline displayed.
ResponseDeadline
Not selected
Maintain the exact version submitted.
RecordkeepingSubmission
Not selected
Keep names, dates, contact methods, and what was requested.
CorrespondenceLog
Not selected
DataQs allows a PDF copy of a finished request from the request details.
DecisionPDF
Not selected
Decision, Reconsideration & Final Review›
Read the decision carefully. A closed request may show no correction, a data correction, or an appended citation result. Use current DataQs review options and deadlines.
Examples include data correction made, no data correction made, or citation results entered.
DecisionStatus
Not selected
Keep the complete decision — not only the status label.
DecisionExplanation
Not selected
Identify what changed, what did not change, and why.
DecisionComparison
Not selected
Keep the final record with the underlying inspection and evidence.
RecordkeepingDecision
Not selected
Use the options displayed in DataQs and the current State review process.
ReviewOption
Not selected
DataQs guidance encourages complete initial submissions and limits repeated dispute of the same data.
ReconsiderationEvidence
Not selected
This is a program standard for participating States, not a guarantee that every individual request will close within exactly 21 days.
2026 ProcessInitial
Not selected
Record submission and decision dates.
2026 ProcessReconsideration
Not selected
Use the current DataQs process and State instructions.
2026 ProcessFinal
Not selected
Keep initial, reconsideration, final review, and supplemental materials separate and labeled.
ReviewRecord
Not selected
Use neutral wording such as submitted, under review, or closed.
CommunicationAccuracy
Not selected
Clear To Roll does not represent users before FMCSA, a State, a court, or an administrative tribunal.
BoundaryProfessional
Not selected
SMS, PSP & Internal Record Follow-Up›
FMCSA systems update on different schedules. Keep the final DataQs decision and verify that the expected display or calculation treatment appears after the relevant system update.
Portal data may update more frequently than the public SMS display.
PortalFollow-Up
Not selected
SMS is generally updated monthly; allow for processing time.
SMSFollow-Up
Not selected
PSP generally includes three years of inspection history and updates monthly.
PSPDriver
Not selected
DataQs states that these associated violations are excluded from SMS calculations and the PSP report.
Citation ResultDismissed
Not selected
DataQs states that SMS severity is set to 1 and PSP reflects conviction of a different charge.
Citation ResultDifferent
Not selected
These outcomes generally retain SMS weight and PSP inclusion under current DataQs guidance.
Citation ResultOther
Not selected
Add the final report, repairs, DataQs decision, and system follow-up.
Carrier FileRecord
Not selected
Keep copies the driver is authorized to retain.
Driver FileRecord
Not selected
Use the event to prevent recurrence without treating the toolkit as a safety audit.
PreventionProcess
Not selected
Record the next SMS, PSP, Portal, or internal review date.
Follow-UpDate
Not selected
Keep screenshots or downloads with dates and contact DataQs support when needed.
SystemsDifference
Not selected
Closure is an internal recordkeeping status, not an FMCSA approval.
ClosureInternal
Not selected
Custom Action Items›
Add operation-specific tasks, evidence, deadlines, contacts, or review items. Custom entries remain in this browser session only.
Browser-only: This free kit is browser/session-only and is not saved when you leave the page.
Official DataQs & FMCSA Resources

Post-Inspection Action Summary

Counts reflect only the items selected for this browser session.

Items Requiring Attention
0
Needs follow-up or missing / unresolved
Inspection review not started
  • Current file statusInspection review not started
  • Inspection dateOct 15, 2026
  • Selected items0
  • Complete / documented0
  • Not reviewed0
  • Needs follow-up0
  • Missing / unresolved0
  • Not applicable0
  • Violation log rows0
  • Evidence log rows0
  • DataQs / correspondence rows0
  • Follow-up action rows0
  • Correct safety defects and comply with out-of-service conditions even when a DataQs review is being considered.
  • Use the correct request type: IRR for a report copy; RDR for data believed incomplete or incorrect.
  • Keep the request ID, uploads, correspondence, decisions, and later SMS or PSP checks together.
  • This summary is not a legal opinion, audit, safety rating, or DataQs outcome.

Clear To Roll helps you organize your own review. It does not determine whether inspection data is correct or submit a DataQs request. Get started with Clear To Roll.

Inspection, Evidence & DataQs Logs

Use these repeating rows to build a clean event record. Rows remain in this browser session only.

Violation Review Log

Record each inspection violation separately and distinguish correction evidence from a possible data issue.

Violation code / sectionOOS / citationReport description / unitCorrection / repair evidencePossible data issue / next step

Supporting Evidence Log

List documents, photos, court records, repair records, ELD records, or other evidence and where the file is kept.

Evidence itemDate / sourceFile locationWhat it supports

DataQs Request & Correspondence Log

Track request IDs, status changes, agency questions, uploads, responses, reconsideration, and final review.

DateRequest ID / statusAgency / contactAction, upload, response, or decision

Follow-Up Action Log

Track repair, report return, court, DataQs, record verification, training, or process-improvement tasks.

Follow-up taskResponsible personDue dateStatus / notes

Official DataQs & FMCSA Resources

Use current official sources and the instructions on the inspection report. Direct links are provided without tracking parameters.

FMCSA DataQs

Official system for submitting and monitoring requests to review Federal and State data believed incomplete or incorrect.

dataqs.fmcsa.dot.gov

DataQs Help Center

Official FAQs covering request types, report searches, evidence, adjudicated citations, monitoring, reconsideration, and system records.

DataQs Help Center

DataQs Inspection Request Guidance

Official inspection-specific request reasons and explanations, including report-copy requests, inaccurate violations, duplicates, attribution, and citation outcomes.

DataQs Inspection FAQs

DataQs Contact & Technical Support

Official DataQs assistance and support contact information.

DataQs Contact Us

FMCSA 2026 Revised DataQs Requirements

Official summary of the revised State review requirements, independent review stages, and timing standards.

fmcsa.dot.gov — Revised DataQs Requirements

FMCSA DataQs Program Update

Official April 2026 announcement explaining the three-stage review process and review timing standards.

fmcsa.dot.gov — DataQs Program Update

Safety Measurement System

Official carrier safety data and inspection history display.

ai.fmcsa.dot.gov — SMS

Pre-Employment Screening Program

Official PSP information and driver record access.

psp.fmcsa.dot.gov

FMCSA Portal

Official portal access for authorized carrier and driver safety systems.

portal.fmcsa.dot.gov

FMCSA Motor Carrier Safety Planner — Vehicle Inspections

Official guidance on roadside inspection reports, repairs, retention, and vehicle-inspection responsibilities.

csa.fmcsa.dot.gov — Vehicle Inspections

Completed Inspection Report Disposition Final Rule

Official DOT page for the final rule effective July 22, 2026.

transportation.gov — Final Rule

49 CFR 396.9

Current federal regulation for roadside inspection reports and disposition.

ecfr.gov — §396.9

Keep Inspection and Follow-Up Records Organized

The public kit helps you review one post-inspection action file during the current browser session. A Clear To Roll account helps organize driver records, inspection reports, repair records, incident files, load files, dates, documents, contacts, and Business Packets over time.

Public worksheet entries do not automatically transfer into an account.

Get Started
Your driver file, ready when opportunity calls.

Frequently Asked Questions

cleartoroll.com855-506-8060support@cleartoroll.com

This action kit is for planning and recordkeeping only. It is not legal, court, citation, DOT, FMCSA, State enforcement, safety, insurance, employment, tax, accounting, or compliance advice. It does not determine whether a violation existed, whether data is incorrect, whether a DataQs request should be granted, or how a court, State, or FMCSA will act. Clear To Roll does not investigate, verify, approve, certify, audit, screen, qualify, represent, appeal, file, submit, or guarantee any inspection, citation, repair, carrier, driver, vehicle, request, correction, decision, or outcome. Use current official sources, the inspection report, the issuing agency’s instructions, and appropriate professional guidance. Official links reviewed July 2026.