Elevator Field Service Software
The right technician, at the right lift, with the right context.
Scheduling and dispatch built around how elevator service actually runs. Routing by skill, location and load. Mobile job cards that keep working in a basement plant room. Proof of visit captured on site rather than reconstructed at the office.
The problem
Dispatch by phone call is a plan that only exists in one head.
In most elevator service teams the day is planned on a whiteboard and adjusted by phone call. The dispatcher knows who is where. Nobody else does. When an entrapment comes in at eleven, the reshuffle happens in a series of calls, and the three visits pushed to tomorrow are remembered rather than recorded.
The technician arrives without knowing what the lift was doing before it stopped, what was fitted last time, or whether a part is already on order. Work gets written on a paper card that reaches the office days later, if it reaches the office at all. Parts consumed are remembered at month end. Chargeable findings are mentioned verbally and quoted a week later, if someone remembers.
Every one of those gaps costs a second visit, an unbilled part, or an SLA you cannot evidence.
Assignment
Four inputs decide who goes.
The system proposes. The planner decides. The weighting between these inputs is set to your operation during the build, because a dense city portfolio and a spread-out regional route do not want the same trade-off.
Fault or request with the unit attached
Technician chosen by skill, location, load
Sequenced into the day, job card cached
Arrival, work, and parts captured
Ticket closed, history and stock updated
Skill
Drive type, controller family, statutory inspection qualification, rope work, entrapment release. Sending a technician who has never opened that drive family is a wasted visit and a second callout.
Location
Where the technician is now and where the rest of the day takes them. A job three streets away goes to the person already in that district, not to whoever answered first.
Load
Open jobs, hours already committed and travel time left in the shift. Assignment respects capacity so the schedule reflects what can actually be done today.
Contract window
The response time you have promised on that site. Urgent work under a tight tier outranks routine work under a loose one, automatically and consistently.
Mobile job card
Everything the technician needs, cached before they arrive.
Plant rooms are in basements. Basements have no signal. A field app that needs a connection to show the last service record is useless exactly where it is needed, so the job card and its context are pulled to the device before the visit starts.
- The decoded fault and the signal history leading up to it
- Full service history for the unit, including the last three visits
- Controller type, drive model, and any site-specific access notes
- Parts fitted previously and parts currently expected for this job
- The checklist the contract or statutory inspection requires
- Open blockers and any pending proposal on the same unit
Captured on site
Arrival and departure
Timestamped with location, which is what a response-time SLA is measured on.
Photos
Before and after, component condition, panel state. Attached to the job and the unit history.
Findings and work done
Structured against the checklist rather than a free-text box nobody can query later.
Parts consumed
Recorded against the van stock and the job, so inventory and the invoice both move.
Customer signature
Captured on the device where the contract requires acceptance on completion.
Follow-up flag
Work identified but not done, converted to a proposal or a scheduled task before the technician leaves.
Show us a typical day for one of your technicians. We will show you what it looks like planned, routed and evidenced.
Book a Session →Route optimization
A day that survives first contact.
Before the shift
Routes are built from AMC visits due, open tickets, and jobs held from yesterday. Each technician gets a sequenced day, and the job cards and asset history are cached to their device.
During the shift
Arrival and departure are captured on site. Planners see live progress against the plan rather than calling round for updates. Jobs running long are visible before they cost the next appointment.
When an emergency lands
An entrapment or critical fault comes in with its unit and site attached. The planner sees who can absorb it without breaching another window, and the remaining route re-sequences around it.
After the shift
Completed job cards close their tickets, write to service history, move parts out of stock, and raise proposals for the chargeable work found. Nothing waits for a paper card to reach the office.
Sample shape only. A routed day keeps utilisation even instead of stacking one technician.
Why RnD Square
Generic field service tools were built for plumbers and printers.
They model a customer, an address and a visit. They do not model a vertical asset in a shaft with a controller family, a statutory inspection cycle, an entrapment protocol and a contract that promises a four-hour response in one district and next-day elsewhere. Fitting elevator service into that shape means workarounds, and workarounds are where evidence goes missing.
RnD Square builds the dispatch layer against your actual operation. Skills taxonomy, job card format, checklist content, sign-off rules, statutory paperwork and the weighting the router uses are all specification items rather than settings you hope exist.
Because the hardware and firmware come from the same team, the job card carries decoded controller data rather than a customer description of a noise. The technician knows what the fault was before opening the panel. That is the difference between one visit and two. See the full elevator management software suite for how dispatch connects to the rest.
FAQ
Common questions
Yes. The job card, asset history, checklist and previous fault data are cached to the device before the visit. Everything the technician records on site, including photos and signatures, is stored locally and syncs when the phone regains a connection. Timestamps are preserved from the moment of capture, not the moment of sync.
Related
Connected modules.
Get the whiteboard out of the dispatch office.
Tell us how many technicians you run, how your territories are structured, and what your paperwork looks like today. We will come back with a scope.