All posts

Time Tracking for Pool Service Techs: Routes, Drive Time, and Weekly Payroll (2026 Guide)

8 min read

Time Tracking for Pool Service Techs: Routes, Drive Time, and Weekly Payroll (2026 Guide)

The short answer: Track a pool tech the way the work happens, stop by stop. That means a geofenced punch-in at each pool, paid drive time between stops, per-stop or hourly pay that still calculates overtime correctly, and a weekly approval before payroll. Punch does all of it at one flat price per workspace, so adding a tech for peak season does not add a per-user fee.

A pool tech does not work a shift. They work a route. Twenty backyards on a Wednesday, a green pool that eats an extra hour at stop nine, a pump that needs a return trip, and the driving between every one of them. When all of that lands in payroll as "7 to 4," you cannot tell which pools run long, whether the drive time got paid, or what happened at a specific address on a specific day when a customer disputes a visit.

Route work is where small operators lose money quietly. The hours are real, the location is scattered, and the only record is whatever the tech remembers on Friday.


Where the Route Timesheet Breaks

Four things go wrong, usually in this order.

  1. One shift instead of twenty stops. The tech punches in at the shop and out at the end of the day. Every pool shares one block of hours, so nothing can be costed and nothing can be proved.
  2. Windshield time disappears. Driving between pools during the workday is paid work. Rebuilt from memory at week's end, it gets rounded down or skipped.
  3. No location proof. A service log says the tech was at the pool. It cannot show the truck was in the driveway.
  4. Overtime hides in the mix. Peak season stacks long days. A tech paid per stop can cross 40 hours without anyone noticing until payroll.

The fix is not more discipline. It is a punch that carries the stop, the time, and the location by itself.


Geofenced Punch-In at Every Pool

A geofence is a radius you draw around an address. When a tech punches in, the app checks the phone's location against that radius before the punch counts. Each recurring pool becomes a job site with its own address, and every punch there is anchored to it.

Geofencing applies to punch-in only. Techs punch out and start and end lunch from anywhere, so nobody is stuck on the clock because GPS failed behind a fence. You can read the longer explanation in our geofence time tracking guide.

Punch does not use facial recognition and does not ask for a photo at punch. Your techs are working in customers' backyards all day. A job-site geofence verifies the stop without pointing a camera at your crew, and it is stronger proof because it is tied to an address.

Job sites are a setup feature in Punch, not a billing unit. Add every pool you service. A route of 200 addresses costs the same as a route of three.


Drive Time Between Pools Is Paid Work

This is the most expensive thing small operators get wrong. Under the Fair Labor Standards Act, travel that is part of the day's work counts as hours worked. The Department of Labor's rule at 29 CFR 785.38 says time spent traveling from job site to job site during the workday must be counted. Ordinary home-to-work commuting is treated differently under 29 CFR 785.35 and generally is not compensable.

On a twenty-stop route, the middle of the day is mostly driving. Punch supports paid travel time as its own category, at a travel rate you set, separate from service time. Those hours still count toward the weekly overtime threshold. Our travel time guide covers the edge cases, including trips that run past the last stop.


Paying by the Stop Still Owes Overtime

Many pool companies pay per stop. A set amount per weekly service, more for a green-to-clean recovery, less for a short chemical check. Punch supports this with per-location pay. Set a default per-visit rate for a tech, and every punch-in and punch-out at a job site counts as one visit at that rate. Where one account pays differently, add a site-level override.

Paying per stop does not remove the overtime obligation. A non-exempt tech who works 47 hours still earns an overtime premium, calculated on the regular rate: total pay for the week divided by total hours worked. That is the same rule behind piece-rate pay, and the mechanics are in our regular rate of pay guide.

Punch calculates overtime automatically against the rules you pick. It ships presets for more than 50 countries, plus United States federal and state variations such as California's daily overtime. The breakdown is on the screen before payroll runs, not in a complaint afterward.


Backyards, Gate Codes, and Dead Zones

Pool routes run through gated communities, rural lots, and yards behind a house where signal drops. If an app needs a live connection for every action, the tech cannot punch out when the stop is done, and the hours get rebuilt later.

With Punch, punch-out, lunch start, and lunch end queue on the phone when there is no network and sync when it reconnects. The recorded time is the moment the tech tapped the button. Punch-in needs a connection so the geofence can verify the address. More detail is in our guide to tracking hours without cell service.

Summer is also the season your techs work in the hardest heat. Several states now require paid cool-down breaks for outdoor crews, and those breaks need to show up somewhere provable. Our heat rules guide explains what the timesheet has to show.


The Weekly Review Before Payroll

Raw punches are not payroll. A manager or owner should see the week before it becomes money.

  1. Techs punch in and out through the week, pool by pool.
  2. Shifts land as pending in the approvals queue.
  3. A manager reviews each one: the address, the hours, the travel, the lunch.
  4. The manager approves or rejects. A rejection carries a reason the tech sees in the app.
  5. Approved shifts are marked paid when payroll runs.

Punch gives managers a full approvals queue with bulk approve and reject for a whole pay period, plus single-shift detail when a route looks off. Owners choose weekly or bi-weekly pay periods. The full workflow is in our timesheet approval guide.

When the week is approved, export it. Punch connects to QuickBooks Online and pushes an approved pay period to your books, with a Square integration and a QuickBooks or Excel CSV for everyone else. Because every row carries the pool address, the export also works as a labor record per account. See how the QuickBooks export works, and if you want to know what each route really costs you, read labor cost per job.


What It Costs

Most time tracking apps bill per employee per month, so every seasonal tech you add in April becomes another line item you keep paying in December. Punch is priced flat per workspace. Owners are always free, and every plan includes every feature, so geofencing, travel pay, per-visit pay, overtime rules, and integrations are never held back for a higher tier. We compare the models in per-employee versus flat pricing.


Frequently Asked Questions

What is the best time tracking app for a pool service company?

One that treats the route as a series of stops. Look for geofenced punch-in at each pool, paid drive time, per-visit pay alongside hourly, offline punching, a manager approval step, and automatic overtime.

Do I have to pay pool techs for drive time between stops?

Generally yes. Travel from job site to job site during the workday is hours worked under federal rules. The ordinary commute to the first stop and home from the last usually is not. Punch records between-stop travel as its own category and counts it toward weekly overtime.

If I pay per stop, do I still owe overtime?

Yes, for a non-exempt tech. Per-stop pay changes how pay is earned, not whether overtime is owed. Punch tracks the hours behind per-stop pay so the overtime math has real numbers.

Does Punch use photos or face scans?

No. Punch verifies a stop with a job-site geofence, never a camera.


Start Tracking Your Route

Setting up Punch for a pool route takes about fifteen minutes.

  1. Create your organization and invite your techs.
  2. Add each pool as a job site with an address and radius.
  3. Set pay per tech: hourly, or per visit with site-level overrides.
  4. Add a travel rate for drive time.
  5. Pick your overtime preset and a weekly or bi-weekly pay period.

The free trial starts at signup. Every plan includes every feature.

Put your route on Punch →

More from the blog