When a vehicle goes off the road, the maintenance plan has to change the same day. If it does not, your PMI dates, service mileage, workshop bookings and vehicle availability all start drifting apart. That is how a sensible plan turns into a missed inspection, a wasted bay booking, or a unit going back out with the wrong assumptions attached to it.
The practical answer is simple enough. Treat downtime as a planning event, not just a repair problem. Record why the vehicle is off the road, whether it is still accumulating mileage, what bookings now need moving, and who approved the change. That is the heart of how to keep maintenance planners accurate with vehicle downtime. The hard part is doing it every week, without relying on memory or a spreadsheet that only one person understands.
Why downtime wrecks a maintenance plan
A maintenance plan only works if the dates and mileage on it still match reality. Downtime breaks that link.
Take a six weekly PMI cycle. A vehicle is booked for inspection next Thursday. On Monday it suffers a brake defect and is stood down. The parts do not arrive until Friday. If nobody updates the planner, the inspection still shows as due next Thursday, the bay is still reserved, and operations still think the vehicle might be available by the weekend. None of that is now true.
The first problem is timing. If a vehicle is off the road for several days, or longer, its expected mileage changes. If you run on a mixed maintenance regime, with time intervals backed up by mileage expectations, the forecast becomes unreliable very quickly. Vehicles that are parked do not wear the same way as vehicles on trunk work, but they also do not stop needing a preventative maintenance inspection just because they have not moved. On an O-licence, you still need control of the inspection interval you have committed to.
The second problem is workshop loading. A planner that still shows vehicles arriving on their original dates will overstate the work coming in. Then, when the off-road vehicle finally becomes available, it lands on top of other jobs. Bay time gets squeezed. Fitters get pulled in different directions. Small jobs that should have taken an hour become all-day disruptions.
The third problem is roadworthiness decisions. If downtime is not properly recorded, people start making assumptions. Someone sees the vehicle has not done many miles and thinks its service can wait. Someone else assumes the PMI was completed because the booking was in the diary. Those are exactly the gaps that DVSA looks for when records and actual events do not line up.
We see this a lot when businesses outgrow spreadsheets. The sheet still has the original due date. The workshop whiteboard has a scribble saying "awaiting parts". The transport office has promised the vehicle back to a customer next Tuesday. None of those records agree. If you want a plan that will stand up under scrutiny, the maintenance system has to reflect the vehicle's real status, not the status it had last week. That is one reason we put so much emphasis on a maintenance planner that actually holds up under DVSA.
What counts as downtime for planning purposes?
For planning, downtime is any period when the vehicle cannot be used as normal, or should not be used until a maintenance decision has been made. That is broader than many operators first think.
Breakdowns are the obvious one. If the vehicle has failed at the roadside, is at a dealer, or is waiting recovery, it is in downtime. So is waiting for parts after the initial diagnosis. A vehicle that is physically back in the yard but still waiting for an EBS valve, lamp unit or tyre is not available just because you can see it.
MOT failure counts. If a vehicle or trailer fails MOT, the maintenance plan needs updating straight away. Retest timing, remedial work, parts and bay space all have to be reflected in the schedule. The same applies if a prohibition, inspection failure, or serious defect means the vehicle is stood down pending repair.
Accident damage counts, even if the damage looks cosmetic at first. Bumper damage, side guards, lights, spray suppression, mirrors and bodywork can all affect roadworthiness or stop the vehicle being used in the way you intended. If the unit is at a bodyshop, or waiting estimate approval, that is downtime for planning purposes.
Driver-reported defects count as soon as they affect availability or need workshop attention beyond routine scheduling. A blown bulb may be sorted immediately. A steering complaint, air leak, AdBlue fault, tail-lift issue or tachograph problem may take the vehicle out of service, or at least out of planned use, until assessed.
Vehicles stood down from use also count, even where there is no active defect. Seasonal vehicles, spare units, trailers not currently allocated, and vehicles parked because there is no driver should all be clearly marked. Otherwise the planner treats them as available assets and starts building bookings around them. If they are not being used, somebody still needs to decide what happens to their PMI cycle, battery care, tyre checks and MOT timing.
The key point is this. Downtime is not just "in the workshop". It includes any period where normal use has stopped, expected mileage has changed, or maintenance timing needs review.
How to update PMI and service schedules when a vehicle stops
The safest method is to separate three things. The confirmed PMI interval. The expected service mileage. The booking date currently in the diary. They are linked, but they are not the same thing.
When a vehicle stops, first record the downtime start date and reason. Be specific. "Off road" is too vague. "Awaiting front brake chamber", "MOT fail on emissions", "accident damage, bodyshop", or "driver defect, air leak under investigation" tells you what is happening and who is likely to control the next step.
Second, check whether the vehicle is still moving at all. Some downtime is total. Some is partial. A vehicle may be restricted to local work, shunting, or internal yard use only. That matters because mileage forecasts should only be revised if the actual usage has changed.
Third, review the next PMI due date against your declared inspection frequency. In the UK, you do not simply push a PMI back because the vehicle has stopped. If your system is six weekly, eight weekly or another fixed interval justified by your maintenance arrangements, you keep control of that interval. If the vehicle is likely to remain off the road past the planned date, book the inspection while it is off the road if possible, or formally reschedule it with a recorded reason and approval. What you must not do is let the date pass silently and pretend the downtime itself was the inspection.
Fourth, revise service mileage expectations separately. If the vehicle has done far fewer miles than forecast because it has been parked for ten days, the next service trigger may move. That is fine, provided the time-based controls stay intact and the change is recorded. This is where people get caught out. They treat all maintenance as mileage-led, then end up stretching time-based inspections without meaning to.
Fifth, update the booking board. Cancelled and deferred are not the same. If next Thursday's PMI slot is no longer realistic because the vehicle is at a dealer, take it out of the live workshop loading and give it a new status. If the inspection will still happen, but on the dealer site or when the vehicle returns, note that clearly. A booking that remains in the diary after it has become impossible is how missed work gets hidden.
A practical rule helps here. Every vehicle should always have one clear next action. PMI booked. Awaiting parts. Awaiting dealer report. Ready for retest. Returned to service. If the next action is unclear, the schedule will drift.
How to stop workshop bookings and fleet availability drifting apart
This is where most plans fail. The maintenance planner says one thing. The workshop diary says another. Operations has promised the vehicle to a job based on a third version.
To stop that, we keep one live status for the vehicle and use it everywhere. If a job overruns, the overrun has to move three things at once. The expected finish date. The workshop resources tied up on the job. The date the vehicle becomes available to traffic again.
Bay time is the first pressure point. If a vehicle booked for half a day turns into a two day repair, that bay has gone. The planner needs to reflect that before somebody else drives in for a PMI with nowhere to put the vehicle. The same goes for mobile fitters and subcontract work. If labour is committed elsewhere, the diary must show it.
Parts are the second pressure point. A booking without parts is often not a booking at all. If a vehicle is waiting on stock, mark it as waiting on stock. Do not leave it shown as workshop-ready. That one bad assumption cascades into wasted labour and missed inspection slots.
Vehicle availability is the third pressure point. Transport should not be working from an old return date. If the workshop says "probably Thursday" but parts are not due until Wednesday afternoon, the planner should not show the unit available Thursday morning. Build in the actual handover point, including road test, paperwork and defect sign-off.
This is where workshop-led systems earn their keep. We built ours from running Woolpit Truck Repairs, not from guessing how a workshop might behave. The planning problem is not just dates on a calendar. It is the link between defect reporting, booked work, completed work and actual return to service. If you want to see how we approach that, our piece on workshop software that keeps fleets roadworthy goes into it in more detail.
One more point. Do not hide overrun jobs by moving the planned finish date after the event. Keep the original booking, record the slippage, and show why it changed. That gives you a proper history and helps if patterns start appearing with certain vehicles, suppliers or job types.
What records you need for DVSA and the Traffic Commissioner
If maintenance dates move, keep enough evidence to show that the move was controlled, justified and completed. That matters for DVSA visits, and it matters if the Traffic Commissioner ever asks how your maintenance system is run.
At minimum, keep these records:
- The original planned date for the PMI, service, MOT preparation or repair
- The reason the date changed
- The date the change was made
- Who made or approved the change
- The vehicle status during the downtime
- Any supporting documents, such as defect reports, dealer job cards, parts delays, recovery notes, MOT failure sheet or accident documentation
- The revised booking date
- The completion date and completed work details
- Evidence that the vehicle was returned to service only after the relevant work was done
For a PMI move, the record should show how the revised plan still sits within your maintenance control, or why the exceptional change was necessary. For a service move, it should show the mileage logic as well as the date logic. For an MOT failure, keep the fail sheet, repair records and retest outcome together.
This is not just box ticking. If an examiner sees a gap in the inspection history, they will want to know what happened. If your answer is "the vehicle was off the road somewhere", that is not enough. You need the chain of events. When did it stop? Why? Who knew? What was moved? When was the work completed? When did it go back into use?
The same applies to defect reporting. If a driver reports a problem and the vehicle is stood down, the maintenance record should link back to that report. If the tachograph develops a fault that affects legal use, the vehicle status and repair action need to be visible in the same system of control, not hidden in emails.
Good records also protect you when the issue is not your fault. Dealers delay. Parts do not arrive. Bodyshops overrun. If your records show prompt action, clear decisions and proper stand-down controls, that is far better than a blank space followed by a late inspection.
If you are tightening up the basics across a small fleet, our article on protecting your O-licence through HGV upkeep covers the wider compliance picture around this.
A simple weekly routine that keeps the plan accurate
The routine does not need to be complicated. It does need to happen every week, on the same day, with the same checks.
Start with every vehicle currently in downtime. One by one, confirm:
- Why it is off the road
- Whether that reason has changed
- Whether parts, dealer input or outside approvals are still outstanding
- Whether the expected return date is still realistic
- Whether the next PMI, service or MOT booking is still valid
Then review every vehicle due a PMI or preventative maintenance inspection in the next four weeks. Check the booking exists. Check the vehicle is expected to be available. Check any known downtime has been reflected. If a vehicle is currently stood down, decide now whether the inspection will be carried out during downtime, moved with approval, or replaced with another slot.
Next, review MOT dates and prep bookings. MOT problems often start with assumptions. Somebody thinks the test is "a while off". Then a vehicle spends two weeks away with accident damage and suddenly the prep slot has vanished. Keep MOT planning visible every week.
After that, review open driver defects. Not every defect creates downtime, but many become downtime because they sit unresolved. A defect that looked minor on Monday may be the reason a vehicle misses its Friday booking.
Then compare workshop capacity against the live job list. Bays, fitters, parts and subcontract work. If two jobs have overrun, do not wait for the week to fix itself. Rebook the affected work while there is still time to warn operations.
Finish with a short sign-off. Who reviewed the list, what changed, and what is now the next action for each affected vehicle. That note matters because it shows active control, not passive hope.
For fleets in the five to one hundred vehicle bracket, this routine is often the difference between a plan that works and one that only looks tidy on screen. Once you get beyond a handful of vehicles, memory stops being a system. If you are still trying to run maintenance, defects and bookings from disconnected sheets, our guide on keeping 10 lorries compliant without missing anything is a good place to start.
Downtime will always happen. Breakdowns, MOT failures, parts delays and accident repairs are normal. What matters is whether your maintenance planner treats those events as live control points. If it does, your PMI schedule stays credible, your workshop loading stays honest, and your roadworthiness decisions stay defensible. If it does not, the plan becomes fiction long before anybody notices.
Should a vehicle's PMI date move if it has been off the road?
Sometimes, but not by guesswork. Any change needs to fit the operator’s maintenance system, the vehicle’s actual use and a clear record of why the date moved.
Is mileage-based planning enough on its own?
No. Mileage helps, but it misses parked vehicles, stop-start use and defect history. Use mileage with fixed dates, downtime status and workshop findings.
What is the biggest planning mistake during downtime?
Leaving the original booking in place while the vehicle status has changed. That creates false availability, missed bay time and late maintenance decisions.
Do I need to record downtime reasons in detail?
Yes. 'Off road' is too vague. Record whether it was a breakdown, parts delay, MOT issue, accident damage or another specific cause.
Who should own downtime updates?
One named person should own the update, even if drivers, fitters and planners all feed information in. Shared responsibility usually means nobody changes the plan properly.
