If DVSA asks you to prove maintenance was planned, not reactive, they are not looking for one magic document. They are looking for a system that makes sense from start to finish. The vehicle should have been put onto an inspection schedule in advance, the interval should be justified, the booking should exist before the due date, and the paperwork should show defects and repairs being dealt with inside that system, not only after something went wrong.
That is the practical answer to how to show maintenance was planned not reactive for DVSA. You need a dated maintenance plan, evidence that the vehicle was called in against that plan, and records that tie PMI, defects, repairs and vehicle usage together. If those records disagree with each other, or only appear after a prohibition, breakdown or MOT failure, DVSA will treat the whole thing as reactive and start asking harder questions about roadworthiness and your O-licence.
What DVSA is trying to see
DVSA is not auditing your intentions. It is checking whether you had maintenance under control before the vehicle came through the gate.
For an HGV operator, planned maintenance usually means:
- a set inspection frequency for each vehicle
- that frequency based on time, mileage, usage or a combination
- a forward schedule showing future PMI dates
- vehicles booked in before they become overdue
- repair work flowing from inspections and defect reporting
- records that show who reviewed defects and closed them out
- evidence that the vehicle was not left in service with safety related defects unresolved
The difference between planned and reactive matters because the legal issue is roadworthiness, not whether you eventually fixed the vehicle. A clean repair invoice after a roadside stop does not prove control. It can prove the opposite.
DVSA knows the pattern. If records only become tidy after a prohibition, a complaint, a fleet check or a public inquiry threat, that is not maintenance planning. It is damage control. For the Traffic Commissioner, that goes to the heart of whether you are fit to hold an O-licence.
The UK position is also specific. Operators here are expected to run a documented preventative maintenance inspection regime alongside daily walkaround checks, MOT preparation and defect rectification. General EU references to vehicle maintenance do not replace the UK operator licensing system, DVSA expectations, or the evidence needed to satisfy a Traffic Commissioner.
Build a maintenance trail before the vehicle arrives
The easiest way to prove maintenance was planned is to create the trail before the vehicle arrives at the workshop. If you build it afterwards, it usually shows.
Start with the inspection policy. For each vehicle, record:
- the PMI interval in weeks
- any mileage trigger used alongside that interval
- the reason for that interval
- who set or approved it
- the date it was set or last reviewed
That interval should reflect actual use. A six weekly cycle may be fine for one tractor unit doing steady trunking, but wrong for a tipper, urban multi drop rigid or anything doing harsh duty. If usage changes, the interval should be reviewed and the reason noted.
Then keep a forward planner. This is one of the first things we would want to see in a file because it shows whether the business is looking ahead. A proper planner should show:
- vehicle registration or fleet number
- last PMI date
- next due date
- due mileage if you use mileage triggers
- booked workshop date
- status, booked, completed, rescheduled, off road
- who updated the plan
The key point is timing. If the planner only shows completed inspections, it is a history log, not a maintenance plan. DVSA wants to see future bookings, not just past paperwork.
If you use mileage as part of your trigger, keep the source. That may be odometer readings, downloaded tachograph mileage, fleet telematics or fuel system mileage. What matters is consistency. If your PMI sheet says the vehicle came in at 412,000 km, but your usage records show it should have been much higher, someone will ask why.
You also need evidence that the booking was made in advance. That can be a workshop diary entry, a planned job in your maintenance system, an email confirmation, or a customer booking record if you are an external workshop. The date the booking was created matters.
For operators still working from paper and spreadsheets, this is where the system often starts to fray. Dates move, vehicles swap work, and nobody can tell later whether an inspection was genuinely planned or just typed into a sheet after the fact. That is exactly why we built workshop-led tools around the same pressure points we deal with in Woolpit Truck Repairs. If you want a deeper look at what a planner needs to hold up under scrutiny, read which HGV maintenance planner actually holds up under DVSA.
Match PMI records to defects, repairs and usage
A single PMI sheet does not prove control. The history around it does.
When DVSA looks at maintenance, the question is whether the records tell one consistent story. That means your PMI sheets need to line up with:
- driver defect reports
- repair job cards
- parts used
- invoices, internal or external
- tachograph or mileage evidence
- brake test records where applicable
- MOT history
- any off-road or VOR notes
Take a normal example.
The forward planner shows Vehicle A due a preventative maintenance inspection on 12 March. The workshop booking was created on 1 March. The vehicle arrives on 11 March at 356,214 km. The PMI sheet records tyre wear, a marker lamp out, and brake imbalance requiring further work. There is a job card raised the same day. The parts issue shows a lamp unit and brake components. The technician signs the repair work. A brake performance record is attached after rectification. The vehicle returns to service on 12 March. During the same week, the driver defect book shows a marker lamp defect reported before the PMI and marked as repaired.
That reads as one planned system.
Now compare it with the file DVSA does not like. The PMI is dated 12 March, but there is no planner entry. The mileage box is blank. The defect report appears to have been filled in with the same pen as the workshop sheet. The invoice is dated after a roadside stop on 18 March. The MOT history later shows a fail for brake issues. That reads like paperwork assembled around events.
This is why we always tell operators and workshops not to treat records as separate piles. A PMI sheet on its own is weak. A PMI sheet tied to usage, defects and rectification is much stronger. If you need to tighten the records themselves, our guide to which maintenance records stand up in a DVSA audit covers the documents that usually matter most.
A few practical points make a big difference:
First, record the odometer at every stage. On the PMI. On the defect report if relevant. On the job card. On the invoice. Mileage drift between documents is one of the quickest ways to lose credibility.
Second, close defects properly. If a driver reports a defect, the report should show the assessment, the action taken, and whether the vehicle remained in service or was taken off the road. An unresolved safety defect with no decision trail is a red flag.
Third, keep repair dates honest. If a defect found on PMI needed parts and was completed two days later, show that. Do not make it look as though everything was repaired instantly if the vehicle was actually parked up waiting.
Fourth, keep MOT and PMI separate but consistent. An MOT pass is not a substitute for scheduled maintenance. If your maintenance seems to cluster around MOT dates only, DVSA may conclude that inspections are being driven by the annual test rather than by a proper preventative regime.
How to deal with changes, missed inspections and breakdowns
Real fleets do not run to a perfect calendar. Vehicles go off the road. Customers change work at short notice. Parts do not arrive. Drivers report defects on the day the unit was meant to leave site. DVSA knows that. The issue is not whether plans changed, but whether you controlled the change.
When an inspection is rescheduled, keep the original due date and the reason for the move. Then record:
- who authorised the change
- the new booked date
- whether the vehicle stayed in service meanwhile
- why that was acceptable, if it did
- any temporary restrictions placed on the vehicle
If the vehicle was off the road, document that clearly. A proper off-road note should show the start date, reason, location, and the date returned to service. That protects you from the appearance of a missed PMI when the vehicle was not operating. We have written more on this in keeping maintenance plans right when vehicles go off the road.
Missed inspections are harder, because they are hard to defend. If one happens, do not bury it. Record:
- the due date
- the actual inspection date
- the number of days overdue
- the reason
- who reviewed the breach
- what action was taken to prevent a repeat
If the vehicle continued in service while overdue, expect questions. You will need a credible explanation and supporting evidence, not a vague note saying workshop busy.
Breakdowns and roadside failures do not automatically make your system reactive. Poor records do.
Suppose a vehicle suffers an unexpected air leak on the road three weeks after a PMI. That can happen in a well run fleet. What matters is the file:
- the PMI was done on time
- no related defect was left unresolved
- the driver reported the breakdown
- recovery or roadside repair was logged
- the repair record shows what failed
- the vehicle was assessed before returning to service
- the next planned PMI remained on schedule, or if brought forward, the reason was recorded
What you must avoid is letting the breakdown become the only maintenance evidence for that period. One roadside invoice, with nothing around it, makes the whole operation look reactive.
What an auditor will spot straight away
Some problems jump off the page. They are the things an experienced DVSA examiner or independent maintenance auditor sees in minutes.
The common ones are:
- PMI intervals that are not defined, or change with no explanation
- forward planners filled in after the event
- inspections completed late with no reason recorded
- mileage triggers mentioned in policy but not tracked in practice
- odometer readings missing, repeated, or clearly wrong
- driver defect reports with no sign off or no repair reference
- repair invoices that do not tie back to a PMI or defect report
- workshop sheets that all appear to have been written up at once
- vehicles shown as in service while major defects were outstanding
- MOT failures for items that should have been picked up in routine maintenance
- brake related work with no supporting test evidence where you would expect it
- off-road periods not documented, making planned dates look missed
- subcontracted maintenance with no evidence the operator reviewed the records
Another one is contradiction between systems. If the tachograph shows the vehicle worked all week, but the workshop record says it was off road awaiting parts, someone is going to ask which is true. If your OCRS has been hit by prohibitions or annual test issues, expect those records to be read with even less goodwill.
This is also where workshops can get dragged into an operator's weak process. If you maintain vehicles for customers, your own paperwork needs to be clear enough to show what was booked as planned work, what was additional defect rectification, and what was emergency repair. If every job card simply says service and repair, you are not helping the operator prove control.
How to present the file on the day
On the day of a DVSA visit, do not hand over a stack of mixed papers and hope the story emerges. Lay it out vehicle by vehicle, in date order, so the system is obvious.
For each vehicle, we would present:
- Vehicle details sheet
Registration, fleet number, make and model, in service date, normal duty, current PMI interval, who approved it.
- Maintenance planner extract
Last PMI date, next due date, future booked dates, and any rescheduled entries with reasons.
- PMI records
Each PMI sheet in order, signed and dated, with odometer reading and inspection outcome.
- Defect reporting records
Driver defect reports, nil defect reporting if used, and workshop assessment and sign off.
- Repair records
Job cards, technician notes, parts records, invoices and any brake test printouts or measurements.
- Usage evidence
Mileage records, tachograph mileage where relied on, and any notes supporting interval decisions.
- Exceptions
Off-road declarations, VOR notes, missed inspection reviews, roadside breakdown records.
- MOT and prohibition history if relevant
Not because these replace maintenance, but because they often trigger questions.
Keep the chronology clean. If an inspection was due on 5 June and carried out on 4 June, the booking evidence should already exist before that date. If it was moved to 7 June, the reschedule note should sit between the original plan and the completed PMI. The reader should not have to guess.
If you hold records electronically, make sure someone can pull them quickly and in the same order. A good system is not just one that stores documents. It lets you show the maintenance logic without hunting across email, spreadsheets, paper files and accounting software. That is the reason we built workshop software that keeps HGV maintenance under control from the workshop floor up, rather than starting with a software diagram and hoping it matched real jobs.
The standard to aim for is simple. A DVSA examiner should be able to pick any vehicle, follow the plan from scheduled PMI to completed repair, and see that maintenance happened because it was due, not because something forced your hand.
If you can show that clearly, you are in a much better position on roadworthiness, on OCRS, and on the wider question every audit leads back to, whether you are exercising proper control of the fleet under your O-licence.
Is a spreadsheet enough to show maintenance was planned?
It can be, if it is kept up to date and backed by dated evidence. DVSA will want more than a list of intended dates. You need booking records, completed PMI sheets, repairs and reasons for any changes.
What if a PMI was done late?
Record why it was late, what happened to the vehicle in the meantime, and the new planned date. One late inspection is easier to explain than a pattern of dates slipping without any record.
Do breakdown repairs make maintenance look reactive?
Not by themselves. Vehicles do fail. The problem is when breakdowns replace a proper preventative maintenance inspection system, or when repeated defects show the planned system is not being followed.
Should PMI dates be based on time or mileage?
They can be based on either, as long as the interval is suitable for the vehicle's use and is actually controlled. If mileage is the trigger, keep reliable mileage records to prove it.
What records should match each other?
Your planner, PMI sheets, defect reports, repair records, mileage or tachograph evidence, MOT history and any invoices or parts records should tell the same story for each vehicle.
