Third call-out this month, different engineer each time
The lift at a retail park keeps stopping between floors. The first engineer finds a door contact dirty, cleans it and leaves. The second, ten days later, resets a fault on the controller and notes that the doors were slow. The third finds the landing door out of adjustment on level two. Each job is closed. Each engineer did something reasonable. Nobody has looked at all three together.
The customer has, though. Their facilities manager has a list, and when they ring, they are not asking about one call-out. They are asking why the lift keeps failing and whether you know what you are doing.
Why patterns stay hidden
Job management systems are built to close jobs, and they do that well. They are not built to read across jobs, and fault notes are free text that every engineer writes in their own way.
- The same fault is described as door fault, doors not closing, DOL issue or landing door adjusted.
- Call-outs are attributed to the site, not always to a specific lift on a multi-lift site.
- Fault codes, if used at all, are optional and picked inconsistently.
- Nobody has a regular job of reviewing call-out history across the portfolio.
- Engineers see only their own visits, not the one from last week.
Repeat faults cost more than the call-outs
Each repeat call-out takes an engineer away from planned work, and on a comprehensive contract it may be work you are not paid extra for. But the larger cost is trust. A customer who sees the same fault three times starts to question the maintenance itself, and will raise it at contract review or in a tender.
Repeats also hide genuine opportunities. A lift that keeps failing with door faults may need a door operator replacement or a wider repair, which is quotable work. Without a clear record, you cannot put that case to the customer with any evidence.
A fault history that reads across call-outs
We build a fault history view on top of your existing job data. It does not replace your job system. It reads from it and adds the pattern-spotting your team does not have time for.
- Call-out records are pulled from your job system each night, including the engineer's free-text notes.
- Each note is classified into a small set of fault categories that your engineers agree, such as doors, levelling, controller, drive, safety circuit, misuse, and no fault found. A language model does the first pass, and anything uncertain is left unclassified for a person to review.
- Call-outs are tied to the individual lift, using the lift reference where it exists and a prompt to the engineer on the next job where it does not.
- Rules you set flag repeats, for example the same category on the same lift more than a set number of times in a set period.
- Flagged lifts appear on a weekly list for the service manager, with the call-out notes laid out in date order.
- The next engineer to attend a flagged lift sees the recent history on their phone before they start.
| What the service manager sees | What it helps with |
|---|---|
| Lifts flagged for repeat faults | Deciding who investigates properly |
| Fault categories by lift over time | Spotting a worsening trend |
| No fault found call-outs by site | Misuse or reporting issues to raise |
| Engineer notes side by side | Understanding what has already been tried |
Classification is there to group notes, not to diagnose lifts. Your engineers decide what the pattern means.
What happens next time the lift stops
The engineer arrives knowing this is the third door-related call-out this month and what the last two engineers did. They can take the time to look at the root cause, or recommend a senior engineer visit. The service manager can ring the customer before the customer rings them, with a plan.
At contract review you can show fault history per lift, and where a repair or modernisation is the sensible answer, you have the record to support it.
Is this happening on your contracts?
- Customers have told you about repeat faults before you noticed.
- Engineers do not see previous call-out notes before attending.
- Fault notes are free text with no consistent categories.
- Call-outs on multi-lift sites are not always linked to a specific lift.
- Nobody reviews call-out history across the whole portfolio.