At 2:07am, your control room phone rings. The display shows a number you don't recognise. A woman's voice, audibly shaking: "I'm stuck in the lift. It's dark."
Your dispatcher has 90 minutes to get a trained technician with rescue equipment to her side, that's the SLA on most residential contracts. The clock starts now. The question is how much of that 90 minutes you burn before the right person even gets in their van.
This guide walks through the rescue workflow stage by stage, identifies where time actually disappears, and lays out what structural changes produce measurable improvements to your average rescue time.
The full rescue workflow
Stage 1, identify the shaft (0:00–X:XX)
This is the decisive stage. Everything else depends on it.
The dispatcher needs to know: which building, which shaft, which floor. Without that, nothing moves. With a traditional phone system, the answer is a number on a screen and a database somewhere else. The dispatcher either recognises the number from memory, searches a spreadsheet, calls the building manager's mobile, or opens the asset management system and types the number in manually.
That search takes 3–8 minutes on average. On a night shift with a new dispatcher, it can take longer.
Stage 2, assess the situation (X:XX–X:XX+3)
Once the shaft is confirmed, the dispatcher needs to ask the right questions:
- How many passengers? Any medical conditions?
- Is the car between floors or at a landing?
- Is lighting present? Can the door be opened manually from inside?
- What floor did the car stop at?
This takes roughly 2–3 minutes for an experienced dispatcher. The quality of this assessment affects which technician you send and whether they bring additional tools.
Stage 3, identify and dispatch the nearest qualified technician
Not just any technician. The responding engineer needs:
- Current rescue training (required under EN 81-28 and most insurance policies)
- Rescue equipment in their vehicle (rescue key, door-release tools, communication device)
- Physical proximity to the asset
If your dispatch is manual, a whiteboard, a shared spreadsheet, or WhatsApp, finding who is on-call, where they are, and confirming they have the right kit takes another 4–8 minutes. If they don't answer, you're starting that search again.
Stage 4, travel time
This is the one stage you can't compress without better dispatch data. The actual driving time is fixed by geography. But if you dispatched the wrong technician, one who is 40 minutes away when a qualified engineer is 12 minutes away, you've made the problem significantly worse. Dispatch quality directly determines travel time.
Stage 5, on-site execution
The technician arrives, assesses access, executes the rescue. For a car between floors, this typically means manual winding of the traction machine, checking the car is aligned with a landing, and releasing the door. For most competent engineers, the physical rescue takes 10–20 minutes. Complications (older equipment, stuck hoistway door components, car roof access required) extend that.
Stage 6, documentation
Post-rescue documentation is a legal requirement. EN 81-28 Clause 5.3 requires that the alarm monitoring station keeps a record of every activation, including time of call, time of identification, time of dispatch, and time of resolution. Beyond the standard, your insurer will require it, and the building owner will ask for it.
Documentation done poorly, or not done, creates liability. Documentation done well creates evidence that your processes work.
Where the time actually goes
Most rescue SLAs are set at 60–90 minutes for the full rescue (technician on site, passenger out of the car). Best practice within the industry is 30–45 minutes for straightforward residential cases during overnight hours.
The breakdown of a 75-minute rescue on an average-performing maintenance operation typically looks like this:
| Stage | Typical Duration |
|---|---|
| Shaft identification | 4–8 minutes |
| Situation assessment | 2–3 minutes |
| Locating and dispatching technician | 5–10 minutes |
| Travel time | 20–40 minutes |
| On-site rescue | 10–20 minutes |
| Initial documentation | 5 minutes |
The identification gap (4–8 minutes) feels small until you run the maths: it's the difference between a 60-minute rescue and a 68-minute rescue. On a 90-minute SLA, that's half your contingency spent before anyone starts driving.
Over a year, across a portfolio of 300 elevators, a 5-minute identification improvement compounds into a material difference in SLA compliance rates.
EN 81-28 and rescue time requirements
EN 81-28 does not specify a maximum rescue time, that falls under national regulations and your maintenance contract. What the standard does require, in Clause 5.2, is that the alarm monitoring station is permanently staffed (or transfers to a permanently staffed location outside of business hours) and is capable of initiating a rescue operation.
The identification obligation is implicit in that requirement. A monitoring station that receives a call but cannot identify which shaft is calling for a minimum of 5 minutes is not capable of initiating a rescue promptly. In a post-incident investigation, that gap will be visible in the log.
For lift maintenance companies operating under BS EN 81-28:2018, the monitoring centre must also be able to confirm to the trapped passenger that a rescue service has been alerted. You cannot confirm that until identification is complete.
The phone-to-asset mapping approach
Every elevator shaft with EN 81-28-compliant emergency communication has a dedicated phone number registered to that specific device. That number is fixed. It doesn't change when a building changes management company, and it doesn't change when a new maintenance company takes over the contract.
That number is a unique identifier for the shaft.
The question is whether your systems make use of it.
When RemoteOps receives an inbound call from an elevator intercom, the platform matches the incoming CLI (calling line identification) against the asset database before the dispatcher picks up. In under 4 seconds, the screen shows:
- Building name, address, floor count
- Shaft identifier and car designation
- Contract reference and SLA time remaining
- Active service history and last maintenance visit
- Nearest available technician with rescue qualification status
The dispatcher doesn't search. They pick up the call already knowing where the passenger is. Stage 1 of the rescue workflow is complete before the first word is spoken.
The difference between 4 seconds and 4 minutes isn't just a time saving. It changes the quality of the Stage 2 assessment. A dispatcher who already knows they're dealing with a 1960s hydraulic lift in a five-storey residential building in the third shaft from the left asks different questions than one still trying to figure out which building is calling.
Dispatch optimisation: getting the right technician there first
Knowing where the passenger is doesn't help if you send the wrong engineer.
The factors that determine who should respond:
Current location. A technician 8 minutes away beats a technician 35 minutes away, all else being equal. If you don't have real-time location visibility, you're dispatching on your best guess about where someone is based on their last known job.
Rescue qualification. EN 81-28 rescue operations should be performed by technicians trained in lift rescue procedures. If your dispatch system doesn't tag which engineers hold current rescue training, you have no way to filter in real time.
Equipment in vehicle. A technician who left their rescue key at the depot needs to make a stop. That stop costs time.
Current workload. A technician en route to another job may not be the fastest option even if they're geographically close.
A dispatcher working from a WhatsApp group or phone list has to hold all of this in their head at 2am. A dispatcher working from a system that surfaces nearest qualified technician, with a red flag if they lack rescue equipment at their current location, makes the right call in 30 seconds instead of 6 minutes.
Real-world scenario: 2am, residential building
Here is how the same trapped passenger call plays out under two different operating models.
Without phone-to-asset mapping:
02:07, Call received. Dispatcher sees an unknown number. 02:08, Dispatcher searches the spreadsheet. Number isn't labelled. Calls the out-of-hours building manager. 02:11, Building manager confirms the address and shaft number. 02:13, Dispatcher calls the on-call technician. No answer. Calls backup. 02:16, Backup technician confirmed, 34 minutes away. 02:50, Technician arrives on site. 03:10, Passenger out of car. Total time: 63 minutes.
With phone-to-asset mapping and dispatch support:
02:07, Call received. Screen shows: Crane House, Flat St, Shaft B, 2nd floor residential, SLA 90 min remaining 89:53, nearest qualified technician, M. Kowalski, 12 min. 02:08, Dispatcher picks up, confirms passenger is uninjured, tells her rescue is 15 minutes out. 02:09, Dispatch sent to M. Kowalski. Confirmed. 02:21, Technician arrives on site. 02:38, Passenger out of car. Total time: 31 minutes.
Same contract. Same SLA. Same geography. 32 minutes faster.
Metrics to track
If you're not measuring these, you can't improve them:
Average identification time. From the moment a call is received to the moment the shaft is confirmed. This is your biggest lever. Target under 30 seconds with phone-to-asset mapping in place.
Average dispatch time. From shaft identification to technician confirmed and rolling. Target 2–4 minutes with current location data and qualification filtering.
Average travel time. This tells you whether your dispatch decisions are optimal. If average travel time is consistently above 35 minutes, you either have a coverage gap or a dispatch quality problem.
Average rescue time. The end-to-end metric. From call received to passenger out of car. Track by building type (residential vs commercial), time of day, and technician.
SLA compliance rate. What percentage of trapped passenger rescues were completed within the contractual time. Report this monthly. It tells you whether your improvements are moving the number that matters to your clients.
Documentation requirements post-rescue
Under EN 81-28 Clause 5.3, the alarm monitoring station must retain records of each alarm call. The minimum record includes:
- Date and time of call
- Duration of call
- Identification of the lift (building, shaft)
- Name of the operator who handled the call
- Actions taken and time of each action
- Time of dispatch and technician identity
- Time of arrival and time of rescue completion
Beyond the standard, your professional indemnity insurer will want to see this record if a claim is made. Document everything during the call, not after, when details fade.
A rescue that was completed well but documented poorly leaves you exposed. The documentation is part of the rescue.
FAQ
What is the standard SLA for trapped passenger rescue in the UK?
There is no single statutory requirement across all contract types. Most residential maintenance contracts specify 60–90 minutes. Premium commercial and healthcare contracts often require 30–45 minutes. EN 81-28 requires that the monitoring centre be capable of initiating a rescue, the time limit is set contractually, not by the standard itself.
Does EN 81-28 apply to all elevators or just new installations?
EN 81-28:2018 applies to new installations. Existing installations built before the standard was adopted are subject to local regulation and, in many EU countries, a risk assessment requirement under the Lift Maintenance Directive. For practical purposes, if you're maintaining a building with an elevator installed after approximately 2003, the emergency communication device was likely specified to EN 81-28 or its predecessor.
How does phone-to-asset mapping work with lifts that use GSM devices?
GSM-based emergency devices (common in MRL lifts and retrofit installations) present a SIM card's MSISDN as the calling number, same as a fixed line. As long as that number is registered in your asset database against the specific shaft, the mapping works identically. The key step is registering every SIM number during commissioning, not retroactively, when the call comes in during a rescue.
What qualifications does a technician need to perform a rescue?
Requirements vary by country. In the UK, the LEIA recommends that all engineers performing passenger rescues complete formal trapped passenger rescue training and refresher courses every three years. Under EN 81-28, the standard requires that the monitoring centre can dispatch a "rescue service", your internal standard for who qualifies should be documented in your QMS and reflected in your dispatch system.
What if the caller cannot communicate? (Unconscious passenger, medical emergency)
If the call connects but there is no response, EN 81-28 still requires that you treat it as an emergency and dispatch. In this case, call the emergency services simultaneously, a trapped unconscious passenger is a medical emergency, not just a lift fault. Document the time you escalated to the emergency services as part of the rescue record.