HGV maintenance record audit checklist
An HGV maintenance audit is not a count of files in a folder. The operator needs to show that inspections were planned and completed, defects were acted on, and records can explain why a vehicle was used. A practical audit follows a sample of vehicles through time and checks whether the evidence chain makes sense.
This is an internal record-quality checklist for UK operators. It does not replace the DVSA Guide to Maintaining Roadworthiness, which should be checked for the current recommendations applicable to the fleet. Nor is it a claim that a green dashboard proves roadworthiness.
Choose samples that can reveal a weakness
Include different vehicle types, depots, workshops and ages. Sample at least one vehicle with a reported defect, one with a late or rescheduled inspection and one that has changed maintenance provider. Include trailers where the operator uses them. A random sample gives breadth; a risk-based sample tests known weak points. Record why each asset was selected so the audit is repeatable.
Build a timeline for each sample: planned inspection dates, actual inspections, driver reports, workshop action, any brake evidence, repairs and vehicle release. If a record is missing, mark it missing. Do not infer that an inspection happened because a later invoice refers to a service.
Check identity and document quality
Can every record be tied to the correct vehicle or trailer? Are dates, mileage or use information, inspector or repairer identity, findings and outcome legible? Are attachments complete? Does a corrected record preserve the earlier version and explanation? A maintenance record is weaker when identifiers change across spreadsheets, garage systems and the operator's own files.
Review whether the current inspection interval and schedule are documented and whether changes have an owner and reason. This audit tests the record of those decisions; it does not recommend a standard interval for all vehicles. A late inspection should lead to an explicit operating decision rather than a backdated schedule entry.
Follow each defect to a defensible end
For every sampled driver report, check assessment, repair or justified decision that repair was unnecessary, recheck where appropriate and communication to the person controlling dispatch. Compare the reported fault with the workshop's final entry. Did an out-of-service item remain visible until it was addressed? If a defect recurred, was it linked to the earlier event rather than treated as an unrelated isolated job?
The DVSA guidance says reports listing defects form part of the maintenance record and should be retained with assessment and repairer details. It also discusses nil-defect reporting as good practice. Avoid turning every recommendation in the guide into an invented statutory rule; state in the audit which source and requirement you are testing.
Test retrieval and retention
Ask a person who did not create the file to retrieve the full timeline for a selected asset. Note missing workshop reports, broken links, inaccessible systems and records held only by a former employee. The GOV.UK operator page says safety-inspection and maintenance records must be kept for at least 15 months. Confirm current requirements and whether a specific record category requires longer under a contract or investigation.
Compare digital and paper copies. If both exist, identify which is authoritative and how corrections are controlled. A record is not auditable merely because it can be exported; the relationships among inspection, defect, repair and release must remain intelligible.
Close audit findings
Describe each gap in terms of what cannot be proved, which assets or dates are affected and what evidence is needed. Prioritise safety-related missing chains. Assign an owner, due date and verification method. If records cannot be reconstructed, say so rather than silently filling the gap with a later statement. Review repeated findings for underlying scheduling, workshop handover or access problems.
For a product comparison, see Complys HGV compliance software. Ask to see how the current product retrieves a sampled vehicle's records. Do not assume it creates inspection intervals, judges defects or certifies an operator's compliance.
Example: one missing link changes the audit result
An operator has a scheduled inspection report, a workshop invoice and a driver defect report for the same vehicle. The defect was reported before the inspection, but neither the report nor the invoice explains how it was assessed. The auditor should not infer that the work was done because the vehicle returned to service. Record the missing link, seek the job card or repairer's evidence and ask who authorised release. If the evidence cannot be recovered, state the limitation and review current vehicle condition through the appropriate process. Then test whether driver defects reliably flow into future garage instructions. This is a stronger audit outcome than retroactively ticking “repaired” on the old report.
Separate record defects from safety defects
A typographical error in an otherwise traceable record may need correction and version control. A missing assessment for a safety-related fault may require immediate operational attention. The audit should state which is which, who decides, and what evidence will close the finding. Do not turn every imperfect document into the same priority, but do not allow a tidy file structure to conceal an unresolved safety question.
For each sampled vehicle, trace a reported defect through assessment, repair, post-repair check and release. Note where the chain breaks, including missing dates or work attributed to the wrong registration. An audit should show who resolved the gap and whether other vehicles share the same recording weakness.