By RoadReady

FMCSA DVIR Retention Requirements: What Small Fleets Need to Know

DVIRs are one of the most audited documents in a motor carrier's files. Yet many small fleets misunderstand how long they must keep them, what constitutes a complete record, and where retention rules overlap with broader maintenance-record requirements. This guide walks through the federal regulations — 49 CFR 396.11, 396.13, and 396.3 — so you know exactly what to retain and for how long.

What Is a DVIR and Who Needs One?

A Driver Vehicle Inspection Report (DVIR) is a written or electronic record documenting the operating condition of a commercial motor vehicle. It is required by two companion regulations: 49 CFR 396.11, which governs the driver's post-trip inspection and condition report, and 49 CFR 396.13, which requires the next driver to review the prior DVIR before operating the vehicle. Together they create a continuous chain of accountability between drivers and the motor carrier.

Every driver who operates a commercial motor vehicle (CMV) in interstate commerce must complete a DVIR at the end of each day's work. The report covers the vehicle and, if applicable, each trailer operated during the day. Critically, the report must be prepared even when the driver finds no defects or deficiencies — a "no defects" DVIR is still a required record.

The regulatory framework assigns distinct roles. The driver completes the condition report after the trip. If defects are noted, a mechanic or other qualified person must review those defects and certify that repairs were performed or that the condition does not require repair before the vehicle is dispatched. The next driver to operate the vehicle must then review the previous DVIR and sign it, confirming awareness of any reported conditions. This three-party loop — driver, mechanic, next driver — is the backbone of FMCSA's vehicle-condition monitoring system.

The pre-trip and post-trip terminology can be confusing. In practical terms, the "post-trip" obligation under 396.11 requires the driver to report the vehicle's condition at the end of the day's work. The "pre-trip" obligation under 396.13 requires the subsequent driver to review the most recent DVIR before starting a trip. Both steps are mandatory and both generate records that must be retained by the carrier.

FMCSA DVIR Retention Requirements

The primary retention rule is found in 49 CFR 396.11(c)(2). It states that every motor carrier must retain the driver's vehicle condition report — and the certification of repairs or conditions — for a minimum of 90 days from the date the report was prepared. This applies to every DVIR, regardless of whether defects were found. A report noting "no defects" or "vehicle in satisfactory condition" carries the same 90-day retention obligation as one listing multiple safety deficiencies.

However, the 90-day rule is only the floor. When a DVIR documents defects and the carrier performs repairs in response, those repair records fall under a separate, longer retention requirement. 49 CFR 396.3(b) requires motor carriers to retain records of inspection, repair, and maintenance for each vehicle under their control. These records must be kept for the entire period the vehicle is under the carrier's control, plus an additional 12 months after the vehicle leaves the carrier's control. In practice, this means that if a DVIR triggers a brake adjustment, a tire replacement, or any other repair, the documentation of that repair — including the relevant portions of the DVIR and the mechanic's certification — must be retained for years, not just 90 days.

Small fleets often overlook the interplay between these two rules. The 90-day requirement under 396.11 applies to the DVIR itself as a daily-condition snapshot. The 396.3 requirement applies to any maintenance action that results from the DVIR. When in doubt, retain the full DVIR alongside the repair record for the longer period. FMCSA investigators expect to see a clear trail from defect identification to repair certification, and gaps in that trail create compliance exposure.

It is also worth noting that the condition report must be retained even when the vehicle is in satisfactory condition. Some carriers mistakenly believe that a "clean" DVIR does not need to be filed. The regulation is unambiguous: the report is required, and once generated, it must be retained for the full 90-day period. An auditor who asks for DVIRs from a given week and finds none will treat the absence as a violation — there is no presumption that the vehicle was simply not operated.

What Counts as a Complete DVIR?

Section 396.11 specifies the minimum contents of a compliant driver vehicle condition report. At a minimum, the report must include:

• The vehicle number or other identifying information (typically the unit number or VIN)
• The date the report was prepared
• A listing of any defects or deficiencies discovered by the driver that would affect the safe operation of the vehicle or result in a mechanical breakdown, or an indication that no such defects were found
• The driver's signature attesting to the accuracy of the report

When defects are reported, additional elements become mandatory. A mechanic or other qualified person must review each listed defect and either certify that repairs were performed or certify that the reported condition does not require repair before the vehicle is operated. This certification must include the mechanic's signature and the date. The carrier is responsible for ensuring this certification is completed before the vehicle is dispatched.

Under 49 CFR 396.13, the next driver to operate the vehicle must review the most recent DVIR. If the previous report listed defects, the driver must sign the report to acknowledge awareness of those defects and the mechanic's certification. This "review and sign" step completes the chain: the original driver reported the condition, the mechanic addressed it, and the subsequent driver confirmed the vehicle is fit for operation.

A DVIR that is missing any of these elements is non-compliant. Common audit findings include unsigned reports, missing dates, defect descriptions too vague to be actionable ("check brakes" without further detail), and mechanic certifications that lack a signature or date. Each missing element is a separate potential violation, and investigators will review DVIRs line by line during a compliance review.

Electronic DVIRs have a structural advantage here: well-designed systems enforce required fields before allowing a report to be submitted. A driver cannot skip the signature. A mechanic cannot certify without selecting a disposition for each defect. The form itself prevents the omissions that paper-based processes frequently produce.

Common Retention Mistakes Small Fleets Make

