Elevator Entrapment and Callback Log
Log elevator entrapment and callback events with timestamps, response actions, restoration checks, and follow-up repairs in one record. Use it to document life-safety incidents, track service reliability, and close the loop on deficiencies.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Commercial Real Estate · Property Management · Healthcare Facilities · Hospitality · Facilities Maintenance
Overview
The Elevator Entrapment and Callback Log is a structured incident record for documenting when an elevator traps occupants, repeatedly callbacks, or is taken out of service for a safety-related event. It captures the building and elevator identity, the time the report was received, response and arrival times, occupant condition, dispatch details, release time, restoration verification, and the corrective action that follows. The goal is to create a clear chain of custody from the initial complaint through safe return to service.
Use this template when an elevator event affects passengers, requires technician dispatch, or triggers an emergency response, AHJ notification, or lockout-tagout-style isolation. It is especially useful for recurring callbacks, after-hours incidents, and any event where response time and occupant communication matter. The log helps property teams, facility managers, and service vendors compare events over time and identify repeat deficiencies such as door faults, leveling problems, controller issues, or power-related shutdowns.
Do not use this as a substitute for a full preventive maintenance record or a jurisdiction-specific elevator inspection certificate. It is also not the right tool for minor cosmetic defects or routine non-emergency service calls that do not affect safe operation. If the event involves injury, smoke, fire alarm activation, entrapment with medical distress, or a code-required rescue procedure, the log should be completed alongside the appropriate incident report and any required notifications.
Standards & compliance context
- This log supports documentation practices commonly expected under OSHA general industry requirements for safe maintenance response and hazard control.
- For buildings subject to fire-life-safety oversight, the record can support coordination with NFPA-based emergency procedures and AHJ review when an elevator event escalates.
- If the incident involves emergency recall, smoke conditions, or passenger evacuation, the log should align with the building's fire alarm and life-safety procedures.
- Where a technician isolates equipment, the record should reflect lockout-tagout-style control consistent with OSHA maintenance safety expectations.
- Local elevator codes and jurisdictional inspection rules may require separate reports; this template is meant to complement, not replace, those records.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Event Identification
This section captures the who, what, where, and when of the elevator event so the incident can be tied to a specific car and building.
-
Building and elevator identification recorded
Document the building name, elevator number or car ID, and exact location.
-
Event type selected
Select the primary event classification.
-
Event date and time recorded
Record when the event was reported or discovered.
-
Reporter name and contact recorded
Record the person who reported the incident and a callback number or extension.
-
Number of occupants affected
Enter the number of people inside the elevator or otherwise affected.
-
Occupant condition noted
Document the observed or reported condition of trapped occupants.
Response Time and Initial Assessment
This section shows how quickly the report was acknowledged, how fast the site responded, and whether the elevator was secured before further risk developed.
-
Time from report to acknowledgment recorded
Enter the elapsed time between the report and first acknowledgment.
-
Time from report to on-site arrival recorded
Enter the elapsed time between the report and arrival of the responder or technician.
-
Elevator secured and taken out of service
Confirm the car was secured, isolated if necessary, and removed from service pending release or repair.
-
Initial condition observed
Document the apparent condition of the elevator at first assessment.
-
Immediate occupant communication provided
Confirm trapped occupants were informed that help was on the way and given calm, clear instructions.
Technician Dispatch and Coordination
This section documents who was sent, when they were sent, and whether escalation or isolation was needed to control the incident safely.
-
Service technician or vendor dispatched
Confirm a qualified elevator service technician or authorized vendor was dispatched.
-
Dispatch time recorded
Record the exact time the technician or vendor was dispatched.
-
Technician arrival time recorded
Record the exact time the technician arrived on site.
-
Vendor or technician name recorded
Document the company name and technician name or ID, if available.
-
Escalation to AHJ or emergency services required
Indicate whether the incident required escalation to the Authority Having Jurisdiction, fire department, or emergency medical services.
-
Lockout-tagout or equivalent isolation applied when required
Confirm energy isolation and lockout-tagout controls were used when maintenance conditions required them.
Release and Restoration Verification
This section confirms that occupants were released safely and that the elevator was checked before being returned to service.
-
Occupants safely released
Confirm all trapped occupants were released without further incident.
-
Release time recorded
Record the exact time occupants were released.
-
Elevator returned to service only after verification
Confirm the elevator was not returned to service until the condition was verified safe by qualified personnel.
-
Post-event operational check completed
Confirm a functional check was completed after release and before reopening the elevator.
-
Deficiency documented for follow-up repair
Record whether a mechanical, electrical, or door-system deficiency remains and requires repair.
Incident Documentation and Corrective Action
This section closes the loop by recording the suspected cause, repair action, and follow-up needed to prevent repeat callbacks.
-
Root cause or suspected cause documented
Summarize the suspected cause of the entrapment or callback event.
-
Corrective action documented
Describe repairs, adjustments, resets, testing, or vendor actions taken.
-
Follow-up inspection or monitoring scheduled
Record the date and time for any required follow-up inspection or monitoring.
-
Reference to service report or work order
Enter the related work order number, service report ID, or maintenance ticket.
-
Inspector or responder signature
Signature of the person completing the log.
How to use this template
- 1. Record the building, elevator number, event type, date and time, reporter contact, occupant count, and any occupant condition details as soon as the incident is reported.
- 2. Enter the acknowledgment time, on-site arrival time, and immediate actions taken to secure the elevator and communicate with occupants.
- 3. Document the technician or vendor dispatch, arrival time, name, and any escalation to the AHJ, emergency services, or other responders if the event requires it.
- 4. Confirm and record the safe release of occupants, the exact release time, and the post-event operational check before returning the elevator to service.
- 5. Note the suspected root cause, the corrective action, the linked service report or work order, and any follow-up inspection or monitoring that must occur.
- 6. Obtain the responder or inspector signature after the record is complete and review the log for repeat events that indicate a recurring deficiency.
Best practices
- Capture every timestamp in local time and keep the sequence consistent from report to acknowledgment, arrival, release, and restoration.
- Record whether occupants were calm, medically distressed, mobility-impaired, or otherwise at risk, because that changes the urgency and escalation path.
- Do not return the elevator to service until the post-event operational check confirms normal door operation, leveling, and safe travel.
- Photograph or attach the service report, controller fault code, or work order reference when a technical deficiency is identified.
- Use clear deficiency language such as 'door interlock fault' or 'leveling error' instead of vague notes like 'working again.'
- Flag repeated callbacks on the same elevator so maintenance can identify patterns before they become a larger life-safety issue.
- If lockout-tagout or equivalent isolation is applied, document who applied it and when it was removed.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this elevator entrapment and callback log cover?
It records the full incident trail for an elevator entrapment or callback event: building and cab identification, reporter details, occupant impact, response times, dispatch, release, restoration, and corrective action. It is meant to capture what happened, who responded, and when the elevator was safely returned to service. It also leaves room for the service report or work order reference so the log connects to the repair record.
When should this template be used?
Use it any time an elevator stops with occupants inside, repeatedly callbacks out of service, or requires emergency response and controlled restoration. It is also useful after a nuisance shutdown if the event required technician dispatch or a safety-related lockout. If the issue is purely routine maintenance with no service interruption, a standard maintenance log is usually a better fit.
Who should complete the log?
It is typically started by the person who receives the report and completed by the responder, property manager, facilities lead, or elevator service coordinator. A qualified technician should confirm technical findings and restoration steps, while the building team documents communication, occupant release, and follow-up. If the event escalates, the AHJ or emergency services involvement should be recorded by the person managing the incident.
How often should callback events be logged?
Every entrapment, callback, or emergency elevator shutdown should be logged individually, even if multiple events happen on the same day. That makes trend review possible and helps identify recurring deficiencies such as door faults, leveling issues, or controller resets. A single combined entry can hide repeat failures and weaken the corrective-action trail.
Does this template support OSHA or fire-life-safety documentation?
Yes, it supports documentation that aligns with general life-safety and maintenance expectations under OSHA, NFPA, and local code requirements. It is not a substitute for jurisdiction-specific inspection records, but it helps show response timing, safe release, isolation, and return-to-service verification. If the incident triggers a fire alarm, emergency recall, or AHJ review, those details should be captured here as well.
What are the most common mistakes when using this log?
The biggest mistakes are missing timestamps, failing to note whether occupants were safely released, and returning the elevator to service before verification is complete. Another common issue is recording only the symptom, such as 'stuck car,' without documenting the suspected cause or the corrective action. Teams also forget to attach the service report or work order reference, which makes follow-up harder.
Can this log be customized for a property portfolio or CMMS?
Yes, it can be customized with building IDs, asset numbers, vendor fields, escalation contacts, and work order links. Many teams also add fields for repeated-event counts, after-hours response, or whether the event involved passengers with mobility limitations. It can be mapped to a CMMS so the incident record and repair ticket stay connected.
How does this compare with an ad hoc incident note?
An ad hoc note usually captures only the fact that an elevator was down, which is not enough for trend analysis or compliance follow-up. This template creates a consistent record of response time, isolation, release, verification, and corrective action. That structure makes it easier to prove the event was handled safely and to spot recurring deficiencies across elevators or buildings.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Software bloat warning signs explained—spot bloated software early and choose leaner tools that boost performance, adoption, and ROI.
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
SharePoint 2016/2019 end of life guide: timelines, risks, and migration options to help you plan a secure intranet replacement.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
Ready to use this template?
Get started with MangoApps and use Elevator Entrapment and Callback Log with your team — pricing built for small business.
