What Is a DVIR? A Fleet Operator's Guide

The clipboard that doesn't fix the brake

A driver climbs down at the end of a shift and writes "soft brake pedal, unit 14" on a clipboard. The clipboard goes on a hook in the office. Two days later the truck is still rolling on that brake — or it's parked while three people each assume someone else owns the fix. That gap is exactly what a DVIR is supposed to close, so let's answer the real question: what is a DVIR? A DVIR — a driver vehicle inspection report — is the written record of a commercial vehicle's condition that a driver completes around a daily inspection, listing any defect found.

Here's the part the vendor pages skip. A DVIR isn't really about the form. It's about what the form triggers: a defect a driver noticed is supposed to become a certified repair before the truck runs again. The whole federal rule is built around that loop, not around the paperwork.

This guide covers what a DVIR is and what has to be on it, the two paths a report can take, who certifies the repair and when, how long you keep it, paper versus electronic — and the loop that turns a flag into a closed repair instead of a clipboard note.

What a DVIR Is (and What Has to Be On It)

A DVIR is the written report of a daily inspection. The inspection is the walk-around a driver performs; the DVIR is the record of what that walk-around found. The two get used interchangeably, but they aren't the same thing — if you want the actual zone-by-zone check, that lives in our pre-trip inspection checklist . This post is about the report and what happens to it.

FMCSA doesn't leave the contents up to you. Under 49 CFR 396.11, a driver vehicle inspection report must cover at least these parts and accessories:

• Service brakes, including trailer brake connections
• Parking (hand) brake
• Steering mechanism
• Lighting devices and reflectors
• Tires
• Horn
• Windshield wipers
• Rear-vision mirrors
• Coupling devices
• Wheels and rims
• Emergency equipment

A blank DVIR form is just those categories with a place to note a defect and a place to sign. Whether it's a paper pad or an app, that's the skeleton.

The Two Paths: No Defect vs. Defect Found

This is where most explainers blur the line, and it's the part that actually changes what you have to do.

No defect found. Since a 2014 rule for property-carrying vehicles — extended to passenger carriers in September 2020 — a driver is not federally required to file a DVIR when no defect is found. That's the current federal floor. That said, plenty of fleets still require a "no-defect" report every day as company policy, because a consistent record proves the inspection actually happened. That's a smart practice — but it's policy, not the regulation.

Defect found. The moment a driver finds or is told about a defect, a written DVIR listing that defect is required, and a mandatory chain starts. This is the post-trip inspection record that matters — the one a DOT auditor will ask to see, and the one that's supposed to keep an unsafe truck in the yard.

The takeaway: the no-defect day is light, by design. The defect day is where the rule has teeth.

Who Fixes It, Who Certifies It

Once a safety-affecting defect is on the DVIR, the carrier — not the driver — owns what happens next. The DVIR requirements here are specific:

• The carrier must repair any listed defect or deficiency that would likely affect the safe operation of the vehicle (396.11(a)(3)(i)).
• The carrier or its agent must then certify on the DVIR that the defect was repaired — or that repair was unnecessary — before the vehicle is operated again (396.11(a)(3)(ii)).

Then the loop closes back at the driver's seat. Before driving, the next driver must be satisfied the vehicle is in safe operating condition, review the last DVIR, and sign to acknowledge the review and the repair certification (49 CFR 396.13).

Read those together and the design is obvious: a defect can't just be noted and forgotten. Someone has to fix it or rule it out, someone has to certify that in writing, and the next driver has to see the certification before the wheels turn.

The DVIR-to-Work-Order Loop (Where Fleets Leak)

Here's the gap that costs fleets the most, and it's not a paperwork gap — it's a workflow gap. The rule says certify the repair before the truck runs again. It doesn't make the repair happen. That's on you.

The loop that works is short:

When that loop runs, nothing rots on a hook. The defect becomes a tracked job with an owner, the repair gets done, the certification lands on the report, and the unit is cleared. When the loop breaks — almost always between "flag written" and "work order opened" — the truck either runs unsafe or sits while everyone assumes someone else has it. That's the DVIR-to-work-order loop , and it's the single place paper-and-clipboard fleets leak the most.

