The phone rings at 11:43pm. Your out-of-hours number. The dispatcher on shift picks up, and the caller says they're stuck in a lift. The next question out of the dispatcher's mouth will determine how the next 60–90 minutes unfold: "Which building are you in?"
That question, asked by every elevator maintenance company in the world, is where after-hours emergency handling either works or falls apart.
This article covers how companies actually manage after-hours elevator emergency calls: the on-call structures, the failure modes that trigger the calls, the SLA implications of getting identification wrong, and what a modern dispatch workflow looks like when phone-to-asset mapping is in place.
What triggers an after-hours elevator emergency call
Not all night calls are trapped-passenger rescues. Understanding the distribution shapes how you staff for them.
Trapped passenger is the most urgent and the one with the hardest contractual SLA. Under most UK residential maintenance contracts, the response obligation is 60–90 minutes. Premium commercial and healthcare contracts often require 30–45 minutes. EN 81-28 does not specify a maximum rescue time but requires the monitoring centre to be permanently staffed and capable of initiating a rescue.
Door fault is the most common night call by volume. Doors that fail to close properly trigger the intercom or a building manager calling your out-of-hours number. The car parks out of service. In a residential building, this is an inconvenience. In a hospital or high-traffic commercial site, it may be business-critical. Response times here are typically 4-hour on-call rather than the 90-minute emergency window.
Leveling error occurs when the car stops with a floor gap of more than 20mm, the threshold above which EN 81-20 Clause 5.2.5.1 considers the landing to be inaccessible. The car won't open its doors at a landing if it cannot detect it's aligned. On modern drives, this often clears on reset; on older equipment, it requires manual intervention.
Drive fault or safety chain open covers a range of conditions: overspeed governor tripping, buffer switch activation, pit flooding triggering a stop, phase failure on three-phase supply. These put the car out of service and may or may not have passengers involved.
GSM device alarm without passenger response: the two-way communication device initiates a call automatically in some systems (timer-triggered or after excessive travel time), or a monitoring centre tries to make contact and gets no response. Under EN 81-28, if the alarm activates and no one responds, the monitoring centre must treat it as an emergency.
On a portfolio of 200 elevators, a maintenance company might receive 30–60 after-hours calls per month. Roughly 15–20% will be trapped passengers. The rest are faults that need same-night or next-morning response depending on site criticality and the contract category.
The on-call structure: how companies currently organise it
Most elevator maintenance companies below 40 engineers run a single on-call rota: one technician designated as primary, one as backup, rotating weekly or fortnightly. The rota is managed in a shared spreadsheet, a WhatsApp group, or an HR system that doesn't talk to the dispatch platform.
When a call comes in:
- Out-of-hours dispatcher (in-house or outsourced monitoring centre) receives the call
- Dispatcher tries to identify which building and shaft
- Dispatcher calls the primary on-call technician
- If primary doesn't answer within 3 minutes, dispatcher calls backup
- Dispatcher confirms the technician is rolling and gives them the job details
- Technician drives to site
The weakness in this model is step 2. If identification takes 8–12 minutes (which it can, with an unknown caller number and a poorly maintained asset register), the 90-minute clock is already 10–15% gone before the technician's phone rings.
Companies with 40+ engineers typically run zone-based on-call structures: the UK is split into geographic areas, each area has a designated primary and backup. The dispatcher's task is to match the incoming call to the right zone and call the right pair. The zone boundaries exist in the dispatcher's head, on a wall map, or in a document nobody has updated since the last reorganisation.
Where time disappears during an after-hours elevator emergency
The identification problem is the largest single variable in after-hours response time, and it's almost entirely preventable.
Every lift shaft with EN 81-28-compliant emergency communication has a dedicated telephone number registered to that device. That number doesn't change when a new tenant moves in, when the building changes management company, or when your contract is renewed. It is a permanent unique identifier for that specific shaft.
In most companies, that number is recorded somewhere (a commissioning sheet, an asset register entry, a spreadsheet column) but it is not actively used to route incoming calls. When the call arrives, the dispatcher sees a number on their screen and has to cross-reference it manually.
A well-maintained asset register with 300 entries still takes 3–5 minutes to search by phone number if you're doing it manually. With a new dispatcher on shift, or a number that was added six months ago and wasn't cross-referenced properly, that search can take 10–12 minutes.
Time lost at each stage of a typical 78-minute after-hours rescue:
| Stage | Time |
|---|---|
| Shaft identification | 6–10 minutes |
| Situation assessment | 2–3 minutes |
| Locating on-call technician, confirming availability | 4–8 minutes |
| Travel to site | 25–40 minutes |
| On-site rescue | 10–20 minutes |
| Post-rescue documentation | 5–7 minutes |
The identification stage and the technician-location stage together account for 10–18 minutes that can be cut to under 2 minutes with the right tooling. That is not a marginal efficiency gain; it is the difference between a 60-minute rescue and a 78-minute rescue on a 90-minute SLA.
The most common on-call dispatch failures
The dispatcher doesn't recognise the caller number. No asset register lookup, no automatic identification. The dispatcher asks the passenger which building they're in. If the passenger is distressed, elderly, or unfamiliar with the building, this conversation itself takes 3–5 minutes to resolve.
The on-call roster is out of date. The dispatcher calls the number listed as primary on-call. That person is actually on holiday. This happens more often than any operations manager wants to admit. Without a system that reflects the live rota, the dispatcher is working from stale data.
The nearest technician isn't the one who gets dispatched. The dispatcher calls the primary on-call technician because that's the process. That technician lives 45 minutes from the site. A qualified engineer who lives 12 minutes from the site is on backup. The wrong call was made because the dispatcher had no visibility of technician location.
The technician doesn't have the right equipment. A rescue requires specific tools: a fireman's lift key, door-release equipment for manual rescue, a reliable communication device. If the technician left equipment at a depot or their van is being serviced, they need to collect it. That stop rarely appears on any SLA report.
Documentation is done from memory, after the fact. EN 81-28 Clause 5.3 requires that the monitoring centre maintains a log of each alarm call, including time of receipt, identification, dispatch, arrival, and resolution. Reconstructing this at 3am from memory introduces inaccuracies that create liability exposure if the records are ever reviewed following an incident.
How phone-to-asset mapping changes the workflow
Phone-to-asset mapping is the practice of registering every elevator intercom's telephone number (fixed line CLIP or GSM SIM MSISDN) against the specific shaft in your asset database. When a call arrives, the system matches the incoming number to the asset record before the dispatcher answers.
The dispatcher picks up the call already knowing:
- Building name, address, and floor count
- Shaft identifier and car designation (Shaft A, Lift 2, etc.)
- Contract type and SLA window remaining
- Active fault history and last maintenance visit date
- On-call technician for that zone, with their current location status
Stage 1 of the rescue workflow, shaft identification, is complete in under 4 seconds. The dispatcher's first words are "I can see you're in Shaft B at [building name], can you tell me how many people are with you?" rather than "Can you tell me which building you're in?"
That shift changes the entire quality of the assessment conversation. A dispatcher who already knows they're dealing with a 2008 MRL installation in a six-storey residential building approaches the call differently from one still trying to work out which city the caller is in.
When RemoteOps receives an inbound call from an elevator intercom, the platform matches the CLI against the asset database automatically. The dispatcher's screen shows the full asset record with one-click access to the service history, the active contract, and the nearest technician. The work order is opened during the call, not after it.
On-call rota management: the structural gap
On-call rota management is the part of after-hours operations that gets the least attention and causes the most dispatch failures.
The issues are predictable:
Rota published separately from dispatch. The on-call schedule lives in a spreadsheet or HR system. The dispatch platform has no connection to it. The dispatcher has to look in two places to determine who is on-call tonight, and the two sources are sometimes inconsistent.
No escalation path in the system. When the primary doesn't answer, the dispatcher falls back to memory or a printed sheet to find the backup number. A formal escalation sequence (primary, backup, secondary backup, duty manager) should be documented and accessible during the call, not on a laminated sheet above the desk.
No record of who actually responded. The rota shows who was scheduled. The log shows which technician was dispatched. These should match. When they don't (because someone swapped shifts informally, or the backup was called because primary didn't answer), the post-incident record shows a discrepancy that is difficult to explain.
Technician qualifications not surfaced at dispatch time. EN 81-28 rescue operations should be performed by engineers with current rescue training. If the dispatch system doesn't flag which on-call technicians hold valid rescue qualifications, the dispatcher cannot verify that the person they're sending is authorised to perform the rescue.
A dispatch platform that holds the on-call rota, surfaces the live escalation sequence, tags technician qualifications, and creates a timestamped log of every action taken during the call solves all four of these problems at the same time.
SLA implications of poor after-hours handling
SLA compliance for trapped passenger rescues is directly traceable to two variables: identification time and dispatch quality. Travel time is the variable that consumes most of the clock, but it is largely determined by geography. The human-controlled variables are what happen in the first 10 minutes.
A maintenance company with 300 elevators on contract, averaging 8 trapped passenger rescues per month, with a 90-minute SLA:
- At current performance (8-minute identification, 7-minute dispatch): average response time 73 minutes, SLA compliance approximately 82%
- With phone-to-asset mapping (30-second identification, 2-minute dispatch): average response time 58 minutes, SLA compliance approximately 96%
The 14-point compliance improvement is achieved without adding a single technician, changing any geographic coverage, or modifying any contract terms. It comes entirely from removing avoidable delays in the first 10 minutes of the rescue workflow.
That compliance number appears in your contract reviews, your renewal negotiations, and in the event of any legal action following an incident. It is the number your clients actually care about.
Documentation during and after the call
EN 81-28 Clause 5.3 sets out the minimum documentation requirement for each alarm activation:
- Date and time of call receipt
- Duration of the call
- Identification of the lift (building, shaft identifier)
- Name of the monitoring station operator who handled the call
- Actions taken and time of each action
- Time the rescue service was alerted
- Identity of the technician dispatched
- Time of arrival on site
- Time the rescue was completed
This record must be retained and producible on request. If a claim is made, or if a regulatory inspection follows an incident, this log is the primary evidence that your process was followed correctly.
Documentation done during the call, in a system that timestamps each action automatically, is accurate. Documentation reconstructed from memory at the end of a shift, or consolidated the next morning, is not. The timestamps will not match the actual sequence of events, and that discrepancy is the detail that investigators notice.
When the work order is opened during the call and updated in real time (identification confirmed at 23:43:04, dispatch confirmed at 23:45:11, technician arrival logged at 00:17:38, rescue completed at 00:34:52), the post-rescue report writes itself. There is nothing to reconstruct.
FAQ
What is the typical response time for a trapped passenger call in the UK?
Most residential maintenance contracts specify 60–90 minutes from the time of the call to the passenger being out of the car. Premium commercial and healthcare contracts often specify 30–45 minutes. The specific obligation is set in your maintenance contract, not in EN 81-28, which only requires that the monitoring centre is permanently staffed and able to initiate a rescue.
Do elevator intercom calls always come from the shaft's dedicated number?
In well-commissioned installations, yes. The CLIP presented by a fixed-line intercom or the MSISDN of a GSM device should match the number registered during commissioning. In older installations, or where a building's phone system has been partially reconfigured, the number may have changed or the original record may be inaccurate. A commissioning audit (checking that the number on file matches the number the device actually dials out on) is worth running for any portfolio where you're seeing identification delays.
How should we handle a call where the passenger is not responding?
If the emergency communication device connects but there is no response from the passenger, EN 81-28 requires that you treat it as an emergency and dispatch. You should also notify the emergency services simultaneously, as an unconscious or incapacitated passenger requires medical response that your engineers are not trained to provide. Log the time of escalation to emergency services as part of the rescue record.
What qualifications should the on-call technician hold for a trapped passenger rescue?
Requirements vary by country. In the UK, the Lift and Escalator Industry Association (LEIA) recommends formal trapped passenger rescue training and refresher courses every three years. Under EN 81-28, the monitoring centre must be able to dispatch a "rescue service," and your internal standard for what constitutes a qualified rescue technician should be documented in your QMS and reflected in your dispatch system so that unqualified engineers are not sent to trapped passenger incidents.
How do we demonstrate SLA compliance to a client after an incident?
The evidence is the timestamped rescue log: call received, shaft identified, dispatch confirmed, technician on site, rescue complete. If your platform generates this automatically from the work order activity, you can produce a report for any specific incident in under two minutes. If you're reconstructing it from call logs and WhatsApp messages, the timestamps will be approximate and the sequence may be disputed.