Key Takeaways
- Drive time between stops, not on-site cleaning, is usually where margin leaks first.
- Accurate minute-by-minute logs expose unprofitable accounts hiding inside healthy-looking routes.
- Mobile clock-in tied to GPS removes the friction that kills paper timesheets.
- Reviewing time data weekly, not quarterly, turns the data into route changes you can actually price against.
- Time tracking only pays off when techs see it as protection, not surveillance.
A pool route looks profitable on paper until you measure what really happens between 8 a.m. and 4 p.m. Brushing, vacuuming, and chemistry rarely run more than twenty minutes per residential stop. Yet the typical Florida or Texas technician somehow burns nine hours covering forty accounts. The gap between cleaning time and clock time is where most independent operators quietly lose their margin, and it is invisible until someone starts measuring.
Tracking technician time is not about catching anyone slacking. It is about giving the owner a true picture of what each stop costs to service, which routes deserve a price increase, and where the schedule itself is wasting fuel and labor. Done well, it turns a vague suspicion that "we are busy but not making money" into a spreadsheet you can act on.
What Time Tracking Actually Measures in a Pool Route
When a pool company talks about "time tracking," the conversation tends to drift toward billable hours, the way a law firm or HVAC shop would think about it. Pool service is different. Most residential accounts are flat-rate monthly billing, so the customer pays the same whether the tech spent fourteen minutes or thirty-four. The question is not what to bill. The question is what each stop is actually costing the business in labor and windshield time.
A useful tracking setup captures three buckets per stop. First, on-site service time from the moment the tech opens the gate to the moment the equipment shuts down. Second, drive time from the previous stop. Third, anything that does not fit either category: a customer conversation, an equipment diagnosis, a trip back to the truck for a forgotten brush. The third bucket is where surprises live. A single homeowner who wants ten minutes of pump-room small talk every week can eat eight hours of payroll a year by themselves.
Superior Pool Routes has worked with operators since 2004, and the pattern is consistent across markets. Owners almost always overestimate on-site service time and underestimate drive time. When they finally see the real numbers, the conversation shifts from "we need more accounts" to "we need to re-sequence the route we already have."
The Financial Impact of Knowing Your Real Cost Per Stop
Once you know the true minutes-per-stop on each route, you can do basic math that was previously guesswork. Take a technician's fully-loaded cost, including wages, payroll taxes, workers' comp, vehicle, fuel, and chemicals, and divide it across the minutes worked. Suddenly each stop has a real dollar cost attached to it, and the monthly service fee either covers that cost with a healthy margin or it does not.
This is where unprofitable accounts get exposed. Most routes contain a handful of stops that are not actually making money. They might be older accounts at legacy pricing, oversized pools paying residential rates, or screened enclosures that double brushing time because of leaf load. Without time data, these accounts blend into the average and feel fine. With time data, they show up as outliers. The owner can then raise the price, drop the stop, or restructure the visit, instead of trying to fix the route by chasing more accounts.
Accurate logs also protect the business when a customer disputes service. A homeowner who claims their pool was skipped is a different conversation when the tech can show a fifteen-minute on-site window with GPS coordinates on the property. That single feature has saved more accounts than any reactive credit ever has.
Where the Real Leaks Hide: Drive Time and Route Sequencing
The biggest discovery operators make when they start tracking time is almost never about cleaning speed. It is about the road. A route designed five years ago around twenty accounts often gets stretched to thirty-five accounts over time, with new stops added based on geography that looked close on a map but, in practice, adds a left turn across four lanes of traffic at 11 a.m.
Time tracking turns drive time from an assumption into a number. When the numbers come in, the picture is usually ugly. Routes that should run ninety minutes of cumulative drive often run two and a half hours. The fix is rarely dramatic. It is usually a re-sequence, a swap of two accounts between routes, or moving a single inconveniently located stop to a different day. But you cannot make those calls without seeing where the time is going.
In markets like coastal Florida and the Dallas-Fort Worth corridor, where pool density varies block by block, the difference between a well-sequenced route and a sloppy one can be twelve to fifteen accounts of capacity per technician per week. That is not a productivity tweak. That is a route's worth of revenue hiding inside the schedule the company already runs.
For owners considering expansion, this matters before the first new account is added. Operators looking at Pool Routes for Sale in Florida or Texas often assume they need to acquire new accounts to grow. Tracking time on the existing book usually reveals that there is already room to add stops without hiring, simply by tightening sequence and trimming dead time.
The Accountability Question Without the Surveillance Vibe
Time tracking has an image problem in the trades. Technicians hear "we are going to track your time" and assume they are about to be policed. That reaction is reasonable. Plenty of companies have rolled out tracking systems exactly that way and damaged their best relationships in the process. Top technicians do not stay at companies that treat them like suspects.
The framing that works is straightforward. The data is for the route, not the tech. The goal is to see which stops are taking longer than they should so the company can either fix the conditions or charge more. When a tech consistently spends forty-five minutes on a pool that the rest of the team handles in twenty-five, the right question is not "why is this tech slow" but "what is going on at this pool that the others are not seeing." Usually it is a chemistry issue, a leaf problem, or an equipment quirk that warrants a service note for the whole team.
Used this way, time tracking actually defends the technician. It documents that the pool with the persistent algae problem really does take longer, which justifies a price conversation with the homeowner instead of pressure on the tech to work faster. The best operators present it that way from day one, and adoption stops being a fight.
Mobile Apps, GPS, and the Death of the Paper Timesheet
Paper timesheets do not work in pool service. They get filled out in the truck at the end of the day from memory, they round everything to the quarter hour, and the data they produce is fiction. The same applies to handwritten route sheets where the tech checks a box when the stop is done. Useful for confirming service happened. Useless for understanding time.
Modern field service apps solve this with a simple flow. The tech taps "start" when arriving at a stop, taps "complete" when leaving, and the app stamps both events with GPS coordinates and timestamps. Drive time between stops is calculated automatically. Notes, chemistry readings, and photos attach to the same record. By the time the tech finishes the route, the day's data is already in the system without anyone filling out a form.
The setup that produces the cleanest data usually has three pieces. A mobile app the technicians actually like using, because anything they resent will get gamed. GPS verification on each stop so the timestamps are trustworthy. And a back-office view that rolls the data up to the route level instead of just the daily total. Owners who only see "Pedro worked 8.2 hours today" are still flying blind. Owners who see "stop fourteen on Route 3 averaged twenty-eight minutes over the last four weeks against a target of eighteen" can actually do something.
Integration with billing and payroll is the second wave of value. When time data flows directly into the same system handling invoicing and payroll, the office stops re-keying numbers, payroll errors drop, and the weekly close gets faster. None of that is revolutionary in 2026, but plenty of pool companies still run on a patchwork of spreadsheets and texts, and they feel the friction every Friday.
Turning Data Into Weekly Decisions
Collecting the data is the easy half. Most companies that fail with time tracking fail at the second half: actually looking at it. The data piles up in the system, no one reviews it, and within three months the technicians notice that the tracking is theater. At that point, accuracy collapses.
The fix is a short, scheduled review. Once a week, ideally on the same day, the owner or operations lead pulls up the previous week's data and looks for three things. Outlier stops where on-site time was unusually high or low. Routes where total time crept up without a corresponding revenue increase. And any stop where the GPS record shows the tech arrived but the time on site looks impossibly short, which usually means a real issue worth a conversation rather than a discipline problem.
Twenty minutes of review per week is enough to keep the system honest and to surface the route changes worth making. Quarterly reviews are too slow. By the time a problem stop shows up in a quarterly report, it has already burned a quarter of payroll. Weekly cadence catches it early.
The other discipline is acting on what the data shows. If the same stop has run twelve minutes long for six weeks straight, the company has to do something: raise the price, change the service, drop the account, or accept the cost and stop complaining about it. Data that nobody acts on becomes background noise, and the techs notice.
Seasonality, Forecasting, and Hiring
Pool service is seasonal in every market, even the ones that pretend not to be. Florida and Texas both have a clear summer surge, with longer service times due to algae pressure, heavy bather load, and storm debris. Without time data, owners hire based on gut feeling and either run thin in July or carry too much labor into October. With time data, the previous year's records show exactly how much extra time the average stop took in each summer week, and hiring can be planned against the actual curve.
The same data informs the question of when to add a route. The rule of thumb of "we need a new truck at X accounts" is not wrong, but it is rough. A route of thirty-eight accounts in a tight neighborhood and a route of thirty-eight accounts spread across a county are not the same business. Time data tells the owner which one is at capacity now and which one still has headroom.
Forecasting also gets cleaner. When time-per-stop and drive-time-per-mile are real numbers in a spreadsheet rather than estimates, you can model what a new account in a specific zip code will actually cost to service before you take it on. That single capability changes how an operator prices and which accounts they accept.
What to Implement First
Most companies do not need a complex rollout. The minimum viable setup is a field service app with mobile clock-in, GPS verification on each stop, and a basic report that shows time-per-stop and drive-time-per-route. Anything beyond that is optimization that can wait.
The order of operations that tends to work is straightforward. Roll out the app to one route first, with the strongest tech, and treat the first two weeks as calibration rather than measurement. Use that period to set realistic targets for on-site time on the residential and commercial stops on that route. Then extend to the rest of the team, with the targets already set so nobody feels like they are being scored against a moving line. Schedule the weekly review from day one and protect it on the calendar.
Common mistakes to avoid include rolling out company-wide on the same day, which guarantees that any app issue becomes a crisis. Tying compensation to the time data in the first ninety days, which destroys trust before the data is even reliable. And building elaborate dashboards before anyone has used the basic reports, which wastes the consultant fee and produces something nobody opens.
The Bottom Line on Time and Margin
Pool service is a margin business. The headline revenue numbers look healthy because the per-account fees add up, but the cost structure is sensitive to small inefficiencies that compound across hundreds of stops a week. A route that runs twenty minutes long per day costs the company more than two hours of labor a week, more than a hundred hours a year, on top of fuel and vehicle wear. That is real money for an operation running on standard industry margins.
Tracking technician time is the most direct way to surface those losses and act on them. It is not glamorous, it does not appear in marketing pitches the way new equipment or fancy software does, and it requires actual discipline to review and use. But operators who do it consistently end up with cleaner routes, fairer pricing, and a workforce that trusts the system because the system protects their stops too.
For pool service businesses thinking about growth, the order matters. Tighten the existing book first using time data, then add accounts. The reverse order, which is the default for most operators, is how companies double their revenue and somehow earn less money than before. Look at the time first. The rest follows.