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

Keep HGV annual tests from wrecking your maintenance plan

A practical guide to planning HGV annual tests, repairs and workshop time without losing control of PMI schedules, roadworthiness or uptime.

Keep HGV annual tests from wrecking your maintenance plan

Annual test season only becomes chaos when it is treated as a single appointment instead of a maintenance event with knock-on effects. The practical way to manage annual test preparation and repairs for an HGV fleet is to start from the booked test date, work backwards into fixed workshop slots, and decide early what work must be done before presentation and what can wait for the next planned stop. If you leave that thinking until the vehicle is on the brake rollers failing on imbalance, one defect quickly turns into three missed jobs somewhere else.

We see this from both sides. We run Woolpit Truck Repairs, so we deal with the workshop reality of annual tests, retests, parts delays and squeezed labour hours. We also build the systems we use ourselves. That matters, because the hard part is not knowing that a vehicle needs a test. The hard part is keeping the rest of the fleet on plan while you get that vehicle through the test properly and keep your records in shape for DVSA and your O-licence.

Start with the annual test date and plan backwards

The annual test date is the anchor. Everything else should be scheduled back from it.

For most operators, the mistake is booking the MOT and assuming the workshop will absorb the rest. It will not. A workable plan needs at least four separate decisions.

First, confirm the test booking early enough to control your options. If the vehicle is going to a DVSA test station or an Authorised Testing Facility, you need a date and time that fit the vehicle's work, driver cover and workshop capacity. If you leave the booking late, you usually lose the useful slots and end up forcing the vehicle in at the wrong point in the maintenance cycle.

Second, reserve a dedicated pre-test inspection slot. Not a general look-over, and not "we'll do it during the PMI". The pre-test needs its own booked time, usually around 10 to 14 days before the test for a straightforward vehicle. That gives enough time to identify defects, order parts and still have room for repairs without pushing against the test date. For older vehicles, trailers with known issues, or anything with a recent brake concern, we would want a longer gap.

Third, account for parts lead time before you need the parts, not after you find the defect. Some items are easy. Lamps, wiper blades, markers and common brake components are usually manageable. Others are not. ABS or EBS components, steering parts, body mounts, exhaust aftertreatment sensors, tachograph related items, or manufacturer-specific electrical parts can leave a vehicle waiting. If a vehicle has known wear items nearing limit, it often makes sense to order likely parts in advance of the pre-test slot, or at least confirm availability.

Fourth, build in contingency. A plan with no spare capacity is not a plan. It is hope. We normally want at least one spare workshop slot between the pre-test inspection and the test date. That slot is there for whatever turns up, brake imbalance, kingpin wear, headlamp aim, air leaks, cracked spring leaves, tyre damage, body security, or a warning light that was not on last week.

A simple backwards plan often looks like this:

  • Test date booked for Friday
  • Final wash and driver defect check on Thursday
  • Repair contingency slot on Wednesday
  • Main repair slot on Monday or Tuesday
  • Pre-test inspection and brake assessment the previous week
  • Parts ordered immediately after inspection, or pre-ordered for known risks

That is the shape. The exact dates depend on your operation.

This is also where operators get caught by trying to combine everything into the nearest preventative maintenance inspection. A PMI is part of the picture, but the annual test date should still drive the timetable. If the vehicle's PMI falls six weeks before test, that PMI alone is not enough. If it falls two days before test, that can be too tight if defects are found.

If you run five to twenty vehicles, one failed annual test can consume a large share of workshop attention for the week. If you run closer to a hundred, the issue changes. The risk is not one vehicle. It is several annual tests clustering in the same month and competing with PMIs, LOLER work, tyre jobs and normal breakdown repairs. That is where a visible forward schedule matters. We built our operator compliance software for maintenance planning and test control around that exact problem, because a spreadsheet rarely shows the real pressure on workshop days until you are already short.

What should be checked before the vehicle goes for test?

A proper pre-test inspection is not just a normal service with a different name. The aim is different. A preventative maintenance inspection is there to keep the vehicle roadworthy through its operating period. A pre-test inspection is there to present the vehicle for annual test with as little risk as possible of failure, advisory overload or immediate retest work.

That means the pre-test needs to focus hard on testable items and on anything likely to fail under formal examination.

Brakes are first. Not just lining thickness or visible condition. You need brake performance confidence. Service brake balance, parking brake effectiveness, axle performance, signs of contamination, adjustment issues, air leaks, warning lamps and response times all matter. If you have roller brake test access, use it before annual test, not only after a failure. We have written separately about brake roller test failures and avoiding repeat retest waste, because this is one of the biggest causes of avoidable disruption.

