Twenty Fields, One Defensible Record
An elevator incident involving a passenger entrapment or injury generates regulatory scrutiny within hours. The jurisdictional authority wants an incident log. The building owner wants a liability trail. The maintenance company wants a record that documents their mechanic's license number and the actions taken before the unit was returned to service. Without a structured incident log, those three stakeholders get three different accounts of what happened, assembled from memory and phone calls, and the discrepancies between them become the problem.
The Elevator ID number is the critical link between this incident record and the elevator's maintenance history, inspection record, and regulatory registration. An incident filed without that ID against the correct asset is a free-floating document that tells a story nobody can verify.
The Time Gap Nobody Thinks About Until Discovery
This template captures two separate date fields: the Date the report is logged (when the call comes in) and the Acc. date (when the accident actually occurred). These are not the same field. A passenger entrapment that occurs at 11:47pm Friday may not get reported until Saturday morning. A mechanical failure may be reported hours after the event by a third party. The gap between accident date and reporting date is relevant to regulatory compliance timelines in most elevator jurisdictions. If a fatality or serious injury requires notification within 24 hours, the acc. date determines whether you're in compliance, not the date the paperwork was filed.
The Call From field and Contact field handle the incoming chain of custody. Call From records who initiated the report — the building's property manager, the MEMA safety program, the owner. Contact records who to call back. These are not the same person. The At Phone field stores the number. Two additional Memo fields capture the evolving account as the incident develops — what was known at first call versus what was known after the mechanic arrived on site and diagnosed the actual cause.
The Mechanic License Number as the Load-Bearing Detail
Mechanic license number sits in its own field, not embedded in a notes line. That is deliberate and it matters. When a jurisdictional authority audits the incident log, they're checking that licensed personnel performed the remediation. A mechanic name without a license number is unverifiable. A license number can be cross-referenced against the regulatory body's registry in under a minute.
Action Taken documents what was done. Return to Service records whether the unit was cleared — expected to be Y or N but held as a text field to allow for conditional clearances ("Y - with 30-day reinspection required"). Inspector and Office close the chain of custody on the regulatory side.
At a portfolio level covering multiple buildings across multiple locations, this record structure enables something a paper log never can: pattern analysis across incidents. If Elevator ID 123-P-456 has three incident records in eighteen months and the "What Happened" field mentions leveling issues each time, that pattern is findable in seconds. The mechanic and the building owner and the regulator each have a different reason to want that answer.