📌 Key Takeaway: Track stops-per-hour, drive-time percentage, and revenue-per-tech-hour across every route to spot weak performers before they erode margin and to scale crews with confidence.
Start With Three Numbers That Actually Matter
Most pool service owners drown in data they never use. Cut the noise and focus on three numbers per route, per week. First, stops per labor hour, which is total accounts serviced divided by clock-in to clock-out time including drive. A solo tech in a tight suburban zone should hit 2.8 to 3.5 stops per hour on weekly maintenance; rural routes often fall to 1.8 or 2.0. Second, drive-time percentage, calculated as minutes between stops divided by total shift minutes. Healthy routes sit under 25 percent. Anything north of 35 percent means your geography is fighting you. Third, revenue per tech hour, which is monthly route billing divided by the hours that route consumes. Aim for $75 to $110 depending on your market. If a route falls below $60, it is subsidizing your other work and you do not know it.
Write these three numbers on a whiteboard every Monday morning for every route. Patterns surface within four weeks. You will spot the tech whose Tuesday stops drag the whole month, or the zip code where a $140 monthly account is eating ninety minutes of drive time round-trip.
Capture The Data Without Burning Your Techs Out
The fastest way to kill a measurement program is to make techs fill out spreadsheets. Use what they already touch. Their phones run GPS, so route management apps like Skimmer, Pool Service Software, or even basic Google Timeline can pull arrival and departure timestamps automatically. Pair that with a one-tap status button per stop, completed, skipped, or callback, and you have ninety percent of what you need without adding a single minute of paperwork.
For chemical and labor inputs, weigh tablet buckets at the start of the week and at the end. Divide by stops serviced to get average chlorine cost per pool, per route. A route running 30 percent higher chemical cost than its peers usually has either a tech overdosing, a cluster of green pools, or accounts that are underpriced for their condition. Each of those problems has a different fix, but you will only see them if you measure inputs route by route, not company-wide.
If you operate three or more trucks, a simple weekly export from your scheduling software into a Google Sheet, sorted by route, is enough. Do not buy business intelligence tools until you have outgrown a spreadsheet. Most owners never do.
Benchmark Routes Against Each Other, Not Against Theory
Industry averages are useful for sanity checks but useless for management decisions. Your own routes are the benchmark. Rank them weekly on the three core metrics, then ask why the top route is the top route. Is it density? Tech experience? Account mix, meaning more residential weekly versus commercial bi-weekly? Once you understand what makes your best route work, you can engineer that pattern into the weaker ones.
This is also where acquisition strategy gets interesting. If your top-performing route generates $95 per tech hour with 28 accounts in a four-mile radius, you know exactly what kind of expansion to pursue. Filling in geographic gaps with established accounts, rather than chasing one-off leads twenty miles out, is how you raise the average. Many owners build that density faster by purchasing existing books in their target zip codes through pool routes for sale listings, which lets you add 20 to 50 accounts in a single transaction and immediately tighten drive times.
Run A Monthly Route Audit With Your Techs
Numbers tell you what is happening. Techs tell you why. Schedule a thirty-minute monthly sit-down with each tech to review their route data together. Bring the stops per hour trend, the drive-time percentage, and any callback or complaint logs. Then shut up and listen. Techs know which accounts have broken gates, which HOAs require ten minutes of badge-in time, which pools always have algae from a neighbor's runoff. None of that lives in your software.
Document what you hear in a simple route notes column tied to each account. Over six months you build a map of friction that lets you re-price, re-route, or release accounts with confidence. I have watched owners cut twelve hours per week off a single route just by acting on tech feedback that had been sitting in their heads for years.
Tie a small monthly bonus to hitting target stops per hour and zero callbacks. Not a huge number, $75 to $150 per tech, but enough to make the metrics matter to the people generating them.
Use Productivity Data To Price, Hire, And Expand
Once you have three months of clean route metrics, the data starts driving every other business decision. Pricing new accounts becomes mechanical, take the prospect's location, estimate added drive time, multiply by your target revenue per hour, and quote a price that protects margin. No more eyeballing.
Hiring becomes clearer too. If your best route runs at 3.2 stops per hour and you are about to add a fourth truck, you know that truck needs to hit roughly 100 accounts before it pays for itself at your current revenue per hour. That tells you whether to hire now or wait until you have built the account base. Many owners shortcut this build by acquiring an existing route in the target service area, which front-loads the account count and lets the new hire run a productive book from day one rather than spending six months ramping up. Browsing current pool routes for sale inventory before posting a job ad is often the smarter sequence.
Productivity measurement is not a reporting exercise. It is the operating system that connects what your techs do every day to whether your business compounds or stalls. Three numbers, captured weekly, reviewed monthly, acted on quarterly. That is the whole system.