HGV defect reporting process: from driver report to safe release

An HGV defect process is complete only when a reported fault has been assessed, the vehicle's use decision recorded, necessary repair made and a responsible person has evidence for return to service. A driver tick-box or emailed photo is the start of the chain, not its end. GB operators should connect daily walkaround checks, faults found on the road, workshop findings and maintenance records so an unsafe vehicle cannot quietly return to dispatch.

The DVSA Guide to Maintaining Roadworthiness says drivers must promptly report defects or symptoms that could affect safe operation; reports should be recorded and rectification captured. Defect reports containing faults and related assessment, repair and repairer evidence must be retained for at least 15 months. DVSA recommends keeping “nil defect” reports for at least three months as evidence checks occurred; do not present that recommendation as the same statutory minimum as a fault record. The operator remains responsible for roadworthiness even when maintenance is outsourced.

This page owns the handoff and closure process. The proposed driver daily-walkaround guide owns how to perform the check; the proposed fleet-maintenance guide owns the broader calendar and system design. The existing free Complys walkaround tool captures a first-use check and lets a driver print or save a PDF, but its page says to follow the operator's own DVSA-compliant defect reporting process. It is not proof of a live end-to-end repair and release workflow.

Six decisions every report must support

1. Capture the fault promptly

Give every driver a clear instruction for defects found before use, during a journey and on return. The report should identify vehicle and trailer, date and time, reporter, location, fault or symptom in plain language and who received the report. DVSA's current guide lists these core details and recommends including assessment and rectification. A driver should not be expected to diagnose a brake system to report an unusual response. Provide a phone escalation for urgent in-service hazards, then preserve the written record. A conversation alone can disappear at shift change.

A “nil defect” record is a positive statement that a check occurred and no defect was found; it must not be generated automatically from a blank form. If checks are digital, ensure the driver can complete them offline or under a fallback process where signal fails, and that the result is retrievable. For vehicle-type check content, follow DVSA's HGV walkaround guide rather than relying on a generic all-vehicle list.

2. Send the report to an authorised person

The system must deliver fault reports to a person with authority to decide and act. DVSA says all driver defect reports should go to a responsible person able to ensure appropriate action, including taking the vehicle out of service. Define a named daytime recipient and out-of-hours cover. For a multi-depot operator, specify which depot or transport manager owns the vehicle after a trailer swap. A message placed in a shared inbox without acknowledgement is not effective escalation.

Record when the report was received and who accepted it. Urgent defects should interrupt dispatch rather than wait for a weekly review. Where a driver notices a problem on the road, tell them how to stop safely, contact the operator and follow competent recovery advice. Do not pressure them to complete the route before the fault is assessed.

3. Make a roadworthiness and use decision

The responsible person should consider the fault, vehicle type, circumstances and whether a competent inspection is needed. Record the decision to hold, recover, repair before use or proceed under a documented competent assessment where lawful and safe. This guide does not create a universal “minor defect” list. A light, tyre, braking or steering fault can have different consequences depending on specifics; the assessment belongs to a competent person using current standards. If the vehicle is unroadworthy, DVSA says the fault must be rectified before use.

Make the hold visible to planners and keys/dispatch staff. A “Do Not Use” label in an internal record helps only if the team who allocate vehicles sees it. If a trailer is affected, the hold must follow that trailer when tractor units change. If another worker has already been assigned the vehicle, contact them directly; a silent dashboard update may be too late.

4. Repair and preserve the evidence

Give the garage or maintenance team the original defect report, not an informal paraphrase. Record the repairer, work performed, parts or tests where relevant, completion date and any unresolved issue. A workshop invoice stating “checked” may not show that the reported symptom was reproduced and resolved. If the workshop says “no fault found,” a competent operator still needs to decide whether the vehicle is fit for use and whether further testing or monitoring is required.

Outsourcing maintenance does not transfer responsibility. GOV.UK's goods-operator maintenance guidance says operators remain responsible for vehicle and trailer condition even when a contractor maintains them. Contracts should provide timely defect communication and completed records. File repair evidence with the vehicle's report and safety-inspection history so a regulator or manager can follow the chronology.

5. Recheck and authorise return to service

A booked repair or garage invoice is not itself the final dispatch decision. Check the completed work and any required inspection or test, determine whether open faults remain, and record who approved return to service and when. The DVSA guide says safety inspection records should be complete and the vehicle declared roadworthy before it returns; the transport manager or responsible person should access and review the completed safety-inspection record, with a written-confirmation exception where immediate access is not possible. Use the appropriate procedure for a simple driver-reported fault versus a formal safety inspection, but do not allow “closed” to mean merely “sent to workshop.”

Update dispatch status, tell the driver and retain the closure link. If a vehicle is still held, ensure any replacement has its own first-use and routine checks. A repaired defect may also prompt review of similar vehicles or a maintenance interval if the same failure repeats.

6. Review patterns and retain records

Keep fault reports with their assessment and rectification for the applicable minimum. For GB goods operators, GOV.UK says inspection and maintenance records are kept at least 15 months. DVSA's roadworthiness guide applies that duration to defect reports listing faults; it recommends at least three months for nil reports. Check the exact current framework for vehicle and operator class. Records can be electronic if they are complete, accessible and preserved.

Review repeat defects, late close-outs, “no fault found” patterns and what safety inspections discover compared with drivers' reports. A fleet with almost no driver defects but frequent inspector-identified driver-detectable faults may have a training or reporting problem. DVSA earned-recognition audit standards explicitly use cross-checks of driver reports and safety-inspection findings; operators outside that scheme can still learn from the method without claiming they must meet every scheme-specific audit criterion.

Copyable process record

This table is a workflow record, not a substitute for the vehicle-type check or safety-inspection form. If the vehicle is unsafe, do not wait for every table cell to be completed before preventing use. Safety action comes first; complete the traceable record promptly after.

Example: a brake concern after delivery

A driver reports that the vehicle pulls to one side under braking after a delivery. The controller records the vehicle, location and symptom and instructs the driver to stop in a safe place. A competent person arranges recovery or inspection; the vehicle is held from dispatch. The workshop checks the relevant system, records findings and repair, and provides test results. The transport manager reviews the evidence and authorises return only when satisfied that the vehicle is roadworthy. The original symptom, decision, repair and release remain linked. A text saying “garage sorted it” would leave the crucial decisions unproved.

Failure modes to audit

• Faults are reported verbally but never entered into a record.
• Reports go to a manager who has no authority or coverage out of hours.
• Trailer faults become detached from the trailer when tractor units change.
• Vehicles remain in the dispatch pool while a defect awaits triage.
• A repair booking or invoice automatically closes the fault.
• A “no fault found” result is accepted without further roadworthiness decision.
• Nil reports are generated from blank forms rather than real checks.
• Records are deleted before the required period or cannot be retrieved at a roadside or operator visit.

Complys and next step

The HGV and Operator Compliance page is the relevant money page for planned driver defect, maintenance and Do Not Use workflows. Its public feature table labels the vehicle platform and these controls as launching. This guide therefore makes no claim that Complys currently routes HGV faults, blocks dispatch, manages repairs or declares vehicles roadworthy. The free walkaround tool is an observed live aid for capturing a check, with its own warning to follow the operator's defect procedure. Verify actual implementation and terms before integration.

Write the procedure around named people, authority and evidence. Test it by selecting a recent fault and following the chain from driver to release. If any link is missing, fix the process before relying on the record at audit.

Source, claim, owner, product, links and writer-side QA

Terminal writer-side disposition: READY.