When DVSA asks for maintenance records, they are not looking for a neat pile of paper for its own sake. They are looking for proof that we control roadworthiness in a way that is real, consistent and visible across the fleet. That means being able to show what was planned, what was found, what was repaired, who made the decision, and when the vehicle was safe to go back out.
A maintenance file stands up in a DVSA audit when the history joins up. The PMI sheet matches the schedule. The defects have repair evidence. The brake results are there where they should be. The MOT history does not contradict the inspection pattern. If a vehicle missed a preventative maintenance inspection, the reason is recorded and the catch-up action is clear. Credibility comes from complete records and a traceable process, not from the format alone.
What DVSA is actually looking for in maintenance history
For a UK operator running under an O-licence, the standard is not just “do some servicing”. DVSA and, if matters escalate, the Traffic Commissioner want to see evidence of a proper maintenance system. In practice, that means we need to produce records that show planned inspections, defect reporting, repair completion and management control.
The core records usually include:
- the vehicle’s maintenance planner or schedule
- completed PMI sheets for each inspection
- records of safety inspections and repair work
- brake test results, whether loaded roller brake tests or acceptable electronic brake performance evidence where appropriate
- daily walkaround defect reports and nil defect reporting process
- rectification records for reported defects
- MOT certificates and test history
- records of prohibitions, if any, and what was done afterwards
- evidence of tyre inspections and tyre-related repairs where relevant
- tachograph calibration and related workshop dates where these affect vehicle availability and planning
- odometer readings or mileage capture that supports the inspection frequency being suitable
- records for trailers as well as powered units
DVSA is not just checking whether the documents exist. They look at whether the maintenance history makes sense as a whole. If a vehicle is meant to have a PMI every six weeks, they will notice if there are eight or nine weeks between inspections. If the PMI says “brake imbalance, rectify” but there is no job card, no parts issue, no technician note and no brake re-test, that gap matters. If the vehicle was off road, they will expect the dates and reason to line up with the missing use.
This is where a credible vehicle maintenance history for DVSA audit purposes differs from a file built in a hurry the night before. A credible history shows routine control. The intervals are sensible for the vehicle’s work. The sheets are signed. The outcomes are legible. Defects lead to repairs. Repairs lead to release. Advisories do not disappear.
The UK position is also specific to the O-licence regime. Operators here answer to DVSA and, where necessary, the Traffic Commissioner, in a way that is not the same as a general EU-wide transport rulebook. A continental operator may have equivalent roadworthiness duties, but the exact scrutiny around O-licence undertakings, OCRS impact and public inquiry consequences is a UK matter.
If you want a fuller checklist of what should be on hand before anyone calls, we have set that out in the records to have ready for a DVSA O-licence audit.
Paper files versus spreadsheets versus fleet software
Most operators we see are using one of three methods. Paper files in a cabinet. Spreadsheets on a shared drive. Or a digital fleet system. All three can work up to a point. All three can also fail badly when DVSA asks for evidence.
Paper has one obvious strength. It is simple. A workshop can complete a PMI sheet, attach the brake printout and file it. There is very little training needed. For a very small fleet, with one person controlling maintenance and one workshop doing the work, paper can still be workable.
Spreadsheets are usually the next step. They help with planning. We can colour code due dates, record inspection intervals, list MOT and tachograph dates, and track defects across vehicles. For five or six vehicles, especially where one transport manager knows every registration by heart, spreadsheets often feel enough.
Fleet software comes into its own when the record needs to be joined up, not just stored. That means linking the planner to the PMI, the PMI to the defects, the defects to the repair, and the repair to the decision that the vehicle can return to service. It also means keeping a history of who changed what and when.
When DVSA asks for evidence, the issue is not whether the records are digital. It is whether we can produce a clear maintenance history quickly and without argument. A paper system can do that if it is disciplined. A spreadsheet can do it if the operator is small and the person running it is meticulous. A proper digital system usually does it more reliably because the dates, documents and actions sit in one place.
The trap is assuming software alone makes an operator compliant. It does not. Bad workshop habits can be hidden in expensive systems just as easily as in a lever arch file. What software should do is make it harder to miss things and easier to prove what happened.
We have covered the practical side of this in what DVSA checks in maintenance records, because the problem is usually not a missing feature list. It is a missing link in the evidence.
Where paper records usually come unstuck
Paper records usually fail in ordinary ways. Not dramatic ones. A sheet stays in the cab. A brake printout is left on the workshop bench. A technician writes “see job card” and the job card never gets attached. By the time DVSA asks questions, everybody remembers roughly what happened, but nobody can prove it.
The common weaknesses are predictable.
Missing sheets are the first one. A vehicle may well have had its PMI on time, but if one inspection form has gone missing, the history now shows a gap. In an audit, “we definitely did it” is not worth much without the record.
Poor handwriting is another. We all know workshops where one fitter writes clearly and another writes like a doctor in a moving lorry. If the defect, the action taken or the sign-off cannot be read, the record is weak. That matters even more where the issue was safety critical.
Delayed filing causes just as many problems. The paperwork exists, but it is in a pile waiting to be sorted. When DVSA gives short notice, the operator spends half a day hunting through desks, cabs and trays. That is not just inconvenient. It tells the auditor the system depends on memory and goodwill.
Traceability is often the biggest weakness. Paper does not naturally show relationships between records. We might have the PMI sheet in one file, the repair invoice in another, and the tyre report somewhere else. Unless somebody has cross-referenced everything carefully, the maintenance history looks fragmented.
There is also the problem of altered records. Sometimes it is innocent. A date is corrected. A mileage figure is rewritten. An inspection interval is changed after the event because the planner was wrong. On paper, those changes can look suspicious even when they are not. Without a clear note of who changed what and why, credibility suffers.
For operators using outside workshops, paper gets harder still. Documents move between businesses. Copies are scanned at different times. One side thinks the other has filed the sheet. If the maintenance provider changes, continuity can disappear altogether.
Paper can still work, but only where someone owns the file from start to finish. They chase missing sheets the same day. They attach supporting documents at once. They review the file, not just store it. Most fleets beyond a handful of vehicles struggle to keep that discipline for long.
Why spreadsheets cope for a while and then become a risk
Spreadsheets are useful because they solve the first planning problem cheaply. We can list every unit and trailer, set due dates for each PMI, flag MOT expiry, note vehicles off road and keep a basic defect log. For a small fleet, that is a real step up from paper diaries and wall calendars.
They also help transport managers see the whole month. If three vehicles are due together, we can move bookings around. If a trailer is standing idle, we can bring work forward. For five to ten vehicles, a spreadsheet often gives enough visibility to stop obvious misses.
The problem is that spreadsheets do not control process. They only display what someone has typed into them.
Version control is the usual starting point. There is a master file, then a copied file, then “maintenance planner new”, then “maintenance planner latest”, then a copy emailed to the workshop. Two people update different versions. A due date changes in one place but not another. Nobody is lying. The system is just loose.
Missed dates creep in quietly. A cell colour changes, but nobody sees it because the file was not opened that morning. A filter is left on and one vehicle drops out of view. A formula gets overwritten. A row is inserted badly and the reminder no longer points to the right date. These are ordinary spreadsheet failures. They happen in good businesses.
The bigger issue in a DVSA audit is broken links between records. The planner says a PMI was done on 14 March. Fine. Where is the sheet? The sheet says a brake issue was found. Fine. Where is the repair? The repair invoice exists. Fine. Where is the evidence the vehicle was not used until it was safe? A spreadsheet can point to these things, but it rarely binds them together.
Spreadsheets also depend heavily on one person. Usually it is the transport manager or owner. They understand the colour codes, the comments, the hidden tabs and the workarounds. If they are away, the system becomes brittle. If they leave, the business inherits a file full of private logic.
We see this a lot with fleets that have outgrown the “I know every truck” stage but are not big enough for a full enterprise setup. That is exactly where missed PMIs and weak audit trails start to hurt. If that sounds familiar, our guide on how to stop missed PMIs on lorries before DVSA finds them goes into the practical warning signs.
What a usable digital record should let you prove
A digital system is useful when it helps us prove maintenance control, not when it simply turns paper into PDFs.
At minimum, it should let us show the planned schedule for every vehicle and trailer, including the set inspection interval and any justified changes to it. It should show when a PMI was due, when it was completed, and whether it was early, on time or late.
It should link the completed PMI to the actual vehicle record. Not just as a detached upload, but as part of the maintenance history. If a defect was found, we should be able to move straight from that inspection to the repair record. If the repair needed parts, outside work or a brake re-test, those should sit with it.
A usable system should also keep an audit trail. If someone changes a due date, amends a defect status or marks a vehicle back on the road, we need to know who did it and when. That matters in real life, not just in audits. When something goes wrong, the first question is often simple. Who made that call?
It should also help with exceptions. Vehicles go off road. Jobs overrun. MOT bookings move. A workshop finds extra work during a preventative maintenance inspection. The record needs to show the reason and the decision, not just present a clean schedule as if nothing ever slipped.
For workshops, the practical links matter. A defect from a driver report should be traceable to technician action. A PMI advisory should not vanish because it was not an immediate fail item. Brake performance evidence should be easy to retrieve. If a prohibition or roadside issue occurred, the follow-up should be visible in the same history.
None of this means software makes us compliant by itself. It does not inspect the vehicle. It does not train the fitter. It does not challenge a weak maintenance provider. But it should make weak control harder to hide and proper control easier to demonstrate.
That is the standard we work to because we run a real workshop ourselves. The point is not to create more admin. It is to leave a usable trail from defect to decision. We have written more on that in proving defects were fixed before they became a problem.
How to choose the right record system for a five to hundred vehicle fleet
The right system depends less on ambition and more on how the work is actually done.
If we run five vehicles, use one workshop, and one person controls the diary closely, paper or a basic spreadsheet may still be enough. But only if the filing is disciplined and the inspection schedule is simple. The moment PMIs start slipping, documents go missing or trailers are being forgotten, that system is already too small.
For a fleet around ten to twenty vehicles, spreadsheets often become the weak point. There are enough bookings, defects and date changes that manual control starts to fray. If we also use a mix of in-house and external workshop support, the chance of broken records rises again. This is usually the point where a digital maintenance record starts paying for itself, not because the fleet is huge, but because the audit risk is now real.
From twenty vehicles upward, especially with trailers, multiple depots or mixed workshop arrangements, we would usually want a proper digital system. Not a bloated one. Just one that gives us scheduling, document control, defect linkage and a reliable audit trail. The person responsible for the O-licence should be able to review the fleet status without chasing three people and two filing cabinets.
Workshop setup matters as much as fleet size. A strong in-house workshop can maintain good records if the admin process is built into the job. An external maintenance provider can also do it well, but only if we receive complete documents promptly and review them. If the provider sends a batch of PDFs at month end, that is not good control. That is delayed visibility.
Think about audit risk honestly. Have we had roadside encounters that could affect OCRS? Do we rely on one person’s memory? Are PMIs ever moved because the vehicle is busy, without the reason being written down? Do MOT, PMI and repair records live in different places? If yes, the system is probably already weaker than it looks.
The answer is not always to buy the biggest package. Fleets in the five to hundred vehicle range usually need something practical. Easy to use in the workshop. Clear enough for the transport office. Strong enough to answer DVSA without a week of preparation. That is a narrower requirement than many software sellers make out.
A maintenance record system should fit the business we actually run. If it takes too much effort, people work around it. If it cannot show joined-up evidence, it fails when it matters. The best choice is the one that lets us prove roadworthiness day after day, not the one with the longest brochure.
For operators reviewing their current setup, start with one test. Pick a vehicle at random and try to produce six months of maintenance history, including PMIs, defects, repairs, brake evidence and MOT, in order, with no gaps and no guesswork. If that is hard, DVSA will find it hard too. That is the point where the record system needs fixing, before the audit does it for us.
What counts as vehicle maintenance history for a DVSA audit?
It is the record of planned maintenance and what happened after it. That usually includes PMI sheets, defect reports, repair records, brake test evidence where applicable, MOT history and proof that defects were rectified.
Can a spreadsheet be enough for DVSA?
It can be enough if it is accurate, current and backed by proper inspection and repair records. The problem is not the spreadsheet itself. It is the gaps, missed dates and weak audit trail that often come with it.
Do I have to keep maintenance records digitally?
No. Records do not have to be digital just because DVSA may inspect them. They do need to be complete, legible and easy to produce when asked.
How far back should maintenance records go?
Keep them in line with current DVSA guidance and your operator licensing obligations. The key point in an audit is that the records are available, organised and cover the period DVSA asks to review.
Will software improve my OCRS on its own?
No. OCRS is affected by outcomes such as encounters, prohibitions and test results, not by the fact you bought software. A system can help you keep control of maintenance, but it does not replace doing the work properly.
