The short answer
You confirm every stop got serviced by checking the record each visit leaves - a completed checklist, readings logged at the pool, a completion time, and the service report sent to the customer. If a stop has no completed record by end of day, it was not done. You do not need to track the tech's location.
The question gets sharper the moment you can no longer ride along. With one truck you know every stop got done because you did it. Add a tech or two and you are trusting a completion you did not see, usually right when a customer calls to say nobody came.
The instinct is to reach for GPS tracking, but location does not prove a pool was serviced - a truck can sit at the curb while nothing happens in the backyard. What actually proves the work is the record each visit leaves behind. Here is what that record contains, how to spot a skipped stop the same day, why GPS is the wrong tool, and how to handle a stop that was marked done but was not.
At a glance
Key takeaways
- Confirm a stop was serviced by the record it leaves - a completed checklist, logged readings, a completion time, and a service report - not by tracking the truck.
- A stop with no completed record by end of day is the one that did not happen; accountability is scanning for the blanks, not auditing every visit.
- GPS proves the truck's location, not that the pool got serviced - a truck can sit at the curb while nothing happens in the backyard.
- Review the day's completed records at the end of each route day so you catch a skipped stop before the customer calls.
- Send an automatic service report after every visit; a customer who gets one weekly rarely calls to confirm you came.
- You catch a falsely-marked-done stop by the thinness of its record - a 90-second entry with no readings stands out against full ones.
- Set the standard that a stop is not done until its readings and checklist are logged at the pool, then let the record do the watching.
How do I know if my pool technician completed every stop?
You know a stop was serviced by the record it leaves, not by watching where the truck went. A completed visit produces a small pile of evidence - a checked-off service checklist, the chemical readings logged at the pool, the time the visit was marked done, and a service report - and the presence or absence of that record is your answer. At the end of the day you see every stop's status on the route, and any stop still sitting without a completed record is the one that did not happen.
This is a cleaner test than it sounds. On a two-tech book of 110 pools you are not auditing 110 events; you are scanning for the handful of stops with no record by 4pm. A completed visit is a positive signal that stands on its own - a timestamp, readings, and a report tie the work to a specific pool at a specific time. A blank is the exception, and the exceptions are the only thing you need to chase. Accountability, done this way, is subtraction: everything with a record is proven, and you go ask about the rest.
A completed visit leaves a record - that is your proof
The proof of a serviced stop is the four-part record it produces, captured at the pool in about 15 seconds, not reconstructed from memory that night. Each piece answers a different challenge: the timestamp answers did-you-show-up, the readings answer was-the-water-actually-tested, the checklist answers did-you-do-the-work, and the report answers can-the-customer-see-it. Logging the reading and the dose together is the same habit that lets you prove what was done at the pool weeks later, and it is what turns a completed visit into something you can defend.
| Piece of the record | What it proves |
|---|---|
| Timestamp | The tech was at the pool, and when (e.g. 10:42am Tuesday) |
| Chemical readings | The water was actually tested, in numbers (free chlorine, pH) |
| Completed checklist | The routine work got done - skim, brush, empty baskets, test |
| Notes or a photo | The condition on arrival and anything that needed attention |
| Service report | The whole visit, packaged so the customer can see it too |
Why GPS tracking is the wrong answer for pool service
GPS location tells you where the truck was, not whether the pool got serviced, which is why it is the wrong tool for this job. A truck parked at the curb for 12 minutes proves the tech reached the address; it says nothing about whether the basket got emptied, the water got tested, or a dose got added. The incumbent software answer leans hard on real-time location and geofenced check-ins, but that measures presence, and presence is not service.
PoolBoss deliberately does not track technician location - accountability is built on the completed-visit record instead, which is both a more honest signal and one your techs will not resent. A GPS leash tells a tech you are watching their movements; a completed-visit record tells them to do the work and log it, which is the actual job. The record also holds up better in a dispute: a customer does not care that a dot was on their street, they care that free chlorine read 2.4 ppm and the filter got cleaned. Prove the work, not the whereabouts.
Spotting a skipped stop before the customer calls
Catch a skipped stop by reviewing the day's completed records at the end of each route day, so you find the gap before the customer does. The review takes a minute: open the day's route, look for any stop without a completed visit, and follow up while the tech can still remember and, if it is early enough, still go back. A stop that is blank at 4pm on its service day is either skipped or unlogged, and both need an answer that same day, not next week when a customer is already annoyed.
Take an owner in Tucson running two techs across 110 pools who cannot ride along with either one. A customer in Oro Valley calls Thursday saying nobody came Tuesday. Instead of guessing, the owner opens Tuesday's route: the stop shows a completed visit at 10:42am with free chlorine and pH logged and a service report on file - proof the tech was there, no GPS needed. On a different Tuesday the same stop might be the one with no completed record, and that blank is exactly the stop to ask the tech about. Either way the route answers the question in seconds.
Send the customer the proof, not just yourself
The completed record proves the stop to you; a service report proves it to the customer, and sending one after every visit ends most did-you-come disputes before they start. An automatic service report per visit shows the date, the time, the readings, and what was done, and it lands in the customer's inbox within a minute or two of the tech leaving. A customer who gets that report every week rarely calls to confirm you came, because the proof already arrived.
This is the same record working two jobs: internally it is your completion check, and externally it is the customer's receipt. Pairing the report with the invoice is even stronger - the service report the customer gets right before the bill shows exactly what they are paying for, which cuts both the did-you-show-up call and the what-is-this-charge call. The report is not marketing; it is the completed-stop record, formatted for the person paying for it.
What to do about a stop marked done that was not serviced
When a stop is marked complete but you doubt the work happened, you catch it by the thinness of the record, not by an automatic fraud alarm. A visit marked done in 90 seconds with no readings logged, no checklist items, and no photo is a tell - a real stop leaves a real record, and a hollow one stands out against the full ones around it. The system does not flag a false completion for you; you spot it because the evidence is reviewable and a rushed or empty entry looks different from an honest one.
Handle it as coaching backed by the record, not accusation. Show the tech the difference between their thin entries and a complete one, and set the standard that a stop is not done until its readings and checklist are logged at the pool. Most 'marked done but not really' problems are a tech skipping the logging step under time pressure, not skipping the pool, and tightening the logging habit fixes both the proof gap and the underlying rush. Spot-check a few of a new tech's pools in person during their first few weeks, then let the record do the watching once you trust the pattern.
FAQ
Frequently asked questions
How long should I keep records of completed pool service visits?
Keep completed-visit records for at least one to three years, and longer for commercial accounts where the chemical log can be a compliance document. The records cost nothing to store in software and they are what protect you if a customer disputes a visit months later or an incident gets tied to water quality. For residential routes, a year of history is enough to settle almost any did-you-come argument and to show a pattern of consistent service. For hotels, HOAs, and gyms, a health inspector can ask to see chemical logs, so retention there is not optional. Store it in software rather than on paper, because a record you cannot produce on the spot is the same as no record at all, and paper is slow to search and easy to lose.
What if my technician forgets to mark a stop as done?
An unmarked stop looks identical to a skipped one in your end-of-day review, which is actually the point - the blank forces the question either way. When you follow up and the tech says they did service it but forgot to log it, that is your signal to tighten the habit, because a completed stop with no record is not proof of anything. Set the expectation that marking the visit done and logging the readings happens at the pool, before the tech pulls away, not from the truck at the next stop or from memory that night. The forgetting usually comes from time pressure on a packed route, so if it happens often, the route may be too long rather than the tech careless. Either way, you would rather chase a forgotten log than never know a stop was missed.
Can I confirm my techs' completed stops on paper, or do I need software?
Paper works for a handful of pools, but past roughly 20 stops it stops being a reliable way to confirm completion. The problem is not capturing a record on paper - it is reviewing it fast enough to catch a skipped stop the same day, searching it when a customer calls in three weeks, and getting a report to the customer automatically. A paper route sheet sits in a truck; you cannot scan it from home at 4pm or pull up one pool's history in seconds. Most operators past 20 pools move to software specifically so the day's completions are one screen and the customer's report sends itself. Below that count, a disciplined paper checklist plus a quick photo can hold, as long as you actually review it daily.
How do I hold a 1099 or subcontractor technician accountable for completing stops?
Hold a subcontractor to the same completed-record standard you would an employee: the stop is not done, and not payable, until the readings, checklist, and a service report exist for it. Because you cannot direct a 1099 tech's minute-to-minute movements the way you might an employee, the record matters even more - it is the deliverable you are paying for, defined by output rather than hours. Tie payment to completed visits with real records, not to a claimed stop count, and the incentive lines up on its own. Send the customer a service report on every subcontracted visit too, so an account never depends on a sub's word. A subcontractor who consistently turns in thin or missing records is one to replace before a customer does it for you.
Should I still spot-check pools in person if I have completion records?
Yes, spot-check occasionally, especially with a new tech in their first few weeks, because a record proves a visit happened but not that it was done well. Drop by a handful of pools a day or two after they were serviced and look at the water against what the record claims - if the report said free chlorine at 2.5 ppm and the pool is cloudy and green, you have found a problem the record alone would not surface. Once a tech has a few weeks of complete, accurate records that match what you see in the field, you can back off and let the record do most of the watching. Spot-checks are how you calibrate your trust in the record, not a permanent replacement for it. A quarterly pass on your best techs is plenty; a new or subcontracted tech earns more.
Does a completed-visit record help when I sell my pool route?
A clean history of completed visits is one of the most valuable things you can hand a buyer, because it turns your claimed route into something they can verify. A buyer pricing a route wants proof the accounts are real and consistently serviced, and months of timestamped visits with readings and reports are exactly that proof - far more convincing than a spreadsheet of names. Routes with a documented service history tend to command better multiples and closer to full asking price, because the buyer is not guessing at what they are buying. It also makes the handoff cleaner: the new owner inherits each pool's history and can step in without re-learning every account from scratch. The record you keep for daily accountability quietly builds the asset you eventually sell.
