DVIR Requirements Explained: Reports, Defects and the Repair Trail
CabFiles Compliance Team · March 4, 2026 · 2 min read
A DVIR is only half a record. The other half is proof that a reported defect was repaired before the vehicle went back out — and that is what auditors check.
Vehicle files fail audits for a different reason than driver files. The inspection reports usually exist. What is missing is the repair trail that connects a reported defect to the work that fixed it.
What the report has to cover
Part 396.11 lists the components a driver's report addresses, including service brakes and trailer brake connections, parking brake, steering mechanism, lighting devices and reflectors, tires, horn, windshield wipers, rear vision mirrors, coupling devices, wheels and rims, and emergency equipment.
The report identifies the vehicle, the date, and any defect or deficiency discovered or reported that would affect safe operation or result in a mechanical breakdown.
The part carriers miss
A defect report must be followed by:
- Certification that the defect was repaired, or a certification that repair was unnecessary, signed by the carrier or its agent.
- Retention of both — the report and the certification — for at least three months.
- No dispatch of the vehicle while a safety-affecting defect is outstanding.
An auditor reading a DVIR with a brake defect will look for the repair certification next. If the vehicle shows trips after that date without one, that is the finding.
Building a defect-to-repair trail
- Capture defects as structured items, not a free-text note, so the same defect can be followed to closure.
- Record who resolved it, when, and what was done — repaired, or repair not needed with a reason.
- Keep the trail attached to the unit, so a vehicle's history is readable in one place.
- Store the annual inspection and periodic maintenance records against the same unit; auditors ask for them together.
Where paper breaks down
Paper DVIRs live in the truck, then in a pile, then in a drawer. The repair happens in a shop that keeps its own invoices. Nothing links the two, so the carrier holds both halves of the evidence and cannot present the connection.
CabFiles files a DVIR against the driver and the unit, records the reported defects as items with notes, and captures the repair resolution — including the date and the person — against the original report. Outstanding defects stay visible as open items until they are resolved, and the vehicle's inspection and maintenance documents live in the same archive, so a request for a unit's file is one export.
Related: the DOT audit preparation checklist and DOT record retention requirements.
General guidance on federal inspection and maintenance recordkeeping; not legal advice.
Frequently asked
- When is a DVIR required?
- Under 49 CFR 396.11, a driver must prepare a report at the completion of each day's work on each vehicle operated when a defect or deficiency is discovered or reported that would affect safe operation.
- How long must DVIRs be kept?
- Reports and the certification of repairs must be retained for at least three months from the date the report was prepared.
Keep every file audit-ready
CabFiles tracks expiry and review dates, scores driver files against the Part 391 checklist, and exports a complete audit packet in one download.
Related reading
- New Driver Onboarding Checklist: The First 30 Days, Compliantly
Onboarding is where compliance is won or lost. This checklist separates what must exist before the first dispatch from what the rules allow you 30 days to finish.
- Trucking Funding Options and the Paperwork Every Lender Asks For
A neutral look at how merchant cash advances, invoice factoring and equipment loans work for carriers — and the document pack that decides how fast any of them close.
- Choosing DOT Compliance Software: 12 Questions Worth Asking
Most compliance tools store documents. Fewer track the dates, restrict access properly, and produce a packet an investigator can read. These are the questions that tell them apart.