What it is
The DVIR Vehicle Inspection Form is a Driver Vehicle Inspection Report for pre-trip and post-trip inspections, built to satisfy the expectations of FMCSA 396.11 and 396.13. It walks the driver through the truck and trailer in order, lets them mark each component OK or defective, captures the header detail an inspection needs — unit number, trailer, driver, carrier, date, odometer, location and inspection type — and then routes the form through the mechanic-certification and driver-review chain before the vehicle goes back into service.
The form is designed as a loop, not a checkbox exercise. When a defect is found, the driver describes it and marks the component defective; the form then carries the mechanic's repair action, the mechanic's certification signature and date, and confirmation that the next driver reviewed the prior report. That chain is exactly what FMCSA requires: a defect affecting safe operation must be repaired and certified before the vehicle returns to service, and the form is structured so none of those steps can quietly be skipped.
Because it is a printable PDF, it works in a glovebox for a fleet that hasn't digitized inspections, or as the documented standard behind a digital DVIR app. It also includes practical guidance — for example, what to do when a defect is found — so a new driver knows how to complete it correctly.
What it's used for
Fleets use the DVIR form to make daily vehicle inspections consistent, documented and compliant, and to ensure that reported defects actually get fixed and certified before a vehicle carries another load. It is a frontline safety and compliance instrument for any operation running commercial vehicles.
- ✓ Conducting and documenting pre-trip and post-trip inspections in the order FMCSA expects, marking each component OK or defective.
- ✓ Capturing the inspection header — unit, trailer, driver, carrier, date, odometer, location and inspection type — for a complete, auditable record.
- ✓ Logging defects with a clear description and routing them to maintenance rather than leaving them on a back seat.
- ✓ Documenting mechanic repair action and certification so a defect-affected vehicle is not returned to service until it is safe.
- ✓ Recording the next driver's review of the prior report, closing the inspection-to-inspection loop.
- ✓ Providing roadside-inspection evidence that the fleet runs a real, daily DVIR process.
- ✓ Training new drivers on a correct, consistent inspection routine with built-in guidance on handling defects.
Who uses it
The DVIR is completed by drivers and certified by mechanics, with safety and compliance owning the standard. It is one of the few documents that every link in the operating chain touches every day.
Context & good to know
The DVIR is the daily mechanism by which a fleet keeps its vehicles roadworthy and proves it. FMCSA 396.11 requires drivers to report any defect that would affect safe operation, and 396.13 requires the next driver to review the previous report and be satisfied the vehicle is in safe condition before operating it. The form's value is in making that legal chain concrete: a defect is described, repaired, certified and reviewed, with a signature at each step, so the record stands up to a roadside inspector or an auditor.
Vehicle Maintenance is one of the seven CSA BASIC categories, and the violations that populate it — brakes, lights, tires, and the like — are exactly what a properly run DVIR is designed to catch before the vehicle ever leaves the yard. A fleet with a real DVIR process and clean documentation tends to fare better at roadside inspections, which in turn lowers inspection frequency and supports insurance and contract standing.
This is one of the areas where software has clearly improved on paper. Whip Around is built specifically around mobile DVIRs that photograph defects, push them straight to maintenance and track the repair-to-certification loop, and Samsara, Motive and GPS Insight all offer digital DVIR workflows tied to their ELDs. A digital DVIR removes illegible handwriting, timestamps and geotags the inspection, and makes the defect-to-repair handoff instant. The paper form remains useful as a backup, a standard for a fleet that hasn't digitized, and a clear specification of what any DVIR app should capture.
The most common failure mode the form is designed to prevent is the defect that gets noted but never fixed. A DVIR with a logged defect and no corresponding repair certification is arguably worse than no DVIR at all, because it documents that the fleet knew about an unsafe condition and operated the vehicle anyway. The certification chain on this form exists precisely to close that gap.