Buying elevator maintenance software is one of the most consequential operational decisions an elevator service company makes. The wrong platform will cost you six months of configuration, a migration mid-year, and a team that never fully adopts the tool. The right platform will become the operating system of your business.

This guide covers what to look for, what to ask, how to evaluate pricing, and how to run a pilot that gives you a real answer before you commit.

The eight must-have features

1. Work order management with auto-dispatch

The core of any elevator maintenance platform. Evaluate: Does the system auto-create work orders from fault reports? Does it assign technicians automatically based on skill, location, and availability? How long does it take from a customer fault call to a dispatched technician?

The best platforms reduce this to under two minutes without human intervention.

2. Preventive maintenance scheduling from contract terms

Preventive maintenance should be scheduled automatically from the contract — not manually entered by a dispatcher each month. The platform should generate work orders, assign technicians, and alert on SLA risk without a person managing the calendar.

Ask vendors: "If I have 500 elevators on monthly preventive contracts, how does the system generate and assign those jobs automatically?"

3. Offline-first mobile app for field technicians

This is non-negotiable for elevator maintenance. Technicians work in basement machine rooms with no mobile signal. The app must function completely offline — checklists, photo capture, signature collection, parts logging. "Limited offline mode" is not sufficient.

Test this before buying: ask for a demo where the vendor puts the device into airplane mode and demonstrates a complete job workflow.

4. Inspection checklists (EN-81 or A17.1)

If you operate in Europe, EN-81 compliance documentation is a regulatory requirement. In North America, A17.1. Verify whether checklists are built into the platform or whether you must configure them manually from scratch.

Manual configuration means weeks of setup, inconsistent results across technicians, and ongoing maintenance as standards evolve. Built-in checklists mean immediate readiness and consistent documentation quality across your entire team.

5. OEM brand-aware technician dispatch

Elevator OEM certifications matter for warranty preservation and compliance. Your dispatch system should know which technicians are certified for KONE, Otis, Schindler, ThyssenKrupp, Mitsubishi, and Hitachi — and auto-match jobs accordingly.

If your dispatchers currently cross-reference certifications in a spreadsheet, a proper dispatch engine eliminates that step entirely.

6. Per-elevator contract billing

Elevator maintenance contracts are typically billed per elevator per month, not per service call or per hour. Verify that the platform handles this billing model natively. Many general-purpose tools require an accounting integration or manual reconciliation to produce accurate invoices from contract terms.

Look for: automatic invoice generation from completed work orders against contract billing rules, tier-based pricing support (silver / gold / platinum), and auto-renewal management.

7. Spare parts and inventory management

Technicians carrying the wrong parts — or no parts at all — is one of the largest sources of repeat visits and customer dissatisfaction in elevator service. A platform that tracks van stock in real time, maintains reorder thresholds, and surfaces low-stock alerts before technicians leave for a job is worth measurably more than one that doesn't.

Bonus: OEM-specific parts catalogs preloaded (Schindler, KONE, Otis, ThyssenKrupp, Mitsubishi, Hitachi) save significant catalog-building time.

8. Customer portal for fault reporting

Property managers and building supervisors should be able to report faults, check job status, and download invoices without calling your office. A self-serve portal reduces inbound call volume and response times — and the data it generates (fault frequency, building-level patterns) is operationally valuable.

Pricing models: per user vs per elevator

There are two dominant pricing models in this category. Understanding which one is cheaper for your operation matters.

Per user per month (UpKeep, Limble, FieldEdge)

  • Typically $40–$95/user/month for full-featured plans
  • Every technician, dispatcher, and office staff member is a billable user
  • Cost scales with headcount

Flat monthly plan (LiftGrid)

  • Starter: $24/month (3 users, 150 elevators)
  • Pro: $49/month (10 users, 750 elevators)
  • Business: $79/month (30 users, 2,500 elevators)
  • Cost is fixed — does not increase with headcount

Example calculation — 10 technicians, 3 dispatchers, 2 office staff, 200 elevators:

| Model | Platform | Approx. monthly cost | |---|---|---| | Per user | UpKeep Business | 15 users × $85 = $1,275 | | Flat plan | LiftGrid Business | $79 (30 users, 2,500 elevators) |

For operations with many technicians relative to elevator count, per-user pricing can be expensive. For operations with large fleets and lean office teams, both models may be comparable. Run your own numbers before evaluating vendor demos.

Questions to ask vendors before buying

Before a demo, ask these questions. The answers will tell you more than a scripted demo:

  1. "Is your mobile app truly offline-first?" Ask them to demo a job start-to-finish in airplane mode.

  2. "Are EN-81 / A17.1 checklists built in, or do I configure them?" The answer reveals how much setup work lands on your team.

  3. "How does your dispatch engine handle OEM certifications?" If they look puzzled, it doesn't.

  4. "Show me how per-elevator contract billing works natively." If the answer involves QuickBooks integration, it's not native.

  5. "What does implementation look like — time, cost, and who does the work?" Add their implementation fee to the first-year cost.

  6. "How many elevator service companies are currently on your platform?" General tools used by elevator companies is different from a platform designed for elevator companies.

  7. "What does support look like after go-live?" Ask specifically about response times and whether support is included or priced separately.

How to run a 14-day pilot

The best way to evaluate elevator maintenance software is to run it against a real region of your operation for two weeks. Here is a structured approach:

Days 1–2: Data import Import a subset of your portfolio — one region, one building cluster, or 50 elevators. Verify that building data, elevator records, and technician information import correctly.

Days 3–5: Field technician test Have two or three technicians use the mobile app for real jobs. Confirm: Does offline mode work in your specific locations? Can they complete the EN-81 checklist? Do photos attach to the job record correctly?

Days 6–8: Dispatch and scheduling test Run a week of jobs through the dispatch engine. Verify: Does auto-assignment match OEM certifications correctly? Do SLA timers fire breach alerts on time?

Days 9–11: Billing test Generate invoices from completed work orders for a subset of your maintenance contracts. Verify: Are the amounts correct? Does the billing logic match your contract terms?

Days 12–14: Operator dashboard review Have your operations manager and dispatcher use the platform daily. Are they getting the visibility they need without calling the field? What questions can't they answer from the dashboard?

At the end of 14 days, you have real data — not a demo impression.

Summary checklist

Before signing a contract, confirm the platform delivers on each of these:

  • [ ] Work orders auto-created from fault reports
  • [ ] Preventive maintenance scheduled automatically from contract terms
  • [ ] Mobile app works completely offline (tested in airplane mode)
  • [ ] EN-81 / A17.1 checklists built in — no manual configuration required
  • [ ] Dispatch engine aware of OEM certifications
  • [ ] Per-elevator contract billing native — no integration required
  • [ ] Spare parts tracked at van and warehouse level
  • [ ] Customer portal for self-serve fault reporting
  • [ ] Pricing model understood: per user vs per elevator
  • [ ] Implementation time and cost included in year-one budget

Start a free 14-day LiftGrid trial — full access, no credit card →