Elevator safety standards in the UAE are enforced through a mix of national and local requirements, with inspection, maintenance and record keeping resting largely on the building owner. Understanding who is responsible for what makes compliance easier to manage and reduces the risk of an installation being taken out of service without warning.
Who is responsible for lift safety
The owner of the installation carries the underlying duty to keep a lift safe, even where a management company, facility manager or tenant handles day-to-day operation. In practice the owner appoints a competent maintenance contractor, funds maintenance and corrective work, and holds the inspection and maintenance records. Contracts should be clear about who reports faults, who authorises repairs and who liaises with the authority.
Obligations also reach the people using the lift. Passenger behaviour, overloading, misuse of the door and unauthorised access to the shaft are recurring causes of callouts. Clear signage, a working emergency communication path and a simple process for reporting faults matter as much as the mechanical condition of the equipment on any given day.
Responsibility should also be written into the lease. A tenant who controls access to a lift or uses it for commercial deliveries needs to know how to report a fault, what response to expect, and what load or use the installation was designed for. Ambiguity here tends to surface as an argument after a breakdown rather than as a plan before one.
Inspection and the approval chain
Inspection is the point at which an installation is checked against the requirements of the relevant authority, rather than against the maintenance contractor’s opinion. It usually combines a periodic inspection with the maintenance visits that sit between them, and it may be carried out by an approved inspector depending on the emirate and the installation type. The owner should know which authority is involved, who schedules the inspection and what evidence is needed on the day.
Approval does not end with the first certificate. Maintenance, repairs, component replacement and any modernization all feed into the ongoing status of the lift, and a defect noted at one inspection can affect the next. A lift that fails an inspection is usually required to correct the defect and be re-inspected, and in some cases it may be taken out of service in the interim.
The authority picture in the UAE is layered rather than single-track. Municipal requirements, Civil Defence expectations and the building’s own insurance conditions can all apply at once, and they are administered differently between emirates. The owner’s practical task is to establish, for each installation, which approvals and inspections apply and who is accountable for arranging them.
Maintenance obligations that matter
A maintenance contract is not a substitute for maintenance. The useful distinction is between routine, planned tasks that keep the equipment in condition and a fault-response service that only appears when something stops working. A contract should define visit frequency, the tasks in scope, response times for entrapment and other faults, the treatment of spare parts and the records the contractor will provide.
In older installations, obsolescence is the practical constraint on maintenance. Where a controller is no longer supported or a component is unavailable, the maintenance contractor cannot restore full reliability no matter how attentive the visits are. That is a lifecycle issue to plan for, not a fault to be absorbed indefinitely. The point at which support ends should be known before it arrives.
Planned maintenance should also be visible to the people who pay for it. Visit reports that record what was checked, what was found and what is outstanding give the owner a basis for budgeting and for challenging a contractor whose visits have become routine sign-offs. A maintenance contract without reporting is difficult to manage and easy to under-deliver against.
Safety devices and functions to verify
A routine maintenance visit should confirm that protective functions operate, not merely that the lift runs. Door protection, levelling, overspeed protection, the alarm and emergency communication, lighting in the car, and the fire-related operating modes all deserve verification and a recorded result. Testing every device at every visit is not realistic; the schedule should set out which functions are tested when and how the outcome is recorded.
- Door protection and the door open and close sequence
- Levelling accuracy and re-levelling behaviour
- Overspeed protection and the safety gear arrangement
- Car alarm, emergency lighting and two-way communication
- Fire recall and firefighting operating mode where required
- Signage, capacity plates and the current inspection certificate
- Pit, machine room and landing access conditions
Records that support audits
Records are the weakest part of many lift installations. A complete file should include the as-built information, the current maintenance contract, visit reports, test results, corrective work, spare parts used, inspection certificates and correspondence with the authority. It should be possible for a new contractor or an inspector to understand the installation’s history from the file alone.
The file should also record what has changed. Controllers, rope sets and door operators are replaced over the life of a lift, and the file is often the only reliable record of when. That history supports maintenance planning, budgeting and any later decision on modernization or replacement, and it protects the owner if an insurer asks how the equipment has been managed.
Retention matters too. Records kept only in a contractor’s system are not really the building’s records. The owner should hold a current copy, including the latest certificate and the outstanding defects list, so that a change of contractor or a sale of the asset does not begin with a search for documents.
A lift maintained without records is difficult to audit, and an audit is exactly the position an owner may need to defend after an incident.
Discuss a similar requirement