OCRS Improvement Checklist

OCRS improvement starts with evidence, not slogans

When an operator asks how to improve OCRS, the useful answer is rarely a generic speech about compliance culture. The Operator Compliance Risk Score moves when the business identifies what generated enforcement attention, fixes the operational cause, and produces evidence the fixes are real. That means understanding the enforcement history, the maintenance and defect position, drivers' hours behaviour, tachograph follow-up quality, record keeping discipline and how far the transport manager and senior team actually control the fleet day to day.

Operators often want recovery to be fast. The regulator's concern is whether the pattern that caused the score deterioration is still present. A recovery checklist therefore has to examine pressure points honestly. If there have been prohibitions, poor brake performance, inconsistent walkaround checks, weak tachograph management or recurring paperwork failures, those need to be treated as operational failures requiring proof-based correction, not paper exercises.

It is also worth understanding that OCRS contains a built-in lag. Events stay on the score for three years on a sliding weight, with the most recent twelve months carrying the heaviest influence. A clean three months does not erase a bad year. Improvement programmes need to be planned over twelve to twenty-four months of consistent behaviour, with the first measurable score movement usually appearing one to two quarters after the underlying behaviour changes.

1. Establish the enforcement picture clearly

The first stage is to understand what is already known. Has the operator experienced roadside stops, fixed penalties, prohibitions, MOT first-time failure issues, drivers' hours infringements, graduated fixed penalties or traffic office attention? If so, the pattern matters more than any single event. Document each incident with date, vehicle registration, driver, location, encounter type and outcome. Classify each as roadworthiness or traffic, because the OCRS bands are scored separately and need separate corrective action.

This stage often shows whether the business has been too reactive. If the only record of an event is the original prohibition notice or a manager's recollection, that itself points to weak internal control. The operator should be building its own incident picture rather than waiting for DVSA encounters to define it.

2. Review maintenance planning and roadworthiness controls

Most roadworthiness OCRS problems trace back to maintenance evidence. That does not always mean the fleet is badly maintained. The real issue is often poor control of planning, defects and records. Examine:

Preventative Maintenance Inspection intervals set against the licence undertaking, and actual completion against plan.
PMI sheets for genuine brake test results, including laden roller brake tests with print-outs, not "brakes ok".
Repair sign-off dates, parts records and the gap between defect identification and rectification.
MOT first-time pass rate over the last twelve months and reasons for any failures.
Tyre, lighting and load security trends across the fleet.

If the operator uses a third-party maintenance provider, the contract, monthly KPI returns and the operator's own scrutiny of those returns all need to be visible. The licence holder carries the compliance duty, not the workshop.

Roadworthiness recovery also needs a management layer. Someone has to review defect trends, repeated repair categories, missed inspection dates and workshop communication. Without that review, the fleet drifts back into the same pattern after the initial clean-up.

3. Test driver defect reporting and drivers' hours controls

OCRS deterioration is often driven by driver behaviour as much as by vehicles. Daily walkaround checks, defect capture, defect escalation and rectification of reported faults all need scrutiny. If defect forms repeat identical "nil defect" entries day after day across multiple drivers, if reported faults cannot be traced through to repair, or if drivers are clearly under time pressure at start-of-shift, the operator has a governance problem the OCRS will eventually reflect.

The same principle applies to drivers' hours and tachograph analysis. Look beyond the headline report and ask:

Are infringements followed by a documented driver discussion, signed by both parties?
Are repeat infringements escalated through a written disciplinary route?
Are missing mileage, manual entries and other-work codes investigated rather than accepted?
Are infringement trends reviewed at depot and driver level, not just system-wide?
Are working time records held separately and reconciled?

In practice, OCRS recovery fails when these systems are treated separately. A business may tidy maintenance records but ignore poor walkaround discipline, or focus on drivers' hours while leaving defect reporting weak. The regulator looks at whether the whole system works together.

4. Review management control and transport manager oversight

If OCRS has worsened, oversight must be examined directly. Who reviews compliance reports, how often, and what evidence exists of that review? When an issue repeats, what happens? Is the transport manager close enough to the operation, with enough hours and authority, to intervene properly? Has senior management protected the time, budget and headcount needed for the intervention to hold?

The checklist should identify meeting routines, reporting packs, escalation thresholds and named responsibilities. It should also test whether the business can tell a before-and-after story: what failed, who owned it, what changed, when, and how the operator now knows the change is holding. A monthly compliance meeting with minutes and actions is the minimum a Traffic Commissioner expects to see in a recovery file.

"When I review an OCRS recovery file, the first thing I check is whether the operator can show me the moment they noticed the problem themselves, before DVSA did. If every corrective action is dated after a prohibition, that tells the Traffic Commissioner the controls only react. If the operator can show internal exception reports, driver coaching notes and management minutes that pre-date the enforcement, the case for continued good repute looks very different."

Liam Gafoor CMILT IOSH, senior compliance adviser

5. Build a defensible improvement file

Recovery is easier to evidence when the operator builds a structured file. Include:

An incident log with classification, roadworthiness or traffic, and root cause.
PMI completion data, brake test prints and MOT outcomes for the last twelve months.
Defect reporting samples showing both genuine and nil defect entries.
Tachograph infringement reports with closed-out driver discussions.
Driver coaching, induction and refresher training records.
Workshop process changes and contract review notes.
Management review minutes showing exceptions discussed and actions tracked.

The point is not a paper mountain. It is a defensible record that the operator identified the root causes and put proper controls in place. If a DVSA follow-up visit, customer audit or public inquiry question arrives, that file becomes the backbone of the explanation.

6. Sustain improvement with a real review cycle

OCRS should be treated as an indicator of operational control, not a score to manipulate. Sustainable improvement comes from repeatable behaviour set against a clear cadence:

Weekly: defect reports, tachograph infringements, walkaround sampling.
Monthly: PMI completion, brake test sampling, MOT performance, compliance meeting with minutes.
Quarterly: trend review of all the above, transport manager report to senior management, refreshed risk register.
Annually: independent audit and licence undertaking review.

If the operator can hold that cadence for twelve months, the OCRS score will follow.

Build a clear incident and enforcement picture, split by roadworthiness and traffic.
Review PMI planning, completion, brake evidence and MOT outcomes over twelve months.
Test defect reporting quality, nil-defect patterns and rectification trails.
Check drivers' hours analysis, infringement follow-up and repeat-offender management.
Examine transport manager hours, authority and senior management support.
Create an evidence file showing what failed, what changed and when.
Set weekly, monthly, quarterly and annual review points and hold them.

How to work through the 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 customer auditor. Where evidence is missing, record who owns the action, when it will be completed and what proof will be kept afterwards. Expect the OCRS score itself to lag behind the operational fixes by one to two quarters.

What good evidence for the operator's licence record looks like

Records are current and 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 individual.
Repeated defects, infringements or missing records carry management review evidence.
The file can be explained without relying on memory or informal messages.

Official guidance used: this checklist gives general guidance for operators and should be read alongside current GOV.UK guidance, DVSA guidance, Senior Traffic Commissioner statutory documents and the conditions or undertakings on the operator's licence. It is not legal advice.

Where Operator Licence Ltd fits in

Operator Licence Ltd can help review this evidence, identify the gaps and connect you with the right specialist support for OCRS recovery, transport manager oversight and pre-public-inquiry preparation. If the score has already drawn DVSA attention, that review should happen before the next encounter, not after it.