The short answer
Cut drive time by grouping pools into tight geographic zones, assigning each zone its own service day, and ordering the stops in true driving sequence instead of by customer name. Let the map set the calendar, not the other way around, and reprice or move the isolated stops that pull a tech across town.
Drive time is the hidden tax on a pool route. Every minute a tech spends behind the wheel is a minute they're not testing water or getting paid, and on a loose route it can swallow a third of the day. For a solo operator or a small fleet, trimming that windshield time is the cheapest way to fit more pools into the same hours without finishing after dark.
The fix isn't a faster truck. It's how you group, sequence, and price your stops. Here is how to cut the driving without dropping a single account: clustering pools into zones, letting location set the service day, ordering each day to avoid backtracking, dealing with the one far-off pool, and keeping the whole thing tight as the route drifts.
At a glance
Key takeaways
- Drive time, not time at the pool, is what caps a tech's day, so cutting windshield time is the cheapest way to fit in more pools.
- Group pools into tight geographic zones and make each zone its own service day before you worry about anything else.
- Let the map set the calendar: a pool's location decides its service day, not the customer's casual day preference.
- Order each day's stops in true driving sequence, the shortest practical loop, never alphabetically or by sign-up date.
- Re-clustering one crisscrossing day by zone can cut roughly an hour of driving a week without dropping a single account.
- Price a far-off stop to cover the round trip, move it to the closest day's route, or drop it at renewal, but don't absorb the drive silently.
- Re-check routes monthly for stops out of order and do a full re-cluster each season, heaviest before peak summer.
Drive time, not pool time, caps how many stops fit in a day
Group your pools into tight geographic zones and make each zone its own service day. Drive time, not pool time, is what caps how many stops a tech can finish, so the biggest single lever you have is how closely the day's pools sit together. A day spent inside one subdivision runs far more pools than the same hours scattered across three towns. The same density test is the first thing to apply before you buy a route someone else built, because stops that cluster are worth far more than a scattered book that hands you a full day of driving on every visit.
Start by plotting every customer on a map and looking for natural clusters: a neighborhood, one side of the highway, a corridor of HOAs on the same road. Each dense cluster becomes a day. When you win a new account, it should join the day that already covers its area, not whichever day has an open slot. In a tool built to manage your service routes, you assign each stop to a route and the day stays grouped, so the clustering you set up doesn't quietly erode every time you add a pool. Cutting drive time assumes the work belongs on a recurring route in the first place; for the one-off work that doesn't repeat, like a repair or a green-to-clean, deciding between a route and a standalone job comes first.
Assign customers by zone first, then fit their day preference
Assign by zone first, then fit customer preferences inside it. The habit that quietly wrecks a route is letting the calendar drive the map: saying yes to "can you come Thursdays?" over and over until your Thursday route is scattered across every neighborhood you serve. Let the map decide the calendar instead. The pool's location sets its service day, and you offer the customer the day that already covers their street.
Most residential customers don't actually care which weekday you come, as long as it's the same day every week and the water stays clean. Reserve hard day requests for the few who genuinely need them, like a restaurant that wants the pool right before the weekend or a rental with a Friday turnover, and cluster everyone else by geography. Hold that line on new sign-ups and your routes stay tight on their own, instead of needing a rescue re-sort every few months.
Re-sorting one day by driving order can save an hour a week
Once a day's pools are grouped, order the stops the way you'd actually drive them, shortest practical loop, not alphabetical or by sign-up date. Start where the tech begins the day, chain to the nearest sensible next stop, and finish near where the day needs to end. The aim is to never cross the same ground twice.
Take a solo operator running 55 pools across Chandler and Gilbert. His Tuesday route was built in the order customers signed up, so it crisscrossed both towns all day: Gilbert, back to Chandler, back to Gilbert. Re-sorting that one day by zone and driving order cut about an hour of windshield time a week, with no accounts dropped. That hour is either two more pools or a Tuesday afternoon back.
Route software can suggest an optimized stop order for you, which saves the by-hand sorting on a big day. Keep it preview-and-confirm, though: you approve the new order before it goes live, because the map doesn't know about gate codes, a customer's time window, or the stop you always hit first because the dog is out after nine. The software proposes; the operator still decides.
How do I handle a customer far off my route?
Price the isolated stop to cover the round trip, or move it, but don't quietly absorb the drive. A pool fifteen or twenty minutes outside your tightest cluster costs you that drive on every single visit, which can turn a normal-looking account into one that loses money once you actually count the hours behind the wheel.
You have three honest options for the stranded stop: charge a premium that covers the extra drive and the capacity it burns; move it to the day whose route already passes closest to it; or, if it's underpriced and truly out on its own, let it go at renewal and put those hours back into pools near home. A single far-off pool also eats into how many pools one tech can service in a day, so the cost is rarely just the fuel. The exception is a far stop that's the first of several you plan to win in a new area; then it's a beachhead, and the math changes as density fills in behind it.
How often should I rebalance a pool route?
Re-check your routes monthly and do a deeper rebalance each season. Routes drift on their own: you add accounts, lose a few, customers move, frequencies change with the weather, and a loop that was tight in March is crisscrossing by June. A route is never finished, it's maintained.
Keep it light most of the time. A monthly pass is just a scan for any stop that's landed out of driving order or on the wrong day, fixed in a couple of minutes. Save the full re-cluster for the start of each season, especially heading into peak summer when weekly service packs every route tighter and a sloppy sequence costs you the most. Operators who rebalance on a schedule rarely face the all-day rebuild that comes from letting a route sprawl for a year.
FAQ
Frequently asked questions
How do I cut drive time on my pool route?
Cut drive time by attacking how your stops are grouped and ordered, not by driving faster. Start by clustering your pools into tight geographic zones and giving each zone its own service day, so a tech spends the day inside one area instead of hopping between towns. Within each day, sequence the stops as a single shortest loop, beginning where the tech starts and ending near where they finish, rather than ordering them alphabetically or by when each customer signed up. Then deal with the outliers: a pool far from everything else should be repriced to cover the round trip or moved to the route that passes closest to it. Those three moves, grouping, sequencing, and handling the far stops, are where almost all the savings live. Most routes carry an hour or more of avoidable driving a week before anyone tightens them up.
What is windshield time in a pool service business?
Windshield time is the time a technician spends driving between pools rather than working on them. It's unpaid, unproductive time, and on a loosely built route it can eat a third of the workday. Operators track it because it's the real ceiling on how many pools fit into a day: two techs with identical pool counts can have very different days if one runs a dense subdivision and the other crosses town between every stop. Total route time is really drive time plus service time, and while service time per pool is fairly fixed, drive time is the part you can shrink by grouping and sequencing stops well. Cutting windshield time doesn't just save fuel, it frees up hours you can fill with more pools or hand back to the tech as an earlier finish.
Should I group pool stops by location or by customer's preferred day?
Group by location first, then fit preferences inside the zones. If you let customer day requests drive the schedule, you end up with routes scattered across every neighborhood you serve, because you said yes to enough "can you come Tuesdays?" asks that Tuesday now spans the whole metro. Instead, let the pool's location set its service day and offer each new customer the day that already covers their street. In practice most residential customers don't care which weekday you come as long as it's consistent and the water stays clean, so you can hold this line on nearly everyone. Keep hard day requests for the handful who truly need them, such as a commercial account that wants service before a busy weekend. Doing this on every sign-up keeps routes tight without constant re-sorting.
How do I sequence my pool stops so I'm not backtracking?
Order each service day as the shortest practical loop through that day's pools. Start from where the tech begins, chain to the nearest sensible next stop each time, and end near where the day needs to finish, so the route never doubles back across ground it already covered. Don't order stops alphabetically or by account number, which is how most inherited routes are built and exactly what causes the zigzagging. After any change, like adding a stop or a reschedule, re-check the order rather than tacking the new stop onto the end. Route software can propose an optimized order and let you drag stops into place, which makes this a quick job instead of a manual re-plan, but you should still confirm the sequence yourself so real-world details like gate codes and time windows are respected.
What should I do with a pool that's far from the rest of my route?
You have three honest options, and absorbing the drive quietly isn't one of them. First, reprice it: charge a premium that covers the round trip and the capacity that drive burns, since the pool costs you on every visit, not just once. Second, move it: if another of your routes passes closer to it on a different day, shift the stop there. Third, drop it at renewal: if it's underpriced and genuinely stranded, those hours are usually worth more spent on pools near home. The one exception is a far-off pool that's the first account in an area you plan to build out. In that case it's a beachhead, and the per-visit drive cost falls as you add density around it, so it can be worth carrying at a thin margin for a season.
How often should I re-optimize my pool service route?
Re-check routes monthly and do a full re-cluster each season. Routes drift on their own as you add and lose accounts, customers move, and service frequencies shift with the weather, so a route that was tight in spring can be crisscrossing by midsummer. The monthly pass is light: scan for any stop that's drifted out of driving order or landed on the wrong day, and fix it in a couple of minutes. The seasonal pass is the real work: re-cluster the whole book, especially going into peak summer when weekly service packs routes tighter and a loose sequence costs the most drive time. Operators who rebalance on a schedule avoid the painful all-day rebuild that comes from ignoring a route for a year, and their windshield time stays low instead of creeping up unnoticed.
