How to run a fleet audit without missing evidence

A fleet audit is a structured check of the records that prove your vehicles, trailers, drivers and control systems are being managed properly. For a UK operator, that means more than tidying files. It means being able to show the DVSA and the Traffic Commissioner that your systems are real, current and followed in practice.

The easiest way to miss evidence is to treat an audit as a paperwork exercise at the end. The safer approach is to run it like an operator-licence check from the start, with a clear scope, a fixed sample, named documents, dated findings and actions that are actually closed out. If an examiner asks how you know inspections were done on time, defects were repaired, tachograph issues were reviewed, or Driver CPC and licence checks were completed, your audit file should answer that without guesswork.

What a fleet audit means for a UK operator

For a UK operator, a fleet audit is an internal review of compliance against the undertakings on your operator licence and the systems expected under the DVSA Guide to Maintaining Roadworthiness. It is how we test whether our controls are working before somebody else does.

For goods vehicles, the audit usually centres on roadworthiness, maintenance intervals, safety inspections, MOT performance, driver defect reporting, tachograph compliance where applicable, and the management controls behind them. For passenger fleets, the same principle applies, but the evidence often needs to cover annual-test planning, preventative maintenance, daily walkround checks, driver hours and records linked to PSV operation. For mixed fleets, the risk is that one system fits one part of the business but leaves gaps in the other. That is exactly what an audit should expose.

In operator-licence terms, the point is not only whether a vehicle was legal on the road on a given day. It is whether we can prove that our systems would keep the whole fleet compliant over time. The Traffic Commissioner is interested in management control, not just isolated fixes. A perfect inspection sheet for one vehicle does not compensate for a workshop planner with missed dates or a defect process that relies on memory.

This matters just as much for smaller operators. Owner-drivers and single-vehicle businesses often assume they know where everything is. That can be true until there is an unexpected DVSA visit, a public inquiry, a maintenance provider change, or a vehicle off road marked as VOR with no documented repair trail. A fleet audit turns assumed control into evidence.

What records should a fleet audit check?

A proper audit should cover the records that show legal use, planned maintenance, driver competence, tachograph control and management oversight. The exact list will vary by operation, but the core records are predictable.

For vehicles and trailers, we should check:

• Vehicle and trailer lists against the operator licence and actual assets in service
• Registration numbers, fleet numbers and VIN or chassis details
• MOT and annual-test dates, booking records and pass or fail outcomes
• Safety inspection schedules and completed inspection sheets
• Preventative maintenance inspection, or PMI, records
• Brake test evidence, where required by your maintenance regime
• Repair records, job cards, invoices and sign-off
• Calibration certificates for tachographs where relevant
• Insurance records and policy dates, with cross-checks where needed against askMID, which relies on Motor Insurers' Bureau, or MIB, data
• VOR records showing when a vehicle was taken off the road, why, and when it returned to service

For drivers, the audit should check:

• Driving licence checks with dates and outcomes, usually against DVLA data
• Driver CPC status, including expiry dates and evidence of completed training
• DQC expiry dates and copies where held
• Driver induction records
• Signed daily defect reports, including nil defect reports if that is your process
• Tachograph infringements, coaching notes and follow-up actions
• Agency driver records where agency labour is used

For tachographs and drivers' hours, the audit should cover:

• Download schedules for vehicle units and driver cards
• Evidence that downloads were completed on time
• Analysis reports
• Infringement reports
• Investigation notes for repeated or serious issues
• Missing mileage, unaccounted days and manual entry checks
• Working Time Directive records where your operation requires them

For compliance controls, we should also review:

• The maintenance planner and whether dates were set correctly
• Escalation reminders for upcoming tests and inspections
• Procedures for booking MOT or annual-test appointments
• Defect reporting workflows and repair authorisation
• Management review notes, transport meetings or audit reviews
• Training records for transport office staff and transport managers
• Document retention and version control

Deadlines matter. A record that exists but was created late can still show a system failure. If a safety inspection was due every six weeks, the audit should check the actual interval, not just the presence of a sheet. If a driver licence check was due monthly for a high-risk driver, quarterly for another, or on a set internal policy date, the audit should test that rule against the evidence.

