Fleeta Limited: fleet technology with a real workshop foundation
+44 (0) 1284 844114
← Back to all articles

How MOT and planned maintenance work together

A practical guide to how MOT and planned maintenance fit together for UK HGV operators, workshops and O-licence holders.

How MOT and planned maintenance work together

If you run HGVs or PSVs in the UK, the MOT and your maintenance system do different jobs. One is a statutory annual test. The other is the routine control that keeps vehicles fit between tests and proves you are managing roadworthiness properly under your O-licence. Confusing the two is where trouble starts.

A pass at MOT time matters, but it does not rescue weak maintenance planning, missed PMI dates, poor defect control or patchy records. Good operators treat the MOT as one checkpoint inside a wider maintenance plan, not as the plan itself. That is the practical link between MOT and planned maintenance.

Why MOT is not the same as planned maintenance

The annual MOT test tells you whether the vehicle met the required standard on the day it was presented. That is all. It is not a substitute for an inspection programme, and it is not evidence that the vehicle has been maintained properly all year.

Under the UK operator licensing regime, you are expected to keep commercial vehicles in a fit and serviceable condition at all times. That means scheduled inspections, defect reporting, repair control and records. For most operators, that centres on the PMI, often called a preventative maintenance inspection, at a frequency that matches the age, mileage, load and operating conditions of the vehicle.

That distinction matters because the MOT is a point-in-time event, while planned maintenance is continuous. A vehicle can pass its MOT and still have had overdue inspections, repeated defects, weak brake performance trends or repairs delayed longer than they should have been. If DVSA looks at your systems, they are not only interested in whether the certificate exists. They want to see how you keep the vehicle roadworthy between certificates.

This is also where UK rules need stating clearly. In the EU generally, roadworthiness testing and operator compliance frameworks vary by country. In Great Britain, the combination of annual test requirements, O-licence undertakings, DVSA enforcement and the role of the Traffic Commissioner creates a very specific expectation. You must be able to show a maintenance system that is planned, followed and evidenced.

For HGV operators, that usually means a documented inspection schedule for at least six months ahead, with each vehicle allocated inspection dates. Those dates must be realistic. If a unit is due every six weeks, then every six weeks means every six weeks, unless there is a properly managed reason to bring it in earlier. Letting it drift because the truck was busy is not a system. It is how small gaps become a public inquiry problem.

So when people talk about MOT planned maintenance as if they are one thing, we think it helps to separate the roles. The MOT is the annual legal test. Planned maintenance is the discipline that keeps you compliant all year and supports the annual test result.

What DVSA expects to see from an operator

DVSA expects evidence, not intentions. If you say your vehicles are inspected every eight weeks, there should be a forward planner showing those dates, inspection sheets showing they happened, repair records showing defects were dealt with, and daily reporting that catches issues between workshop visits.

At a practical level, operators should expect to produce the following.

First, a maintenance planner. This should show each vehicle, the planned PMI dates, and enough forward visibility to demonstrate that maintenance is actually planned. Six months ahead is the usual benchmark people work to under an O-licence.

Second, completed inspection records. A PMI sheet should show the inspection date, vehicle details, odometer reading, what was checked, what defects were found, and who carried out the inspection. If work was outsourced, the provider’s paperwork still needs to be complete and retained by you. Outsourcing the workshop does not outsource the responsibility.

Third, evidence of rectification. If an inspection found defects, there should be a repair record, job card, invoice, technician notes or another clear document showing what was done and when. Where defects are safety related, the records should make it obvious that the vehicle was not returned to service before repair.

Fourth, driver defect reporting. Daily walkaround checks matter. The exact form can vary, paper or digital, but the process must be real. Nil defect reporting is still reporting. If drivers only fill something in when they spot a problem, you create a hole in your evidence.

Fifth, records for items with their own compliance rhythm, such as brake testing, tachograph inspections and calibrations, and any other scheduled checks your operation requires. Those records need to sit alongside the rest of the vehicle history, not in three different drawers and somebody’s inbox.

