Quick answer: A DVIR (Driver Vehicle Inspection Report) is the federally required record of a pre-trip and post-trip check of a commercial vehicle's safety systems — brakes, lights, tires, coupling devices, steering, and more. Under the Federal Motor Carrier Safety Administration's rule at 49 CFR 396.11, drivers must inspect the vehicle before driving and file a written report at the end of each day noting any defect that could affect safety or cause a breakdown. If a defect is found, the carrier must fix it and certify the repair before the vehicle goes back on the road.
Key takeaways
- Federal rule 49 CFR 396.11 requires a post-trip DVIR any time a defect or deficiency is found or reported; no defects found still needs documentation under most carrier policies.
- A DVIR must cover specific systems — FMCSA lists brakes, steering, lights, tires, horn, mirrors, wipers, coupling devices, and emergency equipment among the required items.
- The carrier, not just the driver, has a legal duty: 49 CFR 396.13 requires the motor carrier to repair any defect that would affect safe operation before the vehicle is dispatched again.
- Electronic DVIRs are legal and widely used — FMCSA guidance confirms electronic signatures and records satisfy the paper requirement as long as the system captures the same data.
What exactly is a DVIR, and who has to file one?
A DVIR is a written or electronic record showing a driver checked a commercial motor vehicle for safety defects before or after a trip. The requirement comes from the Federal Motor Carrier Safety Administration (FMCSA), under 49 CFR 396.11 and 396.13, and it applies to drivers operating vehicles that require a CMV inspection under DOT rules — generally trucks over 10,001 pounds GVWR, buses, and other commercial vehicles subject to Part 396.
The report isn't optional paperwork. It's the paper trail that proves a driver looked the vehicle over and that the carrier acted on what was found. If a truck rolls out of the yard with a cracked brake line and no DVIR was filed, both the driver and the carrier are exposed — during a roadside inspection, after a crash, or in a DOT compliance audit.
Independent owner-operators leased to a carrier still have to comply. The rule follows the vehicle and the operation, not the size of the company.
What must a driver inspect before every trip?
A pre-trip inspection has to cover the systems FMCSA identifies as safety-critical, and skipping any of them is the most common way drivers miss a real problem before it becomes a roadside violation. The exact list a carrier requires can vary slightly, but the federal reference points (49 CFR 393 and 396) generally point drivers toward these areas:
- Brakes — service brakes, parking brake, and brake connections for air or hydraulic systems
- Steering mechanism — free play, linkage, and steering column condition
- Lighting devices and reflectors — headlights, taillights, turn signals, brake lights, and reflective tape
- Tires — tread depth, sidewall damage, inflation, and wheel condition
- Horn — confirming it's audible and functional
- Windshield wipers — operation and blade condition
- Rear-vision mirrors — cracked, missing, or improperly adjusted mirrors
- Coupling devices — fifth wheel, kingpin, and trailer connections for combination vehicles
- Emergency equipment — fire extinguisher, spare fuses, and warning devices (triangles or flares)
A pre-trip check should take a driver several minutes minimum, not thirty seconds. Rushing it defeats the purpose — most roadside out-of-service violations trace back to something that was visible at the dock but never got looked at.
What happens after the drive — what does a post-trip DVIR actually require?
At the end of each day's work, the driver must complete a written report covering the vehicle they operated, and the report must note anything found that would affect safety or cause a mechanical breakdown. Per 49 CFR 396.11, the post-trip DVIR needs to include:
- The vehicle identification (unit number or plate)
- The date
- A list of every defect or deficiency the driver discovered or was told about that day
- The driver's signature
- Certification that the required repairs were completed, or that repair is not necessary, before the vehicle is used again
If nothing is wrong, most carriers still require the driver to submit a report stating there were no defects — this isn't strictly spelled out in the same way for every scenario under federal rule, but it's standard carrier policy because it closes the loop for every vehicle, every day. Confirm your specific carrier's policy on this, since some carriers only formally require a report when a defect exists.
Don't skip this: under 49 CFR 396.13, a driver is not permitted to operate a vehicle that has a defect likely to affect safe operation. If the previous driver's DVIR flagged something, the next driver has to review it before the trip starts — not after they're already loaded and rolling.
Who signs off, and what's the carrier's responsibility?
The carrier's obligation doesn't end when the driver hits submit — FMCSA requires the motor carrier to certify that any defect noted on a DVIR was either repaired or determined not to need repair before the vehicle is dispatched again. That certification, along with the driver's original report, has to be kept on file. FMCSA requires DVIRs and related records to be retained for a set period (carriers should confirm the current retention requirement directly with FMCSA, since retention rules are periodically revisited), and they need to be available for review during a roadside inspection or a compliance audit.
This is also where a lot of small and mid-size fleets lose track. A paper DVIR pad in the truck door pocket is easy to lose, easy to forge, and easy to forget to reconcile against the shop's repair log. That gap — a defect reported but never formally closed out — is exactly the kind of finding that shows up in a DOT compliance audit. We cover what auditors actually look for in What to Expect During a DOT Compliance Audit.
What should a driver look for in a DVIR app?
A DVIR app needs to do more than let a driver check boxes on a phone — it should route the report to someone at the carrier who can act on it, and it should block the truck from being treated as ready if a defect hasn't been resolved. The most useful features to look for:
| Feature | Why it matters |
|---|---|
| Photo capture on the report | Documents the actual defect, not just a text note |
| Direct routing to a review queue | Nothing sits unread in a driver's outbox |
| Defect-to-repair linkage | Ties the report to the shop's fix and certification |
| Dispatch block on open defects | Stops a truck from getting reassigned before it's safe |
| Digital signature and timestamp | Satisfies FMCSA's requirement without paper |
| Searchable history per vehicle | Makes audit prep and CSA review faster |
FMCSA has confirmed that electronic DVIRs and signatures meet the requirement, as long as the system captures the same information a paper form would. The format doesn't matter to the regulation — completeness and follow-through do.
On the Yolda platform, drivers submit DVIRs and other ops reports straight from the mobile app, and every one lands in a single review queue alongside DOT inspections, repairs, and fuel receipts — nothing gets auto-approved, so a company reviewer always has to look at it before it's closed out. The app also blocks dispatch-related work with a clear banner when a compliance document is missing or expired, which keeps a defective or non-compliant vehicle from quietly slipping back into rotation.
DVIR checklist for drivers and dispatchers
Use this as a quick daily reference, whether the fleet runs paper forms or an app.
Before the trip:
- Walk the full perimeter of the vehicle and trailer
- Check all tires for tread depth, inflation, and visible damage
- Test brakes, including parking brake, before leaving the yard
- Confirm all lights and reflectors are working, including trailer lights
- Inspect coupling devices — fifth wheel, kingpin, glad hands, safety chains
- Test the horn and windshield wipers
- Verify mirrors are intact and properly adjusted
- Confirm emergency equipment is on board and accessible
- Review the prior driver's DVIR for any open defects
After the trip:
- Note every defect or deficiency found or reported during the day
- Include vehicle unit number, date, and odometer if required
- Sign the report
- Submit it before leaving the vehicle, not the next morning
- Confirm with dispatch or the shop whether a listed defect grounds the truck
Getting this daily habit right ties directly into a fleet's broader safety record — repeated DVIR gaps or ignored defects show up in CSA scores over time, which we walk through in How DOT Safety Scores (CSA/BASIC) Actually Work.
DVIRs feel like routine paperwork until the day a missed brake defect turns into a roadside out-of-service order or worse. The habit is simple, the rule is clear, and the fix is usually cheap compared to what happens when it's skipped. If your fleet is still chasing paper DVIR pads across multiple trucks, Yolda gives drivers a straightforward way to submit inspection reports from their phone and puts every one in front of a reviewer before the truck goes back out. Reach out to see how it fits your operation.
