The two most common results of a DVSA fleet audit are operators who pass comfortably and operators who discover that the records they believed existed do not, in the form an auditor will accept, actually exist. Maintenance schedules that are not documented, walkaround check records that show no defects for three months, brake tests that were carried out but not recorded in the file, driver licence checks that happened verbally but have no written evidence. The audit does not find compliance failures the operator did not know about — it finds compliance gaps the operator assumed were covered. Preparation is the process of finding those gaps before the auditor does.
Understanding what type of audit is coming determines how to prepare. Not all audits operate on the same basis or look at the same documents:
DVSA auditors sample maintenance records across a period that typically covers a minimum of four PMI cycles for the vehicles included in the sample. For most fleets using 6-week inspection intervals, this means records from the previous 6 months. However, DVSA guidance specifies that records should be retained for at least 15 months, and auditors may sample across a longer period if they identify concerns. Preparing for audit means organising 15 months of records in a form that can be presented quickly, not hunting for documents in folders on the day.
The document set that must be ready for a DVSA or Traffic Commissioner audit includes:
A FORS audit is announced in advance and conducted against a published standard. The advantage over a DVSA inspection is that the auditor’s checklist is known — the FORS standard document specifies exactly what is being assessed at each level. Preparation for a FORS Silver audit should start with the published FORS v7 standard and work through each requirement, documenting the evidence that will be presented for each one.
The areas where FORS Silver audits most commonly find gaps:
For fleets preparing for a FORS audit or a Traffic Commissioner audit, the operational status of camera and sensor systems is a specific evidential requirement. An auditor who asks whether proximity sensors are operational and is shown a walk test record — signed by the fleet manager, dated, confirming each sensor was tested and generated an appropriate alert — has what they need. An auditor who receives a verbal assurance that the sensors are working does not.
Walk tests should be documented on a consistent template: vehicle registration, date of test, each camera and sensor position tested, result (operative/inoperative), and the signature of the person conducting the test. Any system found inoperative should have a corresponding defect record and evidence of repair before the vehicle returned to service. A walk test record that shows no failures over six months is a yellow flag in the same way that a walkaround check record showing no driver-reported defects is — occasional failures and repairs demonstrate that the process is real.
Running a self-audit against the relevant standard one to two weeks before an expected DVSA inspection or a scheduled FORS audit is the most effective preparation tool available. The self-audit does not need to be conducted by an external consultant — a systematic check against the DVSA’s published audit criteria or the FORS standard checklist, conducted by the transport manager, will surface the same gaps that an external auditor will find.
A mock audit approach that comes up consistently among well-prepared fleet operators: pull the vehicle record for three or four vehicles at random and reconstruct the maintenance history from records. If the records cannot produce a complete, coherent picture of what inspections took place, when, by whom, and what defects were found and rectified, the file has a gap that an auditor will find. The same exercise applied to three or four driver records — licence, CPC, tachograph analysis — surfaces driver compliance gaps before they appear in an audit report.
A DVSA fleet inspection that identifies serious or persistent compliance failures will be referred to the Traffic Commissioner. The operator receives a call-up letter specifying the concerns identified. The outcome of a public inquiry depends on the severity of the failures and the evidence of remedial action taken between the inspection and the hearing. Operators who can demonstrate that the failures identified in the inspection have been addressed, and that the systems causing them have been corrected, are in a significantly better position than operators who present no evidence of action.
A failed FORS audit results in loss of accreditation at the relevant level. For operators who rely on FORS Silver to access CLOCS-adopting construction sites or meet contract requirements, this has immediate commercial consequences. FORS offers a re-audit pathway but there is a waiting period. Preparing adequately for the initial audit is materially cheaper than managing the consequences of a failed one.
DVSA guidance requires that records are retained for at least 15 months. The sampling for an audit typically covers four consecutive PMI cycles for the vehicles included in the sample — for most operators, that is the previous 6 months at 6-week intervals. However, if the auditor identifies a concern in recent records, they may look further back. Records that are complete, organised, and easily retrievable for the full 15-month period are a better audit position than records that are complete for recent periods but patchy before that.
Yes. A DVSA fleet inspection targeting the operating centre can be unannounced — it is triggered by OCRS data or enforcement intelligence, not by a scheduled review. This is a significant difference from the FORS audit, which is booked in advance. The operational implication is that records must be maintained and accessible at all times, not organised specifically for an expected audit. A fleet whose records are in good order continuously will find an unannounced inspection no more stressful than a scheduled one.
The FORS auditor will assess whether the required camera and sensor equipment is fitted and operational. They may ask to see the vehicle, observe whether cameras are displaying on in-cab screens, and check that proximity sensors generate alerts when an obstacle is placed in the detection zone. Walk test records documenting that the fleet manager has periodically verified the operational status of all systems are supporting evidence. A system that is fitted but generates no alert because the driver has adjusted the sensitivity or disabled the buzzer will not pass the operational assessment.
DVSA Earned Recognition is worth considering for operators who already maintain a high compliance standard and want to formalise this through a recognised audit. It provides exemptions from some DVSA roadside scrutiny and serves as a credible compliance signal to clients and insurers. The audit standard is higher than the standard fleet inspection, so operators who are not confident in their current compliance level should focus on achieving standard compliance before pursuing Earned Recognition.
Vehicle safety equipment not being demonstrably operational is the most common single failure point. The camera and proximity sensor requirements at FORS Silver are specific: the equipment must be fitted, operational, and generating appropriate alerts. If a sensor has been disabled by a driver, a camera lens is obscured, or the MOIS system is not functioning, the vehicle fails the equipment assessment. Walk test records demonstrating that the fleet manager has been verifying operational status are the most reliable protection against this failure.
A printable checklist covering the six areas an auditor will examine: documents, camera and sensor walk tests, driver records, FORS Silver v7 requirements, DVSA Earned Recognition, and mock audit steps.
Tell us what vehicles you run and what you need — we will come back with a recommendation and a price. Prefer to talk? Call 01656 721871.
Related guides: How Safety Systems Reduce Claim Payouts · The Legal Benefits of In-Vehicle Evidence Recording
4 August 2026