A technician finishes a CCTV installation in Lat Phrao at 1 PM. The dispatcher’s next open job is an aircon service request in Thonburi. Between the current site and the next booking: 90 minutes of mid-day Bangkok traffic. The technician arrives at 2:40 PM for what was booked as a 2:00 PM slot. The customer waits. Two more appointments cascade. The day ends at 7 PM.

The problem is not traffic. Traffic in Bangkok is consistent and predictable — any dispatch system built without accounting for it is wrong by design. The real problem is that no zone rule existed to keep this technician in their own district rather than crossing to Thonburi.

Zone-based technician assignment — a system where each technician is the primary dispatcher contact for a defined geographic area — is the structural fix for this pattern. It does not eliminate Bangkok traffic. It stops sending technicians through it unnecessarily.

What Is Zone-Based Technician Assignment?

In a zone-based system, each technician is assigned primary responsibility for a defined cluster of districts or a geographic band. When a new job comes in, the dispatcher’s first question is not “who is free?” but “whose zone is this?” The zone technician gets the assignment unless they are at capacity, lack the required skill, or an emergency overrides the rule.

This is different from daily route optimisation, which arranges a confirmed appointment list into the most efficient travel sequence. Zone assignment happens first — it determines whose job list a new booking belongs on before the route is built.

Most dispatch inefficiency in growing Thai installation businesses is a zone problem, not a route problem. A dispatcher choosing between five technicians and nine incoming jobs does not need better routing software. They need a reliable default answer to: who does this job belong to?

Why Does Random Dispatching Hurt Bangkok Field Teams?

Bangkok traffic punishes cross-city dispatch more than any other factor. When jobs are assigned to whoever seems most available — without reference to location — technicians regularly cross each other’s paths.

A typical unmanaged Tuesday: Technician A drives from Nonthaburi to Ramkhamhaeng after his morning job (52 minutes via the expressway). Technician B drives from Ramkhamhaeng to Bang Yai that same afternoon (47 minutes). Neither assignment was wrong viewed in isolation. Together, they represent 99 minutes of unnecessary cross-city travel on a day where zoning would have kept both technicians within 15 minutes of their next job.

At an implied opportunity cost of 500 baht per technician-hour, 99 minutes of avoidable travel is roughly 825 baht lost in a single day. Across a team of four over a five-day week, unmanaged dispatching can consume 15,000–20,000 baht per month in lost productive capacity — before accounting for overtime, late arrivals, or the fatigue that accumulates in technicians who drive 90 minutes between jobs.

How Do You Draw the Zone Boundaries?

Start from where your jobs actually cluster, not from a map. Pull your job history for the past three to six months and plot the districts. Most installation businesses in Bangkok find their jobs concentrate in three or four natural clusters. Those clusters are your starting zones.

Practical zone structures by team size:

Two technicians: A north/south or east/west split using the expressway ring road or the Chao Phraya as a boundary. Simple to communicate, easy to override when needed. Each technician stays on their side except when the other is full.

Three to four technicians: A quadrant model — northwest, northeast, southwest, southeast. This maps naturally onto Bangkok’s expressway interchange structure. Outer jobs in Pathum Thani, Samut Prakan, or Nakhon Pathom belong to the adjacent quadrant technician, with a small premium baked into the call-out charge to compensate for the extra distance.

Five to seven technicians: District cluster assignment. Group neighborhoods that share natural travel corridors: Klong Toei + Phra Khanong + On Nut as one zone; Nonthaburi + Bang Yai + Pak Kret as another; Bang Na + Samrong + Bearing as a third. Each cluster is one technician’s primary territory.

Keep zone boundaries loose enough that a 10–15 km exception can still be handled by the zone technician without breaking their day. If a minor cross-zone job creates a cascade of rescheduling, the zone is drawn too tightly.

What Happens When a Job Falls Outside the Assigned Zone?

Three situations legitimately override zone assignment — and all three should be agreed in advance so dispatchers do not need to debate each case.