The most widespread mistake is only retaining DVIRs when defects are found. Many small carriers treat a "no defects" report as disposable — the driver fills it out, nobody files it, and it ends up in the trash or blows out of the cab. This is a direct violation of 396.11(c)(2). Every DVIR, regardless of content, must be retained for at least 90 days. During an audit, FMCSA investigators will cross-reference DVIRs against driver logs to verify that a report exists for every day the vehicle was operated. Missing reports are counted as violations.

Paper-based record systems create their own category of problems. DVIRs stored in the cab are routinely lost, water-damaged, illegible, or discarded prematurely. A driver finishes a week on the road, cleans out the cab, and throws away a stack of condition reports that haven't been scanned or filed. By the time an auditor requests records from that period, the carrier has nothing to produce. The regulation requires the carrier — not the driver — to maintain the records, so the carrier bears the enforcement consequences.

Another frequent gap is the failure to document the 396.13 driver review. The regulation requires the next driver to review the prior DVIR and sign it before operating the vehicle. In many small fleets, this step simply does not happen — or it happens verbally without a written record. An unsigned prior-report review is treated as a missing record during enforcement.

Retention periods also catch carriers off guard. The 90-day minimum sounds generous until you consider how quickly paper accumulates and how easily it gets purged. Carriers with weekly cab cleanouts, monthly office purges, or no filing system at all routinely fall below the threshold. And as noted above, when a DVIR triggers a repair, the associated records must be kept far longer under 396.3(b) — a fact many small operators are unaware of.

Finally, some carriers fail to retain the mechanic's certification as a distinct record. The repair certification is a separate regulatory obligation from the driver's condition report. If the mechanic signs off on the same physical form as the driver, that form must be retained intact. If the mechanic uses a separate work order or repair log, both documents must be retained and cross-referenced. Carriers that keep the DVIR but discard the shop ticket — or vice versa — create a gap that investigators will flag.

Penalties for Non-Compliance

FMCSA treats DVIR violations as a vehicle-maintenance issue, which means they directly affect the carrier's Vehicle Maintenance BASIC score in the Compliance, Safety, Accountability (CSA) program. Each missing, incomplete, or improperly retained DVIR adds violation points to the carrier's Safety Measurement System (SMS) profile. Carriers with elevated BASIC scores face increased scrutiny, including warning letters, targeted investigations, and cooperative safety plans.

Civil penalties for DVIR violations are assessed on a per-violation basis. Under FMCSA's current penalty schedule, fines for recordkeeping violations typically range from $1,270 to $16,000 per violation, depending on the severity, the carrier's history, and whether the violation demonstrates a pattern of non-compliance. A single audit that uncovers 30 days of missing DVIRs could result in 30 separate violations — the math adds up quickly for a small fleet operating on thin margins.

During roadside inspections, an inability to produce a current or prior DVIR is itself a violation. Inspectors can cite the driver and the carrier separately. The driver may receive an out-of-service order if the inspector determines that the vehicle's condition cannot be verified, particularly if the inspection also reveals mechanical deficiencies. These roadside violations feed into the carrier's CSA profile and compound the BASIC score impact.

Beyond direct penalties, DVIR non-compliance can trigger broader enforcement actions. High violation rates in the Vehicle Maintenance BASIC can lead to a comprehensive compliance review — a full-scale audit of the carrier's operations, safety management, and records. For small fleets, these audits are time-consuming and disruptive, often revealing additional violations in other areas. The cost of responding to an audit — in lost productivity, legal fees, and corrective-action plans — far exceeds the cost of maintaining compliant records in the first place.

Insurance implications are worth noting as well. Underwriters increasingly request CSA scores and compliance-review results. A poor Vehicle Maintenance BASIC score driven by DVIR violations can result in higher premiums or difficulty obtaining coverage — a material financial impact that compounds year over year.

How Electronic DVIRs Simplify Retention

The strongest argument for electronic DVIRs is structural: a well-designed system eliminates the most common compliance failures by making them mechanically impossible. When a driver submits a DVIR through an app, the record is automatically stored in the cloud with no cab cleanout, no filing delay, and no chance of water damage. Most electronic DVIR platforms retain records indefinitely by default, far exceeding the 90-day regulatory minimum without any manual effort from the carrier.

Electronic records are timestamped and tamper-evident. Each submission is logged with a precise date and time, tied to the driver's authenticated identity, and stored in a format that prevents after-the-fact alteration. During an audit, this removes any ambiguity about when a report was filed, who filed it, and whether it has been modified. Auditors can verify the integrity of electronic records far more efficiently than sifting through boxes of paper forms with questionable provenance.

Searchability is another practical advantage. When an FMCSA investigator requests DVIRs for a specific vehicle over a 90-day window, an electronic system can produce them in seconds — filtered by vehicle, date range, defect status, or driver. Paper-based carriers may need hours or days to locate and organize the same records, assuming they can find them at all. The ability to export audit-ready reports on demand turns a stressful compliance event into a routine data pull.

Perhaps most importantly, electronic DVIR systems enforce completeness by design. Required fields — vehicle identification, date, defect listing or "no defects" confirmation, driver signature — are built into the submission flow. A driver cannot skip the signature. A mechanic cannot certify repairs without addressing each listed defect. The 396.13 prior-report review can be prompted automatically when the next driver logs in. These guardrails eliminate the human-error patterns that generate the majority of paper-DVIR violations.

RoadReady is built around these principles — capturing every required data point at the moment of inspection, storing records securely and indefinitely, and making your entire DVIR history available for audits with a single search. If your fleet is still managing DVIRs on paper, the compliance risk alone may justify the switch.