How do you carry out a fleet audit step by step?

Start by fixing the scope. Decide whether the audit covers the full operator-licence system or one area such as maintenance, drivers, tachographs or trailers. Define the period under review, for example the last three months, six months or 12 months. If the business has multiple sites, state which depot or licence is in scope.

Next, set the sample. For a small fleet, the sample may be every vehicle and every driver. For larger fleets, select a spread that reflects risk. Include different vehicle types, at least one trailer group if relevant, newer and older assets, and drivers with different patterns such as agency, full-time, tramping or part-time. Include any asset or driver with previous issues. If a vehicle has recently been VOR, include it.

Then gather the source documents before you start checking. Pull the maintenance planner, PMI sheets, MOT or annual-test certificates, defect reports, repair records, licence checks, Driver CPC and DQC records, tachograph reports and management notes. Avoid auditing from summaries alone. Dashboards are useful, but the evidence is in the underlying records.

Now test each item against a checklist. For vehicles and trailers, ask:

• Was each inspection completed by the due date?
• Was the interval correct for the stated maintenance schedule?
• Is the inspection sheet complete and legible?
• Are defects categorised clearly?
• Is there evidence of rectification?
• Is there a sign-off showing the vehicle was fit to return to service?
• Were MOT or annual-test bookings made in time?
• If there was a fail, is there a retest and repair trail?

For drivers, ask:

• Was the licence check done when due?
• Were endorsements reviewed and risk assessed?
• Is Driver CPC current?
• Is the DQC in date?
• Are defect reports submitted properly and signed?
• Are tachograph infringements reviewed and followed up?

For tachographs, test both timing and response. A compliant-looking report is not enough if no one reviewed it. The audit should find evidence that infringements were seen, explained where appropriate, and corrected through coaching or disciplinary steps if needed.

Log findings in a consistent format. Each finding should state the asset or driver, the document checked, the date, the issue, the risk and the action required. Avoid vague wording such as "maintenance needs attention". Write the actual failure, for example "Vehicle AB12 CDE had a PMI due on 14 March, completed on 20 March, with no documented reason for extension".

Grade the findings. A missed annual-test date or unroadworthy defect with no rectification evidence is critical. A missing signature on one completed record may be minor, but if it appears across a whole depot it becomes a control issue. Grading helps us decide what must stop a vehicle going out and what can be corrected through process training.

Assign actions to named people with deadlines. A finding without an owner is only a note. The transport manager, workshop controller, fleet administrator or external maintenance provider should each know what they must fix and by when. Recheck the actions after the deadline and record closure.

Finally, keep the audit pack together. If the DVSA visits or the Traffic Commissioner asks how we monitor compliance, the audit report, evidence sample, action log and closure notes should be available in one place. That is one reason many operators move from separate spreadsheets and folders to roadworthiness record software that stands up at audit.

Where fleet audits usually fail

Most failed audits do not fail because no one cared. They fail because evidence is split across inboxes, workshops, paper files and memory.

The most common gap is the incomplete PMI file. The sheet may be present, but one page is missing, the technician has not signed it, the odometer reading is absent, or there is no repair record tied back to defects found. If a prohibition issue later appears, that missing link matters.

Missed MOT or annual-test dates are another regular problem. Operators often have the pass certificate but not the booking trail, or they rely on a wall calendar with no escalation if somebody is on leave. For growing fleets, reminders need to be systematic. We cover that in a guide to choosing a fleet reminder system that keeps tests on time.

Defect reporting is often weaker than managers think. Drivers may report issues verbally, send photos by message, or hand in paper sheets late. The repair may be done, but the chain is broken. An audit should be able to show the report, the decision on roadworthiness, the repair, and the return-to-service sign-off. If any part is missing, the evidence is weak.

Unsigned evidence is another frequent failure point. A checklist with no driver signature, no technician sign-off, or no manager review date can be challenged. In UK operator-licence work, a document is stronger when it shows who did what, when they did it, and who checked it.

