DVIR Defect Before Dispatch: Repair, Certification and Driver Review

A driver finishes a shift and reports a defective brake component, lamp or tire. Dispatch needs the vehicle again in the morning. The mechanic may be available overnight, or a supervisor may think the reported condition does not require repair. The next driver still needs a vehicle that is safe to operate and a report that shows what happened to the defect. A note saying “checked” is not always enough to explain the decision.

For covered US commercial motor vehicle operations, the federal sequence comes from 49 CFR 396.11 and 396.13. The driver reports the relevant defect on a driver vehicle inspection report, commonly called a DVIR. The motor carrier evaluates and addresses the report. Before the vehicle operates again, the carrier or its agent certifies on a report listing a defect that it was repaired or that repair is unnecessary. The next driver reviews the required prior report, signs the acknowledgment where the rule calls for it and is satisfied that the vehicle is safe to operate.

Those steps answer different questions. The driver's report identifies what was found. The carrier's certification records the response. The next driver's review acknowledges the prior report and certification. None of these steps makes an unsafe vehicle safe merely because a box was checked. This guide focuses on that defect-to-next-dispatch decision. It does not replace the separate rules for roadside inspection reports, intermodal equipment, state requirements or a mechanic's technical assessment of a particular fault.

First decide whether the report and vehicle are within this rule

The federal DVIR provision has a defined scope. Under section 396.11, a driver of a covered vehicle supplied by a motor carrier prepares a report at the completion of the day's work for each vehicle operated, subject to the provision's terms and exceptions. The report identifies the vehicle and lists a defect or deficiency discovered by or reported to the driver that would affect safe operation or lead to mechanical breakdown. It is signed by the driver. A driver who operates more than one covered vehicle during the day deals with each vehicle separately.

The current federal text says drivers need not prepare a report if no defect or deficiency was discovered or reported. It also excludes a private motor carrier of passengers that is a nonbusiness operation, a driveaway-towaway operation and a motor carrier operating only one commercial motor vehicle from the rules in this section. Intermodal equipment supplied by an intermodal provider has its own process in a separate paragraph. A fleet manager should therefore check the operation and the applicable rule before issuing a blanket statement that every driver must file a no-defect report every day.

This distinction matters because some older guidance summaries still describe a passenger-carrier no-defect reporting split. The current section 396.11 text controls the federal proposition used here. A carrier may choose a fuller internal reporting process, and other legal or contractual duties may apply, but that choice should not be presented as the same federal DVIR requirement. This article starts where a required DVIR actually lists a defect.

Put the reported defect in the right decision queue

Section 396.11 asks the driver to report defects and deficiencies that would affect the safety of operation or result in mechanical breakdown. It lists components such as service and parking brakes, steering, lights, tires, coupling devices, wheels and emergency equipment. That is a reporting framework, not an invitation to dismiss an unusual problem because it is absent from an example list. The condition and its effect on operation matter.

Once a report reaches the carrier, preserve the original description. A mechanic may find that the component is functioning, that a different part is at fault, or that repair is needed. Recording the original observation alongside the later assessment makes the chain intelligible. Replacing the driver's words with a later summary can make it hard to establish which defect was reported and how it was resolved.

An internal triage should identify the vehicle, report date, driver, reported component, current location, planned next trip and person responsible for the response. This is a practical workflow, not an extra federal DVIR form. If the condition might affect safe operation, prevent an ordinary dispatch decision until the carrier has made the required repair and certification determination. For an uncertain mechanical fault, obtain a competent technical assessment rather than asking a dispatcher to turn an unresolved safety question into a paperwork label.

The general unsafe-operation rule in section 396.7 also matters. A motor vehicle must not be operated in a condition likely to cause an accident or breakdown. That provision contains a limited rule for a condition discovered while the vehicle is already on the highway: movement to the nearest place where repairs can safely be made is allowed only if that is less hazardous to the public than leaving it on the highway. It is not a general permission to start a new trip with a known unsafe defect.

