How to run a fleet planner that stands up to DVSA

A fleet planner that stands up to DVSA is not just a diary of due dates. It is the control that shows we know what each vehicle and trailer needs, when it needs it, who checked it, what defects were found, what was repaired, and whether anything was missed or taken off the road. If DVSA or the Traffic Commissioner asks how we manage roadworthiness, the planner is one of the first places they will expect to see that control working in practice.

For that reason, a proper vehicle maintenance planner has to do more than send reminders. It needs to tie together inspections, MOT or annual-test bookings, driver defect reporting, workshop activity, VOR periods, document expiry dates and the evidence file behind each event. If it cannot show the full story quickly, it is not doing the compliance job we need it to do.

What a vehicle maintenance planner needs to do

At minimum, a vehicle maintenance planner should show every safety inspection and test requirement for every vehicle and trailer on the fleet, with due dates calculated in advance and visible in one place. That sounds obvious, but the compliance standard is higher than a simple calendar.

DVSA looks at systems, not just isolated records. A planner should therefore function as a compliance control. In practice, that means it should:

• schedule all planned maintenance events
• show what has been completed
• flag what is coming due
• highlight anything overdue or missed
• link defects and repairs to the relevant asset
• retain evidence of work done
• show who reviewed and signed off the event
• make it clear when a vehicle was unavailable or VOR

For HGV and PSV operators in the UK, that usually means building the planner around the inspection regime set out in the DVSA Guide to Maintaining Roadworthiness. For vans and mixed fleets, the same discipline still matters, even where the legal framework differs from operator-licence maintenance systems. A fleet of 3.5 tonne vans may not be on an O-licence, but if we are running commercially and putting drivers on the road every day, we still need a defensible maintenance process.

The planner should also cover trailers as separate assets, not just as notes against a tractor unit. Trailers have their own inspection intervals, annual test requirements where applicable, tyre and brake issues, and repair histories. If a trailer can move independently through the operation, it needs its own record.

A good planner also records evidence, not just dates. A completed inspection needs the inspection sheet, the fitter’s findings, the rectification work, any deferment decision if lawful and safe, and the sign-off showing the vehicle was roadworthy before return to service. If we are asked to produce records, we should not be hunting through inboxes, paper files and workshop whiteboards.

Which dates and intervals should be in the planner?

The core principle is simple. If a date affects roadworthiness, legal use, or our ability to prove control, it belongs in the planner.

For most operators, the key scheduled items are:

• safety inspections for vehicles
• safety inspections for trailers
• MOT dates for relevant vehicles
• annual-test dates for HGVs, PSVs and testable trailers
• routine servicing
• brake inspections and brake performance testing
• tachograph calibration dates
• speed limiter inspections where applicable
• LOLER dates for any lifting equipment fitted to the vehicle
• road fund licence renewal where managed centrally
• insurance dates
• driver licence check dates
• Driver CPC and DQC expiry dates
• any company-set review dates for driver walkaround checks and declarations

In UK operator-licence work, the annual-test is not just another service event. It needs separate visibility because the booking lead time, preparation work and failure consequences are different. The same applies to MOT on vehicles outside the annual-test regime. The planner should distinguish between these event types clearly.

Driver checks also need a place. Daily walkaround checks are not scheduled in the same way as a six weekly inspection, but they still need control. We should know whether defect reporting has been completed, whether nil defects are being declared where required by our process, and whether missing checks are visible. If a driver reports a defect at 06:00 and the vehicle still goes out at 07:00, we need a record showing why that was safe and authorised, or why it should not have gone.

Document expiry dates matter because they often expose wider control failures. If a vehicle is in service but the insurance record, DQC, driving licence check, tachograph calibration, or annual-test date has lapsed in the system, that tells DVSA our oversight is weak. We should also track hired-in vehicles, hired trailers and temporary additions from the point they come into service. Our guide on bringing a vehicle into service with the right compliance records covers that handover point in more detail.

Where a rule differs between the UK and the EU generally, the planner should follow the UK requirement that applies to our operation. For example, UK annual-test and operator-licence expectations are not simply a copy of EU-wide fleet practice. Operators working internationally may also need to keep an eye on local test, emissions or access requirements, but the DVSA-facing planner must reflect the UK control standard first.

