The short answer
Assign routes by dividing your service area into geographic zones, then giving each technician a zone or a set of days and ordering the stops inside each zone to cut backtracking. Balance the days by service hours, not pool count, and keep each tech on the same zone so they learn the pools.
The day you add a second truck, route assignment stops being automatic. With one tech, the route is just the whole book. With two or three, someone has to decide which pools each person services and on which days, and the easy answer - split the customer list down the middle, or by who signed up when - is the one that quietly burns hours in drive time every single week.
The method that holds up is geographic: cluster the pools into zones, hand each tech a zone or a set of days, balance the days by how long the work actually takes, and keep people on the same ground long enough to learn it. Here is how to group the pools, assign zones to techs, size each day by service hours, keep techs on a consistent route, and cover a route the day someone calls in sick.
At a glance
Key takeaways
- Assign pools to technicians by geography - split the service area into zones first, then hand each tech a zone, rather than dividing the customer list by name or sign-up date.
- Give each technician a whole zone or a fixed set of weekdays so their week is a few tight loops, not stops scattered across the metro.
- Order the stops inside each assigned zone as one continuous loop, and keep optimization preview-and-confirm so the owner approves the sequence.
- Balance days by service hours, not pool count - 50 close-together residential pools can be a lighter day than 30 spread-out commercial ones.
- Use 40-50 stops a day per tech as a starting point, then move a few streets between days until each shift is full but finishable.
- Keep techs on the same zone week to week so they learn the pools; reassign only for a departure, a split, or an absence.
- Because pools are already grouped into zones, covering a sick day means handing off one area to the nearest working tech, not untangling a scattered list.
How do I assign routes to my pool service technicians?
Divide your service area into geographic zones, give each technician a zone or a fixed set of weekdays, and order the stops inside each zone so the truck runs one loop instead of crossing town. That single rule - assign pools to technicians by where the pools are, not by the order they signed up or by splitting the list alphabetically - is what separates a route that fits in a workday from one that doesn't. Good route software lets you assign and reorder routes by dragging stops between techs and days, so the plan you build on a map is the plan that shows up on each tech's phone the next morning.
There are really only two decisions in route assignment: which pools share a day, and who works that day. Get the geography right first and the second decision gets easy, because a tech is really being assigned an area, not a random list of 45 addresses. Assigning by area also means the pool service technician routes stay stable as the book changes: a new customer joins the zone that already covers their street, rather than landing on whoever happens to look light this week.
Group the pools into zones before you assign anyone
Plot every customer on a map and look for the natural clusters before you hand out a single route. Pool route zones usually fall out of the geography on their own - a subdivision, one side of a freeway, a corridor of HOAs on the same road - and each dense block of pools becomes a zone you can turn into a service day. This is the same geographic routing work whether you have two techs or ten, and it's worth reading how to group stops by neighborhood first before you split them among people, because you can't assign zones you haven't drawn yet.
Take an owner in the Phoenix metro who grows from one truck to three and has 300 pools scattered from Peoria to Mesa. Assigned by sign-up order, all three techs crisscross the valley every day and no one is ever near the next stop. Regrouped into three zones - West Valley, Central Phoenix and Scottsdale, and the East Valley - each tech works one slice of the map, and the daily driving drops without dropping a single account. Route planning at that scale is a geography problem first and a staffing problem second.
Give each tech a zone or a set of days, not a scattered list
Once the zones are drawn, hand each technician a whole zone or a defined set of weekdays inside it, so their week is a small number of tight loops rather than stops sprinkled across the metro. A multi-tech pool route works best when the boundaries between techs follow the same lines as the zone boundaries - Tech A owns the West Valley Monday through Thursday, Tech B owns the East Valley, and neither one is driving through the other's territory to reach a stray pool.
Ordering matters as much as ownership. Inside each assigned zone, sequence the stops as one continuous loop - start where the tech begins the day, chain to the nearest sensible next pool, and end near where the day should finish - instead of a zigzag that doubles back. Route optimization tools can propose that order for you, but keep it preview-and-confirm: the tech or the owner approves the sequence before it goes live, because the map doesn't know about the gate code, the customer's time window, or the yard with the dog out until nine.
Balance the days by service hours, not pool count
Balance each technician's day by how long the work takes, not by how many pools are on it. Fifty small residential pools sitting close together can be a lighter day than 30 large commercial bodies of water spread across town, so counting pools alone produces one brutal day and one that wraps by early afternoon. Start from a realistic figure for how many pools a tech can handle in a day given your pool mix and drive times, then balance pool service routes by moving a street or two from the heavy day to the light one until each day is a full but finishable shift.
A common target for a residential route is 40-50 stops a day per tech at roughly 20-25 minutes a pool including drive time, but treat that as a starting point, not a law - the right number falls fast when pools are big, far apart, or heavy on repairs. The signal that a day is unbalanced is simple: if one tech is regularly finishing two hours before another, the boundary between their zones is in the wrong place, and rebalancing the two days is usually a matter of shifting a handful of pools, not redrawing the whole map.
Keep each technician on the same route
Leave a technician on the same zone week after week instead of reshuffling assignments constantly. A tech who runs the same pools learns them - which pumps are temperamental, which pools go cloudy in a heat wave, where the equipment pad is, which customers want a text before arrival - and that knowledge is worth real money in fewer callbacks and faster visits. Rotating techs across zones every week throws that away and makes every visit a first visit.
Consistency also protects the customer relationship. Homeowners and property managers notice when the same person services their pool, and a familiar tech gets fewer 'did anyone even come?' calls because the customer recognizes the truck and the face. Reserve reassignment for real reasons - a tech leaves, a zone outgrows one person and has to split, or someone is out - rather than churning the schedule for its own sake. Stability in who services what is one of the quiet advantages a route-based operation has over job-by-job dispatch.
How do I reassign a route when a technician is out?
Reassign a route by moving that day's stops onto the techs who are working, ideally splitting them by which remaining zone sits closest, so no one absorbs a two-hour detour. Because the pools are already grouped into zones, a sick day becomes a contained problem - you're handing off one area, not untangling a scattered list - which is exactly why the geographic setup pays off under pressure. Walk through the full playbook for how to cover a route when a tech is out so the reassign-pool-route scramble becomes a five-minute decision instead of a morning of phone calls.
In practice this is where drag-and-drop assignment earns its keep: pull the absent tech's stops onto the working techs' routes for the day, and each of them sees the added pools on their phone without a single phone call. This is route-level dispatch, not GPS tracking - you are reassigning who owns which stops, not watching trucks move on a live map. When the tech is back, drag the stops home again and the zones return to normal, with no permanent change to who owns what.
FAQ
Frequently asked questions
How many pools should I assign to each technician?
A common starting point is 40-50 residential pools a day per technician, at roughly 20-25 minutes per pool including drive time, but the right number depends heavily on your mix. Large commercial pools, long distances between stops, and accounts that include repairs all pull the number down - a tech on scattered commercial work might handle 20-25 stops in the same day a tech on a tight residential subdivision handles 55. Rather than picking a fixed count, size each day by total service hours and adjust until it's a full but finishable shift. If a tech is consistently finishing two hours early or running an hour late, move a handful of pools between days to rebalance.
How do I handle a new customer that falls between two techs' zones?
Put the new pool in whichever existing zone's route already passes closest to it, even if that isn't the zone that looks lightest on paper. Adding one stop to a route that already runs near the address costs almost no extra drive time, while dropping it on a distant tech because their day looks open creates a permanent detour on every visit. If the new customer genuinely sits between two zones, give it to the tech whose loop comes nearest, or to the one with a little more room in their day. A pool that falls outside every zone is a signal to either price it to cover the trip or treat it as the first account in an area you plan to build out.
How often should I rebalance my technicians' routes?
Do a light check monthly and a deeper rebalance each season, plus a real re-zone heading into peak summer when weekly service packs the routes hardest. Zones drift on their own as you win and lose accounts and as service frequencies change with the weather, so a balanced set of days from spring can be lopsided by midsummer. The monthly pass catches the obvious problems - a new pool in the wrong zone, a day that has started running long. The seasonal pass is the real work: look at where accounts have landed and shift streets between days so each tech's shift is even again. Operators who rebalance on a schedule avoid the all-day rebuild that comes from ignoring routes for a year.
What if one technician is faster than another?
Assign by output, not by an identical stop count, when your techs work at genuinely different speeds. A seasoned tech might comfortably run 50 pools a day while a newer one is solid at 35, and forcing both to the same number either overloads one or wastes the other's capacity. Give the faster tech a denser or larger zone and the newer tech a smaller one, then adjust as the newer tech speeds up. What you should not do is fix a speed gap by scattering one tech's stops across another's territory - keep each person's pools geographically together and let the zone sizes, not the map boundaries, absorb the difference. Track visits completed per tech over a few weeks to see the real gap before you rebalance.
Can I assign one route to more than one technician?
You can, but it's usually better to split a too-large area into two smaller single-tech zones than to have two people share one route. Sharing a route blurs accountability - when a stop gets skipped, it's unclear whose it was - and it tends to mean both techs drive through the same area, which is the wasted mileage zoning is meant to kill. The clean version is to divide the oversized zone along a real boundary like a freeway or a major road, give each half to one tech, and let each own their pools end to end. The exception is a large commercial property or a big HOA complex that genuinely needs two people on site at once, which is a single job with a crew, not a shared route.
Should I let each technician pick their own stop order?
Let techs adjust the order within reason, but set the baseline sequence yourself or with route software so the day starts as an efficient loop. Experienced techs know things the map doesn't - a customer who wants the pool done before a pool party, a gate that's locked until a housekeeper arrives, a street that's brutal at school pickup - and letting them tweak the order captures that. What you don't want is every tech rebuilding their route from scratch each morning, which wastes time and makes it impossible for anyone to cover for them. The workable middle is a system-proposed order that the tech confirms and can nudge, so the route is efficient by default and flexible where local knowledge beats the map.
