DVIR requirements: what US fleets must know about §396.11
Understand DVIR requirements for US fleets to ensure compliance and safety. Learn essential regulations and record-keeping tips.
DVIR requirements: what US fleets must know about §396.11
A Driver Vehicle Inspection Report is required under 49 CFR §396.11 at the completion of each day’s work whenever a driver finds a defect that could affect safety, and daily reports remain mandatory for passenger-carrying commercial vehicles regardless of defects found. The governing rules also sit in §396.13, which covers pre-trip review, carriers must keep DVIR records for a minimum of three months, and properly built electronic DVIRs satisfy the requirement just as paper ones do.
TL;DR:
- Drivers must file a DVIR at the end of each shift if they operate a commercial vehicle that could pose safety risks or when mandated daily for passenger carriers, regardless of defects found.
- Electronic DVIRs are legally acceptable as long as they capture all required data, signatures, and timestamps, with no format restrictions.
- Record retention must be for at least three months, and a complete DVIR includes detailed defect descriptions, signatures from the driver and mechanic, and review by the next driver.
- Failure to properly complete or retain DVIRs can lead to fines, CSA score penalties, and out-of-service orders, especially when records are falsified or incomplete.
- Building a workflow that enforces certification, signature, and proper record export is essential to passing audits and avoiding compliance violations.
Table of Contents
Who must complete a DVIR under federal rules?
The DVIR requirement applies to drivers operating a commercial motor vehicle (CMV) with a gross vehicle weight rating of 10,001 pounds or more, any vehicle designed to carry nine or more passengers for compensation, or any vehicle placarded for hazardous materials. FMCSA’s guidance on §396.11 and §396.13 makes clear the obligation sits with the driver operating the vehicle that day, while the motor carrier is legally responsible for ensuring the reporting, certification and retention chain actually happens.
A few scope points trip fleets up more than the rest:
- Leased owner-operators still file DVIRs; the carrier under whose authority they’re running remains responsible for the paperwork trail.
- Intermodal chassis and drayage combinations count as separate units, so both tractor and chassis need coverage.
- Smaller carriers running one or two trucks are not exempt from the reporting duty itself, only from some of the administrative overhead larger fleets carry.
- “Driver” in the regulation means whoever operated the vehicle that shift, not necessarily the assigned regular operator.
When does a driver have to file a DVIR?
The regulatory phrase “completion of each day’s work” means the point at which a driver stops operating a given vehicle for that shift, not necessarily midnight or a fixed clock time. A driver running a single 10 hour shift files at the end of it; a team driver swapping mid-route files when they hand off the vehicle, not when the truck itself stops moving.
- Property-carrying CMVs only require a written DVIR when the driver identifies a defect or deficiency that could affect safe operation or lead to a mechanical breakdown.
- Passenger-carrying CMVs require a DVIR at the end of every day’s work regardless of whether any defect was found, a distinction FMCSA’s 2014 rulemaking preserved even as it dropped the no-defect requirement for property carriers.
- The completed report must be turned over to the motor carrier before the driver goes off duty, so the carrier can act on any defect before the vehicle is dispatched again.
That 2014 change is worth understanding on its own terms. FMCSA rescinded the requirement that property-carrying drivers file a report even when nothing was wrong, reasoning that a mandatory “no defects found” form generated volume without safety value. Passenger operations kept the daily requirement because the agency judged the risk profile, and the number of people on board, justified the extra paperwork.
What must a DVIR actually contain?
A legally sufficient DVIR covers, at minimum, the eleven categories named in §396.11 of the Code of Federal Regulations: service brakes, parking brake, steering mechanism, lighting devices and reflectors, tyres, horn, windshield wipers, rear-view mirrors, coupling devices, wheels and rims, and emergency equipment. Most fleets layer additional items onto that base list, fluid levels, suspension components, load securement, because the regulation sets a floor, not a ceiling, and a defect in an unlisted component can still trigger an out-of-service order.
Defect descriptions need to be specific enough that a mechanic can act without questioning the driver again. “Brakes bad” fails; “right rear brake chamber leaking air, audible at idle” passes. The test the regulation applies is whether the defect could “affect the safety of operation” or contribute to a breakdown, a deliberately broad standard that FMCSA guidance interprets to include anything a reasonable mechanic would flag before releasing the vehicle.
The signature chain is where most audit failures actually happen:
- The driver signs the DVIR at completion of the day’s work, certifying what they found.
- If a defect was noted, a mechanic or carrier representative signs to certify repairs were made or that repair is unnecessary, per §396.13.
- The next driver to operate that vehicle reviews the prior DVIR and signs to confirm they’ve reviewed it before departure, closing the loop required under FMCSA’s official sample form.
Pro Tip: Train drivers to describe defects the way a mechanic would write a repair order, location, symptom, and severity, rather than a one-word complaint. It cuts the back-and-forth that delays certification and keeps the paper trail defensible in an audit.
Exceptions and special cases fleets get wrong
Passenger-carrying CMVs remain the clearest exception to the “defects only” rule; they need a daily DVIR whether or not anything is wrong, a distinction that catches shuttle and paratransit operators off guard when they assume the 2014 changes applied fleet-wide.
Drop-and-hook operations raise a separate question: does the trailer need its own report? It does, whenever that trailer continues in service under a different driver, since documentation has to track each unit separately rather than following the tractor alone. A few other cases worth flagging:
- Single-vehicle owner-operators still file DVIRs; there’s no blanket exemption for small operations, only fewer hand-offs to manage.
- Driveaway/towaway operations (moving unladen vehicles for delivery) have their own inspection provisions under Part 396 that run parallel to standard DVIR duty.
- Combination vehicles require the driver to be satisfied both the power unit and the trailer are safe before operating them together, per FMCSA guidance on driver-vehicle inspection reports.
- Leased equipment under an independent contractor arrangement doesn’t shift the reporting duty away from whoever is driving that day.
How long must you keep DVIRs, and are digital ones legal?
FMCSA’s minimum retention period for DVIRs and the related repair certifications is three months from the date of the report, a figure set out in the CSA Safety Planner’s vehicle inspection guidance. Many fleets keep records considerably longer than that floor, since a defect report can become the key document in a post-accident liability claim years after the fact.
An auditor pulling a DVIR file is checking for a specific, unglamorous set of things:
- A legible, dated report for the vehicle and date in question.
- The driver’s signature, and, if a defect was noted, both the mechanic’s certification and the next driver’s acknowledgement signature.
- A clear description of any defect and what was done about it, not just a checkbox.
- Consistent timestamps that match the vehicle’s dispatch and hours-of-service records.
Electronic DVIRs are fully acceptable under federal guidance, provided the system captures every required data field, preserves signature authenticity, and can produce a readable export on demand. FMCSA’s position, laid out in its DVIR guidance, treats a compliant eDVIR the same as a paper one; the format doesn’t matter, the completeness and integrity of the record does. Systems that enforce required fields and timestamp every signature tend to eliminate the two failures auditors flag most, missing signatures and incomplete defect descriptions.
What happens when DVIR compliance fails?
Missing, incomplete or falsified DVIRs are among the most commonly cited maintenance violations in roadside and compliance review audits, and the consequences stack: a monetary fine per violation, a hit to your CSA score that follows the carrier for months, and, if the defect itself is serious enough, an out-of-service order that pulls a truck off the road mid-route.
Enforcement records tied to §396.11 show fines escalate sharply when a carrier is found to have falsified records rather than simply missed one. The out-of-service cost is often the more expensive part: a driver stranded, freight delayed, a customer relationship strained. The fix is unglamorous but effective, close the loop on every signature before the vehicle leaves the yard, and don’t let “we’ll certify it later” become standard practice.
Building a DVIR workflow that survives an audit
Getting DVIR compliance right isn’t complicated, but it does need a system that doesn’t rely on drivers remembering every field under pressure at the end of a long shift.
- Run the pre-trip inspection and log any carried-over defects from the prior DVIR before departure.
- Capture defects immediately at end of shift, with enough detail that a mechanic can act without a follow-up call.
- Route the report to a certifier who signs off on repair completion or explains why repair wasn’t necessary.
- Require the next driver to review and sign before operating the vehicle, closing the §396.13 loop.
- Export retained records into an audit-ready format the moment a compliance review is requested.
The technical bar for an eDVIR system worth trusting is fairly specific: immutable timestamps that can’t be edited after the fact, genuine signature capture rather than a generic “acknowledged” button, per-vehicle record separation, and a clean export a compliance officer can hand over without reformatting anything. Logivo’s transport management platform builds defect reporting and audit exports around exactly that chain of custody, and its walkaround inspection tools let drivers log and certify defects from the same mobile app they already use for job tracking. Fleets can trial the full workflow for a month before committing to anything.
Pro Tip: Don’t wait for an audit letter to test your export process. Pull a sample DVIR packet from your system today and time how long it takes, if it’s more than a few minutes, your record chain has a gap worth fixing now.
The gap between DVIR policy and DVIR practice
Most fleets already know the regulation exists. Where compliance actually breaks down is in the assumption that having a DVIR form, paper or digital, is the same as having a compliant process. It isn’t. The regulation cares about the chain: driver report, certifier signature, next-driver review, all inside the retention window. A form with one signature missing is not a partial compliance win; it’s a documented failure waiting for an auditor to find it.
The conventional advice, “make sure drivers fill out the form”, undersells the actual risk. The bigger failure point sits with carriers who never build a repair certification workflow tight enough to close the loop before the truck goes back out. A driver who reports a defect and then watches the same truck get dispatched the next morning without a certifying signature has just handed an auditor, or a plaintiff’s lawyer after an accident, exactly what they need.
If you take one thing from this, prioritise the certification step over the reporting step. Drivers report defects reasonably well once trained; it’s the mechanic sign-off and next-driver acknowledgement that carriers let slip under schedule pressure. Fix that link first, and the rest of the DVIR chain tends to hold together on its own.
— Vytautas
This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.
Sources
FAQ
Who is required to fill out a DVIR?
Drivers operating a CMV with a GVWR of 10,001 pounds or more, a vehicle designed for nine or more passengers, or a hazmat-placarded vehicle must complete a DVIR under §396.11. The motor carrier is responsible for ensuring the process, including certification and retention, is followed.
What is not a DVIR requirement?
DVIRs are not required for property-carrying CMVs on days when no defect affecting safe operation is found, following the 2014 rule change; passenger-carrying CMVs are the exception and still need a daily report regardless.
When should a driver complete a DVIR?
A driver completes a DVIR at completion of each day’s work, meaning when they stop operating that specific vehicle for the shift, and must hand the report to the carrier before going off duty.
How do I know if I am subject to FMCSR?
You’re subject to the Federal Motor Carrier Safety Regulations if you operate a CMV over 10,001 pounds GVWR, carry nine or more passengers for compensation, or transport placarded hazardous materials in interstate commerce.
Recommended