What Your Elevator Callback Reports Are Actually Telling You

Your elevator company sends you callback reports every month. Maybe quarterly. Most property managers file them with the rest of the paperwork and never look at them again.

That's a mistake. Callback data is the single best indicator of service quality you have. It's the one metric your elevator vendor can't game, can't spin, and absolutely tracks internally even if they tell you they don't. Here's how to read your callback reports like your vendor's regional manager does.

What Callbacks Actually Measure

A callback is any time the elevator company has to return to your building between scheduled maintenance visits. Entrapment, malfunction, outage, tenant complaint. If the technician shows up outside of the regular monthly visit, it counts as a callback.

High callback rates mean poor preventive maintenance. When your vendor catches problems during scheduled visits, you don't get callbacks. When they rush through visits or skip inspections, small issues turn into emergency calls.

Your vendor tracks callback data religiously. They use it to evaluate technician performance, route efficiency, and contract profitability. Regional managers review it weekly. Service managers use it to decide staffing. The data exists, and it matters. If your vendor says they don't track callbacks, they're lying to avoid accountability.

Benchmark Table: What's Normal

Not all callback rates are equal. Here's the industry benchmark for commercial buildings:

These benchmarks assume standard commercial traffic and equipment in reasonable condition. A high-rise office building with 20-year-old equipment will naturally see more callbacks than a low-rise medical building with new controllers. Age and usage matter.

But context cuts both ways. If you have newer equipment and you're still seeing 10+ callbacks per unit per year, something is wrong. The question to ask your vendor: "What's my callback rate compared to similar buildings in your portfolio?" If they can't or won't answer, that tells you something too.

Red Flag 1: Repeating Cause Codes

Your callback report includes a cause code for each visit. Door malfunction, drive issue, controller fault, miscellaneous. If you see the same cause code appearing three or more times per month on the same unit, you don't have a callback problem. You have an equipment problem that's not being fixed.

Door-related callbacks that keep repeating usually mean a failing door operator or misaligned track. Drive-related callbacks point to controller or motor issues. Both are expensive fixes, and some vendors will patch the symptom rather than address the root cause because they're hoping to sell you a modernization later.

Watch for overuse of "miscellaneous" as a cause code. That's a technician who either doesn't know what's wrong or doesn't want to document it. Poor diagnostics lead to repeat callbacks because the real problem never gets identified.

Action item: Request a breakdown of your callbacks by cause code. If you see patterns, demand root cause analysis in writing.

Red Flag 2: Response Time Creep

Your callback report should include response times. How long between when the issue was reported and when the technician arrived. Industry standards:

• Entrapment: 30 minutes during business hours, 1 hour after hours
• Routine malfunction: 3-4 hours

If your vendor is consistently taking longer, you have an understaffing problem. Technicians covering too many buildings, routes stretched too thin, or not enough on-call coverage. That's a vendor capacity issue, not an equipment issue.

Calculate the average response time from your callback reports for the last six months. If entrapments are averaging over 45 minutes or routine callbacks are taking 6+ hours, your vendor doesn't have the resources to service your building properly. That's a contract conversation.

Red Flag 3: No-Problem-Found Entries

NPF. No problem found. The technician arrived, couldn't reproduce the issue, and left. One or two NPFs per year isn't unusual. Intermittent problems happen. But multiple NPFs on the same unit within a few months means the technician is giving up instead of investigating.

The worst pattern: NPF followed by an entrapment days later. That means the intermittent issue became a critical failure, and your vendor missed the chance to catch it early. Passengers got trapped because a technician didn't dig deeper.

NPFs should trigger root cause analysis. Why couldn't the problem be reproduced? Was it tested under the same conditions as the complaint? Is there a pattern of when the issue occurs? If your vendor logs multiple NPFs without investigation, they're treating symptoms instead of diagnosing.

Red Flag 4: Post-Visit Callbacks

Compare your callback dates to your scheduled maintenance dates. If you consistently see callbacks within 24-48 hours after a scheduled visit, your vendor is rushing through preventive maintenance.

Monday maintenance visit, Tuesday callback. That's not bad luck. That's a technician who didn't complete the inspection, didn't catch a developing issue, or caused a problem while servicing. It happens once or twice, fine. It happens every other month, you have a service quality problem.

This pattern suggests inadequate preventive work. The vendor is checking boxes instead of actually maintaining equipment. Track the number of days between each scheduled visit and the next callback. If the average is under a week, your vendor isn't doing the job they're billing you for.

How to Use This as Leverage

If you have a full maintenance contract and your callback rate is 10+, you have grounds for a breach conversation. Full maintenance means the vendor is responsible for keeping the equipment running. High callbacks prove they're not meeting that obligation.

If you have an examination contract and your callback rate is climbing, your vendor will try to sell you a modernization. Counter by asking for callback data from similar buildings in their portfolio. If your rate is significantly higher, the issue might be service quality, not equipment age.

The nuclear option: "I'd like to see your callback data for other buildings like mine before we discuss contract renewal." If they refuse, you know they're hiding poor performance. If they share it and your building is an outlier, you have negotiating power. Either they improve service or you have documentation to support switching vendors.

Know Your Service Quality Benchmarks

Upload your callback reports to our Contract Scanner. We'll benchmark your callback rate against industry standards, flag patterns in your data, and show you exactly where your vendor is underperforming.

Most property managers don't analyze callback data because they don't know what they're looking at. Now you do. Your vendor has been reading these reports for years. It's time you started reading them too.