What PoolBoss Says
Add a stop by placing the pool on the route in the position its geography earns, not at the end of the list, then set the day it repeats on. Remove one by taking the pool off the route rather than deleting the customer, so the service history and any unpaid invoices stay intact.
Building a route is a one-time job. Keeping one is not. A live route churns every week you own it - a sale here, a cancellation there, a snowbird gone until March, a repair customer who wants one visit and nothing after that. Most operators hit their first real version of this inside the first year, usually the week they pick up two accounts and lose one.
The mechanics take about thirty seconds. What costs money is the part nobody writes down: where in the day a new stop actually belongs, what happens to the visits already sitting on this week's calendar when you pull a pool off, and how the technician driving that route finds out before 6am.
At a glance
Key takeaways
- Insert a new stop where its geography earns, not at the end of the route - the end position is a default, not a decision, and it can cost 20 minutes of backtracking.
- Remove a stop by taking the pool off the route, never by deleting the customer, so service history and unpaid balances survive.
- Set the recurring day and frequency when you add the stop; a stop with no recurrence is a stop that never appears on anyone's day.
- Pausing an account and cancelling it are the same action on the route and completely different facts nine months later - keep the customer active when the absence is temporary.
- Visits already completed never move when the route changes; only still-scheduled future visits follow the change.
- A pool added today gets its first visit on the next occurrence of its day - schedule the first one directly if you promised service this week.
- Tell the technician about every add and every removal before the day starts, because an unannounced stop is a skipped stop.
How do I add and remove stops from a pool service route?
To add a stop to a pool route takes three steps. Create the pool under its customer so the address, gate code, and pool details exist. Place that pool on the route in the position that matches where it sits geographically. Set the recurring day and frequency it repeats on. The third step is the one people skip, and it is why a stop sometimes exists on a route but never appears on anyone's Tuesday.
To remove a stop from a pool service route is two steps, and the first one is a decision rather than a click: you are taking the pool off the route, not deleting the customer. Take the stop off, then close out whatever is still open on the account. Decent pool route software keeps these as separate actions for exactly this reason, and PoolBoss is the same - the controls that build and reorder pool service routes are separate from the customer record, so removing a stop leaves the customer, the pools, the invoices, and every logged reading exactly where they were.
Both are route changes, not customer changes, and that distinction is the whole post. A pool service route is a running order that happens to point at customers. When you treat it as the customer list itself, every cancellation turns into a deletion and you find out in nine months, when someone disputes a chemistry problem and the three years of readings that would have settled it are gone.
The stop order is a number, not a suggestion. Adding a new pool customer to a route almost always drops it at the end of the list by default, because that is the only position software can pick without knowing your roads. Moving it to where it belongs is a manual, ten-second act, and skipping it is the single most expensive habit in this whole workflow. If you are starting from nothing rather than maintaining something, build a route from scratch first - the order you establish there is what every later insertion has to respect.
Where a new stop belongs in the sequence
Insert by geography, not by signup date. The order of stops on a route is a driving line, and a new pool belongs wherever it falls along that line - which is almost never at the end, and has nothing to do with when the customer signed.
The test is simple arithmetic. Look at the stops on either side of where the new pool sits geographically and ask what inserting it there costs in drive time. On a dense residential route in one metro, a correctly placed stop usually adds 3-5 minutes: the drive from the previous stop, plus the service time, minus the drive you were making anyway. The same pool dropped at the end of the list can add 20 minutes or more, because you are now driving back across territory you already crossed.
This is the same reasoning behind building the route in the first place. If you have not read it, the case for grouping stops tightly is worth having in your head before you start inserting into a route you already run - it is the difference between a route that absorbs new accounts and one that degrades every time you win one. The short version: cluster stops by geography first, then treat every later insertion as a question about which two stops the new one goes between.
Here is what that costs in a real week. An operator running three routes out of Mesa, Arizona picks up two new pools in Queen Creek on a Tuesday and loses one in Apache Junction the same week. Queen Creek falls between stops 6 and 7 on the Wednesday route geographically. Dropped at the end of that route, the two new pools add about 22 minutes of backtracking to every Wednesday from now on. Inserted in position, the same two pools add about 9 minutes total. That is roughly 13 minutes a week, or about 11 hours a year, bought with one decision that took ten seconds. The Apache Junction cancellation comes off the route the same afternoon, but the customer record stays put, because there is still $135 outstanding and three years of readings that would matter if that homeowner ever disputes a chemistry problem.
Two things override geography, and only two. A customer with a genuine time window - a commercial pool that has to be serviced before the property opens, or a gate that is only unlocked between certain hours - gets placed by the window, and the drive time is the cost of the account. And a pool that needs a longer service slot sits where the day can carry it, usually not last. Everything else follows the line.
Removing a stop is not the same as deleting a customer
There are four different things operators mean by "take this pool off my route," and they have four different correct answers. Getting them confused is how service history disappears and how a customer who paused for the winter comes back in March to find no record that they were ever a customer.
The rule underneath all four: the route is the only thing you change. Everything that is evidence - visits, readings, photos, invoices, notes - stays attached to the pool and the customer no matter what happens to the stop. That holds whether you are ending an account, pausing one, or just need to move a pool to a different route because a second truck now covers that side of town.
| What you want | What to change | Visits already scheduled | History and billing |
|---|---|---|---|
| Customer cancelled for good | Remove the stop from the route; keep the customer record | Remaining scheduled visits come off the calendar | All history, invoices, and unpaid balances stay intact |
| Pausing for the winter or a long absence | Take the pool off the route; leave the customer active | Future visits stop generating until it goes back on | Untouched - the account picks up where it left off |
| Moving a pool to a different route | Move the stop to the other route and set its position there | Upcoming visits follow the pool to the new route and technician | Untouched - it is the same pool, serviced by someone else |
| One-time visit, no recurring service | Do not put it on a route at all; schedule the single visit | One visit only, nothing repeats | Logged and billable like any other visit |
- Never delete a customer to get a stop off a route. Deleting is for a record created in error, not for a relationship that ended.
- A paused pool and a cancelled pool look identical on next Tuesday's route sheet and completely different in nine months.
- If a pool is coming off because of an unpaid balance, the balance is a billing decision and the stop is a route decision - make both, in that order.
What happens to visits already on the calendar this week
This is the part the help articles skip, and it is where the real confusion lives. Your route generates visits ahead of time - that is what makes a route sheet exist before the day arrives. So when you change the route, there is already a set of scheduled visits sitting on the calendar that were created under the old arrangement.
Removing a stop mid-cycle should take its still-scheduled future visits off the calendar with it. A visit that has already happened never moves: it is a completed record with readings and a timestamp attached, it may already be on an invoice, and it stays exactly where it is. The line is between what has been done and what was merely planned, and only the planned half follows a route change.
Adding a stop mid-cycle works the same way in reverse, with one wrinkle worth knowing before it surprises you: a pool added on Wednesday does not retroactively acquire a visit for Monday. Its first visit is the next occurrence of the day you set. If you promised a new customer service this week and the recurring day has already passed, schedule that first visit directly rather than waiting for the route to produce one.
The frequency the stop inherits is worth a deliberate look rather than a default. Weekly, every other week, and monthly stops on the same route produce very different calendars, and the recurrence you pick is what the route will keep producing for months. It is a two-second decision to set the recurring day the stop repeats on correctly now, and a tedious cleanup to fix forty generated visits later.
Tell the technician before the route sheet changes under them
A stop that appears silently is a stop that gets skipped. The technician who has run the same 40 pools for eight months is not reading the list carefully at 6:20am - they are driving a sequence they know by muscle memory, and an unannounced eleventh stop between the tenth and twelfth is genuinely easy to drive straight past.
Say it out loud, in whatever channel you already use. Not a memo: one message that names the customer, the position in the route, and anything unusual about the property. Thirty seconds of warning is worth more than any amount of software here, because the failure mode is not that the technician cannot see the stop - it is that they were not looking for a change.
A removal needs the same treatment, for a different reason. A technician who pulls up to a house that is no longer on the route has usually done it because nobody told them, and the customer standing in the driveway watching a pool company arrive after they cancelled is an awkward conversation you paid for. Worse is the reverse: a technician who assumes a missing stop is a software glitch and services it anyway, unbilled.
Do not rely on the change being visible as its own announcement. Route changes are recorded and a new stop does show on the day's list, but a record is something you consult after a question, not something that reaches a person before they need it. The message is the announcement; the record is the proof it happened.
FAQ
Frequently asked questions
How do I pause a customer for the winter without losing their history?
Pausing a pool service account means taking the pool off the route and leaving the customer and the pool records active. That stops future visits from generating while keeping every logged reading, photo, invoice, and note attached to the account, so when they come back in spring you put the stop back on the route and continue rather than starting over. The mistake to avoid is deleting the customer or the pool to make the route sheet clean - a snowbird who leaves for five months is not a former customer, and the readings from last September are exactly what you will want if there is an argument about a stained surface in April. Note the expected return month somewhere on the record while you are at it. A paused account with no return date is the one that quietly becomes a lost account, because nobody remembers to put it back.
What do I do when a customer cancels mid-month and has already been billed?
Work out what they actually received, then either credit the difference or let it stand, depending on how you bill and what your agreement says. Monthly billing usually covers a set number of visits, so a customer who cancels after two of four visits has paid for two they will not get - most operators issue a partial credit or refund for the unserviced portion, because the alternative is a chargeback and a bad review over a small amount of money. If you bill in arrears for visits already completed, there is nothing to unwind. Either way, take the stop off the route first so no further visits generate, then settle the money as a separate decision. Doing it in the other order is how a cancelled customer gets serviced one more time and billed for it, which turns a clean exit into a dispute.
Can I add a one-time visit without putting the pool on a recurring route?
Yes, and you should - a one-time pool service visit does not belong on a route at all. Routes exist to produce repeating visits, so putting a one-off customer on one means either remembering to remove them afterward or generating visits nobody wants. Schedule the single visit against the pool directly instead. This is the normal shape for a repair call, a green-pool recovery for a non-customer, a vacation-rental turnover, or a real-estate inspection clean. The visit still gets logged with its readings and notes, still bills like any other work, and still becomes part of that pool's history if the customer later signs up for recurring service. If a one-time customer does convert, that is the moment to put the pool on a route and set its recurring day - not before.
How many stops can I add to a route before I need to split it?
Look at the day rather than the count. A residential pool tech typically handles 15-25 stops a day depending on density and service time, so a weekly route running five days sits somewhere around 75-125 pools. The signal to split is not a number you hit, it is the day ending later every week, techs skipping the last two stops when anything goes wrong, or drive time creeping up as new accounts land outside the original cluster. Splitting usually means creating a second route from the geographic half that has grown, rather than dividing the list evenly - the goal is two tight routes, not two mediocre ones. If most of your growth is landing in one part of town, that part is the new route, and the original keeps everything else.
What if a new customer wants a service day that doesn't fit my route?
Offer the day your route already runs in their area first, and price the exception if they insist on another one. A customer who wants Friday in a neighborhood you service on Tuesday is asking you to make a special trip, and a single out-of-area stop can cost 30-40 minutes of driving for one 20-minute service. That is a real cost, and it belongs in the price rather than absorbed quietly. Most customers accept the standard day once they understand it is the reason your pricing works. When someone genuinely cannot flex - a commercial property with an access window, or a rental with a fixed turnover day - decide whether the account is worth the detour at your normal rate, and if not, quote it at what the drive actually costs. The accounts that damage a route are the ones taken at standard price on non-standard terms.
Does removing a stop delete the chemical readings I already logged?
No, as long as you remove the stop rather than delete the customer or the pool. Readings are recorded against the visit and the pool, not against the route, so taking the pool off a route changes nothing about what was logged. The full history stays on the pool record and remains available when you need it - which is usually months later, when a homeowner asks what happened to their surface or an insurer wants to see what the water was doing on a specific date. This is exactly why deleting a customer to tidy up a route is the wrong move: it is the only action in this whole workflow that can actually cost you the evidence. If you need a former customer out of your working views, archive the record rather than removing it, which keeps the history intact and out of the way.
How often should I re-sequence a whole route instead of just inserting stops?
Re-sequence when the day stops matching the map, which for most routes is once or twice a year rather than every time something changes. Individual insertions handle normal churn fine if you place each one properly. What accumulates is the drift from the ones you did not: a dozen stops added at the end over eight months, each adding a few minutes, until the route is quietly 45 minutes longer than it should be. Signs it is time: techs finishing late consistently, obvious backtracking on the map, or a cluster of new accounts in an area the original order did not anticipate. Re-order the whole route as one deliberate pass rather than nibbling at it, review the proposed order before it takes effect, and tell the technician - a re-sequenced route is the change most likely to cause a missed stop the following week.
