If you are asking what records you need for an operator licence audit, start with this: DVSA is not coming to admire a tidy folder. It is checking whether we can prove continuous control. Control of vehicle roadworthiness, control of drivers, and control of the systems that are meant to keep both in order every week, not just the day before the visit.
That means the right answer is not “our MOTs are up to date” or “the workshop knows the vehicles”. We need records that show planning, action, follow-up and management oversight. If a vehicle had a defect, there should be evidence it was reported, repaired and signed off. If a driver had tachograph infringements, there should be evidence we reviewed them and did something. If an inspection was missed, there should be a record of why, what risk was assessed, and how the vehicle was brought back into schedule.
What a DVSA audit is really checking
A DVSA audit under an O-licence is about proof. The undertakings on the licence are not met by good intentions or verbal explanations. The auditor wants to see whether the operator has effective and continuous systems in place.
In practice, DVSA is usually testing a few basic questions.
Can we show every vehicle has been kept in a proper maintenance regime?
Can we show inspection intervals are set correctly for the vehicle’s use, age and work?
Can we show defects are found and fixed before they become a roadworthiness problem?
Can we show drivers are properly managed, including licence entitlement and tachograph compliance?
Can we show the transport manager, or the responsible person in a smaller operation, is actually exercising control rather than reacting after the event?
That is why an audit often feels wider than “maintenance records”. It is not just about the file in the workshop office. It is about the whole chain. The inspection planner, the PMI paperwork, the defect book, the brake test evidence, the driver licence checks, the infringement reports, the maintenance provider invoices, the MOT history, and the internal checks that show someone is watching the system.
If the records are complete and consistent, an audit is usually manageable. If they are patchy, contradictory or clearly assembled in a rush, DVSA starts asking what else is missing. That is often where trouble starts, especially if the issues point to a loss of continuous and effective control, which is exactly what concerns the Traffic Commissioner.
The vehicle maintenance records you need first
Start with the vehicle file. Build it vehicle by vehicle, not by whatever happened to be nearest the printer.
For each vehicle, we would want the following in front of us.
First, the maintenance planner or inspection schedule. This should show the agreed inspection interval for that vehicle and the dates inspections were due and completed. If the vehicle is on a six weekly cycle, the file should show that clearly. If the interval changed, there should be a reason. Heavy use, urban stop-start work, age, mileage and load profile all matter. DVSA will expect the interval to make sense for the operation.
Second, every PMI sheet. Each preventative maintenance inspection should be present, legible, dated and properly completed. That means the inspection has enough detail to show what was checked, what was found, what was measured where measurements matter, and who carried it out. If a PMI sheet is unsigned, partly blank or impossible to read, it is weakened evidence.
Third, repair history linked to the inspections and defects. If a PMI found worn brake components, a lamp fault, tyre damage or steering play, there should be a repair record showing what was done and when. If the work was outsourced, keep the job card, invoice and any supporting worksheet. If the work was done in house, the workshop record needs to be just as clear.
Fourth, MOT results and any associated rectification work. The annual test pass certificate matters, but the failures and advisories matter too. If a vehicle failed or picked up advisories, keep evidence that the issues were rectified. A clean audit file does not hide failures. It shows how they were dealt with.
Fifth, brake performance evidence. This is where many otherwise tidy files weaken. DVSA increasingly expects objective brake test evidence, not just “brakes checked” written on a PMI. If you use roller brake testing, keep the printouts with the relevant inspection or service record. If you use a decelerometer where appropriate, the record still needs to be clear and defensible. If you want a practical view of what good evidence looks like, see our piece on what customers should expect from brake roller testing.
Sixth, safety defect records and proof of rectification. This includes driver-reported defects, workshop findings between inspections, roadside issues and any prohibition-related work if that has happened. The point is not just that defects were found. The point is that they were controlled. If a nil defect report is part of your system, keep that too.
Seventh, evidence of downtime or non-use where there are gaps. If a vehicle appears to miss an inspection cycle, the file must explain why. Off road for accident damage, laid up, sold, on long-term hire movement, waiting major repair, all of that can be legitimate. What causes trouble is an unexplained hole in the timeline.
For a deeper look at the workshop side, we have set out what DVSA checks in maintenance records.
Driver and tachograph records that must match the fleet file
The maintenance file and the driver file have to agree with each other. A vehicle cannot be shown as off road in one place and used in tachograph records in another without a very good explanation.
For each driver, keep a current licence check record. That should include the full licence entitlement, expiry dates, endorsements and the date the check was carried out. One check done years ago is not enough. The frequency should reflect risk. Higher mileage drivers, drivers with points, agency drivers and anyone with recent issues should be checked more often.
Keep driver CPC records where relevant, plus any induction or policy sign-off documents. If the driver has been briefed on defect reporting, walkaround checks, tachograph use or drivers’ hours rules, keep evidence of that briefing.
Tachograph records need particular care. In the UK, DVSA will expect to see that driver card data and vehicle unit data are downloaded at sensible intervals and analysed. The exact interval may depend on your system, but “when we remember” is not a system. The records should show the downloads happened, the reports were reviewed, and infringements were followed up.
That follow-up is what many operators miss. An infringement report sitting unread in a folder is not management control. We need evidence that someone reviewed it, spoke to the driver where necessary, recorded the outcome and checked whether the issue repeated. A repeated drivers’ hours or missing mileage problem with no action taken tells DVSA the system is not working.
Keep records of missing mileage explanations, manual entries, lost cards, card faults and any periods of driving without a card where legally permitted and properly documented. If there was an exception, write it down at the time. Trying to reconstruct it months later rarely looks convincing.
Agency and relief drivers are another weak spot. Their records should be as complete as employed drivers. Licence checks, tachograph analysis, induction and defect reporting arrangements still apply. If they drive our vehicles, they sit inside our O-licence risk.
Where records overlap, make sure they match. If a tachograph report shows a vehicle in daily use, but the maintenance file shows it was waiting rectification of a safety defect, that contradiction will be noticed.
Proof that your systems work in practice
DVSA is rarely satisfied by isolated documents. It wants to see a working system.
Daily defect reporting is one of the clearest examples. Keep the driver walkaround check records, whether paper or digital, including nil defect reports if those form part of the process. Where defects were reported, keep the rectification record and any decision on whether the vehicle could continue in service or had to be stopped.
Missed inspections need their own trail. Vehicles do sometimes miss a booked PMI. Parts delay, workshop capacity, breakdown, customer pressure, all of that happens in the real world. The problem is not that it happened. The problem is when there is no record of who authorised continued use, what assessment was made, and when the inspection was rearranged. A missed inspection should create management action, not silence.
OCRS monitoring is another useful piece of evidence. If your OCRS profile has changed, or if there have been encounters at the roadside, keep a record that someone reviewed the cause and responded. That might mean tightening inspection intervals, reviewing brake performance, retraining drivers on walkarounds, or checking whether a maintenance provider is slipping.
Training records matter more than people think. Keep toolbox talks, defect reporting briefings, tachograph training, licence checking procedures, and any transport manager review notes. If a driver or fitter has been instructed on a recurring issue, record it. Verbal systems are nearly impossible to prove later.
Internal checks also help. That might be a monthly file review, a sample audit of PMI completion, a check that brake test printouts are attached, or a review of overdue defects. These are simple controls, but they show active management. They also stop small errors becoming a pattern.
This is where workshop-led systems make a difference. We built our operator compliance software for maintenance evidence and audit trails around the records a real audit asks for, because we deal with those records in a working HGV workshop every day.
Common gaps that turn a tidy file into a bad audit
Most bad audits do not come from one dramatic failure. They come from ordinary gaps repeated across the file.
Unsigned PMI sheets are common. So are sheets with no clear outcome, no odometer reading, or defects listed without any matching repair record.
Unexplained date gaps are another. A vehicle disappears from the inspection pattern for weeks, then reappears with no note of lay-up, no off-road declaration in the file, and no management comment. That looks like loss of control.
Missing brake test evidence is a regular problem. If the PMI says brakes were checked but there is no measured result and no supporting printout where one should exist, DVSA may doubt whether the check was robust enough.
Poor filing causes avoidable damage. When records exist but cannot be produced, that still hurts. An auditor will not assume the missing document is perfect. They will assume the system is weak.
Contradictory records are worse than missing ones. A defect marked repaired before the parts invoice date. A vehicle shown on hire to another site but still on local defect sheets. A driver signed as doing walkaround checks while on holiday. These things get noticed.
Another weak spot is over-reliance on the maintenance provider. Even if inspections are outsourced, the legal duty under the O-licence stays with the operator. “The garage has it” is not a defence. We still need the records, and we still need to review them.
Smaller restricted operations often fall into this because the same person is booking work, chasing drivers and paying invoices. If that is your setup, our article on keeping a restricted licence fleet under control may help tighten the basics before an audit exposes the weak points.
How to prepare the records so the audit runs cleanly
Prepare the audit pack in the way the auditor is most likely to ask for it, by vehicle, by driver and by date.
For vehicles, create one file or digital folder per unit and trailer if applicable. Put the maintenance schedule at the front. Then the PMI sequence in date order. Behind each PMI, attach the repair records and brake test evidence that belong to it. Keep MOT certificates and annual test history together in their own section. Add defect reports and rectification records in date order if they are not already linked elsewhere.
For drivers, keep one file per driver. Start with the licence check record and entitlement evidence. Then CPC and training records. Then tachograph analysis reports, infringement follow-up notes, and any disciplinary or coaching records where relevant. Agency drivers should have the same structure.
Use a simple index. Vehicle registration, fleet number, inspection interval, last PMI date, next PMI due date. Driver name, licence check date, last tachograph review date. This saves time and shows control immediately.
Before the audit, do a reconciliation check. Pick a sample vehicle and compare the maintenance planner, PMI dates, defect reports, MOT history and tachograph activity. Do the dates line up. Do the defects have closure. Are there any periods of use that do not fit the maintenance story.
Do the same with a sample driver. Check the licence, recent infringement reports, follow-up action and any vehicle defect reporting against the dates they were driving. You are looking for contradictions before DVSA does.
If documents are missing, do not try to disguise the gap with a fresh printout and no explanation. Record what is missing, why it is missing, what steps were taken to recover it, and what has changed to stop it happening again. Honest remedial action is far better than a file that looks manufactured.
Finally, make sure the person handling the audit knows where everything is and understands the system. A good record set can be undermined by hesitant answers and confusion over who reviews what. The auditor is not only reading the paperwork. They are assessing whether the operation is actually under control.
That is the practical answer to the question of what records you need for an operator licence audit. We need enough evidence to show a continuous, working system. Not just maintenance done, but maintenance planned, completed, checked and followed up. Not just drivers employed, but drivers managed. Not just paperwork stored, but paperwork that proves control of roadworthiness under the O-licence every day.
How far back should O-licence audit records go?
Keep records in line with current UK requirements for each record type. DVSA may sample different periods, so the safe approach is to have a complete, orderly history for maintenance, drivers and tachograph records.
Will DVSA only look at maintenance records?
No. roadworthiness is central, but DVSA may also review driver licence checks, tachograph management, defect reporting, maintenance planning and evidence that the transport operation is properly controlled.
Do digital records count for a DVSA audit?
Yes, if they are complete, readable and easy to produce. A digital system helps, but only if the records are accurate and show dates, actions, sign-off and follow-up clearly.
What if a PMI or defect record is missing?
A missing record is a problem because you may be unable to prove the work was done. One gap can lead DVSA to question the rest of the system, especially if there is no explanation or supporting evidence.
Should workshop repair invoices be kept with compliance records?
Yes, where they help prove what was found and what was fixed. Invoices, job cards and parts records can support PMI sheets and defect reports when DVSA wants evidence of follow-up work.
