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

HGV upkeep that protects your O-licence

A practical guide to HGV maintenance for UK operators: PMI, defect reporting, MOT prep and records that stand up to DVSA scrutiny.

HGV upkeep that protects your O-licence

Good HGV maintenance protects your O-licence because it proves control. Not control in a policy folder, but control in the real sense, vehicles inspected when they should be, defects reported properly, repairs completed before the vehicle goes back out, and records that show the whole chain from fault to rectification.

That matters because DVSA and the Traffic Commissioner do not judge maintenance by what you intended to do. They look at what actually happened. If a vehicle is found with defects at the roadside, if PMIs are missed, or if your paperwork does not show follow-up, the problem is not just a repair bill. It becomes a question of roadworthiness, systems, and whether you are meeting the undertakings behind your O-licence.

What good HGV maintenance actually means

In UK operator terms, HGV maintenance is not just fixing things when they break. It is the full system that keeps a vehicle and trailer fit for service at all times.

That system has a few parts.

First, scheduled inspection work. For most operators this means a regular PMI cycle, with each preventative maintenance inspection carried out to a set standard, with the results recorded. That inspection has to be thorough enough to pick up wear, damage and developing faults before they become prohibitions, MOT failures or roadside defects.

Second, repair control. Finding a fault is only half the job. Good maintenance means deciding whether the vehicle is safe to use, raising the work, getting it repaired, checking the repair has actually been done, and keeping evidence of that. A defect sheet with no repair record behind it is not maintenance control.

Third, daily condition monitoring. Roadworthiness is not something a workshop restores every six weeks and then forgets about. Drivers have to carry out walkaround checks, report defects clearly, and understand when a vehicle must not move until repaired.

Fourth, records. You need a maintenance history for each unit and trailer that shows inspection dates, findings, repairs, brake results, MOT outcomes and any follow-up. If DVSA asks how you know a vehicle was roadworthy on a given date, your file should answer the question without guesswork.

This is where operators often oversimplify the job. They think maintenance means booking the truck into a workshop every so often. It does not. A vehicle can attend every PMI on time and still leave you exposed if the inspection quality is poor, defects are vague, brake performance is not being checked, or repairs drift.

The UK approach is also more specific than a general EU view of fleet servicing. Here, the O-licence system puts clear responsibility on the operator to keep vehicles and trailers fit and serviceable. That responsibility sits with us, even if we use an external workshop. Outsourcing the work does not outsource the duty.

How to set a maintenance system that fits your fleet

A maintenance system has to match the work the fleet actually does. The right interval for a lightly used rigid on local work may be wrong for an artic doing heavy mileage on trunking, and wrong again for a tipper or vehicle working in dirt, tight sites and stop-start conditions.

The starting point is the inspection frequency. In practice, operators usually work to a set number of weeks between PMIs, but that interval should be based on use, not habit. Mileage matters. So do load weights, route type, terrain, trailer use, seasonal peaks and vehicle age.

A few examples make the point.

A newer unit on steady motorway work, with predictable mileage and good driver reporting, may support a longer interval than an older vehicle doing mixed work with repeated urban braking and kerbing. A trailer on occasional use is still part of the maintenance system, but the programme may differ from one in daily service. A vehicle working at or near maximum weights will generally need closer attention than one doing lighter work.

The mistake is picking one interval for the whole fleet because it is easy to remember. Simple is helpful, but only if it still reflects reality.

The second part is the content of the inspection. A preventative maintenance inspection is not just a service. It is a structured roadworthiness check. The sheet used matters. It should cover the items that need inspection, prompt the technician to record findings properly, and leave no doubt about whether defects were advisory, requiring repair, or requiring the vehicle to be stopped.

Brake performance deserves special attention. We have seen plenty of fleets with tidy PMI schedules and weak brake evidence. That is a bad combination. DVSA will expect to see that braking performance is being monitored properly, whether by laden roller brake testing where appropriate, decelerometer results where suitable, or other recorded evidence that matches the operation and vehicle type. A tick box saying brakes checked is not enough on its own.

