Elevator Reporting Software: What to Actually Measure

By Sumeet Katariya, ElevatorPlus · Published 14 September 2026 · Last updated 14 September 2026 · ~9 min read

In short: Elevator reporting software turns the service records a lift company already creates into four answers an owner needs: which contracts make money, whether technicians are productive, whether response promises are being met, and what is due to renew. Those four numbers are the ordinary questions asked in a monthly review, and most firms cannot answer them because reporting sits downstream of capture. A report can only show what was recorded at the job.

Key takeaways

• Four numbers are enough. Contract profitability, technician utilisation, response performance and renewal exposure answer the questions an owner actually asks. Everything else on a dashboard is decoration.
• Reporting is downstream of capture. A report cannot invent a job number that was never written down. Parts issued on trust, job cards written from memory on a Saturday and a renewal spreadsheet on one laptop make the four numbers impossible before any software is bought.
• An average is the most comfortable lie in this business. Total parts spend divided by contract count says the fleet is fine. In practice a handful of sites usually consume the margin the rest earned, and they hide inside a healthy looking total.
• Utilisation on its own rewards slow work. Hours on site divided by hours available flatters the technician who takes four hours over a two hour job. Pair it with first visit fix rate and with repeat visits to the same lift inside thirty days, or you are congratulating a team for the trips its earlier trips created.
• There are two clocks on every breakdown, not one. Time to acknowledge and time to attend are different measurements, and the customer judges the first one hardest. Reporting that captures only attendance is measuring the clock nobody complains about first.

What this guide covers: what a report should actually tell you · why the four numbers sit downstream of capture · contract profitability and the average that hides it · technician utilisation and the two numbers that must sit beside it · the two response clocks · renewal exposure · what makes a report worth opening · FAQs

What should elevator reporting software actually tell you?

Most owners do not want more dashboards. They want four numbers they can trust, once a month, without asking three people to compile them.

None of these are exotic. They are the ordinary questions an owner asks in a review meeting, and they are the ones that usually get answered with a shrug and a promise to check.

Why can most companies not answer these today?

The honest reason is that reporting sits downstream of capture. A report cannot invent a job number that was never written down.

Think about how the data usually arrives. A part is issued from the store on a verbal request and nobody notes which lift it went to. A technician writes up three job cards on Saturday morning from memory, because Thursday was busy and the paperwork slipped. A renewal date sits in a spreadsheet on one laptop, kept current by one person who has been meaning to update it.

Every one of those is a normal, forgivable habit in a busy service company. Together they make the four numbers impossible. A report is a mirror. It can only show what was recorded, and if the record is thin, the report will be confidently wrong rather than usefully incomplete.

That is the part worth sitting with before buying anything. Software does not create discipline at the point of capture, it just makes the discipline cheap enough that technicians actually keep it up.

Contract profitability, and why an average hides the problem

Ask an owner what a contract costs to service and you will often get total parts spend divided by the number of contracts. That is an average, and averages are the most comfortable lie in this business.

The average tells you the fleet is fine. The reality is usually that three or four sites are eating the margin the other forty earned. An old installation with a worn controller, a building manager who calls for every trivial fault, a site two hours from the depot. Those contracts are not slightly less profitable, they are often the only ones losing money, and they hide inside a healthy looking total.

To see it you need cost attached to a job, and the job attached to a contract. That means spare parts tracked against the job rather than issued from a store cupboard on trust, and technician hours booked to the same work order.

Once that chain holds, contract profitability stops being an estimate. You can sort your contract list by margin and look at the bottom five, which is a very different conversation from looking at a fleet average. Some of those sites need a price correction at renewal. Some need a repair rather than another visit. One or two may need to be let go.

Technician utilisation, the metric most firms get wrong

The common definition is hours on site divided by hours available. It is easy to calculate and it quietly rewards the wrong behaviour, because the technician who takes four hours over a job that should take two looks more utilised than the one who fixed it properly and moved on.

Pair it with two others. First visit fix rate tells you how often a call was closed without a second trip. Repeat visits to the same lift inside thirty days tells you how often a fix did not hold.

Read together, those three numbers describe a team. High utilisation with a low first visit fix rate and rising repeat calls is not a productive team, it is a team generating its own workload. You would be congratulating people for the extra trips their earlier trips created.

Getting there depends on job records that carry a fault, an action and a parts list, which is really a question of how the field side is run day to day. The practical side of that is how the job card gets completed on site, not how the report is drawn afterwards.

Response performance, two clocks not one

There are two clocks running on every breakdown call, and most companies only think about one.

The first is time to acknowledge, meaning how long before someone tells the customer their call has been received and a technician is assigned. The second is time to attend, meaning how long before that technician is on site.

