Smart Elevator / Service History
A record you can
stand behind.
Elevator service history software that ties every visit, part, fault and fix to the unit it happened on. When a client disputes an SLA, when a manufacturer questions a warranty claim, or when an auditor asks for two years of evidence, you answer with records instead of recollection.
The problem
Records only matter on
the day you need them.
Paper job cards, photos in a group chat, and a spreadsheet three people maintain feel adequate right up to the moment somebody challenges you. Four situations where the difference shows.
The client says you never attended
Without a record
A technician remembers going. There is a job card somewhere in a folder in another office. The conversation ends with a credit note.
With the record
The visit is on the unit timeline with the technician, arrival and departure timestamps, the work recorded, and the photos taken on site.
The manufacturer questions a warranty claim
Without a record
Nobody can produce the fitting date of the component, the serial, or the fault that preceded it. The claim is written off as a cost of doing business.
With the record
The component record shows the part, the serial, the fitting date, the warranty terms, and the fault log leading up to the failure. The claim goes out with evidence attached.
A new technician takes over the route
Without a record
Every quirk of every building lives in the head of the person who left. The first three months are rediscovery, and the client notices.
With the record
The unit record carries controller type, access notes, recurring faults, past interventions, and open findings. Context transfers with the route.
An audit asks for two years of maintenance evidence
Without a record
Someone spends a week assembling paper, WhatsApp photos, and half-remembered dates into something presentable.
With the record
The report is generated per unit or per site, in the format the auditor asked for, in the time it takes to select a date range.
The pattern underneath all four is the same. Records scattered across paper and chat on one side, one timestamped log on the other.
What sits on the unit
One timeline per lift.
Everything on it.
A service history is only useful if it is complete enough to answer the awkward question. These are the layers that make it complete.
What each unit record holds, at a glance.
- A chronological visit log with technician, duration and outcome
- Fault history decoded and grouped so recurring behaviour is obvious
- Parts and components with serials, fitting dates and warranty terms
- Warranty position tracked per unit and per part with expiry alerts
- Linked tickets and proposals as one chain, no orphan documents
- Attachments, readings and an amendment trail that stays defensible
Chronological visit log
Every attendance in order: date, technician, type of visit, duration, work performed, and outcome. Planned maintenance, breakdown calls, and quoted repairs sit on the same line so the true service load per unit is visible.
Fault history with context
Controller fault codes decoded into plain language with timestamps, grouped so recurring behaviour is obvious. When the same door fault has appeared eleven times in four months, the record says so.
Parts and component history
What was fitted, when, by whom, from which stock batch, with its own serial and warranty terms. Component-level history is what makes a claim survivable months later.
Warranty position per unit and per part
Unit warranty, extended cover, AMC scope, and component warranties tracked separately, with alerts ahead of expiry and a clear answer on what is claimable at the moment work is proposed.
Linked tickets and proposals
The complaint that started it, the ticket that tracked it, the proposal that quoted it, and the visit that closed it are one chain. No orphan documents.
Attachments and readings
Photos, meter readings, safety checks, and signed job sheets captured on site and attached to the entry rather than sent to a group chat.
Amendment trail
Corrections are recorded as amendments with an author and a timestamp. The original entry is never quietly rewritten, which is what makes the record defensible.
Exportable reports
Per unit, per site, per contract, per date range, in the layout your clients and auditors expect. Generated from live data rather than rebuilt in a spreadsheet.
Tell us what your worst records dispute looked like. We will show you the record that would have ended it.
Book a scoping call →Warranty tracking
Cover that is tracked,
not assumed.
Warranty is the part of service history that has money attached to it. Windows lapse quietly, components get replaced under a cover nobody claimed, and the loss never appears as a line in any report. Four stages that close that gap.
How a visit becomes claim-ready evidence, in four steps.
Attendance, work and photos captured on site.
The entry attaches to the elevator record, not a notebook.
Cover checked per unit and per part, with expiry alerts.
Fault history, serials and logs pulled into one document.
Terms captured at handover
Unit warranty, component cover, AMC scope, and any negotiated extension are recorded when the asset is onboarded, along with the documents that define them.
Cover checked at the point of work
When a technician records a finding, the system already knows whether it falls inside cover. The commercial decision happens on site, not three weeks later.
Alerts before the window closes
Expiry thresholds you set trigger tasks to inspect, claim, or convert to a contract renewal while the cover is still live.
Claim pack assembled from the record
Fault history, fitting dates, serials, visit logs, and photos are pulled into a single claim document without anyone hunting through folders.
Why RnD Square
Your documentation
standard, encoded.
Every elevator company has a documentation standard, whether it is written down or carried by the service manager. Fixed products replace it with theirs and the team quietly keeps a parallel spreadsheet. RnD Square builds the record structure your contracts, regulators, and clients already expect.
Real data behind the log
The IoT hardware and firmware are engineered in house, so fault timestamps come off the controller rather than from a phone call. A service history built on machine-recorded events carries weight that a typed log does not.
Fields that match your work
Statutory inspection items, safety checks, contract-specific tasks, and the fields your clients insist on are part of the schema rather than crammed into a notes box.
One system, no reconciliation
Because ticketing, maintenance, proposals, stock, and accounting are built by the same team into the same system, a visit updates the record, the parts ledger, and the billing position at once. Nothing is retyped between tools.
FAQ
Questions about records and warranty.
Related
What feeds the record.
Build the record once.
Use it for years.
Bring your current job card, your contract obligations, and the reports your clients ask for. We will scope the service history and warranty layer around them.