What is a DVIR: a driver vehicle inspection report is the written report a US commercial driver completes at the end of each day's work on a vehicle, listing any defect that would affect safe operation or is likely to cause a mechanical breakdown.
A DVIR, the driver vehicle inspection report, is the end-of-day defect report that the Federal Motor Carrier Safety Administration (FMCSA) requires from drivers of commercial motor vehicles under 49 CFR 396.11. The driver records any defect or deficiency found during the day, signs it, and hands it to the carrier, who must repair the defect or certify in writing that repair is not needed before the vehicle goes out again.
The term matters outside the United States too, because fleet software and vehicle-inspection apps use "DVIR" as a generic label for any daily defect sheet. In the UK and Ireland the equivalent duty is the DVSA HGV daily walkaround check with a driver daily defect report, including nil-defect reporting where the operator asks for it. The paperwork differs, the idea is the same: the person who drove the vehicle is the one who reports its condition.
What a DVIR must cover
49 CFR 396.11 lists the parts and accessories the report has to address as a minimum:
- service brakes, including the trailer brake connections
- parking brake
- steering mechanism
- lighting devices and reflectors
- tyres (tires in the US wording)
- horn
- windscreen wipers
- rear-vision mirrors
- coupling devices
- wheels and rims
- emergency equipment
The report is prepared at the completion of each day's work, on each vehicle operated, and it has to identify the vehicle. For property-carrying vehicles a report is only required when the driver has found a defect; a clean day needs no form. Passenger-carrying operations have their own wording in the rule, so check the current text before you set a policy for a coach or bus fleet.
How the DVIR process works
Three people touch the report in sequence, and the rule is written around that handover.
- The driver inspects the vehicle at the end of the day, lists every defect that affects safe operation or could cause a breakdown, and signs.
- The carrier reviews the report, repairs the defect or certifies that repair is unnecessary, and records that certification on the report.
- The next driver reviews the previous report before driving and signs to acknowledge that the repairs were carried out. That review is part of the pre-trip inspection duty in 49 CFR 396.13.
The carrier keeps the original report and the certification for three months from the date it was prepared. Electronic reports and electronic signatures are permitted, so a DVIR can be a screen rather than a carbon-copy pad, provided the same content and signatures are there.
DVIR example: a chafed air line and a cracked mirror
A tractor unit comes back to a regional distribution yard at the end of a shift. On the walk round the driver finds the trailer's red air line rubbing on a bracket, the outer sheath worn through in one spot, and the nearside mirror housing cracked after a tight loading bay. Both go on the DVIR: the air line as a defect affecting safe operation, the mirror as a defect too, since the glass is still intact but the housing may not hold it.
The driver photographs the worn line with the trailer number in frame and adds the photos to the submission. The workshop replaces the line that evening and certifies it on the report. The mirror housing is ordered and the carrier certifies that the vehicle is safe to operate with the existing mirror until the part arrives. The morning driver reads the report, sees both certifications, signs, and sets off.
What a DVIR does not do, and the mistakes fleets make
It is not the pre-trip inspection. A DVIR is a post-trip report. The pre-trip duty is separate: the driver must be satisfied the vehicle is safe before driving and must review the last report. Fleets that fold both into one form often end up with a signature and no actual check.
It is not the periodic inspection. The annual inspection under 49 CFR 396.17 is a different record with a different retention period. A stack of clean DVIRs does not replace it.
It does not prove the vehicle was inspected properly. A ticked box says the driver ticked a box. The recurring failures are the same in every fleet: defects reported by phone and never written down, the same brake defect appearing on five consecutive reports with no certification, reports with a signature and no vehicle number, and no photo of the defect, so the workshop spends the first twenty minutes finding what the driver meant. Defect classification that tells a driver what counts as "affects safe operation" cuts most of that out.
Who owns the record
The carrier owns the DVIR, not the driver. It has to be available at the carrier's place of business for the three-month retention period, and inspectors can ask for it. That is why the defect entry needs support: a written line saying "brake line worn" is a claim, while a timestamped photo of the worn line, tied to the vehicle number and the date, is evidence that the defect existed and was seen. Fleets serious about roadworthiness keep both.
Venta Capture, a product of VentaVid, is one way to collect that photo evidence without an app on the driver's phone. The driver opens a secure, personal capture link or scans a QR code on the yard screen, follows the guided steps in the mobile browser (vehicle identifier, each defect, a close-up, a spoken description), and the submission arrives at the fleet desk timestamped, located and sealed (see sealed submission). The DVIR remains the regulatory form; the capture is the evidence behind the defect entry. See the Venta Capture page for how the capture flow is set up.