DVSA will also look at whether the system makes sense. If your planner says six weekly inspections but the paperwork shows repeated seven or eight week gaps, the written interval means very little. If the same defect appears over and over, that points to weak repair quality or weak follow-up. If vehicles are off the road, sold, hired out or standing in the yard, the planner still needs to reflect reality.

OCRS is part of the background here as well. Roadside encounters, prohibitions and test results can all feed into how your operation is viewed. A weak maintenance system does not stay hidden for long if it starts showing up in MOT outcomes, encounter history or missed inspection patterns.

If you want a clearer picture of the paperwork side, we have set out how to prove maintenance was planned for a DVSA visit in more detail.

How to build maintenance around the MOT date

The MOT due date is useful, but only if you treat it as one anchor point in the year. We see operators get better results when they build the maintenance plan around it rather than racing toward it.

Start by plotting the MOT expiry date for every vehicle and trailer. Then work backwards. Allow time for a pre-test inspection, any repairs, a retest if needed, and the booking itself. If you leave presentation until the last minute, a failure becomes an operational problem instead of a workshop job.

In practice, we prefer the pre-MOT inspection to happen early enough that defects can be repaired without wrecking the traffic plan. That sounds obvious, but many fleets still bring a vehicle in just before test day and hope. Hope is not a maintenance process.

The next step is to keep the normal PMI cycle intact. Do not suspend routine inspections because the MOT is coming up. If a vehicle is on a six week cycle, it stays on a six week cycle. The annual test is additional. Sometimes the dates will sit close together, and you can sensibly coordinate workshop time, but the PMI interval should still be met.

A workable way to plan it is this:

  • fix the annual MOT date
  • schedule a pre-MOT workshop inspection before that date
  • keep the regular preventative maintenance inspection dates running through the year
  • add any brake test or specialist checks required by your maintenance policy
  • review the plan whenever mileage or operating conditions change

That last point is often missed. Inspection frequency is not supposed to be arbitrary. A vehicle doing hard urban stop-start work may need a different regime from one doing lighter trunking. If the operation changes, the maintenance interval may need to change with it.

For small and mid-sized fleets, this is where a proper planner earns its keep. You need to see the MOT, the PMI cycle, defects awaiting parts, booked workshop slots and vehicle availability in one place. If you are trying to do that with wall charts, spreadsheets and memory, it works until it suddenly does not.

We wrote separately about fleet software that stops maintenance getting missed, because the real issue is not software for its own sake. It is making sure dates do not slip when the phone is ringing and three vehicles are due in the same week.

Where small fleets usually come unstuck

Small fleets rarely fail because nobody cares. They fail because the system depends on one busy person remembering too much.

The most common problem is missed PMI dates. Not by months, usually. By a few days here, a week there, then a pattern. Somebody thinks the truck was away. Somebody else thinks the workshop moved it. The inspection gets done eventually, but the evidence now shows the planner was not followed.

The second problem is poor paperwork. The inspection happened, the fitter did the work, the defects were sorted, but the sheet is incomplete or missing. No registration. No odometer. No sign-off. No record of rectification. In a DVSA check, an undocumented job may as well not have happened.

The third is delayed repairs. This is especially common with non-safety items that become normalised. A marker lamp, then a warning light, then tyre wear noted for monitoring, then a brake imbalance that gets pushed to next week because the truck is needed. Not every defect requires immediate prohibition of the vehicle, but every defect needs a decision, a record and follow-through.

Another regular failure is treating a MOT pass as proof that everything is fine. It is not. A vehicle can pass and still expose weaknesses in the maintenance system behind it. We have seen fleets with acceptable test outcomes but poor control over intervals, defect reporting and filing. That is still a compliance risk.

There is also the off-road trap. A vehicle goes off the road for a few weeks, perhaps after an accident, a driver shortage or a quiet period. The operator assumes the maintenance clock stops by itself. It does not, unless you actively manage the plan and document the status. Bringing a vehicle back into service after a period off-road should trigger a review, not a shrug.

Then there is split information. Defects on WhatsApp. PMI sheets in a folder. MOT bookings on a wall calendar. Repair invoices in accounts. tachograph dates in somebody’s email. When DVSA asks for evidence, the problem is not always that the work was not done. It is that nobody can assemble the story quickly and cleanly.