Zone technician at capacity. When the zone technician has no available slot, assign to the nearest adjacent zone. “Nearest” means shortest realistic travel time, not straight-line map distance — in Bangkok those are frequently opposite each other.

Skill mismatch. If the job requires a specialist your zone technician does not hold — a solar inverter fault, a fire panel programming, a lift system integration — the specialist goes regardless of which zone the job falls in. Skill beats zone every time.

Priority emergency. An MA customer with a critical failure — cold storage cooling down, an active fire panel fault, a data centre UPS trip — sends the nearest available technician without zone consideration. Zones manage routine and planned work. They do not apply to genuine emergencies.

Document these exceptions as they occur. If the same exception recurs consistently — one zone is chronically over capacity on Fridays, one zone generates specialist jobs at a rate the general technician cannot handle — that is a signal to redraw the zone or staff it differently, not to keep overriding the system.

A Worked Example: Four Technicians Across Bangkok

A CCTV and aircon service business with four technicians handling roughly 20 jobs per week draws the following zones:

Technician A — North: Don Mueang, Nonthaburi, Pak Kret, Lat Phrao. Primarily shophouse aircon MA visits and residential CCTV installs. Average between-job travel: 18 minutes.
Technician B — East: Ramkhamhaeng, Klong Toei, On Nut, Phra Khanong. A mix of commercial CCTV and condominium aircon. Average travel: 14 minutes.
Technician C — West: Thonburi, Phetkasem, Bang Khun Thian. Aircon installs and annual fire alarm checks in the shophouse belt along Phetkasem Road. Average travel: 21 minutes.
Technician D — South/Outer: Samut Prakan, Bang Na, Bearing. Fewer jobs but longer distances; the day is planned with one fewer appointment and pricing is set 10–15% higher to reflect the average travel per job.

Before zone assignment, average between-job transit was 34 minutes. After six weeks, it dropped to 19 minutes — freeing roughly 1.5 hours across the four technicians daily, equivalent to one additional job per day.

How Zone Assignment Builds Customer Loyalty

A technician who repeatedly visits the same customers becomes genuinely useful in ways that transcend the work order. They know which outdoor unit has the blocked drain that needs extra attention. They know the building security desk requires a visitor pass. They remember that this customer’s solar inverter lost network connection for three days last rainy season and what fixed it.

This accumulated knowledge is operationally valuable — but only if it transfers when the technician is on leave, reassigned, or eventually leaves the company. When zone visits are logged with structured service notes, photos, and equipment observations against each customer record, the zone technician’s knowledge lives in the system rather than only in their memory. A stand-in technician inherits the context instead of starting from zero.

Zone assignment creates the repeated exposure. A good record system converts that exposure into durable customer knowledge that the business owns.

FAQ

How do I set up zones if I have no job history to analyse?

Spend one week logging the district of every incoming job request. Even a basic tally — Nonthaburi: 6, Ramkhamhaeng: 4, Thonburi: 5, Samut Prakan: 3 — gives enough data for a first-pass zone map. Adjust after 30 days based on what you observe.

What if my technicians have very different skill sets?

When skill differences are significant, run a hybrid system: zone assignment handles routine maintenance calls where any of your technicians can complete the work; specialist jobs go to the right person regardless of zone. Track the split. If specialist jobs outgrow one technician’s capacity, that is the case for training a second person in that specialty.

When does zone assignment stop being worth it?

Zone assignment adds the most value when job volume is moderate-to-high (10+ jobs per week across the team), most technicians share a broad skill set, and the customer base is geographically distributed. It is less useful when almost every job requires a specific specialist, when jobs are so infrequent that schedule flexibility matters more than travel efficiency, or when the entire service area is small enough that travel time is negligible regardless.

OnSiteQ’s dispatch board shows all open jobs and technician status on one screen — so zone assignment becomes a one-look decision rather than a five-minute LINE exchange before every booking.

Zone-Based Technician Assignment for Thai Install Crews