Digital elevator inspection
We build inspection platforms for companies responsible for lifts and lifting equipment across a portfolio of buildings. Scheduled examinations, defect to repair tracking, and certificates a regulator will accept.
Book a 30-minute scoping call See how we build these
If an off-the-shelf inspection app already fits your schedule of examination, we will tell you so on the first call.
| Suspension ropes Wear and lay length checked | Pass |
|---|---|
| Safety gear and overspeed Function tested under load | Pass |
| Landing door interlocks All 9 floors | Pass |
| Brake test Below spec, repair order raised | Defect |
| Next examination due Six months from today | 14 Feb |
The honest question first
Plenty of field service products cover scheduled maintenance well. Building only pays off when your obligations sit outside what those products model.
Buy a product when
We will name the products worth shortlisting and leave it there.
Build when
These are the parts we have built before, on statutory anchor testing at height and on instrument integration.
Plain definitions
Separating them early decides whether you are shopping for a field service product or building a compliance system.
It is the system a competent person uses to record a statutory examination and produce the report that follows. The record attaches to one specific car, not to a building. It carries the examiner, the date, the findings, the defect severities and the date the next examination falls due.
Accountability is what separates it from a maintenance app. A maintenance visit produces a job sheet. An examination produces a document somebody signs their name and their competence against, and an insurer may read it years later.
Maintenance keeps the lift running. A thorough examination is an independent check that it is safe to keep using, and the two are kept apart on purpose. Under LOLER 1998 in the UK a lift carrying people is examined at least every six months, goods-only lifting equipment at least every twelve, or on whatever interval a written scheme from a competent person sets.
In the US the cycle follows ASME A17.1, with a Category 1 test each year and a Category 5 full-load test every five years, and the authority having jurisdiction decides who may sign it. Software that treats an examination as another job type will fight you. The scheduling, the sign-off, the certificate and the retention rules all behave differently.
What we build
Who carries the obligation
The examination itself is broadly the same everywhere. What differs is who has to answer for it, and to whom.
Our work
We have not yet delivered a lift-specific platform. What we have delivered is statutory inspection at height, instrument integration and device telemetry, which are the three hard parts of one.
Case study, United Kingdom
A digital testing platform for work-at-height anchor and torque checks: scheduled examinations against a defined procedure, capture on site where signal is unreliable, pass and fail logic tied to load values, and a certificate produced at the end that the duty holder can file.
Read the two builds behind it: Hydrajaws instrument integration and the work-at-height testing platform.
How the work runs
Week 1 to 2
We work through your schedule of examination and your current certificate with the person who signs them, and write down what the system must produce.
Week 3 to 4
Asset hierarchy, examination cycles, defect severities, certificate layout, and what happens with no signal.
Week 5 to 12
One engineer, one building, real examinations, while we are still building. Demo every two weeks.
Ongoing
Region by region, then the link into your job management or finance system.
Technology and integration
None of this is exotic. The difficulty is a basement with no signal and a report that has to be right.
Who does the work
Compliance work turns on details that surface only when the person building it has read your schedule of examination. So the people on the scoping call are the people who write the code.
We have shipped statutory inspection software for UK clients already, so the vocabulary on your side of the call is not new to us.
How we work
The models differ in one thing: how much of the management you hand over. Everything else, including who owns the code, is the same in all five.
Changing model later is normal. Augmentation into a dedicated team is the common direction, and the people stay.
Engineers join your team and work inside your process, your board and your code review.
A team that works only on your product, with a lead on our side running delivery.
A long-term engineering site under your standards, where we carry recruitment, HR, payroll and equipment.
04
One price for a scope that is genuinely settled, with the overrun carried by us.
Everything in the centre model, with the whole team moving into your own Vietnamese entity on an agreed date.
FAQs
Not a lift-specific one. We have built statutory inspection for work-at-height anchor and torque testing, which shares the same shape: a defined procedure, offline capture, pass and fail against measured values, and a certificate at the end. We would rather say that plainly than imply otherwise.
Yes. Examinations capture on the device and sync when the engineer gets coverage. This is a normal requirement for us, not an edge case.
Yes, and that is usually the reason to build rather than buy. Your competent person defines the procedure and the system follows it, instead of you bending the procedure to fit a product.
Yes, either inside the platform or pushed into the job system you already run. We have built integrations against ERP and CMMS systems, including older ones with no modern interface.
If the test equipment exposes a Bluetooth profile or a vendor SDK, the value can be captured directly rather than typed. We did this for torque and pull testing with the KTC SDK.
You do. Data sits in your own cloud tenant in the region your policy requires, and all intellectual property in the software belongs to your company.
A pilot on one building usually runs 10 to 14 weeks from kickoff, with a demo every two weeks from around week five.
In the UK, LOLER 1998 sets at least every six months for a lift carrying people and at least every twelve months for goods-only lifting equipment, or whatever interval a written scheme from a competent person specifies. In the US the pattern follows ASME A17.1, with a Category 1 test each year and a Category 5 full-load test every five years. The system holds whichever cycle applies to you rather than a hard-coded default.
None directly. Software carries no certification of its own here, and any vendor telling you their product is LOLER certified is selling you something that does not exist. What the software has to do is produce a record your competent person and your insurer will accept, and keep it available and unaltered for as long as your retention policy says.
Usually it should not, and we will argue against it. If a CAFM or CMMS already holds the estate, the cheaper build sits beside it and pushes defects across as jobs. We have built that kind of integration against older systems with no modern interface, which is normally the part people expect to be hard.
That document plus a sample certificate tells us almost everything. Thirty minutes and you will know whether building is worth it for your portfolio.
