How to check a pool tech's work without riding along

Why ride-alongs stop working past a few techs

A ride-along shows you how a tech works with the owner sitting in the truck. That is not the same pool on a Thursday afternoon in August. Once you have more than a couple of techs and somewhere between 50 and 300 accounts, you cannot ride enough routes to see a real picture.

The usual fallback is waiting for complaints. The trouble is timing: by the time a customer calls about a green pool, the missed visit happened a week ago, and the fix now costs a callback, chemicals and maybe the account.

Step 1: decide what every stop has to prove

Write down the photos a completed stop needs, and make them the same every visit so they can be compared week to week:

• The water after service, one wide shot from the same spot each week.
• Skimmer and pump baskets, emptied.
• Filter pressure gauge, so you can see when a clean is due.
• The equipment pad, to catch leaks and anything that changed.
• Anything unusual, with a one-line note.

If your route software can require photos before a stop is closed, turn that on. A standard nobody enforces is a suggestion.

Step 2: log real readings, every visit

Free chlorine and pH at every stop; alkalinity, cyanuric acid (CYA) and, on salt pools, salt on whatever schedule you set. Then learn the patterns that mean a reading was written from memory:

• The same numbers visit after visit on a pool whose bather load and weather keep changing.
• Chlorine "in range" on cloudy or green water. It can happen right after a shock or with metals or a filter problem, but without a note explaining it, one of the two is wrong.
• CYA climbing for weeks. As stabilizer builds up, the same chlorine reading does less work, and the pool turns even though the log looks fine.
• Perfect readings on every pool on a route. Real water is never that tidy.

Step 3: review every completed stop, the same evening

Spot-checks find the problems you happen to look at. Customers find the rest. Go through every stop from the day with one short checklist:

1. Does the water in the after photo match the readings?
2. Are all the required photos there, and are they from this visit?
3. Were the baskets emptied and is filter pressure noted? Is a filter clean due?
4. Was the time on site plausible for the work logged?
5. Is there a note that needs a call to the customer?

Sort what you find by urgency. Green or cloudy water first, because that customer will call tomorrow. Missed steps second. Data problems, like copied readings, third.

Step 4: turn flags into a morning list and a weekly scorecard

The output of the review is a short list on the office manager's desk before the trucks roll: which pool, which tech, what to fix today. A green pool caught at 7 a.m. is a revisit. Caught by the customer, it is a cancellation risk.

Once a week, look per tech instead of per pool: how many flags, which ones repeat, and how many callbacks. Coach on patterns, not single bad days. Done this way, QA protects your good techs too: when a customer says the pool was never serviced, the photos prove it was.

Who actually does the reviewing?

This is where most owners get stuck. Reviewing every stop takes real hours every evening, and it lands on the owner or an office manager who is already full. The options are to do it yourself at night, give it to someone in the office, hire a dedicated reviewer, or hand it off.

Handing it off is what PoolOps Digital does: our team reviews every completed stop overnight, inside the software you already use (today PoolBrain and Skimmer), and sends the prioritized list by 6 a.m. Whichever way you go, the four steps above are the routine that makes it work.