Many operators also build in administrative prompts around VOL actions, OCRS-related review points, and insurer conditions. Those are not substitutes for maintenance events, but they are often part of the same operational control file.

How do you set inspection frequency?

There is no single interval that suits every fleet. The right inspection frequency is the one we can justify from the vehicle’s use, condition and risk profile, and that still meets DVSA expectations.

Transport managers usually start with the manufacturer’s guidance and the DVSA Guide to Maintaining Roadworthiness, then adjust based on actual operation. Factors that matter include:

• vehicle age
• mileage
• hours worked
• load type and weight
• stop-start urban use
• off-road or rough-site running
• coastal or corrosive environments
• trailer utilisation
• brake wear history
• defect trends
• seasonal peaks
• whether the vehicle is on day work, trunking, refuse-style work, or school and service routes

A newer tractor unit on steady motorway work may justify a longer interval than an older rigid doing high-frequency urban drops with kerbing, harsh braking and tail-lift use. A PSV on intensive local service work may need a different regime from a coach doing longer distance private hire. A lightly used trailer parked for periods still needs a proper interval, because low use does not remove deterioration risks such as brake seizure, tyre ageing or lighting faults.

The key is that the interval should be realistic and documented. If we run inspections every 10 weeks on paper but repeatedly pull vehicles in late, carry defects over, or see recurring brake and tyre issues, the real system is not 10 weekly. It is uncontrolled. DVSA and the Traffic Commissioner will look at actual outcomes, not just the stated policy.

Most operators set a maximum interval and then manage vehicles in earlier where usage demands it. The planner should support both fixed-date and usage-led control. If a vehicle covers more mileage than expected, or is reassigned to tougher work, the next inspection date should be brought forward. If we use ISO week planning across the workshop, that is fine, but the underlying due date still needs to be clear for each asset.

Brake performance deserves special attention. A roadworthiness system is weak if brake checks are treated as occasional add-ons. We should be planning brake inspections, brake test evidence and follow-up work as part of the regular maintenance cycle, not waiting for annual-test preparation to discover imbalance or poor performance.

If we need to evidence why our intervals are set as they are, we should be able to show the policy, the risk factors considered, and the maintenance history that supports the decision. Our operator licence maintenance records guide is useful if you are reviewing whether your current file would stand up to that scrutiny.

How should defects, repairs and VOR time be recorded?

A defect record needs to tell the whole story from report to rectification. Anything less leaves gaps that become difficult to defend later.

When a defect is reported, we should record:

• date and time reported
• vehicle or trailer ID
• driver name
• mileage or odometer where relevant
• defect description in plain terms
• whether the defect makes the vehicle unsafe or unroadworthy
• whether the vehicle was stopped immediately
• who reviewed the report
• the decision taken, repair now, monitor, or remove from service

For workshop action, the record should then show:

• date and time the job was opened
• technician or repairer
• diagnosis
• work carried out
• parts fitted
• any external supplier used
• whether a road test or brake test was done
• date and time completed
• who signed the vehicle back into service

Where a defect is safety critical, the vehicle should be marked VOR at once. The VOR period should have a clear start and finish time, with the reason for downtime recorded. This matters operationally and evidentially. If DVSA asks why a scheduled job slipped, a documented VOR period may explain it. If they ask why a vehicle was used despite a reported issue, the absence of a VOR marker may suggest the defect was not controlled properly.

Missed and deferred work needs care. If an inspection found defects that could safely be deferred, the record should show exactly what was deferred, why that decision was safe, who authorised it, and the deadline for rectification. If a safety inspection itself was missed or completed late, that should not disappear. It should remain visible with the reason, the authorisation, and the catch-up action. Trying to tidy away missed events creates a worse problem when records are reviewed.

This is also where signed evidence matters. Driver declarations, fitter sign-off, workshop completion, and transport manager review should be attributable to named people. Digital signatures, timestamps and a proper audit trail are far stronger than undated paper copies or edited spreadsheet cells.

