Direct Answer
After a DOT roadside inspection, you need to retain the original inspection report, all repair documentation for cited defects, the driver's pre-trip inspection log from that day, a corrective action plan, and follow-up evidence showing defects were fixed. These documents form your corrective action file and are what FMCSA auditors look for if your carrier is ever reviewed.
What This Means
A DOT roadside inspection generates a permanent record in the FMCSA's system. That record shows what was inspected, what was found, and whether any OOS conditions were identified. What it does not automatically show is what you did about it.
That is your job. The documentation you collect and retain after an inspection is what proves (to FMCSA auditors, to your insurance carrier, and to your own management) that your safety program is real and functioning.
Carriers that get investigated often fail not because violations occurred, but because they cannot demonstrate any corrective response. Good documentation is the difference between an investigation that closes quickly and one that escalates.
Regulation Context
- Record retention: 49 CFR 396.3 requires carriers to retain records of inspections, repairs, and maintenance for 1 year from the date of inspection, or 6 months after the vehicle leaves the fleet
- Driver vehicle inspection reports (DVIRs): 49 CFR 396.11 requires drivers to submit post-trip DVIRs noting any defects, and 396.13 requires drivers to review the previous DVIR before operating
- Corrective action evidence: FMCSA auditors expect to see corrective action documentation during compliance reviews under 49 CFR Part 385
Complete Post-Inspection Documentation Checklist
Immediate (Within 24 Hours)
- ☐ Original inspection report: get a copy from the driver if not already on file; available via FMCSA DataQ portal
- ☐ Driver Vehicle Inspection Report (DVIR) from the day of inspection and the day before
- ☐ Driver statement: brief written account from the driver of what occurred at the inspection
- ☐ Notification log: record of when the safety manager was notified and by whom
Repair Documentation (For Each Cited Defect)
- ☐ Repair work order showing: date, vehicle ID, specific defect, repair performed, parts used, technician name and signature
- ☐ Pre-repair photos where possible (especially for tire and brake defects)
- ☐ Post-repair inspection sign-off confirming the defect is resolved
- ☐ Technician certification if required (e.g., brake repairs in some states)
Fleet-Wide Response Documentation
- ☐ Fleet sweep results: inspection of all vehicles for the same defect type, with findings for each vehicle
- ☐ PM schedule update: evidence that your maintenance intervals were reviewed and adjusted if needed
Corrective Action Plan (CAP)
- ☐ Written CAP documenting: violation cited, root cause, corrective action taken, follow-up actions, responsible parties, and due dates
- ☐ Sign-off by safety manager
- ☐ Driver training/retraining record if driver error contributed to the violation
Follow-Up Evidence
- ☐ Post-repair inspection confirmation (re-inspection of the vehicle or component after repair)
- ☐ Updated pre-trip inspection checklist if the standard form was found inadequate
- ☐ DataQs challenge documentation if you are contesting any violation
CSA / BASIC Impact
Documentation does not directly affect BASIC scores. Only DataQs challenges that result in violation removal do. However, documentation is critical for DataQs challenges and for demonstrating a pattern of compliance during FMCSA investigations, which can affect whether a carrier's safety rating is elevated or downgraded.
Corrective Action Steps
- Create a dedicated folder for each inspection. Physical or digital: label it by date, vehicle ID, and violation type.
- Collect documents in order: Inspection report → DVIR → Driver statement → Repair orders → Fleet sweep → CAP.
- Assign a completion deadline for each document. Repair orders should be closed within 24–48 hours. CAP within 72 hours. Fleet sweep within one week.
- Store everything in a central location. A safety manager's email inbox is not a filing system.
- Retain for minimum 1 year per 49 CFR 396.3, but consider retaining for 3 years given audit risk windows.
Prevention Tips
Build documentation into your response workflow, not after it. The moment a violation is reported, open a corrective action file. Don't wait until you have everything to start documenting.
Use templates. Pre-built corrective action plan templates remove the burden of formatting and ensure nothing is missed.
Assign document ownership. Someone specific should be responsible for collecting and closing every document in the file before the file is marked complete.
Frequently Asked Questions
Q: Do we have to submit corrective action documentation to FMCSA after every inspection? No. FMCSA does not require proactive submission of corrective action files. But you must be able to produce this documentation if you are selected for a compliance review or investigation.
Q: How long do we need to keep inspection and repair records? 49 CFR 396.3 requires retention for at least 1 year from the inspection date, or 6 months after the vehicle leaves the fleet. Best practice is to retain for 3 years.
Q: Does having good documentation remove the violation from our CSA score? No. The violation stays in your BASIC score unless you successfully challenge it through DataQs. Documentation supports your DataQs submission and protects you during any investigation.
Q: What does FMCSA look for when they audit our documentation? Auditors look for complete DQ files, current inspection records, maintenance records showing defects were repaired, and evidence that violations generated a corrective response, not just a repair, but a review of the underlying cause.