Roadside inspection report corrections and DataQs requests

A roadside inspection report needs a clear follow-up process: review the findings, address the violations, document the corrections and return the certification as required. Under §396.9(d), the carrier’s signed certification is due within 15 days of the inspection and the carrier retains a copy for 12 months.

Read the whole report first

Identify the inspection date, report number, driver and vehicle. Review each finding and any out-of-service instruction before planning the next movement. An out-of-service order is not simply another reminder in a document tracker. The restrictions in §396.9(c) need to be addressed before the affected operation resumes as permitted.

Confirm that the person arranging repairs has the actual report. A message saying “fix the truck” may omit a finding or send the shop to the wrong vehicle. Preserve the complete report, including any continuation pages.

Build a finding-by-finding work list

• Record each finding as it appears on the report.
• Identify the vehicle or driver it concerns.
• Assign the responsible person and the next action.
• Keep supporting evidence of the response.
• Review the complete report before the carrier certifies corrections.

A report can contain several findings with different owners. Keep them separate until each is resolved; closing the first repair should not hide the remaining items. If a finding needs clarification, use the issuing agency’s instructions or contact information rather than guessing what constitutes a correction.

What counts as useful evidence?

Keep the repair invoice, work order or other appropriate documentation that explains what was done. Match unit identifiers and dates to the report. A photo may help explain a repair, but a photo alone may not explain the work, its date or who performed it. Use enough detail for someone who was not present to follow the response.

The vehicle’s maintenance history can provide supporting context under §396.3. Store the evidence where it can be retrieved from both the inspection follow-up and the vehicle’s record. A private note saying “shop handled it” is difficult to verify later.

Example: two findings, one incomplete response

A report lists a lamp defect and another item that requires separate attention. The shop supplies an invoice for the lamp. That invoice supports one action; it does not close the entire report. Keep the second item open, obtain its evidence and review both before preparing the carrier’s response.

When the response is submitted, save a copy and evidence of submission. Record the actual submission date. If the report or agency provides specific return instructions, follow them. An internal “complete” label does not transmit the certification to the agency.

Roadside reports and DVIRs are different records

A driver vehicle inspection report under §396.11 is not the same document as the roadside report issued by an inspector. A related defect may appear in both workflows, but saving one does not replace the other. Keep their identities, dates and supporting evidence clear.

When the report itself is wrong: DataQs

Certifying corrections answers the findings. It doesn't fix a report that's wrong. If an inspection lists the wrong carrier, a violation that didn't happen or a unit you don't operate, file a Request for Data Review in FMCSA's DataQs system. Every violation on the report counts in the Safety Measurement System whether or not a ticket was written, so it's worth checking each one.

If a citation tied to a violation goes to court and is dismissed, or you're found not guilty, the violation can be removed from the SMS; a conviction on a different charge lowers its weight. Submit the certified court documents through DataQs. The CSA scores guide explains how those violations affect your percentiles.

Keep the deadline visible

Set an internal follow-up date before the return deadline so there is time to review the evidence and submit the response. The statutory timing in §396.9(d) remains the reference. A calendar reminder is useful only when someone owns the work behind it.

For official guidance, see FMCSA’s roadside inspection report guidance. For organizing ordinary service entries, use the truck maintenance log template.