Repair, or document why repair is unnecessary

Section 396.11's corrective-action paragraph requires the motor carrier or its agent to repair a defect or deficiency listed on the DVIR that would be likely to affect the safety of operation before requiring or permitting a driver to operate the vehicle. The carrier or agent must also certify on a report listing a defect that the defect was repaired or that repair is unnecessary before the vehicle operates again.

The two clauses should be read together. “Repair unnecessary” is a certification option, not a way to avoid addressing an actual safety defect. It may fit a report that, after inspection, does not describe a condition needing repair. The person making that decision should be able to explain the technical facts that support it. If the reported condition is likely to affect safe operation, the repair duty applies. If the facts remain uncertain, the answer is further assessment, not an unsubstantiated certification.

For example, a driver reports a lamp that did not illuminate during the trip. A later inspection might find a defective lamp and confirm replacement. Alternatively, it may establish a different reason for the observation and show that no repair is needed. The relevant legal question is not whether the vehicle has a convenient time slot. It is what the reported condition actually was, whether it was likely to affect safe operation and whether the carrier can make the required certification truthfully. The same logic applies to a tire, brake or coupling concern, though the technical and operational consequences may differ sharply.

The federal provision does not prescribe a single maintenance software screen, photograph, work-order label or mechanic sign-off format for every case. A carrier can use those records to support the required certification. Keep the relationship clear: the DVIR identifies the defect, the work record may show what happened, and the certification on the DVIR states the repair or no-repair outcome.

The next driver's review is a separate gate

Before driving, section 396.13 requires a driver to be satisfied that the motor vehicle is in safe operating condition. The driver must review the last DVIR if a report was required under the relevant paragraph of section 396.11. The driver then signs the report to acknowledge review and the certification that required repairs were performed. The signature rule has an exception for listed defects on a towed unit that is no longer part of the vehicle combination.

This is not the same signature as the reporting driver's signature at the end of the prior workday. It is also not the carrier's certification that a reported defect was repaired or that repair is unnecessary. A sound handover makes all three roles visible rather than presenting one undifferentiated “closed” status.

The next driver should know which vehicle and last report are being reviewed, what defect was listed and what the carrier certified. If a new concern is found before travel, the driver cannot treat an old certification as a universal clearance for the vehicle. The before-driving safe-condition duty still applies to the current condition. The driver should report the new concern through the carrier's operating process and should not begin ordinary operation of a vehicle that is unsafe.

Section 396.13's acknowledgment is not an engineering warranty by the driver. It records the review and existence of the repair certification. The carrier retains its own duties under section 396.11 and the broader maintenance rules. A driver should not be asked to sign a prior report they have not seen, or to assume a defect was fixed because a dispatch screen has changed color.

A six-step before-dispatch sequence

The regulations set the duties. The sequence below is a suggested internal control to make those duties workable across shifts and locations.

1. Identify the vehicle and applicable report. Match the DVIR to the power unit or other covered equipment and the most recent operating day. Check that the reported defect is not being handled in a different vehicle's record. 2. Preserve the driver's observation. Keep the original fault description, date and driver signature. Ask for clarification if the report is too vague to support a safe response. 3. Assess the condition. Use a person competent for the relevant component. Decide whether the defect is likely to affect safe operation and whether the vehicle may be used. Keep any necessary vehicle out of ordinary service while that question is unresolved. 4. Complete repair or a supported no-repair determination. Record the action and the evidence behind it. A no-repair conclusion is not a substitute for inspection where the reported condition could affect safety. 5. Make the carrier certification. On a DVIR listing a defect, certify that repair was completed or is unnecessary before the vehicle is operated again. Preserve the link between that certification and the report. 6. Give the next driver the report. The driver reviews it where required, acknowledges it under section 396.13 and is independently satisfied that the vehicle is safe to operate before driving.

