Ask any pool service operator with more than fifteen pools how they manage their routes, and you'll get one of two answers. Either they've figured it out — a system that works, even if it's held together with spreadsheets and habit — or they'll describe a daily scramble that ends with someone ringing around at 7am trying to work out who's doing what. Most operators in the second camp have been meaning to fix it for months.
Route management is one of those problems that's invisible when it's working and very visible when it isn't. A technician finishing the day with three pools unserviced because the run order didn't account for traffic through South Auckland at 4pm. A customer calling to say their tech never showed up, and you're not sure which run they were assigned to. A new tech starting Monday with a printed list and a phone full of forwarded WhatsApp messages. That's what bad route management costs — not in one dramatic event, but in the slow accumulation of wasted time and strained relationships.
The problem with manual route planning
Spreadsheets work for route management until you have about ten to fifteen pools. Below that threshold, you probably know the run by memory anyway. Above it, the cracks start showing.
The most common manual setup: a spreadsheet with pool addresses sorted roughly by suburb, converted to a PDF, emailed or texted to the tech the night before. It gets the job done, mostly. But it doesn't account for the customer who rescheduled Thursday's service to Monday, or the tech who called in sick and whose pools need redistributing across two other runs, or the new pool added last week that ended up at the bottom of the list because that's where it was entered.
WhatsApp and group chats fill the gap: "can you swap these two stops", "skip 14 Kauri Drive today", "customer says gate code changed to 4821". It works, but it's invisible to anyone not in the thread. And when something goes wrong — a pool missed, a customer complaint — the paper trail is a scroll through chat history.
What good route management looks like
Good route management does three things consistently: it orders stops intelligently, it surfaces the right information at the right time, and it distributes work fairly across technicians.
Geographic clustering is the foundation. Pools near each other should be on the same run, sequenced to minimise backtracking. In practice this means stops are ordered by drive time rather than by suburb name or customer ID. A route that loops back across town twice a day is wasting 30–45 minutes that could be another pool service.
Load balancing matters more as the team grows. Two technicians shouldn't be running eight pools and twelve pools respectively when you could split it more evenly. Load balancing also means accounting for pool type and service duration — a commercial pool isn't the same time commitment as a residential one.
Stop information on demand is often overlooked. Gate codes, dog warnings, parking notes, access instructions — this information exists in someone's head or in scattered notes, and every new technician has to be briefed manually. A good system surfaces this per-stop when the tech is en route, not as a bulk briefing they won't remember.
NZ and Australian context: what's different here
Route planning in New Zealand and Australia has a few specific realities that North American or European software sometimes doesn't account for.
Suburban sprawl in Auckland, Christchurch, Brisbane, and Melbourne means drives between pools can be substantial — a "nearby" stop might still be twenty minutes away in peak traffic. Coastal and rural operators face even longer inter-stop distances. Route efficiency matters more here than in densely populated markets where you can knock off fifteen pools in a tight two-kilometre radius.
Residential routes also tend to dominate. Most NZ and AU pool service businesses are serving residential customers, which means pool access depends on homeowners being home, gate codes working, and dogs being secured. All of this access information needs to be stored and surfaced reliably — a common failure point for operators who rely on techs remembering these details from week to week.
How digital tools change this
The shift from manual to digital route management isn't about replacing good judgment — it's about removing the administration that gets in the way of it. A digital run sheet that reorders stops by drive time, sends the tech their day's route before they leave home, and surfaces gate codes as they approach each stop isn't doing anything a skilled operator couldn't do manually. It's doing it consistently, without anyone having to think about it each morning.
The other change is visibility. When a run is on paper, only the person holding the paper knows its status. When it's digital and the tech is checking off stops as they go, the operator can see how the day is tracking in real time. That means intervention before things go wrong — not after.
Good technician scheduling and route management work together: the scheduling system pre-builds each tech's weekly runs, and the route management layer makes those runs navigable without manual effort. And with routes and scheduling locked in, chemical compliance record-keeping becomes much more tractable — every visit is timestamped and structured from the start.
Getting started
If you're currently on spreadsheets or paper, the switch to digital doesn't need to be dramatic. Start by getting all pool access information into a single system — gate codes, parking notes, special instructions. That alone eliminates a recurring source of friction. From there, building run sheets digitally and distributing them to techs via an app is the natural next step.
PoolAxis handles route management as part of its core operations platform — digital run sheets, stop-by-stop access information, and technician visibility all in one place. If you're managing more than ten pools and still routing manually, it's worth a look.