You also need workshop capacity that matches the promise made in the planner. If you schedule inspections every six weeks but the workshop is always full, the plan is fiction. This is one of the reasons we built our systems around the workshop first. Planning only helps if the workshop can see what is coming, reserve time, and deal with the repairs the inspection creates. If you want a practical view of that side of the job, our guide on which HGV maintenance planner actually holds up under DVSA goes into the detail.

For mixed fleets, the best system is usually one that sets standard rules, then allows exceptions where the operation justifies them. Keep the logic clear. If one vehicle is on a shorter cycle, there should be an obvious reason.

What has to happen between PMIs

Most maintenance failures do not start in the workshop. They start in the weeks between inspections, when a defect is noticed, half reported, or ignored.

The daily walkaround check is the first control. It needs to happen before use, and it needs to be more than a signature. Drivers should know what they are looking for, what counts as a safety defect, and what to do next. Tyres, lights, body security, fluid leaks, brake warnings, steering feel, mirrors, reflectors, coupling security, load security equipment and trailer condition all matter. So does anything unusual picked up during driving.

Defect reporting then has to be usable. “Brakes bad” is not a useful report. “Nearside rear brake binding when reversing, wheel hot after run” is. Vague reports waste workshop time and lead to poor decisions. A driver should be able to say what the fault is, where it is, and when it happens.

Once reported, someone has to decide whether the vehicle can continue in service. That decision cannot drift. If the defect affects roadworthiness, the vehicle stays off the road until rectified. If it is minor and can be deferred, that should still be controlled, dated and followed through. Open defects that live on scraps of paper are where fleets come unstuck.

Brake performance monitoring also sits between PMIs, not just during them. If drivers report pulling, poor response, overheating or unusual feel, that needs proper investigation. If a vehicle’s use changes, for example heavier work or different trailers, the maintenance regime may need adjusting. Brake issues are one of the quickest ways to move from a workshop matter to an OCRS problem.

Communication matters more than software here. A driver who thinks reporting defects will get them blamed often says as little as possible. A fitter who writes notes no one reads might as well not write them. A transport office that does not close the loop with the workshop creates the same risk. The system works only when each handoff is clear.

Tachograph records can help with context too. They are not maintenance records, but they can support the picture of vehicle use, mileage and scheduling, especially where actual use has drifted from the assumptions behind the inspection interval.

What DVSA will expect to see on paper

When DVSA looks at maintenance, they are looking for evidence of control, not just evidence that forms exist.

At a minimum, each vehicle and trailer should have a clear maintenance file. That usually includes the planned PMI schedule, completed inspection sheets, repair records, brake test results where relevant, MOT history, reported defects, and evidence that defects were rectified.

The key point is linkage. If a PMI sheet records a defect, there should be a job card, invoice, workshop sheet or other repair evidence behind it. If the defect was deferred, there should be a reason and a later record showing completion. If a vehicle missed an inspection date, there should be an explanation, and it should be the exception, not the normal pattern.

Dates matter. Mileage matters. Vehicle identity matters. Registration, fleet number, trailer number and inspection date should match across the records. If one sheet says the vehicle was inspected on Tuesday, another says repaired on Monday, and a third has no unit number at all, the file stops being persuasive.

You should also be able to show who did the inspection and what standard they worked to. That applies whether the work is done in house or by an external provider. If you use an outside workshop, keep the agreements, booking records and completed documents. “The garage has all that” is not a defence if DVSA asks the operator.

For a maintenance investigation or site visit, DVSA will often look for trends. Are inspection intervals being kept? Are the same defects repeating? Are brake issues being measured and acted on? Are driver defect reports feeding into the repair process? Are MOT failures linked back into maintenance changes?

This is why audit-ready records are more than filing. They need to tell a coherent story. We covered that in more detail in which maintenance records stand up in a DVSA audit and in our guide on how to show maintenance control for your O-licence.

Where operators usually come unstuck

The most common failure is not dramatic. It is drift.

A PMI due this week gets pushed to next week because the truck is busy. Then another one slips because there is no spare slot. After that, the planner still looks tidy because someone intends to catch up. On paper, the system exists. In reality, control has gone.

