Vehicle off-road (VOR) tracking: why a defect log is only half the job

A defect being logged and a vehicle actually being taken off the road aren't automatically the same event, even though it's tempting to assume one implies the other. A daily vehicle check that correctly identifies a serious defect only protects the fleet if that finding reliably translates into the vehicle actually being stood down — vehicle off-road, or VOR, status — until the defect is fixed, rather than the vehicle quietly continuing to run because nobody formally decided to stop it.

Where the gap between logging and stopping actually happens

In a fleet without a clear, enforced process, a defect can sit logged in a book or a system while the vehicle carries on being dispatched, because taking a vehicle off the road has an immediate operational cost — a missed job, a route that needs covering some other way — that a written log entry doesn't force anyone to actually confront in the moment. The defect is technically recorded, which can create a false sense that the compliance obligation has been met, when the more important obligation — not running an unroadworthy vehicle — hasn't been.

What a genuine VOR process needs

A working VOR process needs a clear, low-ambiguity trigger for what counts as serious enough to stand a vehicle down immediately versus what can be scheduled for repair without taking the vehicle out of service straight away, and it needs that decision to sit with someone who isn't also under pressure to keep the vehicle running that day. Where the same person who decides whether a vehicle is fit to run is also the one who feels the operational pain of it not running, there's a structural conflict worth being honest about, even if it doesn't play out badly every time.

Tracking VOR status across a fleet, not just per vehicle

Beyond the individual decision for a single vehicle, it's worth tracking VOR status as a fleet-wide figure over time — how many vehicles are off the road at a given point, for how long on average, and whether that's trending up in a way that might point to an underlying maintenance capacity problem rather than just normal variation. This is exactly the kind of figure worth including among the KPIs a fleet actually tracks, because a rising VOR rate is often an early signal of a maintenance system falling behind before it shows up anywhere else.

VOR and the safety inspection schedule

A vehicle returning from VOR status needs to genuinely re-enter the fleet's normal schedule, not just be put back on the road with the assumption that whatever fixed the defect also covers everything else due for attention. Where a VOR period runs close to a scheduled safety inspection, it's worth confirming explicitly whether the inspection still needs to happen on its original date or whether the repair work effectively covered it — an assumption either way, made without checking, is exactly the kind of gap a maintenance investigation is likely to find.

Recording VOR decisions properly

As with most of this, the decision itself matters less to an investigator than whether there's a clear, dated record of it — when the vehicle was taken off the road, why, who decided, what was done to fix it, and when and by whom it was returned to service. A fleet that can produce this history cleanly for any vehicle, on request, is demonstrating exactly the kind of process DVSA is looking for; one that can only offer a general assurance that defects 'get dealt with' is asking an examiner to take a lot on trust.

VOR and finding cover for the affected work

Standing a vehicle down is the right compliance decision, but it doesn't make the operational problem it creates disappear — a route or job still needs covering, often at short notice. Fleets that treat VOR purely as a maintenance record-keeping exercise, without also thinking through how cover is actually found when a vehicle comes off the road, tend to find the operational pressure of an unplanned VOR event quietly pushes back against the compliance decision itself, whether through a rushed repair, a vehicle returned to service before it's genuinely ready, or a decision-maker who starts unconsciously setting the VOR threshold a little higher than they otherwise would to avoid the disruption.

Third-party and hired vehicles

A vehicle brought in from a hire company or a partner fleet to cover a gap needs the same VOR discipline applied as the operator's own fleet — a defect found on a hired vehicle doesn't stop being the responsible operator's problem simply because the vehicle itself is owned elsewhere. It's worth agreeing explicitly with a hire provider, before a vehicle is actually needed rather than in the moment, how defects found during the hire period are reported and resolved, and who makes the call on standing the vehicle down if something serious turns up while it's on the road under the operator's licence.

Communicating a VOR decision to the rest of the operation

A VOR decision made correctly in the maintenance record still needs to actually reach whoever's planning the day's routes and jobs — a vehicle marked off-road in one system that a dispatcher, working from a separate whiteboard or spreadsheet, doesn't know about is a genuine risk of the vehicle being scheduled anyway simply because the two pictures aren't connected. Fleets running maintenance and operations planning as genuinely separate processes, with no shared, current view of vehicle status between them, are exposed here in a way that's easy to overlook until a vehicle that should have stayed parked is dispatched by mistake.

Common mistakes in VOR tracking

• –Treating a logged defect as equivalent to a vehicle actually being stood down
• –Leaving the stand-down decision with someone under direct pressure to keep the vehicle running
• –Not tracking fleet-wide VOR trends, only individual vehicle status
• –Returning a vehicle to service without confirming whether a due safety inspection still needs to happen
• –Recording that a defect was fixed without a clear date and named record of who did the work and when