Prevention FAQ — FMCSR 396.13(a) DVIR Review & Certification

Inspectors verify that the current or most recent driver has physically reviewed the last completed driver vehicle inspection report (DVIR) and signed it to acknowledge that review. They look for evidence of the driver's signature and date on the DVIR document—either printed, digital, or handwritten—paired with the inspection itself. The citation is issued when that acknowledgment signature is missing or when the driver cannot demonstrate they read the report before taking the vehicle. Our inspection records show this is enforced as a documentation compliance issue rather than a vehicle defect, making it a roadside documentation check.

Build a mandatory pre-trip gate item: driver must locate, read, and sign the prior DVIR before vehicle departure. The checklist step should read: 'Review last DVIR for open items, sign acknowledgment, date entry.' Require drivers to note the date and signature location (logbook, tablet, paper form, or fleet app) and to ask dispatch or maintenance about any open defects flagged in that report. Include a visual reminder placard in the cab stating 'Must sign DVIR before drive.' This prevents the common scenario where drivers inherit vehicles without reviewing what the previous operator reported.

Drivers must carry a copy—digital or paper—of the most recent DVIR or have immediate access to it via fleet app or logbook. The DVIR must include the prior driver's inspection results, date, and signature. The fleet must retain all signed DVIRs for each vehicle in a centralized system (paper log, cloud platform, or ELD) for at least the duration the vehicle is in service, indexed by vehicle unit number and date. When a driver receives a vehicle, that DVIR handoff should be documented: prior driver's name, current driver's name, date, and both signatures. Digital systems should timestamp the acknowledgment. This creates an unbroken chain of DVIR custody and certification.

Our records indicate this violation frequently co-occurs with broader vehicle maintenance documentation failures. When a driver fails to certify a DVIR, check whether the fleet is also missing periodic inspection proof (codes 396.17C and 396.17(c) combined represent over 410,000 citations in our database, both with 0.0% OOS rates—indicating systemic documentation gaps). Investigate whether drivers understand the link between reading the DVIR and identifying defects before they become roadside safety violations. A second pattern: check if maintenance repair records match defects reported in DVIRs—misalignment suggests drivers aren't reviewing reports or maintenance isn't closing the loop. Root-cause conversation: Is the DVIR system visible to drivers? Is there a penalty or recognition for thorough DVIR completion?

Establish a closure protocol: maintenance must sign off on each defect noted in the DVIR, documenting the repair, parts used, technician name, and date completed. Create a DVIR-to-work-order link so no defect is orphaned. Before the vehicle is released, a supervisor—not the repairing technician—must re-inspect the corrected item and initial the DVIR or work order. The next assigned driver then reviews that completed DVIR, confirming the repair is noted and signed. If a defect is deferred (e.g., minor cosmetic issue with DOT clearance), that deferral and authorization must be documented in the DVIR with a supervisor signature and date. This layered sign-off prevents the scenario where a driver inherits a vehicle with an uncertified repair or an open defect flagged by the prior driver.

After a 396.13(a) citation, immediately review the DVIR in question and interview both drivers involved. Ask the cited driver: Did you see the prior DVIR? Where was it? Did you understand what you were supposed to sign? Ask the prior driver: Did you complete and submit the DVIR? Interview your dispatcher: Was the DVIR provided to the new driver before departure? Then audit 10–15 other vehicle handoffs from the same week to spot patterns. Check your DVIR system for missing or unsigned reports. Measure the percentage of DVIRs with driver certification signatures. If it's below 98%, you have a systemic issue—not a one-off. Document findings and retrain drivers on DVIR procedures, emphasizing that certification is not optional and is checked at roadside.

FMCSR 396.13(a) carries a CSA severity weight of 3, meaning each citation contributes to your Vehicle Maintenance BASIC percentile. While our records show zero citations for this code across all 13 million inspections in our database, it remains an eligible violation under Vehicle Maintenance. This means if your fleet does receive a citation, it will impact your BASIC and potentially your safety profile for insurance, shipper vetting, and federal audits. The prevention payoff is significant: avoiding this citation entirely requires only documentation discipline—no parts, no downtime, just process rigor. Compare that to peer violations like inoperable lamps (660,737 citations, 15.4% OOS rate) or general inspection/maintenance failures (236,919 citations, 45.3% OOS rate); DVIR certification is a control that costs almost nothing and directly prevents citations.

Train drivers on four core points: (1) why DVIR review matters—the prior driver's observation catches safety defects before a roadside inspection does; (2) how to read a DVIR and understand notation—what does 'requires repair' vs. 'defer' vs. 'safe to operate' mean?; (3) what the signature means—you are confirming you read it and either accept the vehicle or flag an issue; (4) what to do if you inherit a vehicle with no DVIR or an unsigned DVIR—don't leave; ask dispatch to provide it, read it, and sign it before departure. Use real-world scenarios: 'A prior driver noted brake slack adjuster was tight—you read that, and at the next stop you check it before it becomes a roadside citation.' Include a quick reference card in each vehicle and in the driver handbook. Reinforce during new-hire onboarding and quarterly safety meetings.

Challenge a 396.13(a) citation if you can provide contemporaneous evidence that the driver did read and sign the DVIR, but the inspector did not locate it, misread it, or the signature was unclear in format. For example, if your fleet uses digital DVIR with timestamped driver acknowledgment, pull that record and the timestamp showing the driver opened and confirmed the report. If you use paper and the driver signed but the signature is faint or on a different sheet than the inspector expected, provide a clear image of both documents together. Do not challenge based on procedural confusion (e.g., 'the driver meant to sign but forgot')—that is not a DataQs case. Challenge only if the evidence proves the driver's action actually occurred but the citation was issued due to inspector error or misunderstanding of your documentation system.

Audit monthly. Our records show zero citations for 396.13(a) in the last 90 days and zero all-time, which suggests either nearly universal compliance or extremely rare enforcement. However, that rarity makes it a low-risk area—ideal for a streamlined self-audit. Each month, pull a random sample of 20–30 vehicle handoffs and verify that the incoming driver's signature and date appear on the prior DVIR. Measure your certification rate (e.g., '28 of 30 DVIRs certified = 93%'). If you sustain 95%+ certification, continue monthly audits. If you dip below 95%, increase to weekly audits for two weeks, retrain drivers, and check your DVIR system for usability issues. This cadence is light enough to fit a safety manager's workload but frequent enough to catch compliance drift before an inspector does.