DVIR stands for Driver Vehicle Inspection Report — the record a driver creates confirming they checked the vehicle before or after a trip, and noting anything wrong with it. It's one of the more universally required pieces of trucking paperwork, and one of the easiest to let slide when you're running a small operation without a dedicated safety department. Here's what it actually covers.
Who this applies to
Federal DVIR requirements generally apply to commercial motor vehicles operating in interstate commerce, with thresholds based on gross vehicle weight rating. If you're operating intrastate only, your state may have its own version of the requirement, sometimes with different thresholds or exemptions. This distinction matters and it changes over time, so treat this article as a starting point, not a final answer — confirm your specific obligations on fmcsa.dot.gov or with your compliance advisor.
What the inspection needs to cover
A DVIR is meant to confirm the systems that make a vehicle safe to operate are actually working. The systems typically covered include:
- —Service brakes, including trailer brake connections
- —Parking brake
- —Steering mechanism
- —Lighting devices and reflectors
- —Tires and wheels/rims
- —Horn, windshield wipers, and rear-vision mirrors
- —Coupling devices (for combination vehicles)
- —Emergency equipment
The exact list and how strictly it's enforced can vary — the point of the report is the same regardless: catch a mechanical problem before it becomes a breakdown or a safety incident on the road.
The daily flow
Before driving, a driver should review the previous inspection report for any defects that were noted, and confirm they were either fixed or certified as not affecting safe operation before the vehicle goes back out. After the day's driving, the driver completes a new report — if everything checked out, it's a quick confirmation; if something's wrong, it gets documented with enough detail that whoever handles maintenance next knows exactly what to look at.
A defect that affects safe operation should keep the vehicle out of service until it's actually fixed — not just noted and driven anyway. This is the part that gets skipped under schedule pressure, and it's also the part that matters most.
Keeping records
Carriers are required to retain DVIRs and the certification that any noted repairs were completed. Retention requirements can change and vary by jurisdiction, so confirm the current requirement rather than relying on what was true a few years ago — the safe habit is to keep records longer than you think you need to, since they cost little to store digitally and are exactly what you want on hand if a defect ever becomes a dispute.
Keeping it from becoming a paperwork burden
The most common failure mode for a small carrier isn't not knowing the rule — it's the report living on a clipboard that never makes it back to the office, or a defect getting mentioned verbally and forgotten. Doing this digitally, from the driver's own phone, at the moment they're standing next to the truck, is what actually makes the habit stick.
Haulstats includes a DVIR-lite inspection flow drivers fill out from a shipment — a stage (pre-trip, post-trip, pickup, or delivery), the relevant checks, a defect severity if something needs attention, and an optional photo. A high-severity defect on a pre-trip or post-trip check automatically takes the truck out of service and opens a work order, so it can't quietly get missed. To be clear: this is a practical internal record-keeping tool, not a certified FMCSA compliance product — for formal DOT compliance software, talk to a provider that specializes in that certification. See how the inspection flow works in the maintenance guide.