Khun Nattapong runs a four-technician aircon and CCTV team out of a shophouse on Ratchada. The route plan for the day looks clean at eight in the morning: five jobs, all within Bangkok, crew out by nine. By two in the afternoon Technician A is stuck on the expressway between Bang Na and Lat Phrao. Technician B drove 35 km across the city to a job the first technician passed right by. Job five, a 9 AM appointment in Don Mueang, slipped to 4 PM because no one was nearby at the right time.

The customers were patient. The same five jobs, sequenced differently the evening before, would have finished by three.

This is the silent cost of poor job sequencing — not failed jobs, but hours bled away in traffic and backtracking. For a team doing six to ten appointments a day, the difference between a well-sequenced and a poorly-sequenced day can be two to three billable hours per technician.

What Does a Badly Routed Day Actually Cost?

Before fixing the problem, it helps to see it clearly. On a typical poorly dispatched day:

A technician drives from Bearing to Bangkae, finishes a service call, then drives back to On Nut for the next job — passing within two kilometres of a scheduled job he could have completed on the way
Two technicians arrive within 30 minutes of each other at the same industrial estate, neither aware the other is there
The last job of the day is 25 km further from base than the second-to-last, adding 40 minutes of dead travel to end the shift

Each of these is a routing failure, not a skills or motivation failure. A technician sitting in traffic on Lat Phrao road at 5 PM is not failing — the dispatch plan failed.

At a blended rate of ฿450–฿600 per billable hour, two recovered hours per technician per day across a four-person team represents ฿20,000–฿25,000 in additional monthly capacity — the margin difference between a comfortable business and one that is always too tight.

How Do You Build a Good Job Sequence?

Good sequencing is not complicated software. It is four decisions made in order before the day starts.

First: anchor the time-sensitive job. If one customer has a fixed window — a condo management office that allows contractors only between 9 AM and 11 AM, or a school that wants work finished before afternoon classes — that job gets its slot first, and everything else builds around it. Unanchored fixed-window jobs are the most common cause of last-minute scrambles.

Second: cluster jobs by geography, not by booking order. A customer who called on Tuesday does not automatically get the first slot on Wednesday. Build the route so the technician flows through an area rather than zigzagging. In Bangkok, this usually means thinking in corridors: Thonburi jobs together, eastern expressway jobs together, northern city jobs together.

Third: assign to the nearest qualified technician, not just anyone available. A VRF specialist should not be sent to a routine split-unit clean in the same district as a junior who could handle it. Matching skills to jobs keeps the senior technician available for complex work and keeps travel efficient.

Fourth: leave buffer between jobs. A job listed as one hour is rarely exactly one hour. Parking at a shophouse can take ten minutes. A customer who wants to show the technician two additional units while he is already there is not unusual. Build 15–20 minutes of slack between consecutive appointments, especially during morning peak traffic (7–9 AM) and evening peak (4–7 PM in Bangkok).

What Is Zone-Based Dispatching and When Does It Matter?

For a single technician doing three to four jobs a day, job-by-job sequencing is usually enough. For a team of three or more technicians covering a wide area, zone-based dispatching makes the problem manageable.

Zone-based dispatching means pre-assigning geographic areas to specific technicians for the day. Technician A owns the eastern suburbs; Technician B works the central and northern zones; Technician C handles the inner-city cluster. New incoming jobs go to whichever technician’s zone matches — not whoever is free.

This prevents the dispatcher from solving a complex routing problem from scratch each morning, and means each technician builds familiarity with their area: condo access points, parking near shophouses, which industrial estates have difficult entry procedures.

In Bangkok, practical zones follow major road corridors rather than administrative districts — a zone along the Charoennakhon–Sathorn corridor keeps a technician away from cross-river traffic for most of the day.

What Information Do You Need to Plan the Route?

The route plan is only as good as the information going into it. Before the morning dispatch, you need:

Job location — a full address or GPS coordinates, not just a landmark name or LINE message that says “Chatuchak area”
Estimated job duration — even a rough figure (30 min, 1 hour, 2 hours) is better than nothing
Access and parking notes — condos often require registration at security, factories have time-limited entry; this information belongs in the job record
Parts already confirmed — if a part needs to be collected from the supplier before the job, that collection point becomes a stop in the route, not an afterthought
Customer contact and preferred window — so the technician can send an ETA via LINE when en route rather than the customer calling in at 9:05 asking where the crew is

All of this should be captured when the job is booked. A dispatcher calling three customers at 8 AM to confirm addresses has already lost 30 minutes of planning time before the crew has left.

What Breaks a Good Route, and How Do You Recover?

Even a well-planned route breaks. A job that was estimated at one hour takes two and a half because the customer’s system is in worse condition than the initial description suggested. An expressway closure adds 45 minutes to a midday trip. A customer is not home.

When a job overruns, the cascade is the risk: the next appointment slips, then the one after, until the day ends with one job unfinished and a customer who waited four hours past their window.

Recovery is faster when the dispatcher knows where each technician is and can act before the cascade reaches the customer. If Technician A is running an hour late, the dispatcher can redirect Technician B — who just finished a nearby job — or call the customer with a revised window before they start waiting. None of that is possible if the only team view is a LINE group last updated at noon.

How Do You Manage This Without a Whiteboard of Sticky Notes?

Many Thai install businesses still plan daily routes on a whiteboard, a LINE group, or a notebook. These work up to a point — around three technicians and five daily jobs. Beyond that, the dispatcher is doing mental juggling that a dispatch board handles automatically.

A dispatch board shows every job and every technician on one screen. You can drag jobs between technicians, see who is closest to an incoming job, and check when a day is full without texting and waiting. When a job overruns, you see it before the next customer’s window has already passed.

The tool does not eliminate the need for good sequencing judgment — it removes the friction that stops the judgment from being applied consistently.

FAQ

How many jobs can one technician realistically handle in a day?

For aircon service calls (cleaning, inspection, gas top-up), a well-routed technician in greater Bangkok can typically complete four to six jobs per day. Installation or fault-diagnosis work is more like three to four, given set-up and testing time. Poor sequencing can reduce either figure by one or two jobs through avoidable travel alone.

Should the first job always be the closest to the technician’s home?

Not necessarily. The first job should be the one with the tightest time window or highest priority. Starting closest to home only makes sense when no appointment has an early fixed window. Passing a 9 AM booking because you started with the nearest job creates a bigger problem than the minutes saved on the first drive.

What do I do when a new emergency job comes in during the day?

Insert it as the next job for the nearest available technician, then call customers downstream to adjust their windows. Most accept a short delay if notified promptly. The worst outcome is a customer who learns their slot slipped only when they call in to ask — the dispatcher who calls first controls the conversation.

Route planning looks small until you do the arithmetic. Two recovered hours per technician per day is real revenue and a crew that finishes at a reasonable time. Twenty minutes of planning the night before pays back every week it is done.

Sequence Technician Jobs Right and Cut Daily Drive Time