If you want the short answer to what DVSA checks in maintenance records, it is this: they are looking for proof that your vehicles were kept roadworthy by a real system, used properly, at the right intervals, with defects found, repaired and signed off before the vehicle went back on the road.
DVSA is not just reading forms to see whether boxes were ticked. They are testing whether the maintenance story makes sense from end to end. The dates, mileage, brake results, defect reports, workshop jobs, MOT history and actual vehicle use all need to line up. If they do not, DVSA will usually assume the paperwork is flattering the operation rather than recording it.
Why DVSA asks for maintenance records
DVSA wants to establish three things.
First, whether the vehicle was roadworthy when used. That is the basic point. A maintenance file should show that safety inspections happened when due, defects were reported, repairs were carried out properly, and the vehicle was not used in an unsafe condition.
Second, whether the operator is keeping to the undertakings behind the O-licence. An O-licence is not just permission to run vehicles. It comes with promises about inspection intervals, maintenance arrangements, record keeping and financial standing. DVSA will look at the maintenance records to see whether those promises exist only on paper or are actually being kept in the yard and workshop.
Third, whether the maintenance system works in real life. Plenty of operators have a written policy saying inspections are every six weeks, drivers do daily checks, and brake testing is done regularly. DVSA is used to reading policies like that. What matters is whether the records show it happening consistently across the fleet, including on the awkward vehicles, the busy weeks and the jobs done by outside repairers.
That is why an audit often feels less like a form check and more like a reconstruction exercise. DVSA is asking: was this vehicle used, did anyone inspect it, were defects found, were they fixed, and can you prove the vehicle was fit to go back out?
If the answer is mostly “we know it happened, but the paperwork is a bit thin”, you are already in trouble. In Great Britain, that can feed straight into OCRS, follow-up visits, prohibitions and, in serious cases, a call to the Traffic Commissioner. The UK system is tied to the O-licence regime; that is more specific than the general position in many EU states, where road transport enforcement exists but the licensing structure and record expectations are not identical.
Which records DVSA will usually want to see
The core bundle is usually predictable. If you run HGVs or PSVs, you should expect DVSA to ask for maintenance records for a sample of vehicles and trailers over a set period.
The usual documents include:
- PMI records for each vehicle and trailer
- the preventative maintenance inspection schedule showing planned dates and intervals
- evidence of actual attendance for inspection
- driver defect reports, including nil-defect reporting where used
- workshop job cards and repair invoices
- brake performance records, whether from roller brake tests, electronic brake testing, decelerometer evidence where appropriate, or other accepted records
- MOT pass and fail history
- prohibition history if any
- odometer readings and, where relevant, hubodometer records for trailers
- evidence that defects found on PMI or daily checks were rectified
- records showing when the vehicle was released back into service
- maintenance provider details if inspections or repairs are outsourced
DVSA may also want supporting material that is not filed as “maintenance” but helps show what really happened. That can include:
- tachograph records showing the vehicle was in use between dates
- job sheets or delivery records
- internal emails or defect notifications
- booking diaries from the workshop
- wall planner or digital schedule showing inspection planning
- calibration or service records for brake test equipment if you rely on in-house testing
If a third-party workshop does your inspections, DVSA will still treat the operator as responsible. “The garage has the paperwork” is not a defence. You need the records in your possession and you need to understand them.
A practical way to think about it is simple. DVSA wants the planned maintenance record, the actual inspection record, the defect record, the repair record and the evidence of continued or resumed use. Miss one of those links and the file starts to sag.
What DVSA checks on each PMI sheet
The PMI sheet is usually where the audit starts. If those records are weak, the rest of the file rarely saves you.
DVSA will check the basics first:
- vehicle registration and fleet number
- trailer number where relevant
- date of inspection
- mileage or recorded distance at inspection
- the due date of the next inspection
- the inspection interval actually being worked to
They will compare the inspection date against the stated schedule. If your system says six-weekly inspections but one PMI happened at eight weeks with no explanation, that is a missed inspection. One missed inspection can be treated as an isolated failure. A pattern suggests the maintenance system is not under control.
Then they look at the inspection content itself. A proper preventative maintenance inspection record should show what was inspected, not just that “a service” was done. It needs to cover the relevant safety items: steering, suspension, brakes, tyres, wheels, lights, chassis, body security, exhaust, couplings, mirrors, glass, warning devices and anything else required by the inspection standard for that class of vehicle.
The sheet should make clear whether items were satisfactory, defective, adjusted, repaired or requiring further work. Generic wording causes problems. “Checked vehicle over” tells DVSA almost nothing.
Brake evidence is one of the biggest points. If the PMI form has a brake section, DVSA will expect more than a tick saying “brakes ok”. They want measured brake results where the inspection included a brake performance assessment. On many fleets that means roller brake test figures, axle by axle, showing service brake and parking brake performance and any imbalance. If the measured results are elsewhere, the PMI should point to them clearly.
Where operators ask what does DVSA check in maintenance records, brake evidence is near the top of the list because poor braking is both common and serious. A maintenance file with repeated PMIs but no meaningful brake performance record is a weak file.
Rectification notes matter just as much as defect identification. If a PMI found an item defective, the record should show:
- what the defect was
- whether the vehicle was taken out of service
- what repair was done
- when the repair was done
- who did it
- whether the repair was checked
- when the vehicle was released
A common failure is a PMI with defects circled or noted, but no closure. Another is a separate invoice saying “repair carried out” without enough detail to connect it confidently to the defect on the PMI.
Signatures or named sign-offs are also checked. DVSA wants to know who inspected the vehicle and who accepted the rectification. If records are electronic, the user trail should still show who entered and closed the work. Anonymous entries are hard to defend.
They also look at handwriting, amendments and obvious back-filling. A perfect run of immaculate PMIs all completed in one pen, with no workshop grime and no variation, can attract the wrong sort of attention if the rest of the operation looks messy. That does not prove dishonesty, but it can prompt deeper checking.
How DVSA cross-checks defects, repairs and use of the vehicle
This is where operators often get caught out. A single record may look fine on its own. The problem appears when DVSA compares it with other evidence.
A normal cross-check starts with a defect report. Say a driver reported a tyre cut on Monday. DVSA will look for the workshop job or invoice showing inspection or replacement. Then they may look at tachograph or vehicle use evidence to see whether the vehicle kept running before the repair happened. If the vehicle did another two shifts before the tyre was changed, you need a very good explanation.
The same happens with brake defects, lamp faults, steering play, body security and anything marked safety critical. DVSA is asking whether the defect was:
- reported promptly
- assessed properly
- repaired before further use if necessary
- signed off by a competent person
- not repeated because the underlying issue was ignored
Release back into service is often badly recorded. Workshops may do the job, but the file does not show clearly when the vehicle was fit to return to operation. That gap matters. If the only evidence is that parts were ordered on Tuesday and the vehicle appears on tachograph records Tuesday afternoon, DVSA may conclude it went back out before the repair was complete.
Repeated defects are another giveaway. If three PMIs in a row note worn brake components, insecure marker lamps or the same tyre position losing pressure, DVSA will see that as poor repair quality or poor diagnosis. The issue is not only the defect itself but the fact the maintenance system failed to stop it recurring. Notes that explain root cause help. So do workshop records with enough detail to show more than a quick patch. If your workshop paperwork is thin, this piece on reducing repeat defects through better root cause notes is worth a read.
Driver defect reporting is also cross-checked against PMI findings. If your drivers submit nil-defect reports every day but every PMI finds obvious defects that should have been spotted on a walkaround, DVSA may conclude the driver check system is not credible. That does not always mean drivers are lazy. Sometimes they were never trained properly, or nil reporting became a ritual. Either way, the records do not support the claim that daily checks are meaningful. For a refresher on the sort of faults that should be reported at once, see these notes on daily walkaround defects worth reporting immediately.
Mileage and use patterns are checked as well. If a vehicle covers heavy mileage but the PMI intervals never tighten, DVSA may question whether the inspection frequency is appropriate. If a trailer is supposedly inspected regularly but has no distance record, no booking trace and patchy brake history, that will also be challenged.
The weak points that make records fail an audit
Most failed audits are not caused by one dramatic omission. They are caused by repeated weak spots.
Missed inspections are the obvious one. If the planned interval is six weeks, DVSA expects six weeks unless there is a documented and defensible reason. Running over because the vehicle was busy is not a good reason. Running over because the workshop forgot is worse.
Incomplete PMI paperwork is common. Missing mileage. No next due date. No inspector name. Defects noted but not closed. Brake section ticked with no measured result. Those may sound small, but together they tell DVSA the inspection process is loose.
Poor brake evidence is a major problem. Operators often say the vehicle “felt fine” or the brakes were checked during service work. That is not enough. Where brake testing should form part of the maintenance regime, the file needs evidence that can be read and defended. If it is done by a contractor, get the printout or report every time.
Defect reports that do not match repairs are another weak point. A driver reports “offside rear indicator intermittent”. The invoice says “electrical repair”. The vehicle is back out the same day. Maybe that is all fine. Maybe not. But the paperwork does not prove it.
Repeated defects damage credibility fast. If the same lamp, tyre, ABS warning or door security fault keeps reappearing, DVSA may conclude inspections are superficial or repairs are temporary.
Records that do not match actual vehicle use are particularly dangerous. A vehicle cannot be in the workshop for a PMI and out earning on the road at the same time. A trailer cannot have a clean PMI on Friday and then fail MOT on Monday for defects that do not appear overnight. These contradictions are what turn a weak file into a suspected false record.
Outsourced maintenance does not remove the risk. In fact, it often creates it. The contractor’s invoice may be too vague. The brake printout may never be sent over. The rectification details may stay in the garage system. DVSA will still hold the operator to account.
Finally, there is the problem of records that exist only after DVSA asks for them. If files have to be rebuilt from old emails, workshop memories and scanned invoices, the operation is already on the back foot. Reconstructed records are obvious more often than people think.
How to keep records ready for a DVSA visit
The hard truth is that being ready for DVSA is not about presentation. It is about discipline over time.
Keep one complete maintenance file per vehicle and trailer. Paper or digital is fine if it is complete, legible and easy to retrieve. Each file should show the running story of that asset: schedule, PMI, defects, repairs, brake results, MOT, and release back into service.
Maintain a live inspection planner. It should show due dates far enough ahead that bookings can be moved without missing the interval. Review it every week, not when something is already overdue.
After every PMI, check the paperwork before filing it. Not later. On the day. Make sure the registration is correct, mileage is entered, defects are readable, brake evidence is attached, and rectification is either complete or being tracked. A five-minute check then saves a long argument later.
Do the same for contractor paperwork. Garages vary. Some produce excellent records. Some send an invoice that says little more than “PMI done”. If the paperwork is poor, send it back and ask for the proper inspection sheet, defect list, brake results and sign-off. If a contractor cannot provide records to O-licence standard, use another contractor.
Keep defect reporting tight. Drivers should know what must be reported, when the vehicle must not move, and who authorises release. Nil reporting can work, but only if it is genuine. If your daily defect system produces nothing but blank perfection while the workshop keeps finding obvious faults, fix the process.
Make sure repairs can be traced from report to completion. The file should let an outsider follow the line without guesswork. Defect reported at 06:30. Vehicle assessed at 07:00. Job card raised. Repair completed at 09:15. Checked and released at 09:30. That is what a defensible record looks like.
Retain the evidence for long enough and in one place. Operators often keep the PMI but lose the supporting brake printout or the driver defect sheet. That is no good. The supporting evidence is part of the maintenance record.
Audit yourself. Pick a vehicle at random and test its file the way DVSA would. Check the last six PMIs. Check whether every defect was closed. Compare one repair date with tachograph use. Compare the PMI history with MOT outcomes. If the story does not hold together, fix the system before DVSA sees it.
If you use digital tools, the only thing that matters is whether they help you produce complete, credible records quickly. Fancy dashboards do not impress an examiner. Clean records do. Something built around workshop capture and operator evidence, such as this page on Operator Compliance Software, is useful only if it makes the paperwork stronger at inspection level.
In the end, what DVSA checks in maintenance records is not mysterious. They check whether the vehicle was inspected when it should have been, whether defects were recorded properly, whether repairs were done before unsafe use, whether brake performance was evidenced, and whether the paperwork matches the real life of the vehicle. If your records tell that story clearly, a visit is manageable. If they do not, no amount of explanation on the day will make the gaps look smaller.