If you want to know how to track repeat repairs on the same lorry, the answer is simple enough in principle and awkward in practice. You need one record for every job, the same fields completed every time, and a way of grouping faults so “air leak near rear axle” is not hidden under six different descriptions. Without that, repeat work looks like unrelated jobs and the cost sits there unnoticed until the vehicle starts missing work, failing PMI, or turning up in a DVSA conversation you would rather not have.
We see this all the time in the workshop. The problem is rarely that nobody noticed the lorry had been in before. The problem is that nobody could prove whether it was the same fault, a bad previous repair, a different component in the same area, or a driver report that changed wording each time. If you want to stop repeat repairs early, you need records that make patterns obvious to both the workshop and the transport office.
What counts as a repeat repair
A repeat repair is not just “the vehicle came back with another defect”. That is too loose to be useful. You need a definition your workshop and transport team can apply the same way every time.
For us, a repeat repair is one of these:
- The same component fails again after repair or replacement
- The same symptom returns in the same area of the vehicle
- A PMI item was marked as repaired, then reappears at the next inspection
- A roadside breakdown matches a recent workshop job on the same system
- A defect reported by the driver comes back within a short period or low mileage after sign-off
That still needs boundaries. Otherwise every lamp bulb and every brake issue on the same axle gets lumped together.
A practical way to define it is by four tests:
- Same system
Brakes, suspension, steering, electrical, emissions, cooling, driveline, body, tail-lift and so on.
- Same location
Offside front, nearside rear, axle 2, trailer suzie area, cab interior, fifth wheel, DPF circuit.
- Same fault type or symptom
Air leak, overheating, poor charging, uneven wear, warning lamp, excessive play, fluid loss.
- Reasonable time or mileage since previous work
You decide the threshold and use it consistently.
That last point matters. In a haulage fleet, “repeat” should not mean the same thing after 400 miles as it does after 40,000. We usually suggest setting internal review triggers by both time and mileage. For example:
- Safety critical defects, review if the same issue returns within 90 days
- General mechanical defects, review if it returns within one PMI cycle
- Breakdown-related defects, review if the same symptom returns within 5,000 to 10,000 km, or your chosen mile equivalent
- Consumables, only count as repeat if the life achieved is clearly short for that application
You do not need a perfect industry standard. You need a rule your business can actually follow.
Also separate true repeat repairs from predictable wear. A second brake chamber on the opposite side is not automatically a repeat repair. Nor is a new lamp failure months later on another part of the lighting circuit. If you call everything a repeat, the label becomes useless.
What to record every time a lorry comes in
If the record is thin, you cannot track the fault properly later. Free text alone is not enough. “Fixed air leak” tells you almost nothing six weeks later.
Every job card should capture the minimum below, whether the vehicle came in for a driver defect, PMI, MOT prep, roadside breakdown, or planned workshop work.
Vehicle details
Record:
- Registration
- Fleet number
- VIN or last six digits if that is your house standard
- Make and model
- Unit or trailer
- Odometer reading, or hubodometer for trailers if fitted
- Engine hours if relevant for PTO or specialist equipment
Do not rely on registration only. Mixed fleets and trailer movements make that messy quickly.
Job source
You need to know why the vehicle came in:
- Driver defect report
- PMI
- preventative maintenance inspection follow-up
- Breakdown
- MOT failure or advisory
- Workshop observation
- Customer complaint, if you run third-party work
- Recall or campaign
That lets you see whether repeat issues are being picked up in service, at inspection, or only once the vehicle fails in operation.
Dates and timings
Record:
- Date reported
- Date vehicle arrived
- Date work started
- Date work completed
- Date returned to service
If the defect was raised earlier but the vehicle kept running, keep both dates. That matters for roadworthiness decisions and for showing whether defects are being deferred sensibly or just left hanging around.
Defect details
This is the part most workshops under-record. You need:
- System
- Exact location on vehicle
- Driver symptom or technician finding
- Fault code, if there is one
- Inspection result or diagnosis
- Whether the defect is safety critical
- Whether the vehicle was taken off road
Write the symptom and the diagnosis separately.
For example:
- Symptom: “Driver reports low air warning buzzer sounding overnight, pressure drops when parked.”
- Diagnosis: “Air leak at axle 2 nearside brake chamber supply line fitting.”
That distinction is what helps you later decide if the next job is the same fault or just a similar complaint.
Repair details
Record:
- What action was taken
- Parts fitted, with part numbers if available
- Whether parts were new, exchange, repaired, or reused
- Torque settings or adjustment details where relevant
- Diagnostic steps completed
- Technician name
- Road test carried out, yes or no
- Outcome, rectified, monitored, deferred, referred to dealer, awaiting parts
If a job is deferred, say why and who authorised it. If it was safe to return to service, the reason should be obvious from the record.
Linking previous work
This is where repeat repair tracking starts to work. Each new job should be able to reference:
- Previous related job number
- Previous PMI sheet
- Previous breakdown record
- Previous parts warranty claim if applicable
That can be done in software or manually, but it must be possible. This is one reason we push for one set of records for workshop and transport office. If the workshop history sits in one place and defect reporting sits in another, repeat issues stay hidden longer than they should.
How to group jobs so patterns show up
Most repeat repairs are buried by language. One fitter writes “NSR lamp out”. Another writes “rear marker inop”. Another writes “light fault trailer”. Same broad issue, no usable pattern.
If you want patterns to show up, use codes or categories alongside free text. Keep the coding simple enough that people will actually use it.
A workable structure is:
1. System code
Examples:
- BRK for brakes
- AIR for air system
- ELE for electrical
- STL for steering
- SUS for suspension
- CLG for cooling
- EMS for engine management
- EXH for exhaust and emissions
- BOD for body and ancillaries
2. Location code
Examples:
- OF
- NF
- OR
- NR
- AX1
- AX2
- REAR
- CAB
- CHASSIS MID
- FIFTH WHEEL
For trailers, add enough detail to separate lead axle from rear axle, tail-lift from body rear frame, and suzie connections from tractor electrical faults.
3. Fault type code
Examples:
- LEAK
- WORN
- LOOSE
- CORRODED
- OPEN CIRCUIT
- SHORT
- MISALIGNED
- OVERHEAT
- NOISY
- WARNING LIGHT
- FAILED TEST
4. Work type
Examples:
- INSPECT
- ADJUST
- REPAIR
- REPLACE
- CLEAN
- WELD
- SOFTWARE UPDATE
- SUBLET
That gives you a structure like AIR / AX2 / LEAK / REPAIR. The technician can still write proper notes underneath, but the coding makes reports possible.
Do not try to start with 500 fault codes. It will fail. Start with a short list that covers most workshop work and add only when you have a real need.
The point is not to satisfy software. The point is to make repeat issues visible. If vehicle 27 has had three AIR / AX2 / LEAK jobs in two PMI cycles, you should be able to see that in seconds.
Good job tracking that stops work going missing helps here as well. If work is not logged consistently, you cannot sort, filter, or challenge it later.
How to tell a repeat fault from a new one
This is the hard part. Two jobs can look similar and still be unrelated. Or they can look different on paper and be the same underlying problem.
To decide properly, compare four things.
Symptoms
Start with what the driver or technician actually experienced.
If the first report was “battery warning lamp on intermittently” and the second is “vehicle flat in yard after weekend”, those may still be linked. If the first was “air leak audible at rear when parked” and the second is “poor brake response under load”, they may also be connected.
Do not rely on wording alone. Look at the behaviour.
Previous work done
Check exactly what was repaired last time.
If the last job replaced a height sensor and the complaint returns, ask whether the sensor failed again, whether the wiring fault was missed, or whether the ride height issue was only a symptom of a valve problem.
If the previous job was an adjustment only, and the same defect comes back quickly, that is a stronger repeat signal than if several major components were renewed.
Time and mileage elapsed
A fault returning after two days and 300 miles is different from one returning after six months and two PMIs.
Build internal rules around this. For example:
- Same symptom, same location, under 30 days or under 2,000 miles, treat as probable repeat
- Same system, same location, under one PMI interval, review as possible repeat
- Same system but different side or axle, treat as new unless diagnosis links them
That gives the workshop a consistent starting point.
Underlying cause
This is the main question. Has the original cause returned, or did the first repair only deal with the visible result?
Examples:
- Replacing a blown fuse is not a lasting repair if the loom is chafing behind the cab.
- Replacing one ABS sensor does not fix a damaged reluctor ring.
- Tightening a leaking fitting does not solve a cracked airline.
- Replacing a DPF pressure sensor does not fix an underlying soot-loading issue if regeneration conditions are poor.
When you are deciding whether it is a repeat, think in terms of failure chain, not just parts replaced.
This is where proper notes matter. We have written before about better root cause notes for reducing repeat defects because “replaced part, tested OK” is often not enough to defend the decision later.
What to do when one lorry keeps coming back
Once a lorry crosses your internal threshold for repeat repairs, stop treating each job as isolated. Put it into a simple escalation process.
1. Review the last three to five related jobs together
Pull the history for that system and location. Include:
- Driver defect reports
- PMI sheets
- Breakdown call-outs
- MOT failures or advisories
- Parts used
- Technician notes
One person should read the lot in sequence. Not skim it. Read it.
2. Check whether diagnosis has been too narrow
Ask:
- Did we repair the symptom but not the cause?
- Did we test the surrounding components?
- Was the vehicle returned under time pressure before full confirmation?
- Was the same assumption made twice?
This is common on electrical and air faults. The first obvious defect gets fixed, the hidden cause stays put.
3. Inspect the vehicle with repeat failure in mind
Do not just redo the last job. Inspect the whole chain.
If it is brake wear returning on one wheel end, check caliper movement, sliders, chamber stroke, contamination, hub condition, load sensing, and driver use if relevant.
If it is repeated coolant loss, pressure test, inspect pipe routing, clips, EGR cooler area, water pump, header tank cap, and signs of previous staining. Do not stop at “topped up and no leak found”.
4. Review workmanship and parts
This is not about blaming fitters. It is about checking facts.
Look at:
- Was the correct part fitted?
- Was there a known quality issue with the part brand?
- Was the repair method right?
- Was torque, calibration, or set-up missed?
- Was sublet work checked properly on return?
If the same supplier part keeps failing early, log it and challenge it. If the same type of repair fails after one technician’s jobs but not another’s, that needs training or process correction.
5. Decide whether the maintenance plan needs changing
Some repeat repairs are telling you the schedule is wrong for the work the vehicle actually does.
Examples:
- Urban stop-start work may need closer brake checks
- Tipper or muckaway work may need more frequent underbody and wiring inspections
- Fridge work may need tighter battery and charging checks
- High mileage trunking may need different tyre, alignment, and vibration monitoring intervals
A standard preventative maintenance inspection interval is not always enough on its own. In the UK, what matters is that the schedule is appropriate to the operation and supports roadworthiness. If DVSA asks why a vehicle kept presenting with the same issue, “that is our standard interval” is not much of an answer if the evidence says it was not working.
6. Create one owner for the issue
One person should own the repeat defect review, usually the workshop controller, fleet engineer, or transport manager depending on your size. If ownership is vague, the lorry just keeps cycling through jobs.
This is where workshop software that keeps HGV repairs under control earns its keep. Not because software fixes vehicles, it does not. It helps when one person can see the full history and chase the job through to a proper close.
How repeat repair records help with DVSA and O-licence risk
Repeat repair records are not just for costing and workshop control. They matter if your maintenance systems are ever questioned.
DVSA is interested in whether vehicles are kept in a fit and serviceable condition, whether defects are reported and rectified properly, and whether your maintenance arrangements support roadworthiness. Repeat faults can point to weakness in any of those areas.
Clear records help in several ways.
They support roadworthiness decisions
If a defect was found, assessed, repaired, and checked with a clear audit trail, you can show why the vehicle was returned to service. If the same issue returned, you can also show whether it was treated as a repeat and escalated.
Without that, it can look as though the same defect was simply signed off over and over.
They improve PMI planning
If one vehicle repeatedly shows the same system defects between inspections, that is evidence the inspection content or interval may need changing. A proper preventative maintenance inspection plan should reflect actual fleet experience, not just a calendar.
That is particularly important where the same lorry operates on harsher work than the rest of the fleet.
They help if DVSA asks for maintenance history
At desk-based checks, fleet investigations, or after prohibitions, being able to show joined-up records matters. You should be able to trace:
- defect reported
- inspection or diagnosis
- repair carried out
- sign-off
- recheck if needed
- any recurrence and what was done about it
If records are split between paper defect books, workshop whiteboards, emails, and someone’s memory, that chain is difficult to prove.
They protect the O-licence holder
The person named on the O-licence carries the responsibility, even when day-to-day work is delegated. If repeat defects are building up and nobody has a clear view of them, that becomes a management problem, not just a workshop one.
The Traffic Commissioner will not be impressed by “the fitter knew about it” if the systems did not flag a pattern that should have been acted on.
They can affect OCRS and wider risk
Poor defect control can feed into roadside outcomes, delayed prohibitions, MOT performance issues, and general regulatory attention. Repeat faults that lead to prohibitions or inspection failures are not just repair costs. They can become part of a broader picture about maintenance control.
That is why we treat repeat repair tracking as an operator compliance issue as much as a workshop issue. Our Operator Compliance Software is built around that reality. The workshop history has to support the transport office, and the transport office has to see what the workshop is seeing.
If you want to get on top of repeat repairs, start with discipline, not dashboards. Define what counts as a repeat. Record the same core details every time. Code jobs so patterns can be found. Review returning faults against time, mileage, symptoms, and previous work. Then escalate the lorries that keep coming back instead of letting them drift through another booking.
That is how you track repeat repairs on the same lorry in a way that stands up on the workshop floor and in front of DVSA.
How many times does a repair need to happen before it counts as repeat?
There is no official threshold. In practice, if the same component, system or symptom returns after recent work, treat it as repeat and review it straight away.
Should I track repeat repairs from driver defect reports and PMI together?
Yes. Keep one history for the vehicle. A fault first seen on a driver report may reappear at PMI or as a roadside breakdown, and you need the full picture.
Is the invoice enough to track repeat repairs?
No. Invoice lines are usually too vague. You need the complaint, diagnosis, component, side or axle position, mileage, date and what was actually done.
Do repeat repairs always mean the workshop did the first job badly?
No. The first repair may have been correct for the fault found at the time. Repeat issues can come from missed root causes, poor parts, operating conditions or driver damage.
Which vehicles should I review first?
Start with vehicles that have repeated brake, steering, suspension, tyre, wheel fixing, lighting or emissions faults, or anything that affects roadworthiness and uptime.
