Obtaining a Goods Vehicle Operator Licence — whether Standard National, Standard International, or Restricted — requires demonstrating to the Traffic Commissioner that your organisation has the systems and competence to maintain vehicles in a roadworthy condition throughout their operational life. What many operators underestimate is that the Traffic Commissioner's scrutiny does not stop at licence grant. The ongoing maintenance record-keeping obligation is as much a compliance requirement as the original application undertakings.
This article covers what your R&M records need to demonstrate, how the Traffic Commissioner assesses those records when they investigate or call you to a public inquiry, and how per-vehicle record-keeping relates to the Fleet Operator Recognition Scheme (FORS) standards.
The statutory basis for maintenance record-keeping
The Goods Vehicles (Licensing of Operators) Act 1995 and the operator licensing statutory guidance published by the Office of the Traffic Commissioner set out the expectation clearly: operators must establish and maintain a system for keeping vehicles fit and serviceable, and must be able to produce records of that system's operation on request from an enforcement officer or the Traffic Commissioner.
In practice, "records" means documentation of safety inspections at appropriate intervals, repairs carried out and when, brake tests, tyre checks, and driver defect report resolution. The Senior Traffic Commissioner's statutory guidance (updated periodically; operators should check the current version on the .gov.uk site) specifies that inspection intervals should be no greater than 13 weeks for standard vehicles, and may need to be more frequent for heavily used or older vehicles.
The critical word in that guidance is "appropriate." A vehicle covering 80,000 miles per year and returning from every shift with minor defect reports should demonstrably be on a tighter inspection regime than one covering 20,000 miles per year on light duties. If a Traffic Commissioner reviews your records and finds that a high-utilisation vehicle was on the same 13-week cycle as a low-utilisation vehicle in your fleet, they will question whether your systems are genuinely fitness-for-purpose or merely procedurally compliant.
What the Traffic Commissioner actually looks at
When the DVSA carries out a maintenance investigation — either through a targeted operator check or following a serious incident — the investigator will typically request a sample of maintenance records covering a defined period, usually 12–15 months. The check focuses on several specific areas:
- Inspection intervals vs. undertakings: Does the interval between consecutive safety inspections match what you stated on your operator licence application? A licence granted on the basis of 10-week intervals must show 10-week intervals, or a documented reason for variance.
- Defect report closure: Are driver-reported defects recorded, actioned, and signed off? An unsigned or unclosed defect report for a safety-critical item is a serious finding.
- Brake test records: Roller brake test results, with the date and vehicle mileage at time of test, are expected at each annual test and at safety inspections. Results below the prescribed efficiency minima with no follow-up repair record are a red flag.
- Tyre records: Tyre condition checks at inspection intervals, with replacement records linked to the specific VRM and axle position.
- Record continuity per vehicle: Can you produce an unbroken maintenance history for each vehicle in your authorised fleet? Gaps — vehicles that were operating but for which no inspection records exist during a period — are a significant finding.
The per-vehicle requirement is the one that trips operators most frequently. If your maintenance records are held by a third-party workshop and organised by date of job rather than by vehicle registration mark, producing a continuous per-VRM history on request requires manual assembly. Operators who have been through a public inquiry describe the process of retrospectively compiling vehicle histories from a workshop's date-ordered filing as extremely time-consuming and error-prone. The time to build per-VRM records is before an investigation, not during one.
FORS Bronze, Silver, and Gold: the maintenance dimension
The Fleet Operator Recognition Scheme (FORS), administered by AECOM on behalf of Transport for London and used as a procurement requirement by a growing number of local authorities, construction schemes, and public sector contracts, has its own maintenance and vehicle standards that sit alongside the operator licence obligations.
At FORS Bronze level — the baseline accreditation — operators must demonstrate compliance with operator licence requirements, which means the per-VRM maintenance records described above. Bronze does not add significantly to the statutory baseline, but it does require documentary evidence that compliance systems are in place, including vehicle inspection record formats and defect reporting procedures. Bronze assessors will check a sample of records.
FORS Silver introduces additional requirements around driver licence checks, cycle safety awareness training, and vehicle specifications for work in certain urban environments. On the maintenance side, Silver requires evidence of a formal preventive maintenance schedule — not just reactive repairs — with scheduled dates planned ahead rather than set ad hoc. This is where per-vehicle scheduling, tied to individual vehicle mileage and age rather than a blanket fleet calendar, becomes necessary rather than best practice.
FORS Gold extends further into environmental performance metrics, fuel consumption monitoring, and evidence of continuous improvement in fleet efficiency. At Gold level, your maintenance data needs to feed into a demonstrable improvement narrative — showing trends in defect rates, brake efficiency, and tyre replacement frequency over time. That narrative is only possible if your per-VRM records are structured enough to produce trend data, rather than being a pile of invoices organised by supplier or date.
Per-vehicle records versus fleet-average records: the compliance gap
We're not saying fleet-level reporting is without value — an aggregate view of R&M spend, total safety inspections completed, and defect closure rates is a useful operational dashboard. The compliance problem arises when the fleet-level view is the only view, and individual vehicle histories cannot be reconstructed without manual effort.
A 180-vehicle fleet operating under a Standard National licence, with vehicles spread across three depots and maintained by a mix of in-house and contracted workshops, is a realistic scenario where per-VRM record continuity is genuinely difficult to maintain without deliberate system design. Workshop jobs get recorded against the job number, not the VRM. Defect reports are filed by date and shift, not by vehicle. Tyre records sit in a spreadsheet owned by the workshop manager at one depot that is not shared with the compliance manager at head office.
When the DVSA requests the maintenance history for a specific vehicle following a roadside prohibition notice — which is how many investigations begin — the operator who can retrieve a complete per-VRM timeline within hours is demonstrating a functioning system. The operator who has to spend two days manually reconstructing the history from multiple sources is demonstrating a system that technically produced the right outcomes but has no structural integrity. The Traffic Commissioner will draw their own conclusions about whether that system constitutes adequate management oversight.
Practical steps toward compliant per-VRM record-keeping
The goal is not a perfect system from day one — it is a systematic improvement that can be demonstrated over time. Key steps for operators who know their current record-keeping has gaps:
- Audit your current record structure: can you retrieve the last five safety inspection records for any vehicle in your fleet within 20 minutes?
- Ensure your workshop management system, whether in-house or third-party, records jobs against VRM as a mandatory field, not as a free-text note.
- Set up a per-VRM maintenance schedule that is mileage-triggered, not calendar-triggered — and review it when vehicles change route profile or utilisation level significantly.
- Establish a single source of truth for each VRM's maintenance history, even if the work is done across multiple sites. The per-VRM record is your licence compliance document; it should not be distributed across four separate systems without aggregation.
The DVSA Guide to Maintaining Roadworthiness is publicly available and should be the baseline reference for any operator building or reviewing a maintenance system. The Traffic Commissioner's Senior Traffic Commissioner's Statutory Guidance and Statutory Directions are similarly public documents and set out exactly what "adequate arrangements for maintenance" means in a regulatory context. Reading them alongside your current maintenance records is a useful gap analysis exercise that requires no external assistance.
Record-keeping that can withstand scrutiny is not a different set of records from the ones you need to run the fleet well. It is the same records, organised per vehicle, updated in near-real time, and retrievable without a manual reconstruction exercise. That is both the compliance requirement and the operational best practice — which is why the operators who get this right tend to find the Traffic Commissioner investigation, if it ever comes, is a straightforward conversation rather than a crisis.