Elevator Service Software
Elevator service software for every unit, every test, on record.
Your revenue sits in recurring contracts, and your risk sits in the paperwork. We turn the binders, spreadsheets, and machine room PDFs into one system where every unit carries its own history and its next test date.
Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.
Trusted by
The brief
Start with what is not working.
Good software decisions begin with the constraint, not a list of features or a preferred technology.
An inspector asks about one unit. The answer is in a PDF from last year, somewhere.
Every unit runs two test clocks, an annual one and a five year one, and both live in someone's head.
A contract visit gets missed, the work gets done free later, and nobody can prove either way.
Plain answer
Elevator service software keeps one record for every unit a company services: its maintenance history, its annual Category 1 and five year Category 5 test dates, its Maintenance Control Program records, and the contract that covers it. Custom software fits when generic field service tools cannot hold that per unit record.
What to remember
- One record per unit, holding its make, age, service history, repairs, parts, and open problems, readable in the machine room.
- Two test clocks per unit: the annual Category 1 safety test and the five year Category 5 full load test, each counting down on its own.
- Maintenance Control Program records written as the work happens, not rebuilt from memory before an inspection.
- Contracts generate their own visits and bills, so a missed visit or a quiet renewal date shows up before it costs money.
- Callbacks stay tied to the unit, so a repeating fault reads as one story instead of twelve separate callouts.
Fit
Custom software should protect the record, not just the route.
A feature request is not enough. The case is real when the same strain shows up in unit records, test dates, and contract visits.
An inspector's question about one unit takes days to answer because its history sits across binders, spreadsheets, and old PDFs.
Annual and five year test dates for hundreds of units are tracked in a calendar, a spreadsheet, or one person's memory.
Contract visits, coverage terms, and renewal dates live in separate lists, and missed visits surface only when a customer complains.
A maintained product already holds your unit records, test dates, and contract terms with reasonable setup.
Your contract terms and visit routines are still changing every month, so software would freeze a moving target.
The brief is a feature list with no named owner for the records it is meant to protect.
Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.
The record lives in the machine room. The questions arrive in the office.
An elevator company does not service addresses. It services units. One building can hold four cars from two manufacturers, on two different contracts, with four separate histories. When an inspector, a building owner, or an insurer asks what happened on one of those cars last March, the answer has to be about that unit, not about the building in general.
In most firms, that answer is a hunt. The maintenance record is a paper log in the machine room. The test paperwork is a PDF named by whoever saved it. The contract terms sit in a filing cabinet, and the callback history lives in the dispatch board. Each piece exists. Nobody can assemble them while someone waits.
Underneath sits the part that carries real risk. The safety code requires a written maintenance plan for every unit, and a dated record proving the plan was followed. It also sets two testing clocks per unit, an annual safety test and a heavier five year full load test, while your city or state runs its own inspection on yet another schedule. Miss a date or lose a record and the firm faces fines, a unit taken out of service, or a gap in the paperwork exactly when an incident makes the paperwork matter.
Custom software earns its place when one system holds the unit, its history, its test clocks, its maintenance plan records, and its contract together, so the record is written by doing the work instead of rebuilt before an inspection. The first release should complete that one path for your units. It should not try to replace every tool you own at once. Inspection led work follows the same record discipline in fire safety inspection management, where every device carries its own test history too.
Where units and dates get lost.
The screen is only one part of the job. The real scope is the record each unit carries, the clocks counting down on it, who can see and change what, and how the finished work becomes the proof.
One record for every unit
Make, model, capacity, controller type, install and modernization dates, then every visit, test, repair, part, and callback the unit has ever had. A mechanic opens the unit and reads its story before touching it. It is the same per asset pattern that runs garage door company management, where every door carries its own history.
Two test clocks on every unit
The Category 1 test is the annual safety check, run without a full load. The Category 5 test is the five year check, run at full load and full speed. Each unit carries both due dates, each finished test sets the next one, and your jurisdiction's inspection sits alongside as a third date. Overdue stops being a surprise.
Maintenance plan records written by the work
The Maintenance Control Program is the written plan the safety code requires per unit: which checks, cleaning, lubrication, and adjustments happen, and how often. When a mechanic works the visit checklist on the unit, the dated record, the result, and the photos land on that plan automatically. The binder an inspector opens is the work itself, written down as it happened.
Contracts that generate their own visits
Set each contract up once: its units, what it covers, how often you visit, how it bills, when it renews. Visits and bills then generate from the contract instead of from someone's memory of it. A missed visit appears as a gap on the board while it can still be fixed, and renewals arrive on a list months ahead.
Callbacks tied to the unit, not the day
Every callback and entrapment is logged on the unit with the reported time, the arrival time, the cause, and the fix. Dispatch can check the contract's coverage before sending anyone. And when the same cause returns to the same car, the record shows a pattern that asks for a repair, not another reset.
Which one is yours?
Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.
Two kinds of work
Contracts by the month, projects by the milestone.
An elevator firm runs steady contract work and long project work at the same time. Each needs its own rhythm, and one system has to hold both without mixing them up.
Recurring maintenance contracts
The steady revenue of the business. Visits generate from each contract's own frequency, mechanics work a checklist matched to the unit, and billing follows the contract's rhythm without a monthly rebuilding session in the office. Coverage terms sit on the contract where dispatch can read them.
Repairs and modernization projects
A repair is a quoted job with parts and labour, marked against the contract's coverage, converted from the accepted quote without retyping. A modernization is a project with orders, subcontractors, and staged billing over months. Both write their history back onto the units, so the record stays complete whichever kind of work touched the car.
The office view across both
One board shows today's routes, tonight's contract visits, every test due this quarter, contracts renewing this season, and callbacks still open. Owners see the whole operation without asking for a report, and office staff stop copying between a diary, a spreadsheet, and the filing cabinet. Wider field service work follows the same rule: one record, carried end to end.
Proof
The fifth attempt became a product customers could keep using.
UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.
The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.
Read the UrShipper case studyWhich unit record would be hardest to produce this week?
Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.
How it works
Close one expensive risk before opening the next.
Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.
- 01Understand
Trace one unit's year
Where do this unit's records actually live today?
Follow one busy unit from January to December. Include the paper log in its machine room, the PDF of its last annual test, the contract in the cabinet, and the moment an inspector's question would send the office searching.
Decision produced
A map of one unit's full year: its contract, its visits, its two test clocks, its jurisdiction inspection, its callbacks, and every place those records are kept.Risk closed
Paying to automate the visible symptom while the expensive constraint remains. - 02Shape
Choose the first useful release
What needs to exist together for one useful result to work?
Choose the shape from the way the work happens: office screens for contracts and due dates, phones in machine rooms for the visit itself, working with no signal. Name who can see and change what, the exceptions, and what done looks like for the first path.
Decision produced
The first path, usually the unit record with its test clocks and the contract visits it generates, with the offline field app it cannot work without.Risk closed
A small-looking feature list that quietly depends on several screens, systems, and owners. - 03Prove
Review working software
Will it hold up in a real machine room, not a tidy demo?
Review the product against the agreed workflow. Open one unit and read its whole life. List every test due next quarter. Record a visit in a room with no signal, then watch it arrive in the office record when the phone reconnects.
Decision produced
Working checkpoints tested with your real units, your real contract terms, a test falling due mid month, and a visit recorded with the phone offline.Risk closed
Discovering the important gaps after the routes depend on the release. - 04Transfer
Release, measure, and hand over
Did the new path improve the original constraint, and can another capable team operate it?
Start with one route or one building group. Compare the time it takes to answer an inspector's question, missed visits, and overdue tests with the starting point before adding the next workflow. The wider method sits behind custom software development.
Decision produced
A controlled release, a comparison with the starting point, operating notes, an account ownership map, and a recommendation for what should happen next.Risk closed
Measuring activity instead of the business result, or depending on the original vendor to keep the system running.
What it costs
Every project starts at $10000.
The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.
Starting investment
Starts at $10000
Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.
Not ready to talk? Start here.
Four useful next paths: decide whether to own the software, estimate the cost range, understand what moves the price, or inspect a comparable recovery.
Run the build-vs-buy calculator
Compare the cost and operating trade-offs before turning a workflow into a development brief.
Estimate the cost range
Get a working cost range for your scope before you talk to any vendor. The range moves with unit counts, jurisdictions, and system connections, so bring your real numbers.
Read the cost guide
See the scope factors that move price, timing, team shape, and long-term maintenance.
Inspect a product recovery
See what changed when UrShipper moved from four failed vendor attempts to a controlled migration. It is one comparable recovery, not a promise, and the checkpoints are the part worth copying.
Work with us
Bring one stuck workflow. Leave with a decision.
In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.
- One named workflow owner and one complete path for the first phase.
- Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
- Code, cloud, data, and provider access remain under your control.
- Post-launch warranty cover for defects in the agreed scope.
Common questions
It is the system that carries an elevator service company through its real work: a record for every unit, the recurring contract visits, the code tests each unit is due, the callbacks when something breaks, and the billing that follows. It replaces the mix most firms start with, which is a spreadsheet for contracts, a calendar for tests, and paper or PDF records stored unit by unit.
A Maintenance Control Program is the written maintenance plan the elevator safety code, ASME A17.1, requires for every unit. In plain words, it names which examinations, cleaning, lubrication, adjustments, and tests that specific unit needs, and how often each one happens. The records are the proof the plan was followed: what was done, on which date, at what interval, by whom, plus the callbacks and the corrective work that followed. An inspector who cannot review those records treats the work as if it never happened, so the record has to exist per unit and be easy to produce.
A Category 1 test is the annual safety test, run without a full load, that checks safety devices such as the governor, the safeties, and the buffers. A Category 5 test is the heavier five year test, run at full load and full speed. The problem is arithmetic, not effort: two different clocks on every unit, across hundreds of units, often tracked in one person's head. In software, each unit carries both dates, each completed test sets the next due date on its own clock, and anything approaching or past its date is flagged on one list the office checks weekly. Your city or state inspection runs as a third date on the same record.
The unit's identity first: building, car number, manufacturer, model, capacity, controller type, and install and modernization dates. Then its whole working life: every maintenance visit, every test with its result and photos, every repair with the parts used, every callback with its cause, and any open problem the next mechanic should know about. The point is that a mechanic opening that unit sees its story in one place, instead of searching last year's PDFs in the machine room.
Each contract is set up once with its building, its units, what it covers, its visit frequency, its billing rhythm, and its renewal date. The visits then generate themselves from that setup, and the bills follow the same rhythm, so a visit that never got scheduled shows up as a gap instead of being discovered when a property manager complains. Coverage is written on the contract in plain terms, full maintenance, parts and labour, or inspection only, so the office can check what a callback is covered for before a mechanic is sent. Renewal dates sit on a visible list, not in one person's memory.
Machine rooms, pits, and hoistways are exactly where phone signal drops, so the field app has to work with no signal. The mechanic opens the unit record, reads its history, works through the visit checklist, records pass or fail results with photos, and captures the signature, all offline. Everything sends itself when the phone finds signal again. If the tool needs a live connection to open a record, it will fail in the one place the record matters most.
Authorities having jurisdiction, the city or state body that oversees elevators in your area, can ask for a unit's records on short notice, and building owners and insurers ask after any incident. With one record per unit, the office pulls that unit's maintenance history, test results, and callback log and sends it in minutes. With paper binders and scattered PDFs, the same request becomes days of searching, and any gap in the record reads as work that was never done.
A callback is any return visit between scheduled maintenance, and an entrapment, passengers stuck in the car, is the most serious kind. Each one is logged against the unit with the time it was reported, when the mechanic arrived, what was found, and what fixed it. Because callbacks sit on the unit's record, a fault that keeps coming back shows itself: the same cause three times on one car is an equipment problem asking for a repair, not three unrelated callouts. The timestamps also give you the response record you need when a property manager questions the service.
They run as different kinds of work on the same unit record. A repair is a job with parts and labour lines, marked covered or not covered under that building's contract, and an accepted repair quote becomes the job without anyone retyping the scope. A modernization is a project: months of work, orders, subcontractors, and staged billing, tracked on its own record while the maintenance route for the rest of the building keeps running on schedule. Both write their history back onto the units they touched.
Small firms feel a missed callback or a lost contract more, not less, because each customer is a larger share of the business. The honest starting point is small: a register of every unit, the test and inspection dates counting down, and contract end dates with warnings before they arrive. If a maintained product gives you that cleanly, buy it. Custom software earns its place when your contract types, your jurisdictions, or your mix of maintenance and modernization work no longer fits what the products assume.
Buy an existing product when it holds your per unit records, your test dates, and your contract terms with reasonable setup. Maintained products built for elevator contractors do exist: as one verified example, Forz lists 50 dollars per user per month on an annual plan, with a 10-user minimum, at the time we checked; confirm current pricing on the vendor site. Have custom software made when the way you work is the part the products cannot copy: several jurisdictions with different inspection rules, contract coverage your dispatchers must check before sending a mechanic, or modernization projects that need to live beside the maintenance routes. If your contract terms are still changing every month, settle them first.
The first paid phase may cover a bounded audit, a small working proof, or a first release that completes one full path, such as unit register to test schedule to contract visits. The final price depends on how many units and records need moving over, how many kinds of users it serves, how many jurisdictions it must handle, and whether phones in machine rooms are involved. The agreed phase is priced in writing before it starts.
Timing depends on scope. A first release that covers one complete path, for example the unit record with its two test clocks and the visits its contracts generate, is a smaller engagement than one that also carries modernization projects and a customer portal from day one. The schedule is set once the first path and what done looks like are clear.
You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: pull up one unit and read its whole history, list every test due next quarter, find the contract that renews next month. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads.
You own the code built for you and control where it lives, the cloud accounts, the data, and third party subscriptions. Outside services and open source pieces keep their own licence terms. Your unit records are your business history, and they stay exportable in ordinary formats, so the operating notes and handover material stay current and another capable team can take over.
For one small, well defined task with someone technical managing it, a freelancer is often cheaper. The pattern that goes wrong is a non technical buyer coordinating several freelancers and becoming the project manager, the tester, and the person who finds out the pieces do not fit. An agency earns its fee when the work needs coordination across screens, rules, data, and connections: one accountable party, one phase price, and checkpoints against the whole workflow.
![Elevator service software for [every unit, every test, on record.]](/_next/image?url=https%3A%2F%2Fassets.raftlabs.com%2Fservice-assets%2Felevator-service-management%2Ffeatured.png&w=3840&q=75)