Prevention FAQ — FMCSR 396.11(c) DVIR Defect Repair

Inspectors verify that every defect marked on a driver's pre-trip or post-trip DVIR has been repaired and documented before the vehicle is returned to service. They cross-check the DVIR against the repair log and vehicle maintenance records. Look for inspection notes that flag incomplete repairs, missing sign-offs, or repairs performed but not formally logged. The citation is issued when a driver notes a defect (e.g., cracked mirror, worn brake linings) and the carrier dispatches the vehicle without proof that the defect was corrected. Across our 13 million inspection records, we see this code rarely cited in isolation—most often it co-occurs with other maintenance violations, indicating a systemic gap in your repair-tracking workflow rather than a single missed item.

Your DVIR form must require drivers to document the specific location, component, and severity of each defect. Include mandatory fields: defect description, safety risk level (minor/major), and a box for the driver to confirm whether the vehicle is safe to operate. After the repair, the form must capture the date repaired, technician name, repair description, and supervisor sign-off. Use a color-coding or flagging system so that vehicles with open defects never reach the dispatch lot. Consider a mobile app or QR-code link so drivers can photograph defects and attach them to the record. Most importantly, establish a rule: no vehicle leaves the yard until every defect on that day's DVIR is marked "repaired and verified" in your maintenance system.

Drivers must carry the signed DVIR for the current vehicle (typically the last 7 days of records). The carrier must retain all DVIRs for at least one year, organized by vehicle and date. Each record must include: the original driver signature, defect description, repair date/time, technician name, parts replaced (if any), and supervisor verification. Electronic DVIR systems are acceptable if they are tamper-proof and searchable by vehicle and date range. During inspections, roadside officers request the last 30 days of DVIRs to spot patterns of recurring, unrepaired defects. Keep records accessible—inspectors spend 10–15 minutes cross-checking DVIR against vehicle condition. Missing or illegible repair documentation is treated as a citation because it indicates you cannot prove the defect was corrected.

Our inspection records show 396.11(c) most frequently paired with 396.3(a)(1) (general inspection/repair/maintenance failures), which suggests your repair workflow lacks accountability—defects are logged but repairs are never tracked or verified. The second common pattern links to 393.47E (slack adjuster defects) and 393.11 (lighting/reflector issues), indicating that drivers report defects correctly, but your shop either lacks parts inventory or technicians don't prioritize non-emergency repairs. The third pattern, co-occurrence with 396.17(c) (no proof of periodic inspection), reveals a deeper issue: your fleet may lack a formal maintenance schedule, so defects pile up between inspections instead of being fixed immediately. Root-cause analysis should focus on: Is your repair authorization process too slow? Do technicians skip sign-off? Is there no visibility into which vehicles have open defects? Addressing these three areas closes most 396.11(c) risk.

Implement a three-step verification process. First, the technician who performs the repair must photograph the repair (especially for brake, lighting, or structural defects) and attach it to the work order. Second, a supervisor or lead technician (not the original technician) must visually inspect the repaired component and sign off in your maintenance system. Third, before the vehicle is dispatched, the dispatcher runs a checklist against the DVIR, confirming every defect has a signed repair record. For high-risk defects (brakes, steering, lighting), consider a road test or brake test before dispatch. Document the verification date, time, and supervisor name in the system. If a defect is found to be incompletely repaired during a roadside inspection, the citation is attributed to the carrier, not the technician—so your verification step is your liability shield.

Immediately pull the cited vehicle's DVIR history for the 30 days before the citation date. Identify which defect was not repaired and why: Was it reported on the DVIR? When was it logged? Was a repair work order created? Was the repair completed but not documented? Was it documented but the supervisor failed to sign off? Next, audit your dispatcher's records to see if the vehicle was released despite an open defect. Check your maintenance system for barriers: unclear repair status, missing technician names, or inconsistent sign-off practices. Interview the driver and technician involved. Finally, review the same 30-day period for other vehicles—if one vehicle had a missed repair, your process likely allowed others to slip through too. This post-event review typically reveals a process failure, not a compliance misunderstanding.

Each 396.11(c) citation carries a CSA severity weight of 5, contributing to your fleet's Vehicle Maintenance BASIC score. While we have recorded zero citations for this code across our 13 million inspection records, it remains an active enforcement point, meaning inspectors actively look for it. For context, peer codes in the Vehicle Maintenance category—such as 396.3(a)(1) (general inspection/repair/maintenance) with 236,919 citations and 393.9(a) (inoperable lamps) with 660,737 citations—show much higher citation volume and greater OOS rates. A single 396.11(c) citation moves your BASIC percentile slightly downward; repeated citations cascade into a higher overall maintenance ranking, triggering more frequent inspections and potential roadside enforcement focus on your fleet. Prevention is far more efficient than remediating a damaged BASIC score.

For drivers: emphasize that every defect they mark on a DVIR is a legal record. Train them to be specific (not "brakes feel weird" but "right rear brake pad worn to 1/8-inch") and to refuse to operate a vehicle if a critical defect from the prior shift is still present. For technicians: focus on the importance of sign-off discipline. Teach them that a repair is not complete until the work order is closed in your system with a supervisor signature. Include a session on parts inventory and lead times so technicians can flag likely repair delays early and notify dispatch. For dispatchers: run quarterly drills using your DVIR system to ensure they understand how to read repair status and reject vehicles with open defects. For safety managers: conduct annual audits of DVIR compliance and repair documentation to catch gaps before an inspector does.

A DataQs challenge is appropriate only if the citation is factually wrong—for example, if the DVIR clearly shows the defect was repaired and signed off before dispatch, but the inspector's report omits that documentation. Do not challenge a citation simply because you believe the defect was minor or the repair was incomplete. Gather all contemporaneous records: the original DVIR, the repair work order, supervisor sign-off, dispatch logs, and any photographs or test results. If these records conclusively show the defect was corrected and verified before the vehicle left your facility, submit them to FMCSA with a detailed narrative explaining the timeline. Weak challenges damage your credibility and consume your team's time. Strong challenges are fact-based and document-backed. Given that zero citations have been recorded for this code in our dataset, any citation your fleet receives will be highly unusual—that circumstance alone suggests a closer review of your evidence is warranted.

Run a full audit quarterly (every 90 days). Pull a random sample of 30–50 DVIRs from the prior quarter and verify that every defect marked was repaired and documented before dispatch. Check for defects that recur on the same vehicle across multiple DVIRs—recurring issues may indicate improper repairs or parts that need replacement rather than patching. Use the audit to measure: percentage of DVIRs with complete repair documentation, average time from defect report to repair completion, and any vehicles that were dispatched with open defects. Track these metrics month-over-month so you can see trends. Conduct a deeper audit annually, reviewing 12 months of DVIR data across your entire fleet to ensure no systemic gaps exist. Given that our inspection records show zero enforcement volume for this code, many fleets believe it is not actively enforced—but zero citations does not mean zero risk. Proactive auditing ensures you never become the first citation in your state.