Lift maintenance looks like a scheduling problem and isn’t. Planned visits are the predictable part. What determines whether a maintenance business runs well is how it handles the unplanned: callouts, entrapments, repeat faults on the same unit, and the remedial actions arising from an independent examination that someone else carried out.
Most field service platforms model the planned work adequately and the rest poorly.
The unit is the record, not the contract
A lift has a service life measured in decades. Over that time it will change building owners, managing agents and maintenance contractors, possibly several times each. What should persist is the unit’s own history: components replaced, faults recurring, modernisation work, examination findings, and how quickly issues were resolved.
Software organised around the customer contract loses this at every handover. Software organised around the unit — with an identifier, a location, equipment details and a full history — keeps it, and that history is what lets an engineer arriving at an unfamiliar machine room understand what they’re dealing with.
When evaluating, ask directly: can I see everything that has ever happened to this lift, including under the previous contract? If it needs a spreadsheet export, the model is wrong.
Callouts and entrapments are a separate workflow
An entrapment is not a job. It has a response-time obligation, often contractual and sometimes regulatory; a distinct priority; and reporting requirements that a routine service visit doesn’t carry. If a client asks how many entrapments occurred at their site last year and how long the average release took, that answer should take seconds.
Requirements that matter:
- Separate classification of planned, callout and entrapment attendances
- Response-time clocks against contractual targets, with breaches visible
- Fault codes consistent enough to spot repeat faults on the same unit — the single most useful signal in the trade, and the one weak systems obscure by letting engineers free-type
- Link from a callout to any remedial work it generates, so the loop closes
That repeat-fault view is worth insisting on. A unit that has failed four times in six months for related reasons is either a component about to fail properly or a symptom of something larger, and it’s the difference between a maintenance business and a reactive one.
Statutory examination is somebody else’s job — but your problem
In many jurisdictions, lifts are subject to periodic independent examination, and the examiner is deliberately not the maintenance contractor. In the UK this sits under LOLER; elsewhere it follows the applicable national regime, and the relevant safety standards for lift design and installation differ again. Confirm what applies where you operate.
Commercially, the point is that examination reports arrive from a third party and generate remedial actions you’re expected to price, schedule, and evidence. Software should let you record an external examination, attach its report, raise the defects it identified as tracked items, and show a client the status of each. Systems that only track your own findings leave this in email, which is where it gets lost.
What to test in a trial
- Open a lift unit and show its complete history across contracts.
- Log an entrapment, record the release time, and produce a report of response times against target.
- Show the units with the most callouts in the last quarter, grouped by fault type.
- Record an external examination report and raise its defects as tracked remedial items.
- Complete a service visit offline in a machine room with no signal, including photographs.
- Produce a client-facing report for a portfolio of sites for last month.
- Export everything, including documents and images.
Steps 3, 4 and 6 are where most generic platforms visibly struggle.
Portfolio clients change the requirements
Managing agents and facilities managers with multiple buildings behave differently from a single building owner. They want portfolio-level visibility, consistent reporting, and frequently their own login.
If you’re pursuing that work — and it’s usually the profitable end of the market — check whether the software supports a client hierarchy: a managing agent above multiple buildings, each with multiple units, with permissions that let a site manager see only their own site. Retrofitting that structure later is painful.
Build, configure, or buy
Buy if a product genuinely models units, callouts and examinations, and you service common equipment under a common regime.
Configure if the asset model is right but reporting and forms need shaping to your contracts.
Build where the market is thin: operators combining maintenance with modernisation projects, those working under a regional regime nobody has productised, or businesses whose contractual reporting is a competitive differentiator. The case is strongest when you can point to specific monthly costs — hours of manual reporting, missed response-time claims, work lost for lack of portfolio reporting — rather than general dissatisfaction.
Frequently asked questions
Can we run this on general field service software? Planned maintenance, yes. Entrapment tracking, repeat-fault analysis and third-party examination handling usually need workarounds, and those workarounds are where the admin cost accumulates.
How important is offline capture? Machine rooms and lift pits are among the worst signal environments in the trade. Test it properly, with photographs, before committing.
Do we need a client portal? For single-building owners, rarely. For managing agents with portfolios, it’s increasingly a condition of winning the contract.
What about spare parts and stock? Ask whether parts are tracked against the unit, not just consumed on the job. Knowing which component was fitted to which lift, and when, is what makes a repeat fault diagnosable.
Internal links: #9 field service buyer’s guide, #14 custom vs off-the-shelf, /industries. External references: your national regime for periodic examination of lifting equipment (LOLER in Great Britain; the applicable national code elsewhere) and the relevant lift safety standards for your market. CTA: “Servicing a portfolio no platform quite fits? Tell us how your contracts work.” → /contact