The next common problem is poor paperwork. Inspection sheets with boxes ticked and no meaningful notes. Defect reports that do not identify the vehicle properly. Repair history split between the workshop wall, an email thread and a pile of invoices. If a Traffic Commissioner asks what happened, the answer should not depend on who still remembers.

Small and mid-sized fleets often struggle with role overlap. The same person may be transport manager, planner, customer contact and the one chasing the workshop. That is normal. But it means maintenance follow-up gets squeezed by urgent traffic work. The truck that needs a completed brake report competes with the load that needs covering by 4 pm.

Another weak point is overloaded workshops, internal or external. If the workshop is constantly firefighting, preventative work suffers first. PMIs become rushed. Advisory items are not followed up. MOT preparation gets left until the booking is close, then everyone acts surprised when a failure creates downtime that could have been avoided.

Defect quality is another repeat issue. Drivers write too little. Workshops write too little. Managers accept too little. If a defect says “light out” and nothing else, was it repaired, was it wiring, was it repeated, was the vehicle used before repair? You cannot answer those questions later unless the record is good at the time.

Trailer control is often weaker than unit control. Operators know where the trucks are. Trailers can be less visible, especially in shared yards, seasonal peaks or subcontracted work. Yet the same roadworthiness duty applies. A missed trailer inspection is still a missed inspection.

Finally, some operators rely too heavily on MOT pass rates as proof the system works. MOT is important, but it is only one point in the year. A vehicle can pass MOT and still have weak maintenance control the rest of the time. DVSA knows the difference.

When software helps and when it does not

Software helps when it supports the real maintenance process. It helps with planning inspection dates, flagging units and trailers due in, tracking defects to completion, storing brake results, and keeping an audit trail that can be retrieved quickly when DVSA asks.

It also helps with visibility. A good workshop-led system makes it obvious which vehicles are due, which are overdue, which defects are still open, and which records are missing. That sounds basic, but once a fleet gets beyond a handful of vehicles, those gaps stop being visible on a whiteboard or spreadsheet.

This is exactly why we built operator compliance software for maintenance evidence and audit trails. It came from running a working HGV workshop at Woolpit Truck Repairs and dealing with the paperwork, planning pressure and follow-up ourselves. The software was shaped by the jobs that actually get missed when the phone does not stop ringing.

But software does not fix weak discipline.

If drivers do not carry out proper checks, the system will store poor defect reports more neatly. If the workshop rushes PMIs, the planner will show punctual inspections with weak content behind them. If management does not act on overdue work, alerts become wallpaper.

That is the hard truth. No system can create maintenance control where the operation itself does not support it.

The best results come when the software matches the workshop and the office, not when it tries to replace either one. A fitter needs inspection sheets that are practical to complete properly. A transport manager needs a live view of what is due and what is still open. The responsible person on the O-licence needs records that stand up months later, not just on the day they were entered.

So yes, software helps. It helps a lot when the basics are already taken seriously. It gives structure, reminders, traceability and evidence. It reduces the chance of missed dates and lost paperwork. It makes DVSA visits less painful because the file is there.

What it cannot do is care more about roadworthiness than the operator does.

If you want HGV maintenance that protects your O-licence, start with the workshop standard, the reporting standard and the follow-through. Then use software to make those standards visible and repeatable. That order matters. It is the difference between a system that looks compliant and one that actually is.

How often should an HGV have a PMI?

There is no single interval that suits every fleet. The schedule must be appropriate for the vehicle, trailer, work, mileage, age and operating conditions, and it must keep the vehicle roadworthy.

Is a daily walkaround check part of HGV maintenance?

Yes. A maintenance system is not only workshop work. Daily checks, defect reporting and prompt rectification are part of how an operator keeps vehicles safe and roadworthy.

What records should an operator keep?

Keep PMI sheets, repair records, defect reports, evidence defects were fixed, MOT history and any supporting brake performance records. The point is to show proper control of roadworthiness.

Can I rely on MOT pass rates to prove maintenance is good?

No. A pass helps, but it is not the whole picture. DVSA will look at the full maintenance system, including inspection quality, defect handling, timing and record keeping.

Do trailers need the same maintenance control as units?

Yes. Trailers need planned inspections, defect reporting, repairs and records in the same way. They can damage OCRS and create O-licence risk just as quickly as units.