A dispatcher may add a final release check that the vehicle identifier, repair or no-repair certification and next-driver review are all present. That check is an employer process suggestion. It should not be described as an FMCSA approval, and it does not override an unresolved defect. If maintenance, the driver and dispatch disagree about the vehicle's condition, pause the release and resolve the facts rather than letting a schedule decide.

What does “repair unnecessary” really mean?

The phrase appears in the federal certification requirement. It does not define a blanket category of defects that carriers may ignore. Its application depends on the condition reported and the result of an appropriate evaluation. A mistaken driver observation, a component that is operating correctly after inspection, and a defect that genuinely needs repair are different cases.

Do not build a generic “minor defects may wait” list and present it as federal law. Even if a condition appears minor in isolation, it may matter when combined with the vehicle's intended use or other faults. A carrier's maintenance professional should evaluate the actual equipment. If a defect is likely to affect safe operation, section 396.11 calls for repair before the vehicle is operated again. If the vehicle is in a condition likely to cause an accident or breakdown, section 396.7 independently restricts operation.

Where a no-repair conclusion is appropriate, the file should allow a later reader to understand who examined the issue, what was found and why repair was unnecessary. Those supporting notes are prudent evidence practice; the regulation's specific certification duty remains the controlling requirement. Reassess if the next driver reports the same problem or new facts emerge. A repeated concern can show that the earlier assessment was incomplete.

Keep the DVIR and supporting records retrievable

Section 396.11 requires the motor carrier to retain the DVIR, the certification of repairs and the certification of the driver's review for three months from the date the written report was prepared. The time period applies to this DVIR record set. Other vehicle maintenance records have separate rules and retention periods. Do not reduce the whole maintenance file to a three-month assumption.

The rule allows the report to be created and maintained electronically in accordance with the applicable federal electronic-record provision. Electronic storage is a format permission, not proof that a particular product captures every required role or can produce the needed record. Before relying on a workflow, check whether it preserves the original driver report, the carrier's repair or no-repair certification and the next driver's review in an intelligible, retrievable form.

Create a clear connection between the DVIR and any maintenance work order. A repair record without a link to the reported defect can leave an auditor or supervisor uncertain whether the correct problem was addressed. Likewise, a DVIR marked “resolved” without supporting facts may give the next driver little basis to understand what changed. These are practical record-design considerations, not extra federal form fields.

Keep roadside and intermodal reports separate

A roadside inspection report issued by an enforcement official is not simply another DVIR. It has its own delivery, correction and return rules under section 396.9. A roadside out-of-service direction has consequences beyond an ordinary driver-reported defect. If both a DVIR and roadside inspection refer to the same condition, address each applicable obligation and retain the connection between the records. Do not assume that closing one report automatically closes the other.

Likewise, equipment tendered by an intermodal equipment provider follows the specific reporting and corrective-action structure in section 396.11's intermodal paragraph. The provider and carrier may have different responsibilities. This article's main sequence concerns equipment provided by the motor carrier under the first paragraph of section 396.11. Applying it unchanged to an intermodal arrangement can assign the wrong person the certification task.

State rules, customer contract terms and carrier policies may impose additional reporting or operating steps. They should be identified as such. A federal DVIR minimum should not be described as the entire compliance system for every vehicle and route.

The decision before choosing a record system

The practical test of a DVIR process is whether a real defect can travel from a driver's report to a supported repair or no-repair certification, then to the next driver's review, without disappearing between shifts. The vehicle identifier, dates, roles and underlying evidence must remain clear. A dashboard can help staff notice open items, but a dashboard status is not itself the carrier certification required by section 396.11.

If you are assessing software for a US fleet, explore Complys for US businesses and ask to see the current vehicle-defect reporting, repair-record and driver-review workflow. Verify any DVIR-specific capability in the actual product before relying on it. The motor carrier and driver still need to apply the federal rules to their own equipment and the facts of each defect.

Related guides

See also: CMV Warning Triangle Placement: Road-Specific US Rules, Annual CMV Inspection Evidence: Report, Sticker and 14-Month File.