How to measure pool tech performance: a weekly scorecard that's fair

Why gut feel gets tech performance wrong

Without numbers, an owner's picture of a tech comes from whichever customer called last and whichever tech they see most. The quiet tech who never misses a filter clean gets no credit, and the friendly one who rushes the last five stops of the day goes unnoticed until the cancellations start.

A weekly scorecard fixes the picture. It also protects good techs: when a customer complains, you can show the record instead of arguing from memory.

Step 1: pick six to eight measures and keep them fixed

Most of these come straight from your route software and your complaint log. Pick the ones you can measure reliably and do not change them week to week, or the trend means nothing:

• Completion: stops completed out of stops scheduled, and how many were skipped or pushed.
• On time: stops done on the scheduled day, by the assigned tech.
• Quality flags per 100 stops: from reviewing photos and readings, such as missing photos, water that does not match the readings, or a missed filter clean.
• Callbacks: return visits where the cause was the original visit, such as a pool that turned within days of a stop that skipped a step.
• Complaints and compliments: logged against the tech who did the stop, not the account manager.
• Chemical use per pool: compared with similar pools on similar routes. Far above can mean overdosing; far below can mean readings logged without the work.
• Cancellations on the route: with the reason the customer gave, where you have it.

Step 2: make the comparison fair

Routes are not equal. A route full of screened pools in new subdivisions is easier than one under oak trees with older equipment. Three rules keep the scorecard fair:

• Use rates, not totals. Flags per 100 stops, not flag counts, so a tech with a bigger route is not punished for doing more.
• Compare a tech with their own trend first. Four weeks getting worse says more than one week below the team.
• Compare routes with similar routes. Put chemical use and callbacks next to routes of the same type, not the company average.

Step 3: review weekly, decide monthly

Look at the scorecard every week, but act on patterns. One bad week after a storm is noise. The same missed step three weeks in a row is a coaching conversation. Show each tech their own card, not a public ranking: most people fix what they can see, and a leaderboard mostly teaches techs to argue about the numbers.

Once a month, look across the team: which issues repeat across several techs (a training gap), and which belong to one person (a coaching gap).

What to leave off the scorecard

• Speed on its own. Rewarding stops per hour rewards rushing. Use time on site only to check that it fits the work logged.
• Numbers the tech cannot influence, like a customer cancelling because they sold the house.
• Single incidents. Handle those the day they happen; the scorecard is for trends.

Who builds the scorecard every week?

The hard part is not the design, it is the hours. Pulling exports, matching complaints to the right tech and reviewing photos for quality flags takes real time every week, and it usually falls to an owner or office manager who is already full.

PoolOps Digital builds these weekly and monthly technician reports for paying clients, from the software they already use (today PoolBrain and Skimmer). The quality flags come from our overnight QA photo review, which is what the free 7-day trial covers.