There's a clean compliance payoff for closing it. The closed work order plus the certified DVIR is exactly the evidence a DOT auditor wants: this defect, flagged on this date, fixed on this unit, certified before dispatch. For a DOT/FMCSA-bound trucking fleet , that paper trail is the difference between a clean file and a finding.

This is where the right tooling earns its keep. In FS365, a flagged DVIR defect can turn into a work order against the exact unit the moment the driver hits submit — so the fix gets an owner instead of a hook. It's one example of the loop done right; the principle holds no matter what you run.

How Long You Keep a DVIR

A DVIR isn't done when the truck rolls. Under 396.11(a)(4), the carrier must keep the DVIR, the certification of repairs, and the certification of the driver's review for three months from the date the report was prepared.

Keep all three together, because that bundle is the audit trail. The flag shows the defect was caught; the repair certification shows it was fixed or ruled out; the review certification shows the next driver saw it. Pull any one out and the story has a hole.

One note: the daily DVIR's three-month clock is separate from the longer retention on periodic and annual inspection records. Don't file them on the same shelf and assume one rule covers both.

Paper vs. Electronic DVIRs

You can run DVIRs on paper or electronically — FMCSA allows reports to be created and kept electronically. The choice isn't about looking modern. It's about whether the flag survives.

On paper, a defect lives on a clipboard until someone retypes it, and the three-month retention bundle is a folder somebody has to assemble. With an electronic DVIR, the flag is attached to the unit, it can open a repair record automatically, and the DVIR-plus-certification bundle stays linked through the retention window without anyone rebuilding it at audit time. Same rule, far fewer places for a defect to fall through.

What a DVIR Does to Your Numbers

A DVIR isn't compliance theater. It's where a few fleet KPIs come from:

• Defect-resolution time — the clock from "driver flags it" to "repair certified." You can only shrink it if defects become records instead of clipboard notes.
• Downtime avoided — a soft brake caught in the yard is a scheduled fix. The same defect caught roadside is a tow, a missed load, and a violation.
• CSA exposure — consistent DVIRs and certified repairs are what reduce your Vehicle Maintenance exposure and what an auditor asks to see.
• PM signal — the same defect flagged on a unit week after week is your early warning that a PM interval is too long, the same discipline behind the rest of your DOT compliance file.

Conclusion

A DVIR is the smallest unit of "we caught it and fixed it" in a fleet: one inspection, one report, one defect, one certified repair. Treat it as a form to file and defects die on a hook. Treat it as the front end of a repair — flag to work order to certified fix — and you get the defect-resolution time, the downtime savings, and the audit trail you've been chasing.

The soft brake on unit 14 doesn't need a clipboard. It needs a DVIR that turns into a repair.

Frequently Asked Questions

What is a DVIR in simple terms?

A driver vehicle inspection report — the written record a driver makes of a commercial vehicle's condition, listing any defect found during a daily inspection, so it can be repaired and certified before the truck runs again.

What does DVIR stand for?

Driver Vehicle Inspection Report.

Is a DVIR required by law?

Yes, when a defect is involved. Under 49 CFR 396.11, a driver must file a written report when a defect is found; under 396.13, the next driver must review the last DVIR before driving. Since 2014 (property carriers) and September 2020 (passenger carriers), a no-defect DVIR is not federally required — though many fleets still require one as policy.

What has to be on a DVIR?

At minimum: service brakes (and trailer brake connections), parking brake, steering, lighting and reflectors, tires, horn, wipers, mirrors, coupling devices, wheels and rims, and emergency equipment — plus any defect found and a signature.

How long do you keep a DVIR?

Three months from the date the report was prepared, kept together with the repair certification and the driver's review certification (49 CFR 396.11(a)(4)).

Can a DVIR be electronic?

Yes. FMCSA allows DVIRs to be created and maintained electronically, which is what keeps the flag, the repair, and the retention bundle linked instead of scattered.

What's the difference between a DVIR and a pre-trip inspection?

The pre-trip is the check a driver runs before driving; the DVIR is the written record of what an inspection found. The walk-around steps live in our pre-trip inspection checklist .