Vehicle Off Road (VOR) Management: A Practical Guide for UK Operators

Vehicle off road (VOR) status is an operator control that takes a vehicle out of operational service. It should show the date, reason, location, person responsible, restrictions, planned work and route back into use. For an HGV or passenger-carrying vehicle, the DVSA Guide to Maintaining Roadworthiness says the VOR declaration must be recorded on the vehicle maintenance file, with date and reason, and the operator must prevent use while VOR applies. This is especially important when the vehicle is unsafe. A VOR tag on a dashboard is useful only if dispatch, drivers and maintenance staff share the same status and act on it.

What a VOR declaration does

This guide addresses operational VOR management for Great Britain. It is not the same as a DVLA statutory off-road notification (SORN), which concerns vehicle tax and keeping a vehicle off public roads. A vehicle can be operationally VOR for a safety defect without the operator necessarily making a SORN; the tax and road-use position must be checked separately. DVLA SORN guidance.

When to take a vehicle out of service

A driver may report a defect at a daily walkaround, a technician may find one during inspection, or an operator may plan a seasonal shutdown, repair or refurbishment. A safety-critical defect needs immediate controlled isolation. For a non-critical defect, an authorised competent person should assess whether continued use is safe and lawful, record the reasoning and set a repair deadline. Do not invent a universal list of “driveable defects” in a generic article: severity depends on the vehicle, defect, intended journey and current inspection criteria. DVSA expects a system ensuring unroadworthy vehicles are taken out of service and defects are assessed and rectified. DVSA roadworthiness guide; GOV.UK driver/operator responsibilities.

An operational VOR can also be planned: for example, a seasonal vehicle will be parked for several months. Record that as a planned status with the date and reason. A VOR declaration must never be backdated to disguise a late safety inspection. DVSA's operator audit standard explicitly looks for that misuse. DVSA HGV operator audit standard, section 3.7.

A six-step VOR process

1. Capture the trigger and isolate the vehicle

Record vehicle registration or identifier, time, location, reported defect or planned reason, reporter and who made the decision. If the vehicle is unsafe, prevent allocation or use immediately. Tell the driver and dispatcher, secure keys or access according to the organisation's procedure, and mark the vehicle visibly where helpful. A spreadsheet flag that dispatch does not see is not an effective isolation control.

2. Decide what movement, if any, is authorised

DVSA notes that a vehicle with VOR status can sometimes be legitimately moved before return to service, for example to a maintenance facility, MOT inspection or a road test after repair. That is not a general permission to drive a dangerous or unlawful vehicle. A responsible person should decide whether the proposed movement is safe and legally permissible, specify its purpose and route, and use recovery or other arrangements if it is not. Keep the movement record separate from operational dispatch. DVSA roadworthiness guide.

3. Plan repairs and preserve the defect trail

Send the defect report to someone with authority to act. Record the assessment, repair instruction, provider, parts/work completed, inspection or test result and any follow-up. Drivers should report defects in writing with vehicle ID, date, details and their name. Where a reported defect is not repaired immediately, record why. GOV.UK roadworthiness responsibilities; DVSA maintenance investigation guidance.

4. Manage the safety-inspection schedule

A VOR period may cross a planned safety inspection. DVSA says operators can suspend the safety-inspection schedule when the vehicle is off road beyond the next planned inspection, but this must be a genuine, controlled VOR period. A vehicle that missed a scheduled inspection while VOR must have a safety inspection confirming roadworthiness before return to service. The inspection date may then be used to reschedule regular inspections. An MOT, repair invoice or driver walkaround alone does not automatically replace that required return inspection. DVSA roadworthiness guide.

5. Authorise return to service

The return gate should answer: has the defect been rectified and verified; is the safety inspection current, including one required after a missed interval; are MOT, tax, insurance and other applicable requirements valid; has the driver performed the required pre-use check; and has dispatch received an explicit clearance? A qualified person should sign off the repair and inspection evidence appropriate to the work. Only the authorised status owner should release the VOR flag. Record who cleared it and when.

6. Review the pattern

Repeated VOR events may reveal poor maintenance planning, recurring defects, procurement problems or delays in parts and repair. Review duration and root causes without letting a pressure to improve availability override roadworthiness. Distinguish “vehicle unavailable” from “vehicle unsafe”; both affect dispatch, but the safety control and evidence can differ.

Copyable VOR control record

Use the record to make a decision, not as a substitute for the physical repair or inspection.

Example: seasonal HGV and a missed inspection

An operator takes an HGV out of service for the winter and records its VOR start date, reason and location. Dispatch cannot allocate it. Its planned safety inspection date passes during the genuine VOR period. Before returning it to work, the operator arranges a safety inspection and resolves any defect it finds. It checks the remaining legal documents and the driver's pre-use condition, then records a named release decision. The operator does not simply remove the VOR tag because the seasonal job has restarted.

Common errors and questions

Is VOR the same as SORN? No. VOR is the operator's service/roadworthiness control; SORN is a DVLA notification with tax/public-road consequences. Check both where relevant.

Can a VOR vehicle go for repair? Sometimes, but only after a safe and legally permissible movement decision. Recovery may be necessary.

Can we pause inspections while VOR? DVSA allows a genuine VOR period spanning the next planned inspection to suspend the schedule. A missed safety inspection requires an inspection before return to service. Record the basis and dates.

Does a repair invoice clear VOR? Not by itself. Verify rectification, any required safety inspection and other applicable documents, then have an authorised person release it.

Who owns the decision? The operator remains responsible for the roadworthiness system. Drivers, maintenance providers and transport managers each have roles, but an informal handoff must not create a gap.

Where Complys fits

The live Complys vehicle-compliance page labels its fleet and operator modules Launching and asks users to book a demo or register interest. This guide can link to that page as a future workflow option; it must not say Complys currently blocks dispatch, detects defects, calculates a green status or automates VOR release. The immediate practical step is to implement a documented VOR register, dispatch block and return-to-service approval using the system the operator actually has.

Source, ownership and writer-side QA

Primary sources: DVSA Guide to Maintaining Roadworthiness, updated 28 April 2025; DVSA HGV audit standard; GOV.UK roadworthy vehicle duties; DVLA SORN. Reviewed 6 October 2026. Distinguishes DVSA “must” and example permitted movements; no automatic driving permission inferred.

Owner check: No exact VOR management guide observed on the .co.uk estate. The fleet money page discusses vehicle availability and planned platform capability, but does not provide the operator's procedural VOR answer. Final repository/gated-content and route check remains required.

Product check: Vehicle platform is labelled Launching on the live money page. CTA: “book a demo or register interest,” subject to same-day offer check. No live feature claims. Disposition: READY writer-side; no publication until final repo and product QA.