Tyres need more than a tread glance. Check tread depth across the full width, sidewall damage, cuts, cords, exposed belt, valve condition, matching fitment where required, and any irregular wear that points to alignment, suspension or brake issues.

Steering and suspension need to be checked for wear, movement and security. That means kingpins, track rod ends, drag links, bushes, spring condition, U-bolts, air suspension components, shock absorbers where fitted, and any signs of chassis or mounting damage. Test failures here are often not surprises. They are defects that have been tolerated for too long.

Lights and electrics sound simple until they are not. Full lamp operation, warning lights, reflectors, side markers, number plate lamps, beacon operation where relevant, and headlamp aim all need checking. Electrical defects often multiply once you start. Corrosion in connectors, poor earths, trailer socket faults and previous repair quality all show up at the wrong time if you leave them.

Visibility items matter more than some operators allow for. Windscreen condition in the swept area, wiper operation, washer function, mirror security, camera systems where fitted, and seat belt condition all need proper attention.

Body and structure checks are another area where a normal PMI may not go as far as a pre-test should. Body security, floor condition, spray suppression, sideguards, rear under-run protection, door catches, load security equipment mounts and registration plates all need checking against test expectations. On tippers, skip loaders and specialist bodies, body operation and safety devices can create extra failure points.

Then there is the cab side. Driver's seat security, horn, speed limiter where relevant, dashboard warning lamps, tachograph installation condition, and any obvious signs that the vehicle is not being kept under control. The annual test is not a tachograph calibration exercise, but a visibly poor installation or associated defect can still raise questions.

The difference from a standard preventative maintenance inspection is depth and focus. A PMI is scheduled around the maintenance contract or inspection frequency set for the fleet. It follows your inspection sheet and roadworthiness system. A pre-test inspection should be more ruthless. It is less about "monitor and review next inspection" and more about "would we present this vehicle like this next week". That is a different standard of decision-making.

How do you handle repairs without breaking the rest of the fleet plan?

This is where good intentions usually fail. The vehicle comes back from pre-test with a defect list, everyone piles onto it, and suddenly two PMIs slip, one trailer is still waiting outside, and the technician who should be doing scheduled work is chasing a wiring fault on a unit due at test tomorrow.

The answer is not to treat every annual test repair as an emergency. The answer is to classify the work properly and control capacity.

We split annual test related repairs into three groups.

First, fail-critical items that must be done before presentation. Brake performance defects, steering wear, tyre defects, insecure body components, lighting faults, structural concerns, air leaks affecting brake operation, and anything else that would clearly fail the test or compromise roadworthiness go straight to the top.

Second, likely advisory or near-limit items. These may not fail this test, but if they are close enough to create a retest risk or to bring the vehicle back off the road shortly afterwards, it can still make sense to do them now. That is a judgement call based on workshop time, parts, vehicle age and upcoming workload.

Third, non-test work found at the same time. This is where operators lose control. A pre-test inspection is not the moment to add every cosmetic and convenience job that has been sitting on a driver defect sheet for a month. If the work does not affect the annual test or immediate roadworthiness, schedule it separately unless the vehicle is already stripped and the labour overlap is worth taking.

That triage protects the fleet plan.

The next step is ring-fenced workshop capacity. If annual test work is always fitted around everything else, it will always spill. We prefer fixed slots in the week reserved for test prep and retest work. That does mean saying no to other jobs at times. But it stops one failed vehicle consuming the whole board by surprise.

Parts control matters just as much. Once the pre-test is complete, one person needs to own the parts list, order status and expected arrival. Too many operators assume the workshop and transport office are talking about the same thing when they are not. "Waiting for parts" is not a status unless someone can say what part, who ordered it, and when it is due.

You also need a clear rule on substitute vehicles. If one unit is likely to overrun into the test date, decide early whether to swap work onto another vehicle. Leaving that until the afternoon before presentation creates pressure to send the wrong vehicle out, skip checks, or move a PMI again.

This is one reason we built workshop software that keeps HGV repairs under control. The practical problem is not recording that a repair exists. It is seeing which repairs are tied to annual test deadlines, which jobs are blocking them, and what that does to the rest of the workshop week.

Use the annual test to find patterns, not just pass one vehicle

An annual test result should feed the whole maintenance system. Too many fleets treat a pass as the end of the job and a fail as bad luck. Neither is good enough.

Every failure, advisory and repair linked to annual test prep should be reviewed for patterns.

Start with repeat defects by vehicle. If the same unit has had brake imbalance at two annual tests and multiple brake-related defects during PMIs, that is not a one-off. Something in usage, adjustment, component choice or inspection quality needs attention.

