Scheduling Field Teams and Dispatching Visits

Scheduling Field Teams and Dispatching Visits

Part two closed the gap of the unlogged request. Every request now has a number, a status, an owner and a response time that is measured automatically. But a logged work order does not execute itself. Between the record and its closure sits a decision made dozens of times a day, usually on gut feel: who goes to this job, when, and in what order relative to everything else.

That decision is the source of three of the seven leaks we named in part one: the repeat visit, time burned in transit, and the technician who arrives and only then discovers he does not have what the job needs. The difference between a company completing six visits a day and one completing three with the same headcount is rarely how hard the crews work. It is the quality of the dispatch decision.

Matching the job to the right skill

The first dispatch question is not who is free. It is who can finish this job on the first visit. Sending an electrician to an HVAC fault means one whole visit lost, fuel and hours spent, the contracted response clock burned, and a second visit at your own cost.

What makes matching possible is a written skills register per technician rather than a picture in the supervisor's head: the trades they actually hold, any certificate or licence the work legally requires, and which assets or systems they have already worked on at this specific client. That last one quietly saves the time otherwise spent rediscovering a site on every visit.

• Classify the request by work type at intake, not only by the client's description, because the classification is what shortlists the right technician.
• Record a skill level, not a yes or no. Diagnosing an intermittent fault and executing a known repair are different capabilities.
• Track who actually performs what. After a few months the record usually shows half the work going to three people, and the rest of the roster not genuinely qualified.

Geography: do not cross the city twice

In field operations the biggest waste is not in the work itself, it is between sites. A schedule built in the order requests arrived produces a random route: north of the city in the morning, south at midday, back north in the afternoon for a request that came in late.

The fix is a principle before it is a tool: cluster visits by area. Divide your operating footprint into clear zones, anchor each technician or crew to a primary zone, and let non-urgent requests accumulate inside a one or two day window so they can be executed on a single route. What sits outside this logic is the genuine emergency only, and an emergency is an exception you manage, not the way you run every day.

When you promise the client a slot, promise a realistic window that accounts for travel time between two sites, not a precise appointment that the first traffic jam breaks. Clients accept a two-hour window you keep far more readily than an exact time you miss by half an hour.

Check before you dispatch: the part, the tool, the access

Repeat visits are rarely caused by a weak technician. They happen because nobody asked three questions before dispatch:

• Is the part available? Not in the main warehouse, but in this technician's van or in the site store. That assumes van stock is actually recorded, which is the subject of part six.
• Is the tool or equipment free? Some jobs need a hydraulic lift or a single measuring instrument shared between crews. Reserving equipment is part of scheduling, not a side detail.
• Is access guaranteed? A gate that needs a permit, a site that opens only in set hours, a client representative who has to be present. A visit that arrives at a locked door costs you in full and returns nothing.

Practically, make these three checks the condition for moving a request from logged to assigned. If the part is not available, the correct status is waiting on parts, as we said in part two, not dispatching a technician to find out for himself.

The technician app: it works on weak signal, or it does not get used

Every scheduling system fails at one point: the screen the technician opens on site. A technician in a basement, a warehouse or a building under construction has no stable connection, has both hands busy, and is being timed. An app that demands ten steps to close a visit will be abandoned within two weeks and the crews will go back to WhatsApp.

What makes it actually get used:

• It works offline: it shows the visit details and stores notes, photos and the signature locally, then syncs automatically when the connection returns.
• It shows the day's route on one screen with sequence, address, contact number, fault description and a short asset history.
• It reduces documentation to taps: start visit, photo, short note, complete, signature. Long write-ups are an office task, not a site task.
• It speaks the technician's language. A large share of the technical workforce in Saudi Arabia does not read Arabic, and an interface the user cannot follow produces wrong data rather than missing data.

Attendance and location tracking: the legal side is not a footnote

Tracking technician location is tempting because it answers real questions: where is the crew now, who is nearest to this emergency, and did the visit actually happen. But it processes employees' personal data, and in Saudi Arabia that falls under the Personal Data Protection Law and its implementing regulation issued by the Saudi Data and AI Authority.

The practical position we hold to on implementation:

• A specific, stated purpose: collect location for a clear operational purpose, dispatch and proof of visit, not open-ended surveillance.
• Written notice to the employee: they know what is collected, when, why, and who can see it. Covert tracking is both a legal and a management problem.
• Time boundaries: tracking during working hours and assigned visits only, not around the clock and not off duty.
• Data minimisation and a defined retention period: store only what serves the purpose, and delete what has outlived it.
• Scoped permissions: the operations manager sees location, not everyone who holds an account.

On attendance, documenting working hours and overtime is required under the Labour Law, and a digital attendance record serves you twice: as compliance evidence for the Ministry of Human Resources and Social Development, and as an accurate labour cost per work order when you calculate project margin in part five.

The Origami view

The request we hear most at this stage is for smart scheduling that assigns jobs automatically. We will say it plainly: fully automatic dispatch fails early in most contracting and maintenance companies, because its inputs do not exist yet. The algorithm needs recorded skills, accurate site locations, current van stock and real execution times. Without that data it will produce worse assignments than an experienced supervisor, and it will cost you the crews' trust in the whole system.

The order we recommend: start with a manual dispatch board that shows the supervisor the open requests, the technicians, today's load per person and their zones. The supervisor still decides, but decides while seeing rather than remembering. That alone visibly cuts repeat visits within weeks.

After three to six months of operation you will have accumulated real execution times and documented skills, and only then does an automatic suggestion become useful. Even then, keep it a recommendation the supervisor approves rather than a binding assignment. The rule we keep repeating: automation multiplies the quality of your process, so if the process is undisciplined you are simply multiplying the chaos faster.

In the next part

So far we have been talking about reacting: a request arrives, we schedule it, we execute it. Part four moves to the other side of the equation, preventive maintenance: the asset register as the foundation, scheduled plans and checklists, triggering by calendar versus runtime hours and meter readings, and an honest read on what is realistic today in predictive maintenance and what is still vendor talk.

Sources

• Saudi Data and AI Authority — the Personal Data Protection Law, its implementing regulation, and the rules on collecting and processing data for a specified purpose.
• Ministry of Human Resources and Social Development — the Labour Law and provisions on working hours, overtime and their documentation.
• Zakat, Tax and Customs Authority — e-invoicing requirements that connect to completed work orders.
• Saudi Vision 2030 — the national direction on raising efficiency in construction, operations and maintenance.