Elevator service scheduling software for contract routes and entrapment calls

Elevator service has one of the clearest splits in field service. Most of the work is contract maintenance: a mechanic visits the same buildings on a regular cycle, knows the equipment, and works through a planned list. A smaller share is the opposite: a callback because a car is out of service, or an entrapment, where someone is stuck inside and the clock is the only thing that matters.

The same mechanics do both. That makes the schedule a negotiation between a route that's supposed to be steady and calls that can't wait for it.

How an elevator route is built

Contract maintenance usually works on routes. A mechanic, sometimes with a helper, has a set of buildings they cover. Each building's units get visited at an interval set by the contract, the equipment and whatever your jurisdiction's rules require. Over time, the mechanic knows every machine room on the route.

That familiarity is valuable, and it's why most companies don't shuffle buildings between mechanics lightly. But it also means each route has a geography, and the geography decides how much of a mechanic's day is spent driving.

When routes are built from contract history rather than location, you get overlap: two mechanics passing each other on the way to buildings that would sit better on the other's route. A useful review, once or twice a year:

1. Plot every building by route.
2. Look for buildings that sit inside another route's area.
3. Move them where the move doesn't cost the customer relationship.

That's service territory design applied to routes, and it pays back every day through shorter drives.

Entrapments break the route on purpose

When a car stops with someone inside, the question is simple: who can get there fastest?

Not "who's closest on the map." Who can get there fastest given what they're doing right now? A mechanic two blocks away in the middle of a job with a machine room torn open may be slower to respond than one ten minutes away finishing up paperwork. A mechanic on the phone with the building already might be a third answer.

Three things decide it:

• Where each mechanic will be in the next few minutes, not where their van was parked this morning.
• Whether they can safely stop what they're doing. Some maintenance tasks can be left mid-way; some can't.
• The drive at that hour from there to the building.

Entrapment response is also where on-call rotation and after-hours coverage matter, since cars get stuck at night and on weekends too. The emergency call scheduling entry covers how to hold response capacity on purpose rather than finding it by pulling whoever's nearest.

A worked example: one entrapment, two mechanics

This is an illustrative example. The numbers are made up to show the method; use your own routes and drive times.

At 10:10 a.m., an entrapment comes in at a mid-rise office building. Two mechanics are candidates.

The nearer mechanic arrives later. Sending the closest pin on the map would add 14 minutes to someone's time inside a stuck car. The rest of the day matters too: whoever goes, their remaining route visits need to move, and the move should land them on the next day they're already near those buildings rather than in tomorrow's first gap.

Callbacks and the route that never finishes

A callback for a unit that's out of service isn't usually an entrapment, but building owners care about it a lot, especially if it's the only car in the building or the freight elevator before a move-in. Callbacks also tend to repeat; a unit that keeps going down will keep pulling the mechanic off route. Track them through your callback rate so chronic units get proper repair time instead of repeated short visits.

The day-to-day effect of callbacks is that maintenance visits slide. A building that was due this week gets pushed, then pushed again. Two habits help:

• Leave slack in each route week for the callbacks you know will come, based on your own history for that route.
• Rebook slid maintenance onto the next day the mechanic is in that area, not the first open slot anywhere. Rebooking into gaps is how a tidy route turns into a zigzag.

Fire protection contractors run a similar due-date-plus-emergency mix in many of the same buildings; see fire protection scheduling. The difference between optimising a route after the fact and checking travel when you book is covered in route optimization vs feasible scheduling.

Repairs, modernisations and multi-day work

Larger repairs and modernisation projects take a mechanic or crew off their route for days or weeks. When that happens, someone else covers the route. The scheduling question is which buildings the cover mechanic can reach without abandoning their own, and which visits are flexible enough to wait for the regular mechanic to return. Make that decision explicitly, building by building, rather than letting the route quietly go unvisited.

How CrewLink handles elevator scheduling

CrewLink builds live travel time into availability. When an entrapment or callback comes in, the times it shows are ones a mechanic can physically reach, with travel computed from where they'll actually be (their current or previous job) rather than the shop. That's the comparison in the example above, made at the moment it matters.

On the dispatch board, drive time sits next to each visit instead of being hidden inside it. When a mechanic is pulled off route, you can see what the remaining day looks like and where the displaced visits can go without adding cross-town drives.

Be clear on what it doesn't do. CrewLink doesn't track units, maintenance control programs, inspection certificates, parts or contracts, and it doesn't do GPS tracking of mechanics or invoicing. Your dispatcher still decides whether a mechanic can safely leave a job. CrewLink is a scheduling and dispatch tool built for companies running 5 to 50 trucks, and a walkthrough uses your own territory and service times.

Common questions

How should elevator companies dispatch entrapment calls?

Compare candidates by earliest real arrival. For each mechanic, add the time it takes to safely stop their current task to the drive from where they are at that hour. Send the one who arrives first, then move their remaining visits to days they're already near those buildings.

How do I build elevator maintenance routes?

Start from building locations, not contract history. Group buildings so each mechanic's route is a compact area, then balance the units and visit intervals across routes. Review once or twice a year and move buildings that sit inside another route's area where you can.

How much time should I leave in a route for callbacks?

Use your own history. For each route, count how many hours of callbacks the mechanic handled per week over the last few months and leave roughly that much unbooked. Routes with older equipment or chronic units usually need more.

What is the difference between elevator scheduling software and elevator dispatch software?

Scheduling plans when maintenance visits happen across the cycle. Dispatch decides, today, who goes where, including which mechanic leaves their route for a callback or entrapment. The drive between buildings matters to both, and a plan that ignores it creates problems dispatch has to solve later.