Skip to content
DT Nova
Services

Elevator maintenance software for lift service companies

Elevator maintenance software that knows every unit in your portfolio: each lift, escalator and platform on its own maintenance plan, entrapments routed to the nearest technician before anything else, thorough examinations and inspections planned with their defects followed to closure, and the logbook complete when the examiner asks for it. We build custom lift and elevator maintenance management software for independent lift companies and service organisations, hosted in the EU, and your company owns the code.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

Why lift maintenance needs its own system

Our field service management software page covers companies with technicians on the road in general. Lift maintenance is different in three ways. The work is organised around units, not customers: a housing company may have forty lifts of six makes and ages, each with its own controller, history and plan. The risk is asymmetric: a passenger trapped in a car outranks every other job on the board, and the response is measured in minutes. And the unit sits inside a legal regime of examinations, inspections and records, where the examiner's findings decide whether the lift may run.

Many lift companies still run this with a service planning tool, a separate list of examination dates, paper logbooks in machine rooms and a monitoring portal nobody connects to the jobs.

What the system does

Examinations, inspections and the logbook

Rules on periodic examination of lifts are national. In Great Britain, lifting equipment for lifting persons must be thoroughly examined at least every 6 months, or in line with an examination scheme, and each time exceptional circumstances liable to jeopardise its safety have occurred, with inspections by a competent person at suitable intervals between examinations where appropriate (Lifting Operations and Lifting Equipment Regulations 1998, regulation 9). The person making the examination must notify the employer forthwith of any defect that is or could become a danger, make a written report, and send a copy to the enforcing authority where a defect involves an existing or imminent risk of serious personal injury; the employer must not use the equipment before such a defect is rectified (regulation 10). Other countries set their own intervals and inspection bodies, and in the United States the rules come from state and local codes, many based on the ASME A17.1 safety code.

At the European level, the Lifts Directive requires each lift to be accompanied by instructions covering maintenance, inspection, repair, periodic checks and rescue operations, and by a logbook in which repairs and, where appropriate, periodic checks can be noted (Directive 2014/33/EU, essential requirement 6.2). (All sources read on 12 November 2026.)

The system keeps that record per unit. Each lift carries the interval and examining body that apply to it, and the next examination is planned with enough lead time to book a technician to attend it. When the report arrives, each defect is entered with its category and deadline and becomes a job; a defect that stops the lift is flagged on the unit, and the owner sees the status in the portal. Every visit, repair and check writes to the digital logbook, so the examiner and the owner see the same history the technician sees.

Entrapments and breakdowns first

Lifts must have a way to release and evacuate people trapped in the car and two-way communication with a rescue service (Lifts Directive, essential requirements 4.4 and 4.5). Your response to that alarm is the part of the service the building remembers. In the system, an entrapment from the alarm centre, the monitoring platform or the building's own report opens the highest priority job on the unit. The board shows the nearest technicians who know that controller, with their current job and travel time; the dispatcher assigns, the building contact gets an update, and the technician records the time of arrival and release. The repair that follows is a separate job, so the release time and the fix time are measured apart.

Other breakdowns follow the contract's response time and the building's profile: a single lift in a care home or a hospital ranks above one of four in an office tower. Repeated breakdowns on the same unit are counted, and after the threshold you set, the unit is flagged for a technical review instead of another quick reset.

Maintenance plans per unit

A traction lift from the 1990s, a new machine-room-less lift and a hydraulic goods lift do not need the same visit. The system builds each unit's plan from its type, components, usage and age: the visit frequency from the contract, and the tasks per visit from the components, such as doors and door operators, brakes, ropes or belts, guides, safety gear, hydraulic oil and the alarm line test. Tasks with longer intervals, such as a rope inspection or a safety gear test, rotate through the visits. Visits are grouped by building and area so one technician covers a cluster of units in a day.

Remote monitoring and fault data

Many lifts send fault codes, trips, door cycles and alarms to a monitoring platform. The system reads them where the platform or controller offers an interface or an export, attaches them to the unit, and turns patterns into work: a door fault repeating five times in a day opens a job before the building complains, and run counts can drive usage-based maintenance tasks. For the device and data side, see IoT software development; for maintenance triggered by time, usage and condition in general, see preventive maintenance scheduling software.

