"Nobody came this week" is the most expensive sentence in pool service. Usually somebody did come. The customer was at work, the water looked the same as last week, and the leaves blew back in by evening. Without proof, the office has two options: argue or credit the visit. Over a season, those credits add up, and the customers who doubted you once tend to doubt you again. This post covers what a provable visit looks like, how to collect proof without slowing techs down, and how to use it so most disputes never start.
What counts as proof
A provable visit has four parts. A time, showing when the tech was there. A location, showing the tech was actually at the address. The work record, meaning the readings and chemicals added. And a photo, showing the pool at the end of the visit. Any one of these can be questioned. All four together are hard to argue with.
The crew app records when the stop is marked done, the crew phone's GPS location during the day, the chemical readings and products added, and any photos the tech takes. None of that requires the tech to do anything extra beyond what a good visit already includes.
Photos that actually help
Not all photos are equal. A blurry close-up of water proves nothing. The photo that ends disputes shows the whole pool from a recognizable angle, with something identifying in the frame like the house, a distinctive fence or the equipment pad. Take it from the same spot every week so the customer and the office can compare visits.
Add photos for anything unusual: a broken skimmer lid, a tree limb in the pool, an equipment issue, a gate left open by a landscaper. Those photos protect you when something goes wrong between visits. A pool full of leaves the morning after a storm looks very different when you can show it was clean at 2pm the day before.
Skip with a reason, every time
Some visits cannot be completed. The gate is locked, the dog is out, the pool is being resurfaced, the customer's party is in progress. When a tech cannot service a pool, he should mark the stop skipped with a reason and, if possible, a photo of the locked gate.
The customer gets a skipped alert, so they hear about it from you, the same day, with a reason. That changes the conversation completely. Instead of "you didn't come," it becomes "oh, my gardener locked the gate, can you come back?" Your service agreement should say whether a skip caused by the customer is billed.
Let the customer see it without asking
The best dispute is one that never starts. After each completed stop, the customer can get an alert with the tech's notes and photos. Over time, they can see their full service history in the customer app. A customer who gets a photo every Tuesday afternoon rarely calls on Wednesday to ask if anyone came.
Some owners worry that sending photos invites nitpicking. In practice, it usually does the opposite. Customers who see consistent work feel like they are getting what they pay for, and they are less tempted when a competitor offers a lower price. Keep the notes short and friendly. The chemical log post covers what to say about readings.
Handling the dispute that still comes
Some disputes come anyway. When they do, answer with the record, calmly. "Our tech, Marcus, was at your pool Tuesday at 1:42pm. Here is the photo he took when he finished, and the readings he logged." Most customers accept that right away, and often apologize.
If the record shows a problem, own it. If a visit was missed, or a photo shows the work was rushed, credit it and fix the cause. Proof works in both directions, and owners who use it honestly earn more trust than those who only pull it out to win arguments. Look at disputes over a season: if one tech's stops draw most of them, that is a training conversation.
Keep your tone professional even when the customer is not. Send the record, explain what it shows, and offer to look at anything they are still concerned about. A customer who was wrong and treated politely often becomes loyal. One who was wrong and made to feel foolish usually leaves, even if they stop disputing the bill.
Teach techs to document without slowing down
Techs push back on documentation when it feels like busywork. Show them why it matters to them. When a customer complains, a good photo and log is what protects the tech, not just the company. Tell the story of the last dispute you settled because the photo was there, or lost because it was not.
Then make it fast. One photo from the same spot at the end of every visit, taken as the last step before leaving, adds seconds. Readings and chemicals added are entered as the tech tests and doses, not afterward. Notes are only for things that matter. For the first few weeks, check every tech's stops daily and give quick feedback. Once the habit is set, a weekly sample review is enough. A tech who documents well should hear it, because the habit spreads faster through praise than through reminders.
Use proof to manage, not just to defend
The same records that settle disputes tell you how your routes are running. Completion times show which techs finish too early to have done the full service. Photos show quality across the route. Skip reasons show which customers have recurring access problems that need a fix, such as a gate code on file or a scheduled day change.
Review a sample of each tech's stops every week. Look at photos, readings and times together. Praise the techs whose work is consistent, and have direct conversations when it is not. See how the crew mobile app captures each stop, and how the pool service software overview ties proof of service to billing.
Ready to Run a Tighter Pool Service Operation?
IndustryBossPro gives you everything in this guide — and every other tool your business needs — from $59/month.