Missed PMIs on lorries are usually not caused by one dramatic failure. They happen because the date lived in one diary, one inbox, or one person’s head, and real workshop pressure got there first. If you want to stop them before DVSA does, you need a planning method that books inspections ahead, shows what is due at a glance, and makes it obvious who is acting when a vehicle cannot attend.
The fix is not complicated, but it does need discipline. Set the next PMI date as soon as the current one is finished. Book workshop capacity in advance. Track vehicles that are off the road, away on contract, or tied up waiting for parts. If an inspection is going to be missed, decide early whether the lorry comes out of service, rebook it fast, and record exactly why. That is what shows control when DVSA asks.
Why missed PMIs matter more than one late inspection
A missed PMI is not just a late workshop job. It is evidence that your maintenance system may not be under control.
Under your O-licence, you are expected to keep vehicles fit and serviceable and to follow the inspection intervals you have declared. Those intervals sit at the centre of your maintenance plan. When PMIs slide, DVSA does not just look at the individual vehicle. It looks at whether the operator has a reliable system for protecting roadworthiness across the fleet.
One late preventative maintenance inspection can happen for a real reason. A breakdown. A vehicle stuck away from base. A workshop slot lost because a safety repair overran. What matters is what happened next. Was the vehicle stood down if it could not safely continue? Was the inspection rebooked promptly? Was the reason recorded? Could you show that the delay was managed, not ignored?
Repeated gaps are different. If DVSA sees several vehicles inspected beyond interval, or sees inspection sheets with no clear booking trail behind them, it starts to look like a control problem. That can feed into OCRS, trigger deeper questions at an investigation, and become an issue if your case reaches a Traffic Commissioner.
The point is simple. A PMI interval is not advisory. It is part of the system by which you prove ongoing roadworthiness. If your paperwork says six weekly inspections and the workshop reality is eight, nine, or “when we can get it in”, the paperwork is not your system. The actual behaviour is.
In the UK, this matters in a very specific way because the operator licensing regime looks at maintenance control, not just whether a vehicle happened to pass its last MOT. A pass certificate does not cover missed inspections between tests. Nor does a clean tachograph record excuse a vehicle being run past its declared maintenance interval. Different obligations, different evidence.
Find out where your PMI dates are actually being lost
Most fleets already know the theory. Vehicles need a PMI every set number of weeks. The problem is where dates disappear between the wall planner and the workshop ramp.
The first cause is planner drift. Someone sets the next date from when the vehicle actually attends, instead of from the planned schedule. That sounds harmless, but over a year it moves the whole fleet. A six weekly cycle becomes six weeks plus whatever delay happened last time. Then another delay gets added on top. Before long, your planner is drifting away from the maintenance promise behind the O-licence.
The second is vehicle downtime. A lorry is off the road for clutch work, accident damage, body repairs, waiting for parts, or a long driver absence. Everyone assumes the PMI can be “done when it comes back”. Sometimes it can. Sometimes the return date slips three times and nobody notices the inspection has now gone overdue. Downtime does not remove the need to control the interval. It just means someone has to decide whether to inspect during downtime, replan before return to service, or keep the vehicle parked.
The third is workshop capacity. This is where things get real. You may have enough bays on paper, but then MOT prep runs over, a brake issue turns into a full axle job, and the day disappears. If your PMI bookings are loose, they get bumped by urgent work. If they are firm, with time protected in the diary, they are far less likely to be sacrificed. We wrote more about that in our guide to workshop booking systems that stop missed jobs.
The fourth is poor ownership. This is common in fleets between five and a hundred vehicles. The transport manager thinks the workshop books PMIs. The workshop thinks transport sends the schedule. The director assumes “the system” is handling it. In truth, nobody owns the date from end to end. A missed PMI nearly always has this somewhere behind it.
The fifth is poor visibility of off-site vehicles. Tramping units, contract work, seasonal peaks, hired trailers, and subcontracted workshop support all make the planner harder to trust. If the person booking inspections cannot see where the lorry actually is next week, the booking gets left until “nearer the time”. That is exactly how dates get lost.
The sixth is defects and repairs not feeding back into the plan. A driver reports a defect. The vehicle comes in. The repair is done. But the person handling defects does not check whether a PMI is also due. Or the workshop notices the PMI is close but has no authority to bring it forward. So the lorry leaves, only to need another slot days later, or worse, misses the inspection entirely. Defect control and maintenance planning need to meet in the same place. We cover that in our article on proving defects were fixed before they became a problem.
Build a PMI planner that survives real workshop pressure
If you are working out how to stop missed PMIs on lorries, the minimum standard is higher than a spreadsheet with dates on it. A spreadsheet can work, but only if the process around it is tight. What fails is not the file itself. It is the lack of booking discipline and the lack of a live view when the week changes shape.
A small or mid-sized UK fleet needs five things.
First, a master schedule for every vehicle and trailer. That should show registration or fleet number, PMI interval in weeks, last completed inspection date, next due date, MOT date, and any known booking constraints. If you use safety inspections at different intervals across the fleet, that needs to be explicit. Do not rely on memory.
Second, the next PMI should be scheduled as soon as the current one is completed. Not “we will sort it later”. Not “nearer the time”. Book the next one while the paperwork is in front of you. If workshop capacity is external, send the booking request that day and chase confirmation. If capacity is internal, put it straight into the diary.
Third, book ahead far enough to protect capacity. For many fleets, that means several inspection cycles visible at once, not just the next fortnight. If you only look two weeks out, every urgent repair will beat the PMI to the slot. A proper workshop diary should show due dates, confirmed bookings, and vehicles with no slot allocated yet. This is exactly why a workshop diary that keeps the fleet on the road matters more than a list of dates.
Fourth, use warnings before the due date, not after it. You need an upcoming due list that gives enough notice to act while options still exist. For a local rigid on a stable route, that might be straightforward. For a tramping artic heading north for the week, you need more notice because access to the vehicle is harder. The point is not the alert itself. The point is giving someone enough time to make a booking stick.
Fifth, make one person accountable for each step. One owner for the schedule. One owner for booking. One owner for checking attendance and paperwork return. In a small business that may be the same person, but the responsibilities still need naming. “The office” is not ownership.
There is one more rule that saves a lot of pain. Do not move the maintenance cycle casually. If a vehicle is inspected early for convenience, make sure the schedule logic stays under control. If it is inspected late, record why and decide whether the cycle resets or whether you are recovering back to the original pattern. What you cannot do is let each attendance date create its own future date without anyone noticing the whole programme has slipped.
This is where software helps if it is built around workshop reality. We built maintenance planning and compliance control for operators because this is exactly where spreadsheets start to fail. Not because fleets need grand systems, but because they need dates, bookings, completed inspections and exceptions tied together in one place.
What to do when a lorry cannot make its booked inspection
This is the point where operators either show control or lose it.
If a lorry is likely to miss its booked PMI, act before the appointment is missed. Do not wait for the day to arrive and then call it unavoidable.
Start with the reason. Is the vehicle broken down? Away from base? Still loaded? In bodyshop repair? Waiting on parts? Driver unavailable? Workshop over capacity? The reason matters because it drives the decision on whether the vehicle can continue in service.
If the vehicle cannot be inspected within its planned interval, ask the hard question early. Can we still stand over its roadworthiness, or does it need to come out of service now? If there is doubt, park it. That is the unpleasant answer sometimes, but it is better than trying to explain to DVSA why you knowingly ran past the date with no proper control.
Then rebook immediately. Not “when we get a chance”. Put the next available practical slot in place and make sure the workshop knows it is a missed or at-risk PMI, not a routine service request. If the vehicle is off site, confirm where and when it can realistically attend. If it is in repair, decide whether the PMI can be completed during that downtime.
Record the full story. The planned date. The reason it could not attend. Who made the decision. Whether the vehicle was stood down or allowed to continue. The rebooked date. The actual completion date. If other defects were found in the meantime, link those records too.
This matters because a late inspection with a clear, sensible audit trail is one thing. A late inspection with no reason, no decision record, and no evidence of risk control is something else entirely.
Do not try to tidy it up after the event by changing dates on the planner. That is one of the quickest ways to make a manageable issue look dishonest. Keep the original due date visible. Show the exception. Show the action taken.
The records DVSA expects when it checks your system
When DVSA looks at maintenance control, it is not only checking whether inspection sheets exist. It is checking whether the system around them works.
You should be able to produce, without a scramble, the following.
A current maintenance planner for all vehicles and trailers. This should show inspection intervals and due dates clearly.
Completed PMI sheets for the period being reviewed. They need to be legible, dated, vehicle-specific and signed as required by your process.
Evidence of booking control. That can be workshop diary entries, booking confirmations, internal job cards, or planner records showing when inspections were allocated.
A clear list of late PMIs or changed dates, with reasons. If a vehicle was unavailable, show that. If workshop capacity failed, show what was done next. If the vehicle was taken out of service, show the stand-down and the return-to-service point.
Repair records linked to inspection findings. A PMI sheet that notes defects is only half the story. You also need the job card, parts issue, fitter notes, external invoice, or other evidence showing the defect was rectified.
Driver defect reporting records and follow-up actions. DVSA will often want to see that daily defects and periodic inspections join up, not live in separate worlds.
MOT history and test preparation records where relevant. Again, an MOT pass is not the same as maintenance control, but it forms part of the wider roadworthiness picture.
Any documents relevant to the decision to keep or remove a vehicle from service. That may include internal emails, defect assessments, workshop notes, or transport instructions.
If you use an external maintenance provider, keep the service agreement and the communication trail. Outsourcing the work does not outsource responsibility under the O-licence.
If you want a fuller checklist, we have set one out in our guide to records to have ready for a DVSA O-licence audit, and we also explain how to show maintenance control for your O-licence.
The standard to aim for is simple. If an examiner picks one vehicle and asks for the last few PMIs, the due dates, any changes, the defects found, and the repairs completed, you should be able to show the full chain without piecing it together from three people’s memories.
That is the practical answer to how to stop missed PMIs on lorries. Make the dates visible. Protect workshop time. Give ownership to named people. Treat exceptions as decisions, not accidents. Keep the record of what happened. From the workshop side, that is what holds up when the week goes wrong, and it is what still makes sense when DVSA is the one asking questions.
Is a late PMI always a DVSA offence?
A late PMI is a compliance problem and can count against your systems, especially if it happens more than once. DVSA will look at the pattern, the reason and what you did about it.
Can I move a preventative maintenance inspection date?
Yes, but you need a genuine operational reason, a new booked date and a clear record of why it changed. Repeated movement without control is where trouble starts.
Who should own the PMI schedule in a haulage business?
One named person should own it day to day, but the system must still work if they are off. If only one person knows the dates, the system is weak.
Do spreadsheets work for PMI planning?
They can, for a while. The problem is not the sheet itself but missed updates, hidden changes and no audit trail. Once the fleet grows, that usually becomes the failure point.
What will DVSA ask to see about PMIs?
Expect to show your inspection planner, completed PMI sheets, evidence of booked dates, records of any changes, repair follow-up and proof that safety defects were dealt with.