Trailer records are often overlooked, especially in mixed operations where trailers move between depots or subcontractors. The audit should confirm inspection intervals, MOT status where applicable, brake testing records and defect rectification in the same way as powered vehicles.

Another failure is not checking exceptions. If a vehicle was VOR for three weeks, the audit should ask why, what work was done, whether the planner was updated, and whether any booked inspection had to be rescheduled. Gaps often hide in exceptions, not routine cases.

Tachograph controls also fail where there is analysis but no management response. A file full of infringement reports is not good evidence if the same driver repeats the same issue for months with no coaching note, no investigation and no escalation.

How often should a fleet audit be done?

There is no single legal interval that suits every operator, but there should be a defined audit frequency based on risk and the obligations on the licence. For some operators, quarterly is appropriate. For others, monthly checks on core controls plus a deeper quarterly or six-monthly review is the safer pattern.

We set frequency by looking at five things.

First, fleet size. A larger fleet creates more deadlines, more drivers and more points of failure. More vehicles generally means shorter review cycles.

Second, risk profile. Passenger fleets, high-mileage operations, night trunking, agency driver use, and trailer-heavy operations all justify closer checking. The same applies where tachograph infringements or roadside encounters are more likely.

Third, change. A new transport manager, a new maintenance provider, a depot move, a workshop restructure, or a new software rollout should all trigger an earlier audit. Change is where controls drift.

Fourth, previous findings. If the last audit found overdue inspections, weak defect reporting or poor closure of repairs, the next audit should be sooner and narrower, to confirm the fix worked.

Fifth, licence exposure. If we have undertakings to report changes, specific maintenance arrangements, or a history that could attract Traffic Commissioner attention, the audit schedule should reflect that.

For very small operators, a full review every quarter may be enough if weekly control checks are disciplined. For larger or more complex businesses, monthly compliance reviews with a formal fleet audit every quarter are often more realistic. What matters is that the interval is documented, followed and adjusted when risk changes.

If your systems are still built around separate calendars and paper files, even a small operation can find that reviews slip. In that case, it helps to use reminder apps that keep a small fleet audit-ready.

What good audit evidence looks like

Good audit evidence is specific, dated, complete and easy to follow. It should let an external reader understand what happened without needing the person who created it to explain.

At document level, good evidence has:

• The correct vehicle, trailer or driver identified
• The date the check or event happened
• The due date, where timing matters
• The name or signature of the person who completed it
• The name or signature of the reviewer, where review is required
• Clear defect descriptions, not vague wording
• A linked repair or follow-up record
• A closure note showing the action was completed

At file level, good evidence shows control. If an inspection interval is six weeks, the planner, the completed PMI, any repairs and the next booking should line up. If a driver has an infringement, the analysis report, the discussion note and any retraining should all be in sequence.

Document control matters more than many operators expect. We should be able to tell which version of a policy was in force at the time, whether a checklist was current, and whether a record was added later. That is easier when the system timestamps actions and stores signed evidence centrally.

Credible audit evidence also shows management review. A transport manager note that says "reviewed weekly defects and overdue items in ISO week 32, chased workshop on trailer T18 brake issue, confirmed vehicle XY23 ABC remains VOR pending parts" is far stronger than a generic statement that "maintenance is monitored".

For businesses integrating compliance data into wider systems, the same standard applies. If records move through a REST API or webhooks into in-house reporting, the source record still needs to be intact, attributable and retrievable. Integration should not weaken the evidence chain. Where operators need that connection, we explain it in how webhooks fit fleet compliance into your own systems.

A final point on UK rules versus the EU generally. Some operators use EU-wide templates or software models. That can be useful, but the audit standard must still match UK operator-licence expectations, DVSA practice and what a Traffic Commissioner would expect to see. Terms, intervals and evidence requirements should reflect the actual UK operating regime, including MOT, annual-test, DVLA checks and the records we would produce through VOL or at a site visit.

At Operator Compliance, built by Fleeta Limited, we shape our records around those practical UK requirements. Whether you run trucks, vans, buses, coaches or mixed assets, the aim of a fleet audit is simple. We should be able to prove that our compliance system works, on time, in writing, with evidence that stands up when it is tested.