
Recognize the overbooked signals early
An overbooked route does not announce itself. It shows up as techs finishing after dark, skipped brushing, readings that look copied from last week, and a slow rise in callbacks. Owners often blame the tech, but a day that requires more than twenty stops spread across three towns is a scheduling failure, not a work-ethic one. If your best tech is cutting corners, your capacity is the problem.
Before dropping anyone, confirm you are actually out of capacity rather than badly routed. Map every stop by service day and look for zigzags, cross-town drives, and days that are heavier than others. Rebalancing days and clustering by neighborhood often recovers enough hours that no one has to go. Route software makes this visual in minutes; a wall map and pins does the same job more slowly. Only when the geography is tight and the days are still too long is it time to prune. Related: What is the best way to log chemical readings at every pool stop?
Keep reading: How do you balance pool water chemistry on a weekly service route?, What is the best way to log chemical readings at every pool stop?, Why does free chlorine keep dropping between weekly pool service visits?. See how PoolTendr helps you pool service route scheduling and chemical logs.
Score every account on time, distance, and margin
Pull up each account and estimate three things: how long the stop actually takes (not what you quoted), how far it is from the nearest other stop, and what you clear after chemicals and drive time. The pools that hurt are rarely the biggest or the dirtiest. They are the isolated ones twenty minutes from anything, the ones with a gate code that never works, and the ones where the owner pays slowly and calls often. Those absorb time that your dense, easy accounts are quietly subsidizing.
A simple spreadsheet with a column for each factor and a rough score is enough. Sort by score. The bottom few will usually be obvious once you see them side by side. Be honest about the stops that are personally pleasant but financially bad; the friendly customer with the far-flung pool is still a far-flung pool. Also flag accounts whose service needs have outgrown the price, such as a pool that was quoted as low-maintenance and now has a struggling pump and a heavy tree canopy. Related: Why does free chlorine keep dropping between weekly pool service visits?
Try a price correction before a goodbye
Dropping a customer should be the second option. The first is to price the account correctly. Tell the far-away customer what the drive really costs and quote a rate that reflects it. Tell the slow-paying customer that you are moving to automatic payment. Tell the chronic-complaint customer what a weekly stop includes and what is billable. Some of these accounts will accept the change, and the ones who leave have solved your capacity problem for you.
Frame it as what it is: your route has filled up and you are making sure every pool gets the time it needs. Give at least a few weeks' notice, and if the account is now outside your service area, say so plainly and recommend another company if you know a good one. Customers remember how they were let go, and the pool service world in any given town is small. Related: How do you balance pool water chemistry on a weekly service route?
Fill the freed capacity on purpose
Once the route has breathing room, resist filling it with the next call that comes in. Set a geographic boundary and stick to it. Put new prospects into the route only if they cluster with existing stops on the same service day. Ask about equipment, tree cover, and access before quoting, because those three things drive stop time more than pool size does. A good rule is that a new account should make the day it lands on shorter per stop, not longer. Related: Which chemicals should a pool technician carry on a daily service route?
Track the effect. Stops per tech-day, average drive minutes between stops, and callback count are the three numbers that tell you whether the pruning worked. If drive time is falling and callbacks are down a month later, the route is healthier. Software that records timestamps at each stop makes these numbers automatic, but even a weekly glance at the mileage log tells you a lot.
- Long days, copied readings, and rising callbacks are capacity problems, not tech problems.
- Rebalance and cluster the route first; only prune when geography is already tight.
- Score accounts on real stop time, distance from other stops, and margin, then correct pricing before dropping anyone.
- Refill capacity only with stops that shorten the day they land on.
Every Pool, Every Reading, On Route
Pool service route scheduling and chemical logs. PoolTendr is built to help you put this into practice.
Start free trialMore from the PoolTendr blog

How do you balance pool water chemistry on a weekly service route?

What is the best way to log chemical readings at every pool stop?

Why does free chlorine keep dropping between weekly pool service visits?
Get the PoolTendr playbook
Practical guides on pool service software, straight to your inbox as we publish them. No spam, unsubscribe any time.
