Maintenance audits expose the gap between paperwork and control
A maintenance audit is not a check that the files exist. Its purpose is to test whether roadworthiness control is real, repeatable and visible to someone outside the business. Operators routinely hold inspection sheets, workshop invoices and a planner on the wall and still fail audit because the system behind those documents does not hold together. Common findings include PMIs drifting from the planned interval, defects recorded but never closed, brake evidence that is patchy across the fleet, and managers who cannot describe what they review or when they last challenged the workshop.
A useful checklist cuts through that ambiguity. It asks not only what records exist, but whether those records prove planning, completion, escalation and review. For an operator preparing for a public inquiry, a customer audit, a licence variation or a sale of the business, that distinction is the audit. A file that looks busy can still be a weak system if the entries do not connect logically from planner to PMI to defect log to repair sheet to management review.
1. Test planned maintenance inspection control
Start with the maintenance planner. The operator should be able to show the inspection frequency in writing, explain why that interval suits the fleet, mileage and operation, and produce the completed inspections in the order the planner predicted. Where PMIs are late, brought forward without a recorded reason or simply missing, the audit must record that directly and identify whether the business noticed before the auditor did. An operator who only finds missed PMIs when someone external looks has a management problem as well as a maintenance problem.
Compare the planner with the fleet list, the completed PMI sheets and the vehicle availability pattern. If the workshop is overloaded at quarter end, if specific units repeatedly drift, or if the interval was set when the fleet was smaller and never reviewed, write that finding into the audit. These are usually the root cause of the wider issues that follow.
2. Test the quality of inspection and repair evidence
Completing an inspection sheet is not the same as managing vehicle condition. Check whether inspections are thorough, defects are categorised sensibly and repairs are described with enough clarity that someone reading the file in two years would understand what was done and why. If a unit keeps presenting the same fault, the file should show that the pattern was noticed and the root cause investigated. Vague repair descriptions, missing sign-off, inconsistent dates and weak linkage between the PMI finding and the workshop action all reduce confidence in the system.
Test how safety-critical defects are handled. If a vehicle is identified with a serious fault, the file should show the unit was taken off the road, the repair completed, the work verified, and the return-to-service decision signed by a named person. A maintenance audit that cannot answer those four points is incomplete.
Andrew Logan, transport compliance adviser: When I review a maintenance file, I look first at the link between the PMI sheet, the defect log and the workshop invoice. If those three do not tell the same story for the same vehicle on the same date, the file will not survive scrutiny, no matter how tidy it looks.
3. Review brake performance and roadworthiness evidence
Brake evidence is one of the first records DVSA examiners and Traffic Commissioners look at. The checklist should test whether the operator holds roller brake test evidence at the right frequency, laden or simulated laden results where the vehicle profile makes unladen testing meaningless, and a sensible relationship between brake testing and the PMI programme. If brake performance is not being evidenced regularly and in a structured format, write that finding plainly rather than assume the maintenance provider is taking care of it.
Pull annual test history, rectification records, OCRS data, any roadside encounters and DVSA findings into the same view. Strong audit work joins those threads together. Weak audit work reads each record type in isolation and misses the fleet-wide pattern that an examiner will see immediately.
4. Examine daily defect reporting and close-out
A workshop can look strong and the operation can still fail because driver defect reporting is weak. Review how walkaround checks are completed, whether defects are described in usable wording, how nil defects are recorded, how urgent issues are escalated within the same shift, and how repairs are linked back to the original report. Defect logs full of vague entries, long quiet periods or no evidence of rectification point to a discipline issue that no PMI file will correct.
Confirm that management actually reads defect trends. The purpose of driver defect reporting is to give the operator early warning of vehicle condition and operational risk. If no one is reviewing the data, the system exists on paper only.
5. Test VOR decisions and return-to-service control
Many audits skip this section, and it is often where weak control hides. Ask how a vehicle is placed VOR, who has authority to make that decision, how the unit is physically prevented from being used, and how the return-to-service is recorded. Cross-check the VOR log against the defect log, the workshop diary and the driver allocation sheet for the same period. If a vehicle was reported with a safety-critical defect at 06:00 and shows a tachograph trace at 09:00 without a documented repair, that is an audit finding that needs an answer.
6. Test maintenance provider control and Transport Manager oversight
Where the work is contracted out, the operator still owns the duty. Test whether someone monitors provider performance, checks inspection quality, chases overdue items and questions recurring defects. The Transport Manager and the senior management team should be able to describe what reports they see, what triggers an exception, what they do with it and where their review is recorded. A Transport Manager who cannot show evidence of monthly maintenance review is exposed at public inquiry, even if the workshop paperwork itself is acceptable.
This is where the audit becomes useful as governance evidence. It shows whether the operator is governing the provider or simply trusting that the provider is governing the duty for them.
7. Turn audit findings into a maintenance control plan
Finish with a written action list. That may mean resetting PMI intervals, rewriting the defect reporting standard, improving repair descriptions, adding laden brake testing, formalising the monthly maintenance review, or renegotiating the contract with the maintenance provider. Each action needs a named owner, a target date and a description of the evidence that will prove it has been closed. The best audits convert findings into a control plan that can be re-tested in 90 days. That makes the audit defensible if the operator later has to show a Traffic Commissioner that weaknesses were identified and resolved, not ignored.
Operator licence maintenance audit checklist at a glance
- PMI frequencies set in writing, justified by use, and completed on the planned dates.
- Inspection sheets, defect logs and workshop invoices tell the same story for the same vehicle.
- Brake performance evidenced regularly, laden where the vehicle profile requires it.
- Safety-critical defects show a controlled VOR, a verified repair and a named return-to-service.
- Driver walkaround records show usable detail, escalation, close-out and trend review.
- Transport Manager monthly maintenance review recorded with date, attendees and actions.
- External maintenance provider performance monitored against agreed standards, not assumed.
- Findings turned into a dated action plan with owners and re-test points.
How to work through this checklist
Work through the records in date order and mark any gap that would be difficult to explain to DVSA, the Office of the Traffic Commissioner, an auditor or a client. Where evidence is missing, record who owns the action, when it will be closed and what proof will be kept afterwards. A finding without an owner and a date is not closed.
What good evidence for the operator's licence record looks like
- Records are current and held in the correct legal entity name on the licence.
- Dates, vehicle registrations, driver names and operating centres match the licence record.
- Corrective action is recorded, assigned and closed by a named person.
- Repeated defects, infringements or missing records show management review evidence.
- The file can be explained to an outsider without relying on memory or informal messages.
Official guidance used: this checklist provides general guidance for operators and should be read alongside current GOV.UK guidance, DVSA's Guide to Maintaining Roadworthiness, Senior Traffic Commissioner statutory guidance and the specific conditions or undertakings on the operator's licence. It is not legal advice.
Where Operator Licence Ltd can help
Operator Licence Ltd can help review this evidence, identify the gaps and connect you with the right specialist support for a maintenance audit, including independent PMI sampling, brake performance review, defect reporting redesign and Transport Manager oversight evidence ready for DVSA, customer or Traffic Commissioner scrutiny.
