Driver and Vehicle Stop Checks
›Driver and Vehicle Stop Checks Driver and vehicle stop checks let operators find roadside weaknesses before DVSA finds
Maintenance Recording Checks
Maintenance recording checks review whether an operator’s vehicle files prove proper roadworthiness control. The test is not whether PMI sheets, brake printouts and repair invoices exist somewhere. The test is whether the records connect cleanly enough to satisfy DVSA, a customer auditor or the Traffic Commissioner when the file is questioned.
For HGV and PSV operators, weak maintenance records can make an otherwise well-run fleet look uncontrolled. A vehicle may have been inspected on time, but if the brake test is missing, the defect trail is unclear, or the repair evidence does not link back to the original report, the operator may struggle to show effective maintenance management.
Request a maintenance record check or use our transport services assessment to explain the issue and upload the detail.
What a maintenance record check reviews
A good vehicle file should tell a complete roadworthiness story. It should show what was inspected, what was found, what action was taken, and when the vehicle was confirmed safe to use again. DVSA’s Guide to Maintaining Roadworthiness sets the expectation around safety inspections, defect reporting, brake testing, rectification and record retention. This page turns that expectation into a practical file review.
| Record area | What good evidence shows | Common weakness |
|---|---|---|
| PMI sheets | Vehicle identity, date, odometer reading, inspection items, defects, tester details and sign-off. | Unsigned sheets, missing odometer readings, vague defect wording or no return-to-service decision. |
| Brake tests | Brake evidence matched to the right vehicle, date and inspection, with a clear pass or fail outcome. | Printouts filed separately, incorrect registration, no link to the PMI or unclear pass/fail action. |
| Driver defects | Reported defects linked to repair action, parts, labour and closure. | Defects marked as repaired with no job card, invoice or authorised sign-off. |
| Repair records | Clear evidence of what was repaired, by whom, when the vehicle returned to service and who released it. | Invoices that do not identify the defect, vehicle or completion date clearly. |
| Inspection intervals | PMIs completed in line with the declared maintenance interval and any increased-risk use. | Late inspections, unexplained gaps or files that do not match the operator’s stated system. |
| Annual test history | Pass first time, or pass after rectification with clear remedial evidence on file. | Repeated initial failures with no internal review or system change. |
When operators usually need this review
A maintenance recording check is most useful before someone else asks for the file. Operators often request one after a prohibition, annual test failure, DVSA desk-based assessment, maintenance investigation, customer audit, change of workshop, OCRS movement or warning that maintenance evidence may be scrutinised.
It is also useful where records are split across paper PMI sheets, workshop portals, fleet software, email invoices and driver defect apps. A split system can still be compliant, but only if the evidence can be followed without guesswork. The operator remains the controller of the file even when a third-party workshop holds the master copy.
A pattern we see often is a vehicle with a satisfactory PMI sheet but no matching brake evidence in the same period. The workshop later produces a brake printout, but it shows a different inspection date and the registration is partly obscured. The operator may have maintained the vehicle, but the file does not prove it cleanly. A check identifies that weakness before it becomes a regulatory question.
“When I sample a file, I do not start with the PMI. I start with the annual test history and walk backwards. If a vehicle failed at annual test on brakes, I expect the previous PMI, the brake test, the defect log and the workshop rectification to read as one coherent story. When that story has a gap, the maintenance system has a gap, and that is what a Traffic Commissioner will pick up.”
Andrew Logan, transport compliance adviser
How the record check works
The review normally works through a sample of vehicle files covering the last 12 to 15 months. Fifteen months is the practical benchmark because operators are expected to retain safety inspection and repair records for at least that period. Where there has been a serious incident, prohibition, annual test failure or Traffic Commissioner concern, a wider sample is appropriate.
We read the file in the same order an examiner or auditor is likely to test it: PMI sequence, brake evidence, driver defect reports, repair records, annual test history, repeat defects, deferred items and VOR decisions. Each finding is marked by risk, so the operator can separate housekeeping points from issues that may call maintenance control into question.
The output is a clear action list, not a generic audit note. Typical actions include recovering missing brake test evidence, linking repair invoices to defect reports, correcting vehicle file indexing, confirming tester identity, recording return-to-service decisions, and tightening how late inspections are escalated.
PMI, brake and repair trails
The strongest files make the link between inspection, defect and repair obvious. If a PMI identifies a brake imbalance, the file should show the brake test result, the workshop action, the retest or follow-up evidence, and the decision to release the vehicle. If a driver reports a defect, the same trail should exist from report to closure, including a named person who authorised the return to service.
Brake testing deserves particular attention. GOV.UK roadworthiness guidance sets out expectations around planned safety inspections and brake performance evidence, including the use of laden roller brake tests where appropriate. Operators should always check the current official guidance before relying on a workshop process or testing programme.
VOR decisions also belong on the file. Where a vehicle is taken off the road for a defect, the record should show the date, reason, who authorised the off-road decision, the repair carried out and the date the vehicle was returned to service. A vehicle that was used between defect identification and repair, without a clear safety judgement on file, is one of the questions an examiner will ask first.
Management review
A maintenance file is rarely judged on individual records alone. The Traffic Commissioner will also look for evidence that the operator reads the system, not just operates it. That usually means a periodic review of PMI timeliness, defect trends, annual test outcomes, prohibition history and workshop performance, with notes that show what was changed as a result. Operators who keep that review on paper or in a simple management log are in a much stronger position when evidence is requested.
Relevant official guidance: GOV.UK Guide to Maintaining Roadworthiness.
Maintenance Recording Checks FAQs
How far back should maintenance records be checked?
A 12 to 15 month review is usually appropriate. Fifteen months is preferred where the operator wants to test safety inspection records, repair evidence and annual test history as one continuous file.
What makes a PMI record weak?
A weak PMI record may be late, unsigned, unclear on tester identity, missing odometer detail, vague about defects, disconnected from brake evidence, or silent on whether the vehicle was safe to return to service.
Do brake test records need to match the PMI?
Yes. The brake evidence should be easy to connect to the correct vehicle, date and inspection. If brake records are held in a workshop portal or separate folder, the file should still show where they are and how they map to the PMI cycle.
Can this help before a DVSA desk-based assessment?
Yes. A pre-submission check can identify missing evidence, weak explanations and file gaps before the operator responds. It does not guarantee an outcome, but it can make the evidence clearer and more defensible.
What happens after the record check?
You receive a written summary of the files reviewed, the main gaps found, the likely risk level and the practical corrections needed. The operator can then update the record system, brief the workshop, refresh the management review and prepare a clearer evidence pack.
Operator Licence Ltd can review your maintenance evidence, identify the gaps and connect you with the right specialist support for record control, brake testing trails and management review. If your vehicle files need an independent review before DVSA contact, customer audit or internal compliance action, send the details through our transport services assessment.
