Ask one fleet who owns DVIRs and they'll say their safety and compliance team. Ask another and they'll say maintenance. (Ask a third and they might say, "Not sure. What's a DVIR?" We'll set that one aside for now.)
If you run a fleet but haven't spent much time in the shop or safety office, the driver vehicle inspection report is easy to overlook. It's a one-page form that has been around for decades. Most days, it says nothing. But it is the document connecting your drivers, mechanics, and compliance record. When it isn't handled well, the consequences show up at roadside inspections, in CSA scores, in audits, and in litigation. The handoff to maintenance and back is where records go missing and risk lives.
DVIRs Demystified
A DVIR is the written report a commercial driver prepares when a vehicle has a defect that could affect safe operation or cause a mechanical breakdown. The driver documents the problem and signs. The carrier fixes it, or determines that no repair is needed, and certifies that on the report. Before operating the vehicle, the next driver reviews the last required DVIR and confirms that any safety-related defects have been addressed.
That's the whole federal rule in a paragraph. It comes from 49 CFR 396.11 and 396.13, part of the Federal Motor Carrier Safety Regulations. It applies broadly to motor carriers operating commercial motor vehicles in interstate commerce, with several exceptions, including certain driveaway-towaway operations, private motor carriers of passengers (nonbusiness), and carriers operating only one commercial motor vehicle.
States can impose their own requirements on intrastate operations, and California is an important example. California requires covered drivers to prepare a daily vehicle inspection report at the end of each day's work, including a report indicating when no defect or deficiency was discovered.
Why it exists
The DVIR is the driver's half of the maintenance system. A mechanic sees a truck every few weeks or months. A driver sees it every day, hears it, feels it under braking, and notices when something is different. The regulation exists to make sure that knowledge gets written down, reaches someone who can act on it, and leads to action before the truck is back on the highway.
The requirement has been part of federal trucking rules since the Interstate Commerce Commission era, decades before FMCSA existed. The biggest recent change for property carriers came in December 2014, when FMCSA stopped requiring most drivers to prepare a DVIR when no defects were found.
FMCSA later eliminated the federal no-defect DVIR requirement for most passenger carriers as well. Under the federal rule today, DVIR requirements generally focus on days when a qualifying defect or deficiency is discovered or reported.
Covered California fleets should pay attention to the distinction. California's rules still require drivers to prepare a daily report, including when no defect is found. Don't assume the federal elimination of no-defect DVIRs eliminates your daily reporting obligation.
What it costs to get wrong
The DVIR looks like paperwork, but failures are operational.
Roadside. A truck with an unrepaired safety defect is an out-of-service order waiting to happen. Inspectors check the vehicle, and required DVIRs and repair certifications can become part of the record. A brake defect written up three days earlier with no evidence anyone addressed it makes for a very short conversation.
CSA scores. DVIR violations, including inadequate reports or failures around required review and certification, can land in the Vehicle Maintenance BASIC. That performance can follow a carrier into conversations with regulators, brokers, and insurers.
Audits and investigations. A compliance review or an investigation after a crash may include DVIRs and repair certifications. Missing DVIRs or incomplete repair trails can become findings. Civil penalties can apply, and patterns of maintenance violations can affect a carrier's safety standing.
Litigation. After a serious crash, a plaintiff's attorney may request the vehicle's DVIRs. If a driver reported a defect and the record shows it was never addressed, you have a document in your own files that says you knew. That's how a maintenance oversight becomes a company-level risk.
Downtime. The quieter cost. A defect reported but lost in the handoff leaves a truck sitting unnecessarily or running with a known problem until it fails. Either way, it's revenue.
What the rule requires, step by step
Once a driver finds a reportable defect, a few things have to happen in sequence.
-
Report. At the end of the day's work, the driver documents the defect and signs the DVIR. Under the federal rule, the threshold is a defect or deficiency that would affect safe operation or result in mechanical breakdown. A brake lamp out, a soft brake pedal, a tire cut to cord, an air leak: reportable. A scuffed mud flap may not rise to that federal threshold, though your shop may still want to know about it.
-
Repair before operating, when safety is affected. A defect likely to affect safe operation must be repaired before the vehicle is driven again. Not every item on a DVIR requires repair before operation, but every listed defect still needs to be dispositioned.
-
Certify. The motor carrier or its agent certifies on the DVIR that each reported defect was repaired or that repair was unnecessary. Either outcome is acceptable. What matters is that the defect has a documented disposition instead of disappearing between the driver and the shop.
-
Review and acknowledge. Before driving, the next driver reviews the last required DVIR and confirms that any defect likely to affect safe operation has been certified as repaired. The reviewing driver signs the report as required. Narrow exceptions include certain defects on a towed unit that is no longer part of the vehicle combination.
Then retain it. Under the federal rule, the carrier keeps the DVIR, including the repair certification and required driver's review certification, for three months from the date it was prepared. Related maintenance records can run on longer clocks, so it's important to know which one you're on.
For a typical defect DVIR, that creates a three-part documentation trail: the reporting driver, the person who certified the repair or determined it was unnecessary, and the acknowledging driver. The important thing isn't the signatures themselves. It's being able to show the chain from defect to disposition to the next-driver review.
What a good post-trip inspection actually involves
The federal rule lists the vehicle systems a DVIR must cover, but it doesn't prescribe a detailed post-trip routine. Each fleet builds its own process. A thorough routine might look like this:
-
Park and secure. Engine off, parking brake set, wheels chocked if that's policy.
-
Recall the day. Before touching anything, the driver thinks back: pulling under braking, a new noise, a warning light, a smell. This often-skipped step catches intermittent problems.
-
In-cab. Gauges and warning lights, horn, wipers, parking brake hold, low-air warning, mirrors, windshield, emergency equipment.
-
Lights. Every lamp and reflector, tractor and trailer.
-
Tires, wheels, rims. Tread, cuts, bulges, inflation, cracked wheels, loose lugs, hub seals.
-
Brakes and suspension. Air leaks, hose chafing, slack adjusters, drums, springs, air bags.
-
Steering and coupling. Linkage and tie rods; fifth wheel locked, glad hands, landing gear. For drayage, chassis twist locks and frame.
-
Under the truck and body. Fluid leaks, belts, hoses, exhaust, frame, doors, securement.
-
Decide and report. If it's reportable, describe it specifically enough for a mechanic to find it. "Driver-side rear trailer brake light out" beats "light out."
-
Hand off. Whoever assigns the next driver needs to know the truck has an open defect.
The next morning's pre-trip covers much of the same ground, plus reviewing the previous required DVIR and confirming that safety-related defects have been addressed. Fleets that do post-trips well have short, uneventful pre-trips.
Who owns what
A DVIR is easy to mishandle because it belongs to two departments at once. It starts as a compliance document because the law requires it. The moment a defect is written down, it becomes a maintenance document because the shop has work to do. Once the repair is certified, it becomes a compliance document again: the next driver may need to acknowledge it, and the carrier has to keep the chain on file.
Most fleets handle the first and last parts adequately. Often that's simply how fleet safety and maintenance teams are set up: with very little overlap.
A few structural questions worth asking your team:
Who is the repair authority? The carrier or its agent certifies repairs. Decide who that is for each kind of work: an in-house mechanic, mobile vendor, dealership, or another authorized person verifying the fix. Make sure the process produces the required certification instead of assuming an invoice closes the compliance record.
Where does a defect go the moment it's reported? If the answer is "dispatch looks at it in the morning," you have a gap where a truck could be reassigned with an open defect. The report should become a work item automatically, visible to whoever will fix it.
How does the next driver know? Acknowledgment only works if the DVIR and repair certification are available before operation. If certification happens in another system or on paper, make sure it actually gets back to the driver.
What's your threshold policy? The federal rule focuses on defects or deficiencies affecting safe operation or likely to cause a mechanical breakdown. Decide what you want reported beyond that, and tell drivers. Some fleets want everything written up so the shop can plan; others separate compliance-reportable defects from lower-priority observations. What matters is that drivers know what to do.
Can you produce the record? For any truck, on any day in the applicable retention period, can someone pull the DVIR, repair certification, and driver's acknowledgment in under five minutes? That's the operational test.
What are you measuring? Two numbers reveal whether the program is healthy: how long a reported defect stays open before it's resolved and certified, and whether a unit was dispatched with an unresolved safety defect. If nobody can answer those easily, no one owns the handoff.
Where Axle fits
If your drivers use Samsara, for example, they may already submit DVIRs in the app. What's often missing is the maintenance loop: routing the defect, tracking the repair, attaching the invoice, and returning the resolution to the compliance workflow.
Axle turns each reported defect into a work ticket the moment it's submitted, routes it to your shop or vendor, captures the repair and invoice, and records the "repaired" or "repair unnecessary" resolution by the right person. Integrated with the fleet's existing DVIR system, that status flows back into the driver's workflow so the compliance and maintenance records stay connected.
The DVIR, repair, and associated records stay together by unit according to the fleet's retention requirements. Dispatchers and fleet managers can see which units have open defects, which are waiting on repair, which have been cleared, and how long each has been sitting.
The bottom line
A DVIR is simple until a defect shows up. Then it becomes the one record that has to move cleanly between your drivers, your shop, and your compliance file.
Fleets that handle it well don't treat that as paperwork. They treat the handoff as the job and can prove what happened for any truck on any day.
Exact reporting requirements vary by operation and jurisdiction, but the operational standard is straightforward: reported, evaluated, repaired when necessary, certified, reviewed when required, and retained. Every time.
Want to see how your open defects would look in Axle? Book a demo and bring one truck's DVIRs.
This post is for general information and reflects our reading of 49 CFR Part 396 as currently published. Federal requirements are shown; state requirements may differ, including California's daily vehicle inspection reporting requirements. Confirm specifics with FMCSA, your state agency, or a qualified compliance professional.