· 13 min read
How to pass an operator licence audit first time
A practical guide to preparing for an operator licence audit, with the records, checks and evidence UK operators need to keep ready.
Passing an operator licence audit first time comes down to one thing, control. The auditor is not looking for perfect paperwork for its own sake. They are checking whether we run a compliant operation day to day, whether our systems actually work, and whether the transport manager can show active and continuous management of vehicles, trailers and drivers.
That means an O licence audit is usually won or lost before the auditor arrives. If records are complete, dates are planned, defects are followed through, tachograph issues are reviewed and actions are signed off, the visit is normally straightforward. If records are scattered across spreadsheets, filing cabinets, workshop invoices and driver WhatsApp messages, the audit becomes much harder to defend.
What an operator licence audit is really checking
In the UK, an operator licence audit is about whether we are meeting the undertakings attached to our goods vehicle or PSV operator licence. The exact trigger varies. It may be a DVSA investigation, a follow-up to concerns, a desk-based assessment, a pre-grant check, or preparation for a Public Inquiry before the Traffic Commissioner. Whatever the route in, the themes are the same.
Auditors are trying to confirm that we have effective management control over the fleet. That includes:
- vehicles and trailers are kept fit and serviceable
- safety inspections are carried out at the right intervals
- MOT or annual-test dates are planned and not missed
- reported defects are assessed, repaired and closed properly
- VOR decisions are clear and enforced
- drivers are correctly licensed and qualified
- tachograph records are collected, analysed and acted on
- the transport manager is exercising continuous and effective management
They are not only checking whether documents exist. They are checking whether the documents tell a consistent story. If a PMI sheet shows an advisory for tyre wear, they will want to see whether it was repaired and whether the vehicle continued in service appropriately. If tachograph analysis shows repeated drivers' hours infringements, they will want evidence that the issue was investigated, discussed with the driver and monitored afterwards.
For goods vehicle operators, the audit is tied closely to the licence undertakings and the expectations in the DVSA Guide to Maintaining Roadworthiness. For PSV operators, the same principle applies, but the terminology and some testing requirements differ. In either case, the UK regime is based on operator licensing and Traffic Commissioner oversight. That is not the same as the wider EU picture. EU drivers' hours and tachograph rules still influence what is checked, but the audit itself is about compliance with the UK operator licensing system.
If we want a simple way to think about it, the auditor is asking three questions. Do we have a system, do we follow the system, and can we prove it?
Which records should be ready before the audit
Before any audit, we should gather records into one place and check them for gaps. The aim is not to drown the auditor in paper. It is to make it easy to answer questions clearly.
The core operator file should include the operator licence itself, licence discs, details of the operating centre, authorised vehicle and trailer numbers, and any correspondence through VOL. We should also have named responsibilities for the transport manager and anyone supporting compliance. If there have been changes to entity name, directors, operating centres or transport manager arrangements, the audit file should show what was changed and when.
For each vehicle and trailer, we should have:
- registration number or fleet number
- make, model and VIN if held
- plating details where relevant
- MOT or annual-test due dates
- safety inspection interval
- maintenance provider details, if outsourced
- records of inspections, repairs and brake tests
- VOR history where applicable
The maintenance file needs more than inspection sheets. It should include the planner, completed inspection reports, repair records, job cards, technician notes where available, and evidence that defects were rectified. If work is outsourced, invoices alone are rarely enough. We need the actual inspection and repair detail.
For drivers, we should have:
- driving licence check records
- entitlement verification with DVLA
- right to work records where relevant
- Driver CPC status
- DQC expiry details
- induction records
- policy acknowledgements
- infringement letters, meeting notes and retraining evidence
Tachograph records must also be ready. That usually means driver card download schedules, vehicle unit download schedules, analysis reports, infringement reports, missing mileage checks, manual entry checks, and records showing that management reviewed the reports and acted on them.
If we use agency drivers, the audit file should still show our control. We need evidence of licence checks, Driver CPC and DQC checks, tachograph management, and briefing on our defect reporting and drivers' hours procedures. Responsibility cannot simply be pushed back to the agency.
A good sense check is this. If an auditor picks any vehicle, any trailer and any driver at random, can we produce the full compliance picture quickly? If not, we should fix the filing before the visit. Our guide to operator licence maintenance records goes into the level of evidence worth keeping.
How auditors test your maintenance system
Maintenance is usually the deepest part of an operator licence audit because it goes directly to roadworthiness. Auditors will normally start with the inspection regime. They will check whether safety inspection intervals are appropriate for the vehicle type, age, usage, mileage and operating conditions. A six-week cycle may be right for one fleet and wrong for another. What matters is whether the interval is justified and then consistently met.
They will test the planner against actual completion dates. If inspections are booked every six weeks but completed at seven or eight, the effective interval is already slipping. Repeated lateness suggests weak control. We should check this ourselves before the audit and be ready to explain any exceptions, such as documented VOR periods.
MOT and annual-test planning is another obvious checkpoint. Auditors will look for forward planning, booking dates and pass or fail outcomes. Missed tests, late presentations and repeated prohibitions raise concern quickly. If a vehicle failed, the file should show what was repaired and when it was represented.
Defect reporting is often where systems look fine on paper but fail in practice. The auditor will want to see daily walkaround checks, defect reports, nil defect reporting where used, and evidence that reported issues were triaged correctly. A common weakness is when drivers report defects but there is no clear sign-off showing whether the defect was safety critical, whether the vehicle was taken off the road, and when it returned to service.
That is where VOR control matters. If a defect should have stopped the vehicle, the record must show that it was put VOR and stayed VOR until repaired. Auditors may compare defect dates with job sheets, inspection sheets and usage records. If a vehicle appears to have remained in service with an unresolved safety defect, that is difficult to defend.
Brake testing is another area under closer scrutiny. The expectation is not just that brakes were looked at, but that brake performance was measured and evidenced at suitable intervals. Depending on the fleet and maintenance arrangement, that may be roller brake testing, decelerometer evidence in appropriate cases, or laden brake test evidence where required. The key point is that brake performance must be demonstrable, not assumed.
Repair follow-up is the final piece. If a safety inspection records defects or advisories, we should be able to show the next step. Was the repair done immediately, deferred appropriately, or monitored until the next inspection? An unresolved advisory with no decision recorded can be as damaging as a missing repair invoice.
Where maintenance is outsourced, auditors will still hold us responsible. A contractor can carry out the work, but we must control the schedule, review the paperwork and challenge poor standards. If we have not looked at missed inspections, incomplete sheets or weak brake testing, the problem remains ours.
How driver and tachograph compliance is reviewed
Driver compliance is reviewed with the same logic as maintenance. The auditor is checking whether we have a system, whether we use it consistently, and whether we act when something goes wrong.
Driving licence checks are a core requirement. We should be checking entitlement, categories, endorsements, expiry dates and any restrictions through DVLA at a frequency that matches risk. A one-off check at recruitment is not enough. Higher-risk drivers should be checked more often, and the reason for the review frequency should be clear. If we need a refresher on process, our article on driver licence checks for operators sets out what to verify.
The auditor may also look at whether the driver is in the correct licence category for the vehicle being used. That matters particularly where fleets mix vans, 7.5 tonne vehicles, artics, minibuses and coaches. If we have upgraded drivers, seasonal staff or agency cover, those records should be easy to trace. Our guide to UK driving licence categories for operators is useful for checking edge cases before the visit.
Driver CPC and DQC records should also be current and visible. For in-scope drivers, the auditor will expect us to know whether periodic training is complete and whether the DQC is valid. If a driver was out of scope for a period and then returned to in-scope work, the file should make sense of that history.
Tachograph compliance is reviewed in more depth than many operators expect. It is not enough to say that downloads are done by an external bureau. The auditor will want to see:
- driver card downloads completed on schedule
- vehicle unit downloads completed on schedule
- analysis reports produced regularly
- infringements reviewed by management
- follow-up with drivers
- evidence of retraining or disciplinary action where needed
- missing mileage explained
- manual entries and unknown driver events considered where relevant
Missing mileage is a frequent problem. If the total distance on the vehicle does not reconcile with recorded tachograph activity, we should know why. Ferry movements, workshop moves and exempt driving can all explain variances, but unexplained gaps suggest weak control.
Infringement management must be active. If analysis reports show repeated rest, break or driving time issues, the auditor will expect to see letters, meeting notes, return-to-work style discussions, toolbox talks or further training. Generic signatures on a monthly report are weak evidence. Specific comments and dated actions are much stronger.
This is also where management visibility matters. A transport manager should be able to explain the pattern of issues in the fleet, not just produce software output. The report is the starting point. The audit question is what we did with it.
Common audit failures and how to fix them before the visit
Most audit failures are not caused by one dramatic breach. They come from repeated small gaps that show poor control. The good news is that many can be fixed before the auditor arrives if we review honestly.
A common problem is incomplete maintenance files. The inspection sheet is present, but the repair paperwork is missing. Or there is an invoice, but no detail showing what was rectified. The fix is to reconcile every inspection with the related repair evidence and chase missing documents from the workshop now, not after the audit starts.
Another frequent issue is overdue safety inspections hidden by a planner that was never updated. We should compare planned dates with actual completed dates vehicle by vehicle. If there were missed intervals, record the reason and correct the planning routine immediately.
Defect reporting often fails because nil defects are inconsistent, handwriting is unclear, or there is no sign-off from the fitter or responsible person. Before the visit, sample a few weeks of reports for several drivers. If the pattern is weak, tighten the process and brief drivers again.
Driver files often contain out-of-date licence checks or missing Driver CPC evidence. Run a full exception report, complete the missing checks and record the date they were reviewed. Do the same for DQC expiry dates.
Tachograph compliance commonly fails on action, not analysis. Operators have reports but no evidence that anyone read them. The fix is to create a clear review trail. Record who reviewed the report, what issues were identified, which drivers were spoken to and what follow-up was set.
Transport manager oversight is another weakness. If the transport manager cannot show regular review of KPIs, defects, inspections, infringements and test dates, the auditor may conclude that management is nominal rather than effective. A monthly compliance review, signed and retained, goes a long way.
Finally, check that the operator licence details themselves are current. Authorised vehicle numbers, operating centres, entity details and transport manager arrangements must match reality. If they do not, correct them through VOL and keep the correspondence. Our guidance on operator licence undertakings is a useful reminder of what the Traffic Commissioner expects us to keep on top of.
What good audit preparation looks like for a transport manager
Good preparation is structured, not frantic. A transport manager should know in advance who holds each record, how exceptions are reported, and what evidence proves that decisions were made.
In practice, that means having one current compliance view covering vehicles, trailers, drivers and dates. We should know what is due this week, this month and next month. Using ISO week planning can help when inspections and downloads need to be spread evenly across the year rather than bunching at month end.
Responsibilities should be clear. For example:
- who books inspections, MOT and annual-test slots
- who checks completed workshop paperwork
- who reviews defect reports each day
- who runs licence checks with DVLA
- who monitors Driver CPC and DQC expiry
- who reviews tachograph analysis
- who signs off infringements and retraining
The transport manager does not have to do every task personally, but must control the system and review the output. That means documented reporting lines and evidence of review. Signed meeting notes, action logs, exception reports and monthly summaries are all useful.
Before the audit, we should carry out our own sample test. Pick a vehicle, trailer and driver at random. Then trace the last six to twelve months of compliance history. Can we show inspections completed on time, defects closed, brake testing evidenced, test dates met, licence checks done, Driver CPC current, tachograph downloads completed and infringements acted on? If any part of that chain breaks, fix the process first and then file the evidence.
This is where Operator Compliance is designed to help. We built it at Fleeta Limited around the practical records an auditor asks for, using the DVSA Guide to Maintaining Roadworthiness as the benchmark for how operators actually need to manage maintenance and compliance. That means keeping deadlines, inspection histories, driver records and signed evidence together, rather than spread across separate systems.
For operators with wider fleet systems, integration can matter as much as storage. Some businesses need data feeds into payroll, workshop or telematics platforms. Where that is relevant, a REST API and webhooks can reduce manual rekeying and make audit trails cleaner. Insurance and vehicle validation data may also sit elsewhere, such as askMID through the Motor Insurers' Bureau, also referred to as MIB. The point is not to collect technology for its own sake. It is to make sure the compliance record is complete and accessible when DVSA asks for it.
The same principle applies whether we run one vehicle or a mixed fleet across haulage, bus and coach, vans or specialist operations. Audits are easier when the transport manager can answer directly, produce the record immediately and show that exceptions were identified and dealt with.
A first-time pass in an O licence audit is usually the result of ordinary discipline done consistently. Keep the records complete. Review them on a schedule. Act on what the records tell us. If we can show that clearly, the audit becomes a demonstration of control rather than a search for missing pieces.
What is an o licence audit?
It is a review of whether an operator is meeting the undertakings and systems required under its operator licence. It usually looks at maintenance, drivers, tachographs, records and management control.
Who can carry out an operator licence audit?
An audit may be carried out internally, by a consultant, by a customer requirement or during regulatory scrutiny linked to DVSA or the Traffic Commissioner. The key point is whether your evidence stands up to review.
How far back should records be available?
The exact records requested can vary, so operators should keep maintenance, driver and tachograph evidence in an orderly file and be ready to produce historic records promptly when asked.
What documents do auditors usually ask for first?
They often start with vehicle and trailer lists, inspection schedules, MOT or annual-test dates, defect reports, repair records, driver licence checks, Driver CPC evidence and tachograph analysis reports.
Can software help with audit preparation?
Yes. A system can help track dates, store signed records, organise evidence and show follow-up actions. It does not replace management control, but it can make that control easier to demonstrate.