Then look across the fleet. Are several vehicles picking up lamp failures around the same age? Are trailer brake performance issues clustering on one make or one operating base? Are certain technicians finding defects late that should have been identified at PMI? Are drivers repeatedly reporting the same issue only when the test date is near?

Advisories matter here as well. A vehicle can pass and still tell you a lot about where your maintenance approach is thin. If you are seeing repeated advisories on corrosion, tyre condition, suspension wear or body security, those are early warnings that next year's test prep will be harder than this year's.

This review should also include retest causes. Not just the fail item itself, but why it got to the test in that state. Was the pre-test inspection too rushed? Was the brake test not done? Was a known defect deferred because of parts? Was the vehicle presented too soon after repair without a proper sign-off? Those are process faults, not just vehicle faults.

The useful way to do this is by defect category, vehicle, workshop site, technician and date range. If you can only review one PDF at a time, you will miss the pattern. We see operators make better decisions when they can spot repeat issues early, which is why we put that visibility into our systems and wrote about how to spot repeat lorry repairs before they cost you.

This matters beyond one test pass. Repeat annual test defects can feed into OCRS if they reflect broader maintenance weakness. They can also become awkward evidence if DVSA or the Traffic Commissioner asks whether your maintenance arrangements are really effective.

Keep the paperwork straight for DVSA and the O-licence

Good maintenance control is not just doing the work. It is being able to show what was planned, what was found, what was repaired, what was deferred and why.

For annual test prep and related repairs, keep the records in a way that lets someone else follow the story without explanation.

At minimum, that means:

  • the annual test booking details
  • the pre-test inspection record
  • any brake test results used in preparation
  • defect reports from drivers or workshop staff linked to the vehicle
  • repair job cards or worksheets
  • parts used, where relevant
  • technician sign-off
  • evidence of rectification and reinspection where needed
  • the annual test result, including failure items and advisories
  • retest records if a retest was needed
  • notes of any schedule changes, missed PMIs or substituted inspection dates caused by the repair work

The quality of the record matters. "Fixed brakes" is useless. "Offside rear service brake imbalance traced to contaminated lining, shoes replaced both sides, drum cleaned, retested on rollers, performance within limit" is a record that means something.

The same goes for missed schedules. If annual test repairs force a PMI to move, record the reason, the authorisation and the replacement date. A silent gap in the schedule looks like loss of control. A documented exception with a reason and follow-up date looks like management.

Brake evidence deserves special care. If you are relying on brake testing as part of your roadworthiness system, keep those records together and easy to retrieve. We have covered what inspectors expect in brake test records that stand up at a DVSA visit.

You also need consistency between workshop records and compliance records. If the workshop job card says the vehicle was off road awaiting a steering part, but the transport record shows it allocated to work, you have created a problem for yourself. The same applies to annual test outcomes. A fail should trigger the right internal status immediately so the vehicle is not accidentally returned to service before rectification.

For UK operators, this links directly to the O-licence. The annual test is one visible checkpoint in a wider maintenance system that the Traffic Commissioner expects to be controlled. In the UK, that means being able to show your inspection intervals, PMI completion, defect rectification, brake testing approach, annual test outcomes and management of exceptions. EU operators outside Great Britain may work under different national testing and operator licensing structures, so do not assume the paperwork standard is identical just because the roadworthiness principles are similar. Here, the O-licence framework and DVSA enforcement approach make the record trail especially important.

If you want a simple rule, use this one. Every annual test related decision should leave a record. Every repair should be specific. Every change to plan should be visible. That is how you manage annual test preparation and repairs for an HGV fleet without letting one vehicle's problems spread through the whole operation. The pass matters. The control behind it matters more.

How far ahead should I book an HGV annual test?

As early as you reasonably can. Test slots can tighten up, and you need time for a pre-test inspection, parts and any repairs. Leaving it late turns a manageable defect into a vehicle-off-road problem.

Is a preventative maintenance inspection enough as annual test prep?

Not on its own. A preventative maintenance inspection supports roadworthiness, but annual test prep should be a focused check against likely test fail points, with time allowed to repair anything found.

Should I combine the PMI and annual test prep?

Sometimes, if the timing works and the inspection is still done properly. But do not force them together if it means rushing either job or pushing the vehicle outside its planned maintenance control.

What if a vehicle fails and the repair will take days?

Re-plan straight away. Protect the rest of the workshop diary, move urgent fleet work first, and record why schedules changed. One failed vehicle should not quietly cause missed PMI dates elsewhere.

Do I need to keep annual test repair records?

Yes. Keep inspection findings, repair details, parts fitted, sign-off and test results together. If DVSA looks at your maintenance systems, clear records help show proper control of roadworthiness.