What this is
What is a vehicle defect report?
What is a vehicle defect report?
It is a record raised the moment a defect is found on a vehicle, independent of any scheduled inspection. It captures what the defect is, whether the vehicle kept moving, what was done immediately, and how it was rectified before the vehicle returned to service.
How is it different from a Driver Vehicle Inspection Report?
The DVIR is a scheduled pre-trip or post-trip check that may or may not find anything. This record is raised specifically because something was found — during a DVIR, en route, at the roadside, or reported by someone else entirely. A DVIR can trigger this record, but this record is not the DVIR itself.
Does every defect need one of these?
Every defect that is not trivial cosmetic wear should get one, because the record is what proves a safety-critical fault was actioned rather than driven around. Minor items scheduled through routine maintenance without safety implication are the practical exception.
Scope
When is a vehicle defect report required?
This record covers a specific defect on a specific vehicle from the moment it is found through to verified repair. It is not the scheduled inspection that may have found it, and it is not the work order that fixes it — it links to both.
Use this template when
- A defect is identified on a vehicle, by any route: inspection, en route, roadside, maintenance, or third party
- The vehicle may need to be taken out of service, immediately or after completing a safe manoeuvre
- A new case needs its own ID so it can be tracked from discovery through to verified repair
- The defect needs to be linked forward to a work order and, where relevant, a cold chain excursion
- A pattern across repeat defects on the same vehicle needs to be visible for the maintenance programme to act on
Do not use it for
- Driver Vehicle Inspection Report, which the scheduled pre-trip and post-trip check that may or may not find a defect.
- Roadside Inspection Record, which the record of an enforcement stop, which may reference this report but is a separate event.
- Vehicle Service Record, which the scheduled maintenance history, as distinct from a defect found outside that schedule.
- Reefer Unit Check, which the pre-load check of refrigeration performance, not a general defect finding.
- Anything outside KnowFleet, which belongs in the workspace that owns that process
Compliance mapping
Which FMCSA 396.11 requirements does this satisfy?
FMCSA 396.11 sets the driver's duty to report; the sections below are where this template turns that duty into a record an auditor can actually follow.
| Clause | Requirement | Where it lands |
|---|---|---|
| 49 CFR 396.11(a) | Driver must prepare a report identifying any defect discovered or reported during the day's operation | The defect |
| 49 CFR 396.11(a)(2) | Report must cover parts and accessories that would affect safety of operation or result in mechanical breakdown | The defect |
| 49 CFR 396.7 | A vehicle likely to cause an accident or breakdown must not be operated until repaired | Immediate action |
| 49 CFR 396.11(b) | Carrier must certify defects were repaired, or that repair is not necessary, before the vehicle is operated again | Rectification |
| 49 CFR 396.11(c) | Records of the report and corrective action retained for a defined period | Header |
| 49 CFR 396.3(a) | Systematic maintenance obligation, against which recurring or missed defects are assessed | Analysis |
| 49 CFR 396.13 | Driver must be satisfied the vehicle is in safe operating condition before driving it | The defect |
What it does not cover
- Continued To Drive, which recorded as Yes, completed trip against a defect logged as Braking with no safe-stop justification.
- Verified Before Release, which left as No while Vehicle Returned To Service is marked Yes.
- Driver Informed Of Repair, which marked No on a vehicle that has already gone back out with a different driver.
- Should Have Been Caught At PM, which answered Yes with no corresponding note or reference back to the maintenance schedule.
- Release Signed By Competent Person, which marked No on a Safety Critical defect that has already been returned to service.
Global
Vehicle Defect Report requirements by country
The duty to report a defect the moment it is found is close to universal in commercial road transport, but the instrument that enforces it, and what happens to the operator if the report is missing, differs by jurisdiction.
FMCSA 49 CFR 396.11 and 396.7
The driver has a personal statutory duty to report, and the carrier a separate duty to certify repair before the vehicle runs again — a missing or late report exposes both.
In a post-crash or roadside review, the absence of a timely defect report is treated as evidence the carrier's maintenance programme is not being followed, independent of whether the defect itself caused the incident.
Guide to Maintaining Roadworthiness (DVSA) and Section 41 of the Road Traffic Act 1988
Operators licensed under an O-licence undertaking must show a defect reporting system that drivers actually use, not just one that exists on paper.
A traffic commissioner reviewing an O-licence will ask for defect report volume and closure times as direct evidence of whether the undertaking is being honoured.
National Safety Code Standard 13 — Trip Inspection
Broadly parallel to the US model, with a defined list of defect categories that determine whether a vehicle is out of service immediately or can complete its trip.
Provincial enforcement uses the same defect categorisation this record captures to decide roadside out-of-service orders, so the category chosen here has to match the standard's definitions, not an internal one.
How to complete it
How to complete a vehicle defect report, step by step
The fields record facts. The judgement is in what those facts are allowed to mean for whether the vehicle keeps moving.
Continuing to a safe place to stop is a reasonable and often correct call; completing the scheduled trip with a known safety-critical defect is not, regardless of how the defect was eventually resolved. The field captures both as options precisely so the difference is visible on the record rather than absorbed into a single 'kept driving' answer.
Verification means someone other than the person who did the repair confirmed the fault is actually resolved, not that the work order was closed. A vehicle marked Returned To Service without a Yes on this field has had its repair asserted, not checked — and that gap is exactly what an enforcement stop or a repeat failure will expose.
The same defect returning within months on the same vehicle points at a root cause the repair didn't fix, or a maintenance interval that's too long. A different defect on the same system, on the other hand, is more often just wear catching up with an ageing vehicle. Conflating the two flatters the maintenance programme in the analysis section.
This is a judgement about the preventive maintenance checklist's content, not the technician's competence — a wear item outside the checklist's inspection points was never going to be caught regardless of who did the PM. Answering Yes here should point back at the PM scope, not at an individual.
What auditors find
Most common vehicle defect report findings
These are the findings that recur most often when this record is reviewed after the fact, whether by an internal audit or an enforcement action.
| Finding | Clause | What fixes it |
|---|---|---|
| Defect reported hours after discovery rather than at the time | 49 CFR 396.11(a) | Capture Time Identified as a mandatory field distinct from submission time, and treat a large gap between the two as a finding on its own. |
| Safety-critical defect logged after the trip was completed | 49 CFR 396.7 | Require Continued To Drive and System Affected to be answered before the rest of the form unlocks, so the out-of-service decision is made first, not last. |
| Vehicle returned to service with no verification recorded | 49 CFR 396.11(b) | Block Vehicle Returned To Service from being set to Yes until Verified Before Release is answered. |
| Driver not informed the repair had been made | 49 CFR 396.13 | Route a notification to the reporting driver automatically when Repair Completed is set to Yes, rather than relying on a manual field. |
| Recurring defect on the same vehicle not linked to prior reports | 49 CFR 396.3(a) | Auto-populate Occurrences In 12 Months from the vehicle's defect history instead of leaving it as a manual entry. |
| Defect that should have been caught at PM closed with no action against the maintenance schedule | 49 CFR 396.3(a) | Force an Action Required entry whenever Should Have Been Caught At PM is Yes, so the PM checklist gets reviewed rather than just the vehicle. |
Case in point
Case in point: the brake pull nobody stopped for
A driver felt the truck pull left under braking about ninety minutes into a delivery run. The load was on board, the next drop was forty minutes out, and the pull was mild enough to keep driving. The driver finished both remaining drops before mentioning it at the depot that evening, six hours after first noticing it.
The defect turned out to be a seized caliper, already at the point where uneven pad wear on the opposite wheel was starting. Nothing prevented the report from being filed at the roadside the moment it was noticed — the delay was entirely a judgement that it could wait. The record as eventually filed showed Continued To Drive as 'Yes, completed trip' against a Braking defect category, which is precisely the combination this template is built to surface as indefensible, however reasonable it felt in the moment.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- FLT-005
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Severity band
- Direction
- High is bad
- Singleton
- No
- Basis
- FMCSA 396.11
- Links
- Links Asset; feeds work order
- Tags
- Fleet, Maintenance
- Sections
- 5
- Fields
- 49
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 7
Header
16 fieldsReport ID*
Auto sequence. Format VDR-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Exact Location
Drop a pin. Roadside events rarely have a useful address.
Vehicle*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Unit Number
The number painted on the door, which is what drivers actually use.
Driver*
Person ID*
Links to FDN-003 Person ID
Licence Class
Source Of Report*
Driver inspection, en route, roadside inspection, maintenance, or third party report.
Inspection ID
Links to FLT-001 Report ID
Time Identified*
The defect
7 fieldsDefect Description*
System Affected*
Defect Category*
Safety critical stops the vehicle immediately. Major means repair before next trip. Minor can be scheduled.
Photograph
Vehicle Immobilised*
Location When Identified*
- At depot3 pts
- Customer site1 pt
- Roadside0 pts
Load On Board*
- No3 pts
- Yes, ambient1 pt
- Yes, temperature controlled0 pts
Immediate action
6 fieldsContinued To Drive*
Driving on with a safety critical defect is a personal offence for the driver as well as the operator.
- No3 pts
- Yes, to safe place1 pt
- Yes, completed trip0 pts
Recovery Arranged
- Yes3 pts
- Not needed3 pts
- No0 pts
Load Transferred
Cold Chain At Risk*
- No3 pts
- Yes0 pts
Excursion Record ID
Links to FLT-027 Record ID
Customer Notified
- Yes3 pts
- Not required3 pts
- No0 pts
Rectification
9 fieldsWork Order Raised*
- Yes3 pts
- Not needed3 pts
- No0 pts
Work Order ID
Links to MNT-002 Work Order ID
Repair Completed*
- Yes3 pts
- Partial1 pt
- Outstanding0 pts
Time Out Of Service Hours
Repaired By
Vehicle Returned To Service*
- Yes3 pts
- Still off road1 pt
Verified Before Release*
- Yes3 pts
- No0 pts
Driver Informed Of Repair*
- Yes3 pts
- No0 pts
Release Signed By Competent Person*
- Yes3 pts
- No0 pts
Analysis
11 fieldsRecurring Defect On This Vehicle*
- No3 pts
- Yes0 pts
Occurrences In 12 Months
Should Have Been Caught At PM*
Defects found on the road that a PM should have caught mean the PM content is wrong.
- No3 pts
- Yes0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Fleet Manager*
Signature*
Transport Supervisor*
Second Signature*
FLT-005 · record IDs look like CASE-2026-000 · Links Asset; feeds work order
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
Filing the report is the fast part. Making sure a safety-critical answer actually stops the vehicle, and that verification happens before it goes back out, is where the process breaks down in practice.
Holds the defect report against the vehicle's history, blocks return-to-service until verification is recorded, and surfaces recurring defects on the same asset automatically.
Turns a raised defect straight into a work order, tracks time out of service, and feeds the repair outcome back so this record doesn't have to be chased manually.
Watches for the pattern that matters most — a safety-critical defect answered with 'continued to drive' — and escalates it rather than letting it sit as a completed form field.
Coordinates the crew across these workspaces, rolls open defects and overdue verifications into one view, and holds every write for your approval before it touches a record.
This template lives in KnowFleet — fleet and transport. Drivers, vehicles, hours, cargo securement and operator licence compliance.
Meet KnowFleet→Glossary
Vehicle Defect Report definitions and key terms
- Out of service
- A vehicle status meaning it must not be operated until a specific defect is repaired, whether declared by the operator or by roadside enforcement.
- Safety critical defect
- A fault in a system such as brakes, steering or coupling where continued operation creates an immediate risk of accident or breakdown.
- Certification of repair
- The carrier's documented confirmation that a reported defect has been repaired, or determined not to need repair, before the vehicle runs again.
- PM
- Preventive maintenance — the scheduled inspection and servicing programme a defect is checked against when deciding whether it should already have been caught.
- Recovery
- Arranging for a disabled vehicle, and its load where relevant, to be moved or retrieved rather than continuing under its own power.
FAQ
Frequently asked questions about vehicle defect report
Who raises a vehicle defect report?+
Usually the driver, at the point the defect is found, whether that is during a scheduled inspection, en route, at the roadside, or reported to them by someone else.
Does this replace the Driver Vehicle Inspection Report?+
No. The DVIR is the scheduled check; this record is raised specifically because a defect was found, by any route, and it can reference a DVIR that first identified it.
What happens if the defect is safety critical?+
The vehicle should stop as soon as it can safely do so, not complete the trip. The template scores continuing to drive with a safety-critical fault as the worst available answer for exactly this reason.
Does fixing the defect close the case?+
Not on its own. Repair, verification before release, and informing the driver of the repair are separate scored steps, and all three need to be positive before the vehicle should be considered clear.
Why does the template ask about occurrences in 12 months?+
A defect that keeps recurring on the same vehicle usually means the repair addressed the symptom, not the cause, or that the maintenance interval is too long. That pattern is invisible if each report is only looked at in isolation.
How is this record scored?+
By severity band, where high is bad. It exists to surface which defects and which decisions around them carried the most risk, not to produce a clean completion percentage.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Fleet and Driver Compliance
Transport Provider Assessment
Assesses a haulier for licensing, driver management, vehicle standards, temperature capability and load security
Driver Vehicle Inspection Report
The pre-trip and post-trip inspection a driver completes on a commercial vehicle
Annual Vehicle Inspection
The yearly statutory inspection of a commercial vehicle
Trailer Inspection
Checks trailer coupling, brakes, lights, tyres, doors and structure
Reefer Unit Check
Checks refrigeration unit operation, fuel, temperature setpoint and alarm history
Roadside Inspection Record
Records a roadside inspection by an enforcement officer, including any violations and out of service orders
More in Vehicle Inspections
Driver Vehicle Inspection Report
The pre-trip and post-trip inspection a driver completes on a commercial vehicle
Annual Vehicle Inspection
The yearly statutory inspection of a commercial vehicle
Trailer Inspection
Checks trailer coupling, brakes, lights, tyres, doors and structure
Reefer Unit Check
Checks refrigeration unit operation, fuel, temperature setpoint and alarm history
Roadside Inspection Record
Records a roadside inspection by an enforcement officer, including any violations and out of service orders
Tyre Condition Record
Records tyre tread depth, pressure and damage across the vehicle
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- FMCSA 49 CFR 396.11 — Driver vehicle inspection reports
- FMCSA 49 CFR 396.7 — Unsafe operations forbidden
- FMCSA 49 CFR 396.3 — Inspection, repair and maintenance
- DVSA Guide to Maintaining Roadworthiness
- National Safety Code Standard 13 — Trip Inspection (Canada)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.