The hydraulic hose on truck 14 failed on a Tuesday morning. The technician replaced it, the customer signed the job card and the machine was back in the aisle before lunch. Everyone agreed it was a good response.
Three weeks later the same truck stopped in the same aisle with the same leak. A different technician attended. A new job number was raised. The repair was just as quick and the job card just as tidy.
By the fourth visit, someone in finance asked the question nobody on the floor had asked: “Why do we keep paying to fix this one?”
Each repair can look fine on its own
Forklift repeat breakdowns rarely announce themselves. Each callout arrives as a separate event, gets its own job and closes with its own signature. Judged one at a time, the service looks responsive. The technician attended, the part was fitted and the truck returned to work.
The pattern only shows when those events sit side by side: the same asset, the same fault area and shrinking gaps between failures. Without that view, every repeat failure is treated as bad luck rather than a signal.
That is why a quick fix and a lasting fix can look identical on paper. The difference appears on the next visit, and the one after that.
Memory is not a maintenance record
In many operations the pattern is spotted by a person rather than a record. The workshop foreman remembers that truck 14 “always gives trouble”. The site manager knows which reach truck to avoid on a busy night. The operator who drives it every shift could probably write the fault report from memory.
That knowledge is valuable, but it is fragile. It leaves with people, changes with shifts and rarely reaches the person who approves the repair budget. It also blurs the detail. Was it the same hose, or a different one in the same area? Was it the same technician, or the same supplier?
Repeat breakdown analysis works when the history sits with the machine, not with whoever happens to remember it.
Patterns hide across sites and suppliers
The problem grows with the fleet. One site raises a breakdown with one service provider. Another site uses a different provider for the same model. Rental units arrive and leave. Machines move between branches when demand shifts.
Each move scatters the history a little further. A truck that failed twice at one site and twice at another can look like two minor problems rather than one persistent one. If the service records sit in separate inboxes, spreadsheets and supplier reports, nobody sees all four together.
A repeat pattern needs three things kept in one place: the asset’s identity, where it has been and every service event recorded against it.
Cost per callout tells only half the story
A single repair may be modest. Parts, labour and a callout fee rarely look alarming on one invoice. The concern is accumulation. Four modest repairs on the same machine in a quarter can add up to a figure that would have changed the conversation much earlier, had anyone seen it as one figure.
Then there is the cost that never appears on an invoice: the machine standing, the operator reassigned, the order picked late and the overtime that followed. Downtime on a repeat failure is not a surprise the second time. It is a forecast that nobody acted on.
Looking at repair costs by asset, site and period turns a pile of invoices into a question worth asking. Is this machine still worth repairing, or has it quietly become the most expensive one in the fleet?
Repeat does not always mean the machine
A recurring fault is a signal, not a verdict. Sometimes the machine is genuinely worn and nearing the end of its useful life. Sometimes the cause sits elsewhere: a damaged floor surface, an application the truck was never specified for, a charging routine that shortens battery life or an operating habit nobody has corrected.
Sometimes the repair itself is the issue. The symptom was treated and the cause was not. That is not about blame. It is about having enough history to ask a better question on the third visit than on the first.
A clear history is fair to everyone. It protects the technician who recommended a root-cause repair that was never approved, and it helps a supplier show that a recurring problem began before they took over the contract.
Where FMC supports repeat-failure visibility
FMC gives each machine a digital identity and a central asset record that keeps its location, allocation, documents and lifecycle history together, so the story stays with the asset when it moves between sites.
Service events are recorded against that asset through FMC Service Management, from the moment a breakdown is raised until its outcome is recorded, including repairs and follow-up work identified during previous visits. FMC Dashboards & Reporting then helps authorised users examine breakdown frequency, affected equipment, recorded downtime and recurring operational issues, alongside service, repair and parts costs across individual assets, sites or selected periods.
Software makes the pattern easier to see. Managers, technicians and suppliers remain responsible for investigating it and deciding what happens next.
Where to start this week
You do not need a full fleet review to find the first pattern. Pull the breakdown records for the last three months and ask a few practical questions:
- Which three machines had the most breakdown callouts, and were any of the faults in the same area?
- How long did each machine run between failures, and is that gap getting shorter?
- What did those repairs cost per machine once parts, labour and callouts are added together?
- Did any repeat failure follow a repair that treated the symptom but not the cause?
- For each repeat machine, who owns the decision to repair, rent or replace, and when will it be made?
If answering those questions means a week of digging through invoices and email threads, the records are telling you something too.
One breakdown is an event. The second is a pattern. The third is a decision waiting to be made.
