OCRS Improvement Checklist

OCRS improvement starts with evidence

An OCRS Improvement Checklist should start with the cause of enforcement attention, not with a general promise to “improve compliance”. DVSA’s Operator Compliance Risk Score is used as a risk indicator from enforcement and test history. Operators cannot talk a poor pattern away; they need to show what happened, what changed and how the new controls are being checked.

This checklist is for goods vehicle operators dealing with roadside stops, prohibitions, annual test failures, maintenance record weaknesses, drivers’ hours infringements or weak defect reporting. It helps turn a poor OCRS position into a practical recovery file that a director, Transport Manager, DVSA examiner or Traffic Commissioner can follow.

1. Establish the enforcement picture

Begin with a dated summary of the events that affected the score. Include roadside encounters, fixed penalties, prohibitions, delayed or failed annual tests, tachograph issues and any DVSA or Office of the Traffic Commissioner correspondence. The pattern matters more than one isolated incident.

Classify each event by root area: vehicle condition, maintenance planning, driver behaviour, tachograph control, paperwork, operating centre control or management oversight. If the operator only has a prohibition notice and a manager’s memory of the incident, that is already a warning sign. A well-run transport operation should be able to build its own incident picture without waiting for enforcement to define the problem.

2. Check the roadworthiness controls

Many OCRS problems have a maintenance trail behind them. That does not always mean the fleet is unsafe, but it often means the operator cannot prove control. Review PMI intervals, completion dates, repair timeliness, brake test evidence, annual test outcomes, defect close-out and workshop communication.

Where a third-party maintenance provider is used, the operator still needs evidence that the work is reviewed. The maintenance contractor does not carry the operator licence duty. Good records should show that someone checks late inspections, repeat defects, brake performance trends and unresolved repairs before the same weakness appears at the roadside.

3. Test driver reporting and tachograph management

OCRS recovery often fails when vehicle maintenance and driver controls are treated as separate projects. Poor walkaround checks can produce the same roadside risk as a weak workshop process. Review whether drivers report defects accurately, whether nil defects look realistic and whether reported faults are traceable through to repair.

For drivers’ hours and tachographs, go beyond downloading data. Check whether infringements are reviewed, whether repeat patterns are challenged, whether agency drivers are controlled and whether the Transport Manager can show intervention. Software reports alone are not enough if nobody acts on them.

4. Review Transport Manager and director oversight

An OCRS improvement plan needs named accountability. Who reviews exception reports? How often are defects, infringements and PMI performance discussed? What triggers escalation to a director? Does the Transport Manager have authority to stop a vehicle, challenge a driver or require action from a workshop?

A common anonymised pattern is an operator that fixes the vehicle after a prohibition but never investigates why the defect reached the road. Three months later, the same defect category appears again. The missing step is usually management review: no trend check, no driver briefing, no workshop challenge and no date for follow-up.

5. Build a defensible improvement file

The recovery file should be concise but complete. Include the incident summary, root-cause notes, maintenance review, driver actions, tachograph interventions, workshop changes, Transport Manager review notes and director sign-off. The file should show a before-and-after position: what failed, what changed, who checked it and how the operator knows the improvement is holding.

Recent issues can still be handled credibly if the response is organised and evidence-led. A thin improvement plan with no dates, owners or follow-up checks will carry little weight. A practical plan with clear actions, review dates and supporting records is much easier to defend if DVSA follows up or the Traffic Commissioner asks for an explanation.

6. Sustain improvement rather than chasing the score

OCRS should be treated as an indicator of operational control, not a score to manipulate. The aim is safer, better-managed operation: reliable PMIs, better defect discipline, cleaner tachograph intervention, stronger Transport Manager oversight and regular reporting to decision-makers.

Read this checklist alongside DVSA’s current Operator Compliance Risk Score guidance. Official guidance explains how OCRS works; this page focuses on the practical evidence an operator should build after problems have appeared.

Practical OCRS recovery checklist

• Build a dated enforcement and incident summary.
• Separate vehicle, driver, tachograph, paperwork and management causes.
• Review PMIs, repairs, brake testing and annual test outcomes.
• Test daily defect reporting and repair close-out.
• Check tachograph analysis, driver debriefs and repeat infringements.
• Confirm Transport Manager authority and director oversight.
• Create a recovery file with actions, owners, dates and follow-up evidence.