Short answer: build one controlled record stack per represented lift
Identify each unit and controller, then separate Planning permission, Building Control permit, elevator or conveyance permit, review, inspection, acceptance or final, wider building certificate, periodic certificate evidence, service, faults and outages, emergency information, accessibility interfaces and responsibility. Preserve exact unit identifiers, source, date, scope, limits, mismatch, answer owner, deadline and written closure. A successful ride, sticker, certificate, contract, visit or invoice does not prove present operation, code status, emergency function, accessibility, reliability or safety.
| Lane | Preserve | Do not infer |
|---|---|---|
| Identity and official stages | Unit identifier, type represented, location and served levels, controller, applications, permits, drawings, inspections, acceptance/final and wider certificate records. | That two labels name one unit, a marketing description is technically correct, or one stage proves another. |
| Service and operation history | Contract scope, planned visits, call-outs, repairs, parts, modernization, warranty, fault/outage/entrapment chronology and open work. | Current condition, maintenance quality, reliability, safety, remaining life or future availability. |
| Interfaces and responsibility | Emergency contacts, call/alarm records, power and fire interfaces, accessible-route evidence, private/common control, costs, insurance and handover. | Emergency capability, accessibility compliance, duty, cost allocation, coverage or transaction result. |
Identify every represented unit, served level, and controller
Record the exact property, building, unit or common area, each manufacturer/model/serial or asset identifier supplied, lift type as represented, location, served floors or landings, machine/control-space representation, private or common scope, owner or controller represented, service provider and decision deadline. Keep identifiers consistent across every record and flag aliases or conflicts. Do not classify equipment, infer ownership or enter a shaft, pit, car top, machine room, control room or restricted space.
| Identity field | Capture | Keep open |
|---|---|---|
| Equipment | Displayed and document identifiers, manufacturer/model/serial if supplied, type represented, installation/alteration date, location, served levels and linked drawing or report. | Technical classification, capacity, code edition, present condition, operating status or safe use. |
| Controller and decision | Private/common representation, owner/landlord/strata/manager controller, access authority, service contact, purchase/lease/insurance context, deadline and principal owner. | Legal responsibility, authority, access right, maintenance duty, cost, liability or condition outcome. |
Build the Planning, permit, inspection, acceptance, and certificate stack
Planning separates planning permission, Building Control permits and multi-discipline review, inspection and final or occupancy stages. Its lift guidance describes a distinct elevator or conveyance permit lane, while its final-inspection material distinguishes elevator acceptance/final from broader project finals. Preserve each application and identifier, job-specific drawing and revision, review, permit, inspection, acceptance/final, building certificate, later alteration and unresolved item separately. One stage does not prove current equipment condition or another stage.
| Stage | Evidence | Boundary |
|---|---|---|
| Installation or alteration | Planning/project and elevator permit identifiers, drawings/revisions, reviewer or submission record, conditions, issue dates, unit match and later changes. | Do not decide which permit was required, interpret the design, or infer installed work matches records. |
| Inspection and finals | Exact inspection/acceptance/final record, unit identifier, date, scope/status represented, outstanding items, broader building final/certificate and later periodic evidence. | Elevator acceptance is not the same as a wider final, and neither proves present operation, accessibility or safety. |
Treat January 2020 elevator guidance as dated process context
Planning's January 2020 Elevator/Conveyance Permit Application Guidelines describe job-specific submissions, review, inspection and certification and reference a 2016 code baseline. Label that document visibly as dated context and recheck current requirements with Planning for the exact project and decision date. Do not publish its steps, code reference, reviewer arrangement or submission details as current universal instructions or proof that an exact lift has a permit, certificate or approval.
| Dated source | Safe use | Do not claim |
|---|---|---|
| January 2020 GN0011 | Use it to identify possible record categories and questions; preserve any exact-property submission or response separately with current Planning confirmation. | That the 2016 baseline or process remains universally current, complete or applicable. |
| Current property question | Exact lift, installation/alteration date, supplied record, current Planning source/version, named question, authority response and limitation. | Code edition, grandfathering, approval, certificate status, operation or compliance from the old note alone. |
Reconcile certificate identifiers and dates without interpreting status
For every displayed or supplied certificate, renewal, inspection or test record, preserve the issuer, exact unit identifier, record type, issue or inspection date, stated period or expiry representation, scope, conditions or observations, source, photograph or copy date, alteration after issue and mismatch. The Building Code Regulations establish an adopted elevator-code framework and official periodic inspection and test schedules, but this page does not select a code, calculate an interval or due date, verify a certificate or decide compliance.
| Certificate control | Record | Do not decide |
|---|---|---|
| Identity match | Issuer, record number/type, unit and building identifiers, date, scope, displayed/supplied source, alterations, service records and conflicting labels. | That the record belongs to another similarly named unit or proves current condition. |
| Timing and status | Exact dates and wording as supplied, current official source checked, any follow-up or renewal evidence and the responsible official/qualified question. | Do not calculate a statutory interval, expiry, breach, inspection result, code status or permission to operate. |
Separate service contract, maintenance, repair, and modernization
A service agreement describes promised scope; it does not prove every visit or task occurred. Preserve provider identity, contract dates, assets covered, planned-maintenance scope, attendance records, checklists or reports supplied, call-outs, faults found, parts, repair recommendations, completed and open work, modernization proposals, warranties, exclusions, access issues and termination or transfer terms. Do not rate provider competence, infer maintenance quality or treat a recent invoice as a safe/current lift conclusion.
| Service lane | Evidence | Unresolved control |
|---|---|---|
| Planned maintenance | Contract and asset list, schedule represented, actual visit records, technician/provider, scope, findings, recommendations, closure evidence and missed/access-limited visits. | Contract existence, invoice or sticker from completed maintenance, code status, condition or reliability. |
| Repair or modernization | Fault/work order, qualified assessment, proposal and alternatives, approval record if applicable, parts/obsolescence representation, work completed, test/review record, warranty and open items. | Repair sufficiency, remaining life, modernization need, cost reasonableness, safe operation or future performance. |
Build the outage, fault, shutdown, and entrapment chronology
Record every supplied fault, intermittent operation, outage, shutdown, entrapment, complaint, service interruption and return-to-service representation by exact unit. Include date and duration, source, people affected only where privacy-safe, conditions represented, posted or responsible-party response, provider attendance, findings, work, closure evidence and later recurrence. Absence of a disclosed event does not prove reliability, and chronology does not establish cause or predict performance.
| Event | Minimum record | Do not infer |
|---|---|---|
| Fault or outage | Exact unit, start/end or bounded duration, source, fault wording, shutdown/control response, service call, finding/work, return representation and later event. | Cause, maintenance failure, safe use, reliability, repair completion or future availability. |
| Entrapment or complaint | Date, exact unit, source and role, posted/emergency process used as represented, responsible response, service/official record, closure and privacy limitation. | Fault, liability, rescue adequacy, response-time promise, trauma/medical conclusion or no recurrence. |
Review emergency information and controls without testing them
Preserve posted emergency contacts, call or alarm and communication records, signage, recall or firefighter-control representations, emergency service instructions, inspection/service evidence and unresolved questions. Do not press or test alarms, phones, intercoms, emergency stops, recall, firefighter controls or backup-power operation; do not simulate a fault, force or hold doors, reset or isolate equipment, use technical keys, release occupants or attempt rescue.
- An alarm label or successful call representation is not proof of current communication, monitoring, response or rescue capability.
- Keep fire/life-safety controls inside an authorized qualified scope and the building's wider emergency plan.
- If someone is trapped, or there is smoke, fire, uncontrolled movement, an open shaft/door or exposed hazard, follow posted emergency and official/responsible-party instructions.
- Do not improvise a rescue, enter a restricted space, override equipment or re-open a lift for due diligence.
Keep backup power and electrical evidence in adjacent qualified scopes
Record only supplied representations and reports for lift electrical supply, controller, disconnects, standby generator or other backup-power interface, transfer behaviour, recall interaction, outage history and qualified testing. Use the electrical and generator guides for those systems. Do not open panels, operate switches, simulate a power failure, test transfer or recall, decide required coverage or infer that a generator nameplate or building outage plan proves the lift will operate.
| Interface | Preserve | Boundary |
|---|---|---|
| Electrical | Qualified report and service records, exact lift and circuit/interface identifiers, faults, alterations, permit/inspection records, limitations and open item. | No panel access, electrical test, code interpretation, condition or safety conclusion. |
| Backup power | Generator/transfer representation, lift coverage stated, authorized test or outage records supplied, fire/recall dependencies, service history and responsible professional answer. | No promise that the lift runs in an outage, serves every floor or provides an evacuation route. |
Separate exact-lift access from whole-building accessibility and evacuation
A lift can be one part of an accessible route without answering parking, approach, thresholds, doors, controls, level changes, corridors, refuge, power continuity, evacuation, accommodation or household-fit questions. Preserve the household-defined need, exact route and lift interface, supplied accessibility or occupational reports, dimensions only where professionally supplied, outages, alternatives represented, responsibility and limitations. This page does not certify accessibility or promise that a home suits a person.
| Scope | Evidence | Do not promise |
|---|---|---|
| Lift interface | Served levels, entry/landing relationship, controls and door representation, ordinary access record, qualified accessibility scope, outages and inaccessible items. | Code compliance, independent use, fit for mobility equipment, continuous availability or household suitability. |
| Wider route and emergency | Parking/approach, thresholds, doors, circulation, refuge/evacuation plan, accommodation records, power dependencies, responsible party and qualified limitations. | That the lift is an evacuation solution or that one accessible feature makes the route or property accessible. |
Reconcile private, common, strata, landlord, insurer, and lender records
Use title, lease, strata plan and bylaws, minutes and reserves, management notices, service contracts, insurance and lender records to capture ownership, operation, access, notice, maintenance, modernization, outage communication, cost and handover representations. Do not allocate duty, contribution, liability or insurance from equipment location, account holder, service invoice or management practice. Keep technical, legal, operational, insurance and principal decision questions separate.
| Responsibility lane | Records | Keep unresolved |
|---|---|---|
| Private or tenancy | Sale/lease, inventory, access and handover, equipment/service records, notices, repairs, costs, insurance and promised work. | Ownership, duty, repair responsibility, rent/lease remedy, disclosure or payment. |
| Strata or shared | Strata documents, asset register, management authority, minutes/reserves, contract, outages, planned modernization, insurance, contributions and disputes. | Common/private classification, voting/authority, contribution, liability, modernization decision or coverage. |
Keep ordinary observations non-technical and non-diagnostic
A lawful ordinary-position record may note the displayed unit identifier, landing served, certificate or contact displayed, visible barrier or out-of-service notice, ordinary ride representation supplied by another party, noise or movement wording as reported, and inaccessible records or spaces. It must not become a test or reassurance. Do not repeatedly ride, test doors, load the car, measure gaps, inspect a pit or machine space, assess braking or levelling, or infer maintenance, reliability, accessibility or safety from one trip.
- A normal ride is not evidence of current certificate, inspection, alarm, emergency power, braking, controls, maintenance or future operation.
- An out-of-service sign or shutdown should be preserved with date and source, not overridden or investigated.
- Keep security codes, technical keys, emergency contact details and incident information private and out of public URLs or shared notes.
Close with written conditions and a controlled lift handover
Before closing, signing, releasing a condition, move-in or taking management responsibility, issue one register per lift showing identifiers and served levels, official-stage records, certificate evidence, current-law/version questions, service contract and completed visits, repair and modernization work, outage and entrapment chronology, emergency information, electrical and backup-power dependencies, accessibility interfaces, private/common responsibilities, inaccessible records/spaces, promised work, owner, deadline and closure evidence. Move to Cayman can organize a privacy-safe evidence plan; it does not inspect, test, certify or rescue, accept evidence, calculate due dates, allocate cost, waive a condition or recommend proceeding.
| Closeout | Written evidence | Final control |
|---|---|---|
| Unit and records | Exact identity, permits/inspections/finals, certificates, service/work history, faults/outages, emergency and power records, accessibility scope and mismatches. | Did every record match the exact unit, date, scope and source without becoming a safe/current conclusion? |
| Responsibility and decision | Governing documents, qualified questions, insurer/lender requirements, promised action, owner, deadline, completion proof, condition status and principal action. | Did the principal act on completed evidence rather than a ride, sticker, certificate display, contract or invoice? |
Trust note
Last updated August 2026. This guide is written for relocation planning and should be verified with licensed Cayman professionals for legal, tax, immigration, medical, insurance, or financial decisions.
Reference points: Planning — Building Control Unit, Planning — Building Codes, Planning — Process, Planning — Online Planning System, Planning — File Request, Planning — Laws & Regulations, Planning — Elevator/Conveyance Permit Guidelines (January 2020), Planning — Development Application Process / Final Inspections, Building Code Regulations (2022 Revision).