Most maintenance contracts define neither with any precision. They say "prompt attendance" or "same day response" and leave it there. Customers, meanwhile, judge both, and they judge the first one hardest. A building manager with people stuck between floors will forgive a long travel time far sooner than a long silence.

If your reporting captures only the attendance time, you are measuring the clock your customer complains about second. Timestamp the acknowledgement too, and you usually find the fixable problem is in the office rather than in the van.

Renewal exposure, the one that pays for the software

Here is a test. How many of your contracts expire in the next sixty days, and what are they worth? Now the same question for ninety days.

A firm that cannot answer that in under ten minutes is carrying an unmeasured revenue risk every single month. Contracts do not usually get lost in a competitive fight. They lapse. Nobody called, the anniversary passed, the building manager signed with whoever rang first.

Renewal exposure is the easiest of the four numbers to produce and the one owners most often go without, because it needs nothing more than an end date, a value and a reminder that fires early enough to act on. It is usually the report that justifies the whole exercise within a year.

👉 How many of your contracts expire inside the next ninety days, and what are they worth?

See how AMC contracts and renewal reminders are tracked →

What makes a report worth opening?

A report nobody opens is not a reporting problem. It is a relevance problem.

Aim for one page, four numbers, monthly. Name the exceptions rather than listing everything: the five contracts below margin, the three lifts with repeat visits, the eleven renewals inside ninety days. A forty page pack gets filed unread and teaches everyone that the numbers do not matter.

The four answers are worth having because each one leads to a decision an owner can make this month. That is the only real test of a report.

Frequently asked questions

What should elevator reporting software tell you?

Four things: which contracts make money, whether technicians are doing productive work, whether the response promises written into contracts are being met, and which contracts are due to renew along with what they are worth. Anything beyond those four is usually decoration on a dashboard nobody opens.

How do you measure technician utilisation in a lift company?

The common definition is hours on site divided by hours available, taken from time booked against work orders rather than estimated at week end. On its own it rewards slow work, so it should always be read alongside first visit fix rate and repeat visits to the same lift inside thirty days.

Why can't we calculate contract profitability?

Almost always because cost is not attached to a job and the job is not attached to a contract. Parts issued from the store on a verbal request and hours written up from memory cannot be traced back to a site, so the only figure available is a fleet average, which hides the few contracts that are losing money.

What is a good response time for a lift breakdown?

The number that matters is the one written into your own contract, and whether you can show that you met it. There is no verified industry benchmark worth quoting here, and a figure invented for a blog post is not something to hold your team to. Define acknowledgement and attendance in the contract, timestamp both, and measure against your own promise.

How far ahead should you track AMC renewals?

Far enough ahead that someone can act rather than react. In practice owners ask the question at sixty days and again at ninety, so a renewal report should show both windows with the contract value beside each one, and the reminder should fire while there is still time to visit the customer.

What is the difference between time to acknowledge and time to attend?

Time to acknowledge is how long before the customer is told the call has been received and a technician assigned. Time to attend is how long before that technician reaches the site. They are two separate clocks, and customers judge the first one hardest, which is why capturing only attendance times hides the problem.

Why does nobody read our monthly service report?

Usually because it lists everything instead of naming exceptions. One page, four numbers, and the specific contracts, lifts and renewals that need a decision this month. A long pack gets filed unread and teaches the team that the numbers do not matter.

📲 Join our WhatsApp channel for compliance tips, updates: ElevatorPlus - Business Automation Tool

The four numbers are not hard to define. They are hard to produce, and the difficulty is never in the reporting layer. It is in the store cupboard, the job card and the spreadsheet on one laptop.

So the honest sequence is capture first, reporting second. Get parts and hours landing on a work order, get the work order landing on a contract, timestamp the acknowledgement as well as the attendance, and put the renewal date somewhere other than one person's memory. The four numbers then fall out of the record rather than being reconstructed from it.

What you get in return is not a prettier dashboard. It is the ability to sort a contract list by margin, name the five sites at the bottom, and go into a renewal conversation with a position rather than a hope.

And if the report still goes unread after that, it is not measuring the wrong way. It is measuring the wrong things.

👉 See the four numbers produced from your own service records. Book a demo →

Related reading

• Equipment analytics: what the service record can be read for
• PM and AMC reminders that surface renewal exposure early
• Spare parts tracked against the job rather than issued on trust
• Work order management: where parts and hours have to land

About the author. Sumeet Katariya is the founder of ElevatorPlus, the Elevator Business Operating System used by 200+ elevator companies across 20+ countries.

Sources: Operational patterns described here are drawn from ElevatorPlus onboarding across 200+ elevator companies in more than 20 countries. No third party study is cited because none was used.

Book a Demo with ElevatorPlus

 👉 Follow ElevatorPlus on,
Instagram LinkedIn Facebook YouTube Qoura Substack Twitter