Modernisation projects next to service

Replacing a controller, a drive or a complete lift is a project of weeks, with surveys, quotes, ordering, installation and handover inspection, while the rest of the building's lifts stay in service. Projects are planned in phases with crews and materials on the same board as maintenance, so a modernisation does not quietly absorb the technicians a region counts on. Survey findings from maintenance visits become modernisation quotes, and a unit's history shows the case for replacing it.

The technician app

Technicians see their route, open each unit with its history, wiring diagrams, fault codes and parts, work through the visit checklist, record readings and photos, and sign off. Entrapment jobs arrive with an alert that overrides the day. The app works offline in machine rooms, pits and shafts without coverage and syncs when the signal returns. We build for iPhone and Android from one codebase.

Ready-made software or custom?

Large lift manufacturers run their own service platforms, and independent companies often use general field service platforms such as Salesforce Field Service, Microsoft Dynamics 365 Field Service or IFS, or smaller maintenance tools. For many companies one of them fits, and we will say so. Custom software pays off when your unit register, examination regime, contract types, monitoring sources or owner reporting do not match what the product assumes, or when the logbook still lives on paper in the machine room.

SituationReady-made platformCustom software
Single make, simple contractsUsually enoughRarely worth building
Mixed makes and controllersGeneric asset fieldsComponents, codes and tasks per unit type
National examination regime and defectsOften add-ons or manual listsIntervals, reports and defects per unit
Monitoring from several providersThe vendor's own devicesThe sources you use, on one unit record
Data location and ownershipThe vendor's platform and regionYour account, EU data region

How we build it

  1. Workshop with dispatch and the field. Your dispatchers, service managers and senior technicians show how a week runs, including how entrapments and examinations are handled today. We write it down for approval.
  2. Scope and fixed price in writing. Unit register, plans, priority rules, examinations, integrations and what the first phase leaves out, with a fixed price for that agreed scope.
  3. A test version on real data. Your units, contracts and last season's jobs and examination reports, imported and checked.
  4. Pilot with one region and acceptance. A group of technicians uses the app for a few weeks, rules are tuned, and the phase is accepted against the written scope.
  5. Roll out and measure. Time to release, overdue visits, open defects past deadline and repeat breakdowns are compared with the numbers recorded at the start.
  6. Maintenance. Updates, monitoring, backups and rule changes, on a monthly plan you can cancel with one month's notice.

As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your name. Building owners who manage lifts among many other assets may also want facility management software. See prices.

Questions we get

What does elevator maintenance software manage?

The units you maintain and their history, the maintenance plan per unit, breakdowns and entrapments with priorities, examinations and inspections with their reports and defects, parts, technicians and their authorisations, the digital logbook and the contract billing. Remote monitoring data can raise jobs automatically.

Can it put passenger entrapments ahead of everything else?

Yes. An entrapment reported by the lift's alarm line, the monitoring system or the building is the highest priority type. The system suggests the nearest technician who can respond, notifies the building contact, tracks the time to release, and records the release and the follow-up repair as separate steps.

Does it plan thorough examinations and periodic inspections?

Yes. Each unit carries the examination or inspection interval that applies to it, for example at least every 6 months for lifting equipment for lifting persons in Great Britain under LOLER regulation 9. The system plans the examination and the technician to attend it, and the examiner's defects become jobs with deadlines.

Can it work with the lift controllers and monitoring we already use?

Yes, where the controller or monitoring platform offers an interface or an export. Fault codes, trips and alarms become events on the unit, and repeated faults can open a job before the building notices. Monitoring itself stays with the provider you choose.

Can we start with one region or one contract type?

Yes. Most companies start with the unit register, maintenance plan and technician app for one region, and add examinations, monitoring and the customer portal in later phases, each with its own scope and fixed price.

Who owns the system?

Your company. The source code sits in a repository in your own account, and the database and hosting are in your name in an EU data region.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote