If you want to catch repeat HGV defects before DVSA does, you need one thing above all else. You need to join up the records you already have, then review them in the same way every week. Most operators do have the evidence somewhere. It is just split between driver defect reports, PMI sheets, workshop job cards, MOT history, emails, and someone’s memory.
That is why recurring faults get missed. A lamp fault is written three different ways. A brake issue is repaired twice but never linked back to the first report. A trailer keeps wearing the same tyre position, but nobody looks across six weeks of jobs together. If you want a practical answer to how to track recurring defects on an HGV fleet, start with consistent records, consistent coding, and a simple review routine that your workshop or transport office will actually keep doing.
What counts as a recurring defect
In workshop terms, a recurring defect is not just “something that happened again”. It is a defect that repeats often enough to show one of three things. The original repair did not solve the fault. The inspection routine did not catch the root cause. Or there is a wider pattern affecting more than one vehicle, trailer, component, depot, fitter, or supplier.
It helps to split recurring defects into three types.
First, a one-off fault. A stone cracks a lamp. A tyre picks up a screw. An airline gets damaged by road debris. That matters for roadworthiness, but it is not automatically a repeat issue. You deal with it, record it, and move on unless it happens again.
Second, a repeat on one vehicle or trailer. For example, unit A has an ABS warning, it is cleared, and two weeks later the same warning returns. Or trailer 123 has an offside rear marker lamp defect at every other inspection. That is a recurring defect even if the wording on the paperwork changes each time. In workshop terms, it means the fault was not fixed at source, or the source was not identified.
Third, a pattern across the fleet. You might see cracked mudwing brackets on the same trailer type, repeated brake imbalance on one axle brand, or repeated wheel fastening issues after work from a particular supplier. This is the one that catches operators out, because each single job looks minor until you put them side by side.
A recurring defect does not need to be safety critical every time to matter. Several small repeats often point to a bigger control problem. If the same class of defect appears in daily checks, then at PMI, then again at MOT, that is not bad luck. That is a system issue.
Which records you need to track it properly
You do not need an enterprise data project. You do need a minimum set of records, and they need enough detail to be compared.
Start with driver defect reports. Whether they come from paper sheets or an app, each report should show:
- Vehicle or trailer registration or fleet number
- Date and time reported
- Driver name
- Defect description in plain language
- Defect location, if known
- Whether the defect affects roadworthiness
- Action taken, including whether the vehicle was taken off the road
- Sign-off by the person assessing or repairing it
If your driver defect reporting is vague, repeat issues will hide in free text. “Light out” is not enough when it could mean front marker, rear position, number plate lamp, side repeater, or trailer side marker. This is why we have always pushed for linking driver defects to workshop jobs without gaps.
Next, your PMI sheets and preventative maintenance inspection records. These need more than a pass or fail. At minimum, keep:
- Inspection date
- Odometer or hubodometer reading where relevant
- Inspector or fitter name
- All defects found
- Severity or action category
- Repair required now, monitor, or advisory
- Confirmation of repair completion
- Any brake test result where carried out
- Any note that a defect has been seen before
For UK operators, PMI frequency and content are tied to your maintenance arrangements and O-licence undertakings. A preventative maintenance inspection is not just a workshop event. It is evidence of control.
Then pull in MOT results. These matter because they give you an outside test point. You want:
- Test date
- Pass or fail
- Reasons for failure
- Advisory items
- Vehicle or trailer identity
- Re-test details, if any
If a defect appears on an MOT after being reported internally before, that is a red flag. If the same advisory appears on several test cycles, that is also useful.
Workshop job cards are the other key record. Without them, you cannot tell whether the same fault was repaired properly or just touched. A usable job card should include:
- Job number
- Vehicle or trailer identity
- Date opened and date closed
- Source of the job, such as driver report, PMI, MOT, breakdown, or campaign
- Defect code and plain-language description
- Diagnostic findings
- Work carried out
- Parts used, including part number and supplier if possible
- Fitter name
- Quality check or road test result where relevant
If you are trying to track repeats and your job cards only say “repaired” or “checked ok”, you are working blind. We covered the practical side of this in workshop job tracking that stops missed defects.
You can also add roadside encounter records, tyre contractor reports, brake test printouts, and tachograph mileage data where useful. But the four core sources are driver defects, PMI records, MOT results, and workshop job cards. If those are incomplete, the rest will not save you.
How to code defects so repeats are visible
This is where most fleets make the same mistake. They rely on free text alone. One fitter writes “NSR marker inop”. Another writes “rear side light out”. A driver writes “lamp fault”. All three may be the same issue, but you will never see the pattern if your system treats them as unrelated.
You need simple defect coding. Not a giant manual. Just enough consistency to stop the same fault being hidden under different wording.
We recommend coding each defect with at least four fields:
- System or category
- Component
- Location
- Cause or suspected cause
For example:
- Electrical / Marker lamp / Nearside rear / Bulb failed
- Brakes / Service brake performance / Axle 2 / Imbalance
- Suspension / Air bag / Offside rear / Leak
- Wheels and tyres / Tyre wear / Trailer axle 3 nearside outer / Uneven wear
That structure matters more than the exact labels. What matters is that everyone uses the same list.
Keep the category list short enough that fitters and office staff will actually use it. If there are 200 categories, people will guess. If there are 15 sensible ones, they will pick the right one. Typical top-level categories are:
- Brakes
- Steering
- Suspension
- Wheels and tyres
- Electrical
- Bodywork
- Coupling
- Load security equipment
- Engine and driveline
- Exhaust and emissions
- Visibility
- Tachograph and instruments
Then standardise locations. Nearside front, offside rear, axle number, trailer position, lamp position, and so on. Do not let one person use “left” and another use “NS”. Pick one.
Causes are harder, because the first report often does not know the cause. That is fine. Use a staged approach. The driver report may only have category and location. The workshop diagnosis adds cause later. Common cause codes might include wear, corrosion, impact damage, wiring damage, poor previous repair, adjustment required, manufacturing defect, or no fault found.
This is also how you answer the real question behind how to track recurring defects on an HGV fleet. You are not just logging faults. You are coding them in a way that lets you compare like with like.
If you already have years of bad wording in old records, do not try to clean all of it at once. Start now with a standard list. Then tidy the top repeat offenders as you find them.
How to review the data without drowning in it
The fear is always the same. “We will collect more data and nobody will have time to look at it.” Fair point. So keep the review process small, regular, and tied to decisions.
We use a two-level review.
Weekly, look for fresh repeats and open loops. This should take 20 to 40 minutes for a modest fleet if the records are in order. Review:
- Defects reported more than once on the same vehicle or trailer in the last 30 days
- Jobs reopened after repair
- Defects reported by a driver but not yet attached to a workshop outcome
- MOT fails or advisories that were previously reported internally
- Any vehicle with multiple defects in the same system, such as repeated electrical faults
Sort the list by vehicle or trailer first. Then ask simple questions. Is this the same fault back again? Did we fix the symptom but not the cause? Did we replace a part when the wiring or mounting was the real issue? Has this asset become unreliable enough to inspect early?
Monthly, widen the review. This is where patterns across the fleet show up. Group defects by:
- Vehicle
- Trailer
- Component
- Defect category
- Fitter
- Depot
- Supplier
- Vehicle make or trailer type
You are not trying to build a board report. You are trying to spot things like:
- One trailer type eating through marker lamp brackets
- One fitter having a high level of repeat brake adjustments
- One supplier’s pattern parts failing early
- One depot missing the same defect at PMI and then finding it at breakdown
- One vehicle with more roadworthiness issues than the rest of the fleet
Set a threshold that suits your size. For a smaller fleet, even two or three repeats in a month on the same component may justify action. For a larger fleet, you may review top ten repeats by count and by severity.
The trick is not to read every line. Use exception review. Look for assets with multiple entries, categories with unusual frequency, and defects that move through several records without being closed properly.
This is also where keeping workshop jobs from disappearing between defect and MOT matters. A recurring defect is often not hidden because nobody saw it. It is hidden because the reporting trail broke halfway through.
What to do when a pattern appears
Once a pattern is visible, do not stop at “monitor”. Decide what changes.
If the repeat is on one vehicle or trailer, inspect beyond the failed part. A repeated lamp fault may be a wiring support issue, water ingress, poor earth, or impact from loading. A repeated brake issue may point to contamination, seizure, adjustment problems, or usage pattern. The second repair should be more intrusive than the first if the first did not hold.
If the pattern is across several assets, check whether your inspection routine is good enough. You may need to add a specific line to the PMI sheet, alter the inspection method, or bring a check forward. For example, if a trailer type keeps cracking around a body mounting point, add a targeted structural check at every preventative maintenance inspection rather than waiting for the standard interval.
Then check repair quality. Repeat defects sometimes come from weak diagnosis, but just as often they come from rushed workmanship. Use a simple quality check on selected repeat jobs:
- Was the job card clear?
- Was the root cause recorded?
- Were the correct parts used?
- Was the repair tested properly?
- Did another competent person sign it off where needed?
Parts decisions matter as well. If the same replacement part fails repeatedly, compare brands and suppliers. Cheap pattern parts can cost more in downtime and risk if they do not last. Equally, if an OE part keeps failing in a specific use case, the issue may be mounting, contamination, or application rather than the part itself.
Do not forget the reporting side. If drivers are using broad wording or not reporting early signs, follow up. A driver who writes “brakes poor” may have felt a pull, heard a leak, or seen a warning lamp. Better reporting helps better diagnosis. Sometimes a recurring defect is not a workshop problem at all. It is a driver reporting problem.
Finally, record the action taken against the pattern itself. Not just the repair on each job, but the management response. For example:
- Added brake chamber corrosion check to PMI
- Changed marker lamp supplier on trailer fleet
- Introduced second sign-off for wheel end work
- Brought forward inspection interval on high-mileage urban units
- Briefed drivers to report intermittent ABS warnings immediately
That record matters later if DVSA asks what you did once the issue became known.
How recurring defects affect O-licence risk
Recurring defects are not just a workshop nuisance. They go straight to O-licence risk because they speak to control of roadworthiness.
DVSA does not need to see dozens of bad records to form a view. A roadside prohibition, an MOT fail on a known issue, or repeated defects on annual test can all raise questions. If the same sort of problem appears again and again, the concern is not just the defect itself. The concern is whether your maintenance system is effective.
That can affect OCRS. A poor OCRS profile increases the chance of being stopped, and more stops mean more chances for defects to be found. Once that cycle starts, it is hard to argue it is random.
If your operation is questioned, whether by DVSA or the Traffic Commissioner, you should be able to show more than completed inspections. You should be able to show that you identify repeat defects, investigate them, and change something when needed. In practice, that means being able to produce:
- Driver defect reports
- PMI and preventative maintenance inspection records
- Workshop job cards
- MOT history
- Evidence of rectification
- Evidence of follow-up when defects repeat
- Maintenance planner history showing inspections were brought forward where justified
This point is worth being clear on. A fleet can have defects and still be compliant if the defects are reported, assessed, repaired properly, and managed under a credible maintenance system. What causes trouble is repeated evidence that the same defects are coming back without proper escalation.
The UK position here is practical rather than theoretical. The test is whether you can demonstrate effective systems for maintaining roadworthiness. That includes acting on patterns. It is not enough to say each individual defect was repaired at the time.
For smaller operators especially, this is where spreadsheets start to fail. They can list defects, but they are weak at linking one report to the next, showing repeats by component, or proving what changed after a pattern emerged. That is one reason we built our systems from the workshop outward. Running Woolpit Truck Repairs taught us that the hard part is not recording one defect. It is seeing the fifth one in time to stop the sixth.
If you want to stay ahead of DVSA, treat recurring defects as management signals, not just repair events. Standardise the records. Code defects properly. Review them every week and every month. Then act on what you find. That is how you catch the problem while it is still your problem, not theirs.
How many times does a defect need to happen before it is recurring?
There is no fixed legal number. In practice, if the same defect appears twice on one vehicle in a short period, or repeatedly across similar vehicles, treat it as a pattern and investigate.
Should I track driver-reported defects and workshop defects together?
Yes. If they sit in separate places, you miss the full history. A recurring fault often shows up first in a driver report, then again at PMI or during a repair.
Do MOT failures count when reviewing recurring defects?
Yes. MOT results can show patterns your own process missed. If the same item appears at MOT after earlier inspections or repairs, review both the repair and the inspection method.
Can recurring defects affect OCRS?
Indirectly, yes. Poor roadworthiness outcomes at DVSA checks can affect OCRS. Tracking and fixing repeat defects early helps reduce the chance of prohibitions and other adverse findings.
Is a spreadsheet enough for tracking repeat defects?
It can be, for a small fleet, if the entries are consistent and reviewed every week. The problem is usually not the file itself but missing data, mixed wording and no follow-up.