Vehicle defect reporting requirements: what DVSA expects
By the Smart Strix team · Updated 15 July 2026
A defect report only protects you if it travels the whole loop — found, reported, assessed, fixed, signed off — and the paperwork proves it 15 months later.
What counts as a reportable defect?
Anything that could affect the safe or lawful operation of the vehicle: braking faults, steering play, tyre damage or illegal tread, lighting failures, mirror or glass damage, fluid leaks, exhaust problems, insecure bodywork, load restraint faults, tail lift defects, and warning lamps that stay lit. Cosmetic scuffs are worth noting for fleet management reasons, but the reporting duty centres on roadworthiness. A useful test for drivers: would an examiner at the roadside care? If in doubt, report it — the system exists so that a mechanic, not the driver, decides severity.
How should drivers report defects?
DVSA guidance asks for written reports made promptly — at the daily walkaround, and immediately when a fault develops on the road. A compliant report captures:
- vehicle registration or identifier and odometer reading
- date and time the defect was found
- the driver's name and a description of the fault
- who the report was passed to for assessment
- space for the rectification entry and sign-off
Format is flexible — a duplicate pad, a defect book or an app entry all satisfy the guidance provided the record is legible, attributable and cannot quietly vanish. Photographs strengthen a report considerably, both for the mechanic diagnosing remotely and as evidence of exactly what was found and when. The report normally originates from the daily first-use inspection, so pair this page with our printable walkaround check list.
Is nil-defect reporting required?
No — and this is the point operators argue about most. Current DVSA guidance does not insist on a written "nil" report for every defect-free check; what it insists on is a system that demonstrates checks genuinely happen each day a vehicle is used. That leaves two legitimate designs:
- Report-by-exception: drivers record only defects. Simpler, less paper, but the operator must be able to prove through other means (gate logs, app timestamps, supervision) that checks occurred on the silent days.
- Nil-defect recording: every check produces a record even when nothing is wrong. More admin, but the audit trail is continuous and self-evidencing — one reason many O-licence holders and FORS-accredited fleets choose it.
Digital systems have largely dissolved the trade-off, since logging a clean check takes seconds and timestamps itself. Whichever route you take, write it into your maintenance system documentation so an examiner sees a deliberate choice rather than an accident.
What must happen after a defect is reported?
Reporting is the start, not the end. DVSA expects a closed loop:
- Assessment by a responsible person: is the vehicle safe and legal to use? Safety-critical defects take it off the road immediately.
- Rectification before further use for anything affecting roadworthiness, carried out by a competent person.
- Recording of the repair: what was done, by whom, when, with parts or job-sheet references where relevant.
- Sign-off linking the fix back to the original report, so the trail reads found → reported → repaired → cleared.
The most common failure at DVSA investigations is not missing reports — it is reports with no visible outcome. A defect logged three times across three weeks with no rectification entry tells an examiner the system is decorative. If a vehicle is deliberately kept running with a minor defect, record that decision and who made it.
How long must defect records be kept?
Fifteen months at minimum, per DVSA's maintenance guidance — the same retention that applies to safety inspection sheets and the wider maintenance file described in our fleet maintenance records guide. The retention exists so DVSA can review a rolling window of your systems at an investigation or public inquiry. Paper and electronic storage are both acceptable; the tests are completeness, legibility and retrievability. Fleets running vans outside O-licensing are not bound by the 15-month rule, but matching it costs little and gives a duty-of-care file that answers questions before they are asked.
Who is accountable when defect reporting fails?
Both ends of the chain. Drivers hold personal responsibility for the condition of the vehicle they take out and can be prosecuted for using a dangerous vehicle; operators are accountable for the system — training, time to check, functioning reporting channels and follow-through. At the roadside, an examiner who finds a defect the morning check should have caught will typically ask the driver for the day's report, then pursue the operator's records afterwards. Repeated findings depress an operator's OCRS score, which raises the odds of being stopped again — a feedback loop that rewards operators who fix their reporting culture early.