Skip to main content
GullySystem
Real estate and construction

Technician Scheduling for Elevator companies

Assign service work to suitable available technicians.

Field Service

Does this function belong in your operation?

Use when your business dispatches technicians or field-service teams.

A visit is booked, changed or escalated.

Monthly preventive visits are spread across technicians by area and lift count. Night entrapment calls go to whoever is on duty at that hour. The dispatcher sees who is nearest.

Bring the records the workflow depends on.

  • Jobs and locations
  • Technician availability
  • Skill and scheduling rules

Outputs to check

  • Assigned service schedule
  • Capacity and delay exception list
  • Reassignment history

Follow the technician scheduling workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Collect due work

    Combine accepted jobs, planned visits and authorised priorities.

  2. 2. Check suitability

    Compare requirements with technician skills and availability.

  3. 3. Assign the slot

    Record the responsible technician and planned visit details.

  4. 4. Handle changes

    Review absences, emergencies and overruns before reassigning work.

  5. 5. Reconcile progress

    Use job updates to distinguish planned, in-progress and completed visits.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Service coordinator

Builds the day, absorbs the emergency and knows who is free at three.

Technician

Reviews the assigned jobs, reports availability changes and records progress through the service process.

Supervisor

Watches what is running late and rings before the customer does. Late jobs show first.

Owner

Reviews completed jobs, delays and unfilled assignments before changing field capacity.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Emergency job arrives

Record the priority decision and review work displaced by reassignment.

Technician absent

Reassign open jobs and notify the responsible coordinator.

Visit overruns

Update expected availability before promising the next appointment.

Can this work independently?

Scheduling needs jobs, technician availability and any required skills. It can use entered calendars, but attendance and job-card updates keep capacity current. Dispatch, travel navigation and proof of work are separate capabilities; assigning a job does not confirm arrival or completion.

Systems and records it connects with

  • Job cards: Service findings, approved work, parts and completion records.
  • AMC contracts: Contract coverage, dates and planned service obligations.
  • Service reports: Approved work evidence and unresolved service findings.
  • Attendance: Approved shift attendance, absence and correction records.

Configure, test and introduce the workflow.

  • Describe a typical day and area split. A note shows how jobs will be grouped.
  • Provide the skills, clearances and areas of each technician. A worked example of a day is shown. Try it. A small group uses it for a chosen week. Their feedback returns as changes.
  • Coordinator, supervisors and technicians see their own screens. Phone guides in your language follow. All jobs are assigned through the system. After the opening month a review reads the timing.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Conflicting assignments are visible.
  • Unavailable technicians are excluded.
  • Changes remain linked to the job.
Elevator companies

How the business operates.

An installed lift is a contract that runs for decades. Monthly maintenance, licence renewal and a night call from a watchman are where a lift company’s service is judged.

Lift register

Record each lift by building, make, load, floors served, controller, installation date, licence number and contract type, so any call traces to a machine.

Preventive maintenance schedule

Plan monthly visits by technician and route, with a checklist closed by the technician’s signature.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Lift and building records. Hold each lift with its machine number, make, model, load, speed, floors served, drive type, controller and the building and wing it stands in. A gearless machine is told apart from a geared one at a glance.
  • Enquiries and site surveys. Record enquiries from builders, societies and facility teams, with survey notes on the shaft, pit, headroom and the machine already installed. Photographs of the hoistway and machine room stay with the enquiry.
  • Quotations and modernisation proposals. Quote for a new lift, a repair or a modernisation, listing the parts and labour offered, from a new controller to rope and sheave replacement. Track the quotation to an order, with revisions kept on file.
  • Installation project stages. Follow an erection job through guide rails, machine, counterweight, car, doors, wiring, controller and trial runs. Each stage carries its supervisor and dates. Delays show against the stage that caused them.

Operational bottlenecks to check

Night calls reach the wrong technician

The office phone rings through to a technician who does not cover that area, and the people in the lift wait. The time of the call is not written down.

Service visits cannot be shown to have happened

The association says nobody came, and the only proof is a paper slip in a technician’s bag. The office cannot answer.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and site survey

    A builder, society or facility manager asks for a lift or for service cover. The survey notes the shaft, pit depth, headroom, floors served and the existing machine where there is one, with the machine room dimensions.

  2. 2. Quotation and order

    A quotation covers the lift or the cover offered, with spares and labour included. When it is accepted, the order and payment stages are recorded against the building. Nothing is retyped.

  3. 3. Installation and commissioning

    Erection runs in stages from guide rails, machine and counterweight to car, doors, controller and trial runs. Commissioning and handover close the job, with the governor and buffer test records filed against the lift.

  4. 4. AMC and routine service

    The lift goes on a contract with its visit frequency. Each routine visit opens with a checklist for the machine room, car, hoistway and landing doors, and closes with the technician’s signature. Lubrication is logged.

  5. 5. Breakdown call

    The desk logs the caller, the lift and the fault reported. A technician is sent, and the fault found and the parts used are entered. The call is closed with the outcome, and a trapped passenger is noted as a rescue.

  6. 6. Billing and renewal

    AMC instalments, repair work and chargeable spares are invoiced with tax. Renewal dates appear in advance, so the office can speak to the committee or the facility team before cover lapses.

Industry reports to connect with

  • Lifts under contract by building and cover type
  • Routine visits done against visits due, by route
  • Breakdown calls by lift, with the fault found
  • Spares issued by lift and by technician

Questions before implementation.

When should elevator companies consider technician scheduling?

Use when your business dispatches technicians or field-service teams. A visit is booked, changed or escalated.

What should we bring to the requirements discussion?

Bring anonymised examples of Jobs and locations; Technician availability; Skill and scheduling rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Assign service work to suitable available technicians. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Your authorised team verifies required qualifications. Technicians and coordinators update actual travel, arrival and completion status.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Conflicting assignments are visible. Use this check when reviewing the first working version.

Talk to us

Discuss technician scheduling for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements