If DVSA stops one of your vehicles at the roadside, the question is not whether you meant to maintain it properly. The question is whether you can prove it. That means being able to show a clear maintenance history for that vehicle, with no guesswork, no missing weeks, and no pile of loose paperwork that someone has to sort through later.
The practical answer to how to keep vehicle maintenance records for DVSA roadside checks is simple enough. Keep one complete file for each vehicle. Make sure it shows the inspection plan, every PMI, every defect report, every repair, every MOT result, and the evidence that safety defects were dealt with properly. Then keep it current, not at the end of the month when everyone has forgotten what happened.
What DVSA will expect you to produce
At a roadside check, the examiner is looking at the vehicle in front of them. If they find a defect, or if they have concerns about roadworthiness, they may want to see the maintenance record behind that vehicle. Sometimes that happens there and then. Sometimes the request follows after the stop. Either way, you need to be able to produce records quickly.
For each vehicle, DVSA will expect you to be able to show the maintenance history that supports your O-licence undertakings. In practice, that usually means:
- the planned inspection frequency
- completed PMI sheets
- evidence of defects found and rectified
- driver walkaround check reports
- repair records
- MOT history and test outcomes
- tyre inspection and replacement records where relevant
- records showing brake work, safety inspections, and follow-up actions
- evidence that the vehicle was taken off the road if needed, and returned only when fit
If the vehicle is maintained by an external workshop, DVSA will still expect you, as the operator, to have control of those records. "The garage has it" is not a good answer. The responsibility stays with the operator named on the O-licence.
The standard is not just that a document exists. The records need to make sense as a system. Dates should line up. Defects found on a PMI should have a repair trail. A driver report of a dangerous defect should show what happened next. If an MOT failure picked up a brake imbalance or steering issue, the file should show the repair and any related checks afterwards.
This matters beyond the stop itself. A poor roadside result can feed into OCRS. If the records then show weak control, the issue is no longer just one defect on one day. It becomes a question about management systems, and that is where operators end up answering to the Traffic Commissioner.
If you want a fuller view of the points examiners look for, we have set that out in what DVSA checks in maintenance records.
Build one vehicle file that tells the full story
The cleanest way to manage this is by vehicle, not by document type. In other words, build one file per registration or fleet number, and keep everything for that vehicle together.
That file should let someone follow the full story from one date to the next. They should be able to see:
- when the next preventative maintenance inspection was due
- when it was actually done
- what was found
- what was repaired
- whether any defects were deferred, and why
- when the vehicle went for MOT
- whether there were prohibitions, failures, or advisory items
- what happened between inspections
This sounds obvious, but many fleets still split records across email, paper job cards, a workshop wall planner, a spreadsheet, and a folder of scanned PDFs. That is where gaps appear. One person knows the tyre was changed. Someone else knows the PMI was moved a week because the unit was away. The transport office has the driver defect book. Nobody has the whole picture.
A proper vehicle file should include both planning and evidence. Planning on its own is not enough. A maintenance planner that says a PMI was due every six weeks proves only that you intended to inspect it. You also need the completed inspection record, the rectification work, and any sign-off.
We prefer a structure with these sections for each vehicle:
- Vehicle master details
Registration, fleet number, VIN, make, model, first use date, O-licence disc details, MOT test class if relevant, and who maintains it.
- Maintenance schedule
The planned PMI interval, the basis for that interval, and any changes made over time.
- Inspection history
Every completed PMI in date order, with odometer reading, inspection date, inspector name, and outcome.
- Defects and repairs
Driver reports, workshop findings, job cards, parts fitted, technician notes, and rectification dates.
- Test and compliance records
MOT results, brake test evidence where applicable, calibration or safety records if they form part of your system.
- Off-road periods
Dates the vehicle was unavailable, why it was off the road, and how the inspection plan was adjusted.
If you run a mixed fleet, keep the same logic across vans, rigids, and tractor units, but do not pretend they all need the same level of record detail. Your system should reflect the actual maintenance regime for that vehicle type. In the UK, the expectations around heavy goods vehicles under an O-licence are stricter than what many van operators are used to. That distinction matters.
Which documents belong in the maintenance record
A maintenance record needs more than a stack of PMI sheets. The file should contain the documents that prove the vehicle has been maintained, defects have been managed, and the inspection regime is being followed.
At minimum, we would expect the following.
1. The maintenance planner entry
This should show the scheduled date for each preventative maintenance inspection and any changes to that date. If an inspection was brought forward or pushed back, record the reason. If the vehicle was off the road awaiting parts, say so. If it was out on contract work and could not attend, record that too.
Do not leave unexplained gaps between planned and actual dates.
2. Completed PMI sheets
The PMI sheet is central. It needs to identify the vehicle, date, mileage or kilometre reading, inspector, and the inspection items checked. It should show defects found, the severity, and whether the vehicle was fit for service.
A proper PMI record should also make clear whether any items were not inspected, and why. Blank boxes are not evidence. They are ambiguity.
3. Repair orders and job cards
When a PMI or defect report identifies work, the file should include the job card or repair record that shows what was done. That means:
- date work was carried out
- technician or fitter name
- work completed
- parts used where relevant
- whether the defect was safety critical
- whether the vehicle was off the road pending repair
If the workshop uses shorthand on paper job cards, make sure it is still readable six months later by someone who was not there that day.
4. Driver defect reports
Daily walkaround checks matter because they fill the gap between PMIs. Keep nil defect reports if that is part of your process, or at least keep a clear record that the check was completed. Where a defect is reported, the file should show:
- date and time reported
- vehicle
- driver name
- defect details
- whether the defect affected roadworthiness
- who reviewed it
- rectification date and outcome
This is one of the first places DVSA will spot weak control. If drivers report defects but there is no repair trail, your system is not under control.
5. MOT records
Keep the MOT pass, failure, advisory items, and any repair evidence linked to a failure or advisory. The MOT is not your maintenance system, but it is part of the record. If a vehicle failed on a point that should have been picked up at PMI, expect questions.
6. Tyre records
Tyres generate a lot of roadside trouble. Keep records of tyre inspections, replacements, damage reports, and emergency call-outs. If a tyre was run close to the limit and then replaced, the timing should make sense against driver reports and workshop checks.
7. Brake and safety-related evidence
For HGVs and trailers, keep brake test records where those form part of your maintenance routine. If a safety-critical defect was found, keep clear evidence of when the vehicle was stopped and when it returned to service.
8. Supporting workshop notes
Not every useful record is a formal certificate. Technician notes, photos of damage, parts back-order notes, and authorisation messages can all help explain a timeline. Keep them if they clarify the story.
If you are reviewing your system, our guide to which maintenance records stand up in a DVSA audit goes deeper into the evidence side.
How to keep records current between inspections
This is where good systems usually fail. The PMI gets done. The workshop repairs the defects. The driver mentions a lamp issue two days later. A tyre gets changed on the road on a Saturday. By the following Friday, half of that is still in someone's pocket, inbox, or memory.
To keep records current, you need a routine that catches work as it happens.
Start with driver defect reporting. Drivers should submit defects the same day, not when they are back in the yard three shifts later. If the defect affects roadworthiness, there must be a clear decision on whether the vehicle is stood down. That decision needs to be recorded.
Then workshop intake. Every reported defect should become a job, even if the fix is quick. A bulb changed in ten minutes still needs a record if it came from a driver report or safety inspection. Otherwise the defect exists in one record but not the repair history.
Tyre work needs the same discipline. Mobile tyre jobs are often missed because the invoice turns up later from a supplier and nobody links it back to the vehicle file. Put a process in place so that roadside tyre work is logged on the day, then matched to the supplier document when it arrives.
The same applies to subcontracted work. If an outside workshop carries out repairs, do not wait for month-end paperwork. Get the defect details, the rectification note, and the date of completion into the vehicle record straight away, then add the invoice or signed sheet when it lands.
Vehicles off the road are another trap. Operators often assume that if a vehicle was parked up, the missed PMI does not matter. It still matters, because you need to show control. Record the off-road period, why the vehicle was unavailable, and how the maintenance schedule was reset before the vehicle returned. We cover that in more detail in keeping maintenance plans right when vehicles go off the road.
A final point here is tachograph and mileage discipline. The mileage on the PMI, defect reports, and workshop entries should broadly make sense. If one record says 420,000 km and the next says 398,000 km, somebody should catch that before DVSA does. You are not trying to create perfection. You are trying to stop obvious contradictions.
Common record-keeping mistakes that cause trouble
The biggest problems are rarely dramatic. They are usually ordinary admin gaps that add up.
One common mistake is keeping the PMI sheet but not the rectification evidence. The inspection shows defects. The vehicle later appears on the road. There is no document showing what was repaired or when. From DVSA's point of view, that is not a completed maintenance event.
Another is missing dates. A defect report without a repair date, or a job card without a completion date, leaves you unable to prove whether the vehicle was used before rectification.
Unclear handwriting still causes trouble. So do workshop abbreviations that only one fitter understands. If the record cannot be read by someone outside your business, it is weak evidence.
We also see operators relying on MOT passes to mask poor routine records. An MOT pass does not prove the vehicle was properly maintained between tests. In some cases, repeated MOT advisory items do the opposite. They suggest the same issues are returning without being managed properly.
Nil defect reporting is another area where systems drift. If your policy says drivers complete a daily check, but you only hold reports when something is wrong, make sure you still have evidence the checks happened. Otherwise a roadside issue can turn into a wider question about whether checks are being done at all.
Then there is the spreadsheet problem. Spreadsheets can work for a while, but only if one disciplined person updates them every day and everyone else feeds them properly. Once the fleet grows, versions split, formulas get overwritten, and the planner no longer matches the workshop wall. That is when operators discover they have a list of due dates, but not a reliable maintenance record.
The last big mistake is treating the file as an audit exercise instead of an operating tool. If records are built after the event, they usually show it. Dates get rounded. Details disappear. The sequence does not ring true. DVSA examiners and Traffic Commissioner staff see enough files to spot that quickly.
How to present records quickly when DVSA asks
When DVSA asks for records, speed matters, but so does order. Handing over too little looks evasive. Handing over a disorganised bundle suggests you do not know what you hold.
The best approach is to pull the record by vehicle and check it before sending or presenting it. Confirm that you have:
- the planned PMI dates for the period requested
- all completed PMI sheets
- defect reports in that period
- repair and rectification evidence linked to those defects
- MOT outcomes where relevant
- any notes explaining off-road periods or moved inspections
Put the documents in date order. If there is a gap, explain it plainly. For example, if a vehicle was off the road for three weeks awaiting parts, include the note that shows when it was stood down and when it returned. Do not make the examiner guess.
If the roadside stop relates to a specific defect, trace that item through the file. If the issue was a tyre, lamp, brake defect, steering component, or body security issue, find any earlier reports or inspections touching the same area. That lets you answer the real question, which is whether this was an isolated failure or evidence of weak maintenance control.
Check names, dates, and registrations before anything leaves your office. A common own goal is sending the wrong PMI for a sister vehicle with a similar fleet number.
If records are digital, export them in a format that preserves the order and the audit trail. If records are paper-based, scan them cleanly and label them sensibly. "Vehicle AB12 CDE, PMI 14 March, defect rectification 15 March" is useful. "Scan 47" is not.
Most of all, present the records as one coherent account. That is what shows control. A credible maintenance system is not proved by saying you take compliance seriously. It is proved by being able to put one vehicle in front of DVSA, on paper or on screen, and show exactly how its roadworthiness has been managed from one inspection to the next.
That is the standard we work to ourselves, both in the workshop and in the software we build from it. If your records cannot tell that full story quickly, the fix is not more filing. It is a tighter day-to-day process, built around the vehicle, the work done, and the evidence that proves it.
How far back should vehicle maintenance records be kept?
Keep records long enough to show a clear maintenance history and to support your operator licensing responsibilities. In practice, operators should be able to produce a consistent record set for each vehicle, not just the latest PMI.
Do roadside checks only look at the vehicle on the day?
No. A roadside check can lead to questions about the wider maintenance system. If DVSA finds a defect, they may want to see whether your records show proper inspection, repair and follow-up.
Should driver defect reports be kept with PMI records?
Yes. They should sit in the same vehicle history, or be linked clearly to it. DVSA needs to see that reported defects were reviewed, repaired if needed and closed properly.
Is a spreadsheet enough for maintenance records?
It can be, if it is accurate and backed by the actual documents. The problem is usually not the spreadsheet itself but missing inspection sheets, unclear sign-off and records spread across emails, paper and phones.
What makes a maintenance record look weak to DVSA?
Missing PMI sheets, no evidence of repairs, dates that do not line up, unsigned inspections, repeated defects with no root fix, and records that take too long to find all suggest poor control.
