You Don’t Have to Read Every Service Report Anymore
A while back I wrote about how I stopped doing paperwork at 9 PM by automating the admin side of my 150-pool route. One comment on that post stuck with me: someone asked, essentially, “what does it actually take to stop reading every tech’s notes just to catch the one pool with a problem?”
That question deserves its own answer, because it’s the piece that changed how I run the business the most.
The habit that was quietly costing me
For years, “checking in on the route” meant scrolling. Report after report, tech after tech, most of them completely fine — normal chlorine, normal pH, nothing to do. But I couldn’t skip any of them, because the one report I skipped was always going to be the one with the problem. So I read all of them, every day, looking for the needle in a stack of non-issues.
That’s not oversight. That’s just noise with a job title.
What changed: the system reads first
The shift wasn’t “get better at scanning reports faster.” It was removing the scanning entirely. Now, the moment a tech submits a reading, the system checks it against target ranges — chlorine, pH, alkalinity, cyanuric acid, filter pressure — before I ever see it. If everything’s fine, I don’t hear about it. If something’s off, I get a message with exactly which pool, which reading, and how far out of range it is.
I went from reading 150 reports a week looking for problems to reading the problems. Some weeks that’s three messages. Some weeks it’s none.
Proactive instead of reactive
The bigger change wasn’t the time saved — it was when I found out. Before, a chemistry issue usually surfaced one of two ways: I caught it scrolling through reports late at night, or the customer called annoyed because their water turned. Both of those are already too late to feel good about.
Now the alert goes out the same day, often within minutes of the tech leaving the property. That’s the difference between calling a customer to say “we already caught this and I’m sending someone back tomorrow” versus a customer calling me to ask why their pool looks green. One of those conversations builds trust. The other one costs you the account.
Where it actually shows up: fewer cancellations
I’ll be honest — I didn’t build this thinking about retention. I built it because I was tired of missing things. But the retention effect turned out to be real. A customer who never has to notice a problem before we do doesn’t have a reason to question the service. The complaints that used to turn into “maybe I should just switch companies” mostly stopped happening, because the problem got handled before it became visible to them.
That’s the actual return here. Not “I saved two hours a week.” It’s “fewer customers ever had a reason to be unhappy in the first place.”
What I’d tell someone starting this
You don’t need a fancy dashboard or a data science degree. You need one thing automated first: whatever currently makes you scroll through reports looking for trouble. For most routes, that’s chemistry. Get that piece catching problems on its own — quietly, in the background, only speaking up when something’s actually wrong — and you’ll feel the difference in your evenings almost immediately.
The goal was never to replace my judgment. I still decide what to do about a low-chlorine reading. The system just makes sure I find out about it the same day it happens, instead of finding out from an unhappy customer three days later.