That is why so many operators eventually move away from spreadsheet-heavy systems. The issue is not sophistication. It is reliability. We covered that in small-fleet maintenance records without spreadsheet risk because this is exactly the point where growing fleets feel the strain.

What a workable system looks like in practice

A workable system is boring in the right way. Dates are booked ahead. Inspections happen when planned. Defects are recorded once, clearly. Repairs are signed off. Evidence stays together. Nobody needs to reconstruct the history from memory.

From a workshop-led point of view, the process should look something like this.

The vehicle is on a live planner with its next PMI date, MOT date and any other scheduled events already entered. The planner is reviewed every week, not only when something is overdue. Workshop capacity is matched against upcoming inspections so the bookings are real.

Before the vehicle comes in, the workshop knows what is due. That may include the routine preventative maintenance inspection, a brake test, MOT preparation, outstanding defects from driver reports, and any repeat advisories being monitored. If the truck has had recurring issues, the technician should see that history before starting.

When the vehicle arrives, the inspection is carried out on a proper sheet or digital job. Registration, fleet number, date, mileage, inspector and checklist all need to be there. If defects are found, they are recorded in a way that distinguishes safety critical items from routine repairs. Vague notes help nobody later.

Repairs then move into a controlled job process. Parts ordered, labour recorded, work completed, sign-off done. If the vehicle cannot be fully repaired the same day, there needs to be a clear decision about whether it is fit to return to service, what restrictions apply, and when the remaining work is booked. This is where workshop discipline matters more than software screens.

Driver-reported defects should feed into the same record, not live separately forever. If a driver reported a lamp out on Monday and the vehicle has a PMI on Wednesday, the workshop should see both in one place. The same applies to trailer defects. Too many systems treat trailers as second-class records until they become the reason for a prohibition.

For MOT preparation, the workshop should inspect against likely test failure points and resolve issues before presentation. After the test, the certificate, failure sheet if there was one, and rectification evidence should sit with the rest of the vehicle history. The MOT result belongs in the same story as the PMIs and repairs, not in a separate admin silo.

Finally, records need to be retrievable. Not eventually. Quickly. If DVSA visits, or if you need to answer a question from the Traffic Commissioner, you should be able to produce the planner, inspection history, defect reports and rectification evidence without a half-day search.

That is the thinking behind our own systems. We came at this from running Woolpit Truck Repairs, not from drawing ideal workflows on a whiteboard. In a working HGV workshop, the hard part is not describing a perfect process. It is keeping control when vehicles move, bookings shift, parts are late and the phone never stops. The maintenance system has to reflect that reality.

If you are reviewing your own setup, start with a simple question. Could you show, for any vehicle in the fleet, what was planned, what was found, what was fixed and why it was safe to run? If the answer is not immediate, that is where to tighten the process first.

MOT and planned maintenance work together best when each is used for what it is. The MOT confirms the vehicle met the test standard on the day. Planned maintenance is what keeps the vehicle roadworthy every other day. Under an O-licence, you need both, and you need the records to prove it.

Does a passed MOT prove my maintenance system is good enough?

No. A passed MOT helps, but it does not prove your maintenance arrangements are effective. DVSA can still question missed PMI intervals, poor repair control, weak defect reporting or incomplete records.

Can I plan maintenance just around the annual MOT?

No. The MOT is one annual test point. Vehicles on an O-licence still need regular preventative maintenance inspection intervals that match their use, age, mileage and operating conditions.

How do MOT failures affect my O-licence risk?

Repeated failures, especially for roadworthiness items, can feed into OCRS and attract DVSA attention. One failure is not the whole story, but patterns matter.

Should PMI and MOT preparation be separate jobs?

They can be separate bookings, but they should not be separate systems. The same records, defect history and repair control should support both.

What records should I keep for maintenance and MOTs?

Keep inspection sheets, repair records, safety defect reports, evidence of rectification, brake performance records where required, and MOT history. Records need to be complete and easy to produce.