Maintenance and Planning
›Maintenance and Planning A maintenance planner is only useful if it matches the live fleet, the inspection intervals
What the audit file needs to demonstrate
The audit file must connect each written policy to live operational records that match the current fleet on the day of audit. Expect to evidence:
- Named policy owners, version numbers and last review dates that fall inside the stated review cycle.
- Vehicle list reconciled against the operator licence margin and any specified vehicles.
- Driver list reconciled against payroll, licence check records and CPC status.
- Walkaround and defect records traceable from report to repair to sign-off, with dates that line up.
- PMI records at the declared inspection interval, with brake performance data and roller brake test printouts retained.
- Collision and near-miss reports with root cause, action owner and closure date.
- Driver infringement letters, follow-up coaching notes and re-training where pattern offences appear.
- Fuel and emissions data captured, trended and reviewed, with reviewer named.
- VRU and Safe Urban Driving training records for drivers operating in urban environments.
| Area | What the auditor will check | Common weakness |
|---|---|---|
| Management | Policy ownership, review cycle, action log, responsible person named on the OL | Policies exist but review dates have lapsed or the named owner has left |
| Vehicles | PMI intervals, walkaround app exports, defect close-out, safety equipment fitted to spec, tyre and brake records | Vehicle list out of date; PMI interval declared on the licence not matching what is actually carried out |
| Drivers | Licence check frequency, CPC, induction, toolbox talks, infringement follow-up, SUD/VRU training | Training matrix not reconciled against payroll; agency drivers missing |
| Operations | Routing, sub-contractor control, work-related road risk assessment, load and overhang checks | Sub-contracted work not evidenced to the same standard as own fleet |
| Improvement | KPIs for collisions, fuel, emissions, infringements, with trended review notes | Data collected but not reviewed, or reviewed without recorded action |
Common weaknesses found in mock audits
Most findings are ordinary record gaps rather than systemic failure. Recurring examples include:
- A driver moved onto urban work without the corresponding VRU briefing recorded.
- Collision reviews completed but without a named action owner and closure date.
- Training spreadsheets that do not reconcile to the payroll list on the same date.
- Defect reporting that cannot be traced from the driver’s report to the workshop job card to the sign-off.
- Policies updated centrally but the local depot still operating from the previous version.
- Fuel data downloaded monthly but no recorded review or action.
Verify the current published FORS Standard before preparing the file. Where evidence is held digitally, retain dated exports or screenshots. Auditors will accept system access on the day, but the audit file itself should still stand alone. Avoid rewriting policies during audit week unless the operational process has genuinely changed; an auditor will spot a policy dated three days before the visit.
Pre-audit evidence check
A useful mock audit produces a short, prioritised action list rather than a long report. Typical output:
- Evidence that is ready and reconciled.
- Evidence that exists but does not match the live fleet or workforce.
- Evidence that is missing and must be created before audit day.
- Findings that would be classed as major nonconformities, and findings that would be minor.
- A close-out plan with named owners and dates inside the 28-day window FORS allows for corrective action.
The objective is to align evidence with how the fleet actually operates, not to generate additional paperwork that no one will maintain after the audit.
Adviser insight
“The pattern I see most often is good intent and weak reconciliation. The policies are written, the training has happened and the inspections are done, but the lists do not agree with each other on the day. A mock audit forces those reconciliations: payroll against training matrix, vehicle list against PMI schedule, walkaround reports against defect close-outs. Once those three match, most of the audit is already passed.”
Ian Eltham, transport compliance adviser
How FORS evidence supports operator licence compliance
FORS is voluntary, but the evidence base overlaps heavily with the undertakings given on the operator licence. Driver hours management, vehicle maintenance, defect reporting and roadworthiness records all feed both. Where a mock audit identifies a gap in PMI traceability or driver infringement follow-up, that gap is also a Traffic Commissioner risk. Treat the two systems as one record set with two audiences rather than two parallel files.
FAQs
When should a FORS mock audit be conducted?
About six to eight weeks before submission or renewal. That window gives time to close minor findings, redo any training gaps and reconcile lists, without the cost of an emergency fix the week before audit.
What official guidance applies?
The current published FORS Standard for the level you are auditing against, whether Bronze, Silver or Gold, read alongside GOV.UK operator licensing guidance, DVSA Guide to Maintaining Roadworthiness and the Senior Traffic Commissioner’s Statutory Documents.
What evidence is most critical?
Anything that reconciles a list to a live record: vehicles to PMI schedule, drivers to training matrix, defects to repair sign-off, collisions to closed actions. These reconciliations are where most audit findings sit.
What are common risks?
Relying on generic templates, copied policies or certificates that have expired. The auditor will sample, and the sample will usually find the weakest record rather than the strongest.
Where should operators exercise caution?
Do not treat FORS evidence as separate from operator licence evidence. If a record is weak enough to fail a FORS audit, it is usually weak enough to attract DVSA or Traffic Commissioner attention. Close the gap once, in the place where the fleet actually runs.
Support
Operator Licence Ltd can help review the evidence file, identify the reconciliation gaps and connect you with the right specialist support for FORS mock audit preparation and operator licence compliance. Read alongside current GOV.UK, DVSA and Traffic Commissioner guidance for full regulatory context.
Reviewed by the OperatorLicence.co.uk compliance team.