If you want to test whether your current process would survive a roadside prohibition or maintenance investigation, our article on what a PG9 means for your vehicle and licence risk is a useful benchmark.

What evidence should be ready for DVSA or the Traffic Commissioner?

We should assume that if DVSA visits, or if the Traffic Commissioner calls us to public inquiry, we may need to produce records quickly and in order. The test is not whether the documents exist somewhere. It is whether we can put them in front of an examiner without delay and without contradictions.

The core evidence file usually includes:

• completed safety inspection sheets
• forward maintenance planner for vehicles and trailers
• MOT and annual-test history
• brake test records
• service and repair history
• defect reports, including nil defect declarations if part of our process
• rectification records and sign-off
• records of missed inspections or late events, with reasons
• VOR history
• PMI sheets where used in the operation
• calibration certificates for tachographs
• driver licence check records with DVLA results
• Driver CPC and DQC records
• maintenance provider details and contracts where work is outsourced
• evidence that transport managers review compliance performance
• tachograph analysis records and infringement follow-up
• driver debriefs, acknowledgements and declarations related to drivers’ hours and working time where relevant

Tachograph evidence is often reviewed alongside maintenance because it speaks to overall control. If our maintenance file is tidy but our tachograph follow-up is weak, that still points to poor operator management. The same is true of driver licence checks. If a fleet planner tracks inspections perfectly but not licence and DQC expiry, it is only solving part of the operator-licence problem.

For insurance and vehicle identity checks, some operators also keep supporting evidence from askMID or records linked to the Motor Insurers' Bureau, sometimes written as MIB, especially where hired or newly added vehicles are involved. That is not a substitute for our own insurance controls, but it can support the file.

The best test is to ask, if DVSA requested six months of records for one vehicle, one trailer and one driver, could we export the lot in minutes? If not, the system is too fragmented. Our guide to preparing for a DVSA maintenance investigation sets out the sort of file review we recommend before an external visit.

When does a spreadsheet stop being enough?

A spreadsheet can work for a very small, stable fleet with one responsible person, one depot, straightforward inspection intervals and disciplined admin. Many owner-drivers start there. Some small PSV and van operators do too. The problem is not that spreadsheets are always wrong. It is that they become fragile very quickly.

A spreadsheet usually stops being enough when one or more of these applies:

• more vehicles or trailers are added
• assets move between depots
• inspection frequencies differ across the fleet
• maintenance is split between in-house and external workshops
• more than one person updates the records
• drivers submit defects from the road
• we need signed declarations and timestamps
• reminders are being missed
• annual-test preparation is handled separately from routine planning
• we need a clear audit trail of edits and sign-off
• the Traffic Commissioner file has to be produced at short notice

Trailers are often the tipping point. Operators may manage vehicles reasonably in a spreadsheet, then lose control when trailers rotate, defects are reported against registration rather than fleet number, and workshop records sit somewhere else. Multi-depot operations make this worse. So does shared responsibility between transport, workshop and admin teams.

Another warning sign is when the planner no longer matches reality without manual chasing. If due dates are maintained in one sheet, defect reports in email, repairs in a garage system, licence checks in another file, and tachograph evidence elsewhere, we have several partial truths instead of one reliable compliance record.

That is why we built Operator Compliance the way we did. At OperatorCompliance, we use the practical operator perspective from Fleeta Limited, including running trucks under an operator licence, to structure records around the controls DVSA actually expects to see. That means vehicles, trailers, drivers, deadlines, signed evidence and tachograph records in one place, with options for integrations through a REST API and webhooks where operators need data to move between systems. Some fleets also compare tools such as Fleetalyse or Logivo.AI when reviewing their wider software stack, but the key question is simpler than brand comparison. Can the system show that our maintenance control is active, complete and auditable?

If your current process is close to the limit, it is worth reviewing what a stronger system should include before a compliance issue forces the change. Our piece on how to compare UK truck maintenance planners is a practical place to start.

A planner that stands up to DVSA is one we can rely on daily, not one we tidy up when an investigation starts. If it controls the dates, captures the evidence, records the exceptions and shows who did what, it is doing its job. If it only reminds us that something is due, it is not yet a compliance system.