11
Components a DVIR must cover
3 mo
DVIR retention period (396.11)
2
Certifications required to clear a defect
No
No-defect report no longer mandatory
In This Guide
What a DVIR Is and When It Is Required
A driver vehicle inspection report — universally called a DVIR — is the written record a driver prepares at the end of the workday documenting the condition of the commercial motor vehicle they operated. It is governed by 49 CFR 396.11. The DVIR is often described as the "post-trip" inspection report, and it is distinct from the pre-trip inspection a driver performs at the start of a shift. The pre-trip inspection is a safety obligation; the DVIR is the document that proves the post-trip condition of the vehicle and triggers the repair-and-review cycle.
Under 49 CFR 396.11(a)(1), every motor carrier must require its drivers to report, and every driver must prepare a report in writing at the completion of each day's work on each vehicle operated. The rule applies to commercial motor vehicles operated in interstate commerce, with a specific carve-out for intermodal equipment tendered by an intermodal equipment provider, which is covered separately. The purpose is straightforward: the driver who just finished operating the vehicle is the person most likely to know what is wrong with it, and the regulation captures that knowledge in a document the carrier and the next driver can act on.
The DVIR is not the same thing as the annual inspection under 49 CFR 396.17, and it is not the same thing as the per-vehicle systematic maintenance file under 49 CFR 396.3. The annual inspection is a once-a-year certified inspection. The maintenance file is the long-term history of a vehicle. The DVIR is the daily, defect-driven document. All three are checked in an FMCSA review, but they answer different questions.
DVIR vs. the maintenance file vs. the annual inspection
Think of the three Part 396 records as a timeline. The DVIR (396.11) is the daily snapshot kept for 3 months. The systematic maintenance file (396.3) is the vehicle's lifetime history, kept 1 year in service plus 6 months after. The annual inspection (396.17) is the yearly certified checkpoint, kept 14 months. A defect first appears on a DVIR, gets repaired and certified, and the repair work order lands in the maintenance file.
What the Report Must Contain
When a defect or deficiency is found, 49 CFR 396.11(a)(1) specifies the components the report must address. The report must cover, at a minimum, the following eleven systems. These are the items the regulation enumerates by name — and they are the items a driver should be checking on every post-trip inspection.
| # | Component the DVIR must cover | Why it matters at roadside |
|---|---|---|
| 1 | Service brakes (including trailer brake connections) | Brakes are the single largest source of out-of-service vehicle violations |
| 2 | Parking brake | A failed parking brake is a defect that must be listed and cleared |
| 3 | Steering mechanism | Steering play and component wear are safety-critical defects |
| 4 | Lighting devices and reflectors | Lamp and reflector defects are among the most frequently cited |
| 5 | Tires | Tread depth, sidewall, and inflation defects are common OOS items |
| 6 | Horn | An inoperative horn is a listed reportable defect |
| 7 | Windshield wipers | Wiper defects affect visibility and are explicitly named |
| 8 | Rear-vision mirrors | Missing or damaged mirrors are reportable |
| 9 | Coupling devices | Fifth wheel and coupling defects can cause separation |
| 10 | Wheels and rims | Cracked or improperly fastened wheels are OOS conditions |
| 11 | Emergency equipment | Fire extinguisher, warning devices, and spare fuses must be present |
Beyond the component list, the report has two more content requirements. First, it must identify the vehicle. The identification has to be clear enough that there is no confusion about which truck or trailer the defect belongs to — a fleet running multiple similar units cannot file a DVIR that simply says "the truck." Second, the driver must list each defect or deficiency discovered that would affect the safety of operation of the vehicle or result in its mechanical breakdown. The driver then signs the report under 49 CFR 396.11(a)(2)(ii).
A complete defect DVIR has four elements
- Clear identification of the specific vehicle (and trailer, if applicable)
- A list of each defect or deficiency affecting safe operation
- The driver's signature attesting to the report
- Space for the carrier's repair certification and the next driver's review
The No-Defect Rule, Explained
One of the most misunderstood points about the DVIR is whether a driver must file a report when nothing is wrong. The short answer is no. Under 49 CFR 396.11(a)(2)(i), a driver is not required to prepare a report if no defect or deficiency is discovered by, or reported to, the driver. This is the "no-defect" rule.
This was not always the case. For decades, property-carrying drivers were required to file a DVIR every single day even when there was nothing to report — a "no-defects" report. FMCSA eliminated that mandatory no-defect DVIR for property carriers in a 2014 final rule, concluding the paperwork imposed a recordkeeping burden without a corresponding safety benefit. In 2020, FMCSA extended the same relief to passenger-carrying commercial motor vehicles, rescinding the requirement that passenger carriers submit and retain no-defect DVIRs and harmonizing the two carrier types.
Two clarifications matter here. First, the no-defect rule relieves the carrier of the paperwork, not the driver of the inspection. The driver still must conduct the post-trip review of the vehicle and, before the next trip, be satisfied the vehicle is in safe condition under 49 CFR 396.13. Second, many carriers still require a no-defect record as an internal company policy because it documents that the inspection happened. That is a legitimate business choice — but it is a company rule, not a federal mandate, and a carrier should not confuse the two when training drivers.
The trap: "no report required" is not "no inspection required"
Drivers sometimes hear "you don't have to do a DVIR anymore" and stop inspecting. That is a misread of the rule. The inspection obligation under 49 CFR 396.13 — be satisfied the vehicle is safe — never went away. What changed is that a clean inspection no longer generates mandatory paperwork. A driver who skips the inspection entirely and then has a defect-related roadside violation has a much bigger problem than a missing form.
Carrier Repair Certification: Closing the Defect
A DVIR that lists a defect starts a clock. Under 49 CFR 396.11(a)(3)(ii), before the vehicle is operated again, the motor carrier — or its agent — must certify on the report that the listed defect or deficiency has been repaired, or that repair is unnecessary because it does not affect the safe operation of the vehicle. This certification is the carrier's signature on the report, separate from the driver's.
The "repair is unnecessary" path exists for a reason: not every item a driver flags is actually a safety defect. A driver might note a cosmetic crack or a non-safety item. The carrier reviews it, determines it does not affect safe operation, and certifies that no repair is required. But that determination has to be documented on the report — a carrier cannot simply ignore a logged defect. An open, uncertified defect on a DVIR is evidence that the carrier knew about a problem and put the vehicle back in service anyway, which is exactly the pattern roadside inspectors and FMCSA auditors look for.
The repair path
Defect is listed - carrier repairs it - carrier certifies the repair on the DVIR - the repair work order goes into the vehicle maintenance file under 396.3 - the vehicle returns to service.
The "no repair needed" path
Defect is listed - carrier reviews and determines it does not affect safe operation - carrier certifies on the DVIR that repair is unnecessary - the documented decision protects the carrier at audit.
The Next Driver's Review (49 CFR 396.13)
The final link in the chain is the next driver. Section 396.11 governs what the report contains and how the carrier certifies repairs; 49 CFR 396.13 governs what the driver must do before taking the vehicle out. Before driving a commercial motor vehicle, the driver must do three things:
Be satisfied the vehicle is in safe operating condition
49 CFR 396.13(a)This is the driver's independent safety judgment — a personal obligation that the no-defect rule did not eliminate. The driver cannot delegate this to a form.
Review the last driver vehicle inspection report
49 CFR 396.13(b)If a report was required under 396.11, the driver must review it before driving. This is how the incoming driver learns what the previous driver found and whether it was fixed.
Sign the report to acknowledge the review
49 CFR 396.13(c)The driver signs to acknowledge they reviewed the report and that the certification of required repairs is present. The signature requirement does not apply to defects on towed units no longer part of the combination.
Read together, 396.11 and 396.13 form a chain of custody for vehicle safety: the driver who finds a defect documents it, the carrier repairs and certifies it, and the driver who takes the vehicle out next reviews and acknowledges that the repair was certified. Break any link — an uncertified repair, an unreviewed report, a signature applied before repairs were done — and the carrier has a recordkeeping violation even if the underlying defect was eventually fixed.
Retention: Three Months
Under 49 CFR 396.11(a)(4), every motor carrier must maintain three documents together for three months from the date the written report was prepared: the original driver vehicle inspection report, the carrier's certification of repairs, and the certification of the driver's review. The retention clock starts on the date the report was prepared — not the date a defect was repaired or the date the next driver reviewed it.
Three months is a notably shorter window than the other Part 396 records. The systematic maintenance file under 49 CFR 396.3 must be kept for one year while the vehicle is under the carrier's control plus six months after it leaves. The annual inspection report under 49 CFR 396.17 is kept for fourteen months. Because the DVIR retention period is short and rolling, a carrier that relies on loose paper is at constant risk of having discarded a report an auditor or investigator later asks for. This is one of the strongest practical arguments for keeping DVIRs in a system where the three-month window — and the repair-and-review close-out — is tracked automatically.
| Record | Regulation | Retention period |
|---|---|---|
| Driver Vehicle Inspection Report (DVIR) | 49 CFR 396.11(a)(4) | 3 months from date report was prepared |
| Systematic maintenance file (per vehicle) | 49 CFR 396.3(c) | 1 year in service + 6 months after vehicle leaves carrier |
| Annual (periodic) inspection report | 49 CFR 396.17 / 396.21 | 14 months from date of inspection |
Common DVIR Mistakes That Become Violations
The DVIR is a simple document, but the way carriers handle it creates predictable problems. These are the patterns that turn a routine post-trip report into a citation or an adverse audit finding.
What gets carriers cited
- A listed defect with no carrier repair certification before the vehicle ran again
- Drivers signing the next-driver review before repairs were actually certified
- DVIRs that don't clearly identify which vehicle the defect belongs to
- Discarding DVIRs before the 3-month retention window closes
- Treating the no-defect rule as permission to skip the inspection entirely
- No documented link between a DVIR defect and the repair work order in the maintenance file
What a clean DVIR process looks like
- Every defect report is identified to a specific unit and signed by the driver
- Open defects are tracked until the carrier certifies repair or no-repair-needed
- The next driver reviews and signs only after repair certification is present
- DVIRs are retained for the full 3 months and easy to retrieve
- Repair certifications cross-reference the maintenance file work order
- Drivers are trained that the inspection is required even when the form is not
How FileFlo Tracks DVIRs and the Defect Close-Out Loop
FileFlo is the records and proof layer for your fleet's compliance documents. It is not a telematics platform, an ELD, or a shop maintenance system — it does not replace the tools you use to run inspections or schedule repairs. What it does is organize the documents those processes generate and prove the close-out loop required by 49 CFR 396.11 and 396.13 actually happened.
What FileFlo does with your DVIRs
- Stores the report, the repair certification, and the review together: Keep all three required documents under 396.11(a)(4) as one linked record per defect, so the chain of custody from driver to carrier to next driver is intact and exportable.
- Tracks open defects until they are certified closed: Flag any DVIR defect that does not yet have a carrier repair certification, so a vehicle never quietly returns to service with an uncleared defect on file.
- Holds DVIRs for the full 3-month retention window: No more discarded paper. Every report is retained and time-stamped from the date it was prepared, and retrievable in seconds when an investigator or auditor asks.
- Connects the DVIR defect to the maintenance file: Cross-reference the repair certification to the corresponding work order in the per-vehicle maintenance file under 396.3, so the two records corroborate each other.
- Produces an audit-ready export: When FMCSA reviews your Vehicle Maintenance records, export the DVIR history, repair certifications, and reviews as an organized package instead of digging through a filing cabinet.
Key Takeaways
- A DVIR is the daily post-trip report under 49 CFR 396.11. When a defect is found, it must identify the vehicle and list defects across 11 named systems, and the driver must sign it.
- The no-defect report is no longer mandatory. Property carriers were relieved of it in 2014 and passenger carriers in 2020 — but the inspection obligation under 396.13 remains.
- The carrier must certify repairs before the vehicle runs again. An open, uncertified defect on a DVIR is a classic Vehicle Maintenance violation.
- The next driver must review and sign before driving. 49 CFR 396.13 closes the loop between the driver who found the defect and the driver who takes the vehicle out.
- DVIRs are retained for 3 months. Shorter than the maintenance file (1 year + 6 months) or the annual inspection (14 months) — which makes a tracked system valuable.
DVIR Requirements: FAQ
Answers to common questions about the daily driver vehicle inspection report, the no-defect rule, repair certification, and retention under 49 CFR 396.11 and 396.13.
No. Under 49 CFR 396.11(a)(2)(i), a driver of a property-carrying commercial motor vehicle is not required to prepare a written report if no defect or deficiency is discovered by, or reported to, the driver. The federal rule was changed in 2014 to eliminate the mandatory no-defect DVIR for property carriers, and a parallel 2020 rule did the same for passenger carriers. A driver still must conduct the inspection and be satisfied the vehicle is safe under 49 CFR 396.13 — they simply do not have to generate paperwork when there is nothing to report. Many carriers keep a no-defect record as internal policy, but that is a company choice, not a federal mandate.
When a defect is found, 49 CFR 396.11(a)(1) lists the components the daily report must address: service brakes (including trailer brake connections), parking brake, steering mechanism, lighting devices and reflectors, tires, horn, windshield wipers, rear-vision mirrors, coupling devices, wheels and rims, and emergency equipment. The report must identify the vehicle clearly enough that there is no question which unit has the problem and must list each defect or deficiency that would affect safe operation or result in a mechanical breakdown. The driver must sign the report under 396.11(a)(2)(ii).
The motor carrier. Under 49 CFR 396.11(a)(3)(ii), before the vehicle is operated again, the carrier must certify on the report that the listed defect or deficiency has been repaired, or that repair is unnecessary. This is a separate signature from the driver's. Then, under 49 CFR 396.13(c), the next driver must sign the report to acknowledge they reviewed it and that the certification of required repairs is present. A defect that is logged but never cleared and certified is one of the most common Vehicle Maintenance violations cited at roadside, because the paper trail shows the carrier knew about the problem.
Yes. 49 CFR 396.13 requires that before driving a commercial motor vehicle, the driver must be satisfied it is in safe operating condition, review the last driver vehicle inspection report if one was required under 396.11, and sign that report to acknowledge the review and the certification that any required repairs were completed. The review step is what closes the loop between the driver who found the defect, the carrier who fixed and certified it, and the driver who takes the vehicle out next. Skipping the review — or signing a report before repairs are certified — defeats the purpose of the rule.
Under 49 CFR 396.11(a)(4), every motor carrier must maintain the original driver vehicle inspection report, the carrier's certification of repairs, and the certification of the driver's review for three months from the date the written report was prepared. This is a shorter retention period than the per-vehicle maintenance file under 396.3, which runs one year while the vehicle is in service plus six months after it leaves the carrier's control. The DVIR retention clock is keyed to the date the report was prepared, not the date a defect was repaired.
Yes. FMCSA permits driver vehicle inspection reports to be generated, signed, and stored electronically under 49 CFR 390.32, provided the electronic record reproduces the required information and the signatures are attributable to the correct driver and carrier official. An electronic DVIR system does not change what the report must contain or how long it must be retained — it changes the medium. The advantage of an electronic system is that defect status, repair certification, and the next driver's review can be tracked and time-stamped, which makes it far easier to prove the close-out loop required by 396.11 and 396.13 was actually followed.
Prove Every Defect Was Found, Fixed, and Reviewed
FileFlo keeps your DVIRs, repair certifications, and next-driver reviews together as one linked record, tracks open defects until they close, and holds every report for the full 3-month retention window. When FMCSA reviews your Vehicle Maintenance records, export the whole history in minutes.
Plans from $89/month — No credit card required — 5-day free trial