Fire and rescue services in England attended 13,760 lift release incidents in the year ending March 2026, and behind each one is someone waiting in a lift car. The Lift and Escalator Industry Association (LEIA) advises owners to call their lift maintenance company first, because firefighters often leave non-emergency releases to that firm. That puts a good deal of weight on the contractor's dispatch desk, which is exactly where field service management (FSM) software earns its keep.
This article follows a lift entrapment from the dispatcher's chair: where the minutes go, and how smarter dispatch can win some of them back.
Lift service teams reduce entrapment response times by shortening the gap between the alarm and the right engineer being on the road with the right parts. In practice, that means capturing the callout automatically, dispatching on skills, location, and stock rather than who happens to pick up the phone, and keeping everyone updated until the passengers are out.
It helps to split the lift entrapment response time into four stages: alarm to call handled, call handled to engineer assigned, assigned to arrival, and arrival to release. Travel and the release itself are largely fixed. The two stages in the middle are where dispatch has the most to give, and the pressure on them is real. LEIA warns owners against expecting a maintenance company to respond as quickly as an emergency service, and one lift industry specialist writing in Modern Building Services notes that a contractor may not be able to respond in a reasonable period of time, depending on where its engineers happen to be.
LEIA guidance says passengers should be released by a trained lift engineer or the rescue services, and that for gearless lifts, lifts with bi-directional safety gears, and machine-room-less installations, only a lift engineer should undertake the release. The nearest engineer is therefore only useful if they have worked on that type of installation.
Effective emergency lift callout dispatch needs three things held against every engineer profile: the lift types and manufacturers they are trained on, their release training records (BS 7255 calls for training for anyone authorised to release passengers, with competence assessed and documented annually), and their live availability. With those in an FSM system, the dispatcher sees a ranked shortlist instead of working through a phone list, and a lapsed refresher gets flagged before it matters at 2am.
Skills and parts for a lift breakdown go hand in hand. Once passengers are out, a lift that cannot return to service leaves the building owner waiting on a second visit. If the system holds each lift's make, model, and service history, and shows what is on each van, the dispatcher can favour the engineer most likely to be carrying the part, and the engineer can read the history on the way in. Where a part is not on the van, it can be booked from the nearest depot while the release is under way.
Evenings, weekends, and bank holidays are where out of hours lift callout management gets tested, and demand rarely arrives politely. After a power cut, a contractor may be releasing many passengers at once, with hospitals and schools taking priority. That is a prioritisation call a dispatcher has to make in minutes, and every handover between the alarm, the call handler, the on-call engineer, and the customer is a place where time quietly leaks away.
An FSM platform can tie the on-call rota directly to dispatch, escalate automatically when a callout is not accepted within a set time, attach site contacts and access instructions to the job, and message the customer when an engineer is assigned and again on arrival. Nobody has to remember to make a call at 3am.
A structured callout form can capture the lift ID, floor, number of people inside, and whether anyone needs medical help. That last question carries weight, because LEIA notes that firefighters are not obliged to attend non-emergency lift calls where nobody faces immediate physical or medical danger, so the answer shapes who should be sent and how quickly. It belongs at the top of the form rather than buried in a free-text note.
Contracts differ, so it matters that your team can change those fields and escalation rules themselves. With a no-code application platform sitting alongside the FSM system, a new field or approval step is a configuration job rather than a development ticket that waits behind everything else.
Time-stamp each step (call logged, engineer assigned, job accepted, travelling, on site, released) and lift entrapment management gains an audit trail as well as a speed boost. If assignment takes 20 minutes at 2am and five at 2pm, you have found a rota to fix. The same data lets you show customers how you performed against their contract targets, which is a much easier conversation than reconstructing events from phone logs.
Want to see a lift callout travel from alarm to release in one system? Book a demo of Solarvista, the world's first 2-in-1 field service management system and no-code application platform, and we will build your entrapment workflow around it.