How to Pay Pool Service Technicians: Hourly, Per Stop or Salary

The first technician you hire changes what your business is. The way you pay them decides what it becomes. Pay per stop and you have built a machine that rewards speed; pay by the hour and you have built one that rewards showing up; put them on salary and you have taken the variability onto your own balance sheet. None of the three is wrong. But they are not interchangeable, and the choice is much harder to reverse than it looks, because changing how somebody is paid feels to them like a pay cut even when the number is identical.

This is the owner's side of that decision: what each structure actually rewards, the arithmetic that catches people out, and how to work out your own number from your own route rather than from what somebody on a forum pays.

The three structures, and what each one rewards

Start by being honest that a pay structure is an incentive system whether you intended one or not. Technicians are not gaming you; they are responding rationally to how the money works. So the question is not which structure is fairest in the abstract. It is which behaviour you can afford to encourage, given that you cannot watch thirteen stops a day.

The row most owners skip is the second one. Every pay model punishes something, and you should know what before you pick it rather than discovering it in a customer complaint in July.

Per stop: what it buys, and what it costs

Per-stop pay is popular because it aligns the technician's interest with route throughput and makes labour cost per pool a fixed, knowable number. For an owner trying to work out whether an account is profitable, that is genuinely valuable. It also tends to be popular with strong technicians, who correctly work out that they can earn more than the hourly rate you were going to offer them.

The cost is specific and predictable: it is paid in the work that nobody checks. Brushing the waterline properly takes a few minutes and makes no visible difference today. Emptying the pump basket rather than glancing at it takes thirty seconds. Testing properly rather than eyeballing the water takes a minute. A technician paid to finish stops will, over months and without any dishonest intent, compress exactly these. The pools that suffer first are the hard ones — heavy tree cover, awkward access, the commercial property with the gate code that never works — because those are the stops where the per-stop rate pays worst per hour.

Two adjustments make per-stop pay considerably more defensible, and most operators who run it well use both. Rate the hard pools differently rather than paying one flat figure per stop — if a pool takes forty minutes, pay it like a forty-minute pool. And keep a quality check that is independent of the technician's own report, whether that is photos at the stop or a periodic ride-along, because the model's weakness is specifically the things the office cannot see.

The minimum-wage arithmetic nobody does until it bites

Piece-rate pay

Paying a fixed amount per unit of work completed — on a pool route, per stop — rather than per hour. Piece-rate is a lawful way to calculate pay in most settings, but it does not replace the hourly wage and overtime floors; it has to be converted back to an hourly equivalent to check compliance.

This is the part that turns a pay model into a liability. Paying per stop does not mean you have stopped owing an hourly minimum. For a non-exempt employee you generally have to be able to show that total pay divided by hours actually worked clears the applicable minimum wage, and that overtime was paid for hours beyond the weekly threshold — usually calculated from an effective hourly rate derived from the piece-rate earnings, which means overtime on piece-rate work is not simply the piece rate again.

The week that catches people is the bad week, not the average one. A technician on a good route in June comfortably clears any floor. The same technician in a rainy week with cancellations, or on a day where two pools turned into repairs, can fall below it — and compliance is tested week by week, not annually. Hours worked also include more than time at the pool: travel between stops during the day, loading at the yard, and time spent at the supply house generally count, and a technician's day is usually longer than the sum of their stop times.

The practical consequence is that if you run per-stop pay you need hours recorded anyway — which surprises operators who chose it partly to avoid timekeeping. You cannot demonstrate compliance without them. Recording start, finish and the stops completed as they happen, rather than reconstructing the week on Friday, is the only version of this that holds up, and it is one of the arguments for logging the work at the stop on a phone rather than on a clipboard.

Hourly, and the drive-time problem

Hourly is the simplest to administer, the easiest to explain, and the least likely to go wrong legally. Its real weakness is that it transfers every inefficiency in your route onto your payroll. A technician paid hourly has no reason to care that stops seven and eight are nineteen minutes apart, and no reason to object when a badly built route adds forty minutes of driving to a day.

That is worth naming precisely, because the usual conclusion drawn from it is wrong. The problem is not that hourly pay makes technicians lazy. It is that hourly pay stops hiding the cost of bad routing, and a lot of per-stop pay is really a way of charging the technician for route design the owner has not done. If drive time is your objection to hourly pay, the fix is the route, not the pay model — which is its own discipline, covered in the guide on planning and reorganising a route.

Hourly also suits a specific and common situation better than anything else: the route that is still being built. When you do not yet know how long your stops take, how dense the territory is, or whether a new technician is any good, a per-stop rate is a guess you will have to renegotiate. An hourly rate for the first season, with the explicit understanding that you will revisit it once there is data, is both honest and easier to move away from than a per-stop rate you set too high.

Salary, and when a route is predictable enough for it

Salary works when the work is genuinely steady and you want somebody to take ownership of a route rather than a list of stops. It is the right answer for a lead technician who also handles customer problems, trains the new hire and makes judgment calls you would otherwise make — work that is impossible to pay per stop because none of it is a stop.

What breaks salary is seasonality. In a market with a real off-season, a salary carries the quiet winter at full cost, and the temptation is then to set it low enough to survive February, which makes it uncompetitive in June. Operators who make salary work usually either have a year-round climate, or pair a modest salary with seasonal bonus or overtime so the summer is where the earnings are.

Note also that calling someone salaried does not by itself make them exempt from overtime. Exemption depends on the duties performed and on meeting a salary threshold, and a route technician performing manual service work is unlikely to qualify however they are paid. A salaried non-exempt technician still accrues overtime, which is the detail that turns a tidy payroll line into a surprise.

Bonuses that do not wreck route quality

Most owners end up at some hybrid, and the usual shape is a base — hourly or salary — plus something variable. The variable part is where damage gets done, because a bonus is a per-stop incentive wearing different clothes, and it will distort behaviour in proportion to its size.

The test for any bonus is simple: what would somebody do to maximise this if they were slightly cynical and nobody was watching? A bonus on stops completed rewards rushing. A bonus on revenue per route rewards selling repairs the pool may not need. A bonus purely on speed rewards exactly the invisible corner-cutting that per-stop pay already encourages.

Working out your own number

The figure you need is not a market rate from a salary website. It is what your route can actually carry, which you derive from your own revenue per stop and the time your stops really take. Published salary ranges are useful only as a sanity check at the end.

1. 1

   Measure how long stops actually take

   Not your estimate — the real figure, including the drive, for two or three weeks. Separate the easy pools from the hard ones; you will find the spread is wider than you think, and that spread is the whole argument for differential rates.

2. 2

   Work out revenue per technician-hour

   Monthly revenue from the stops on that route, divided by the hours it genuinely takes to service them. This is the ceiling everything else fits under, and the number most owners have never calculated.

3. 3

   Subtract the costs that are not labour

   Chemicals, fuel, vehicle, insurance, and the share of overhead that route carries. What remains is what is available for labour plus profit — and if that number is uncomfortable, the problem is your pricing, not your pay rate.

4. 4

   Add the true cost of employing somebody

   Payroll taxes, workers' compensation, any benefits, and the hours that are paid but not billable: loading, the supply house, training, the wet week. A wage is not the cost of a technician.

5. 5

   Convert to whichever structure you have chosen

   If per stop, divide by stops and then check the hourly equivalent on your worst plausible week, not your best. If hourly, check the implied labour cost per pool still leaves the margin you assumed when you priced the account.

6. 6

   Sanity-check against the market last, not first

   Now look at what technicians in your area are actually paid. If your derived number is far below it, you have a pricing problem to fix before you have a hiring problem to solve.

If step three or step six lands badly, that is useful information rather than a dead end: it means the route cannot currently support the hire at the rates you charge. Both the arithmetic of whether a route carries a second person and the question of what to charge in the first place are worth settling before the job advert goes out — what decides whether a pool route is profitable and the pricing guide both bear on it.

Write it down before the first payday

Almost every pay dispute in this trade is about the calculation rather than the amount. The technician thought cancellations still counted. Nobody said whether a repair visit was a stop. The rainy Tuesday was never discussed. All of that is cheap to settle in advance and expensive to argue about afterwards, with somebody you need to keep.

Put the answers in the offer, not just in a conversation, and name a review date. A pay structure set when you had sixty pools will be wrong at a hundred and forty, and a scheduled review is far easier than an unscheduled renegotiation prompted by a technician who has been quietly unhappy since April.

The structure question is genuinely downstream of the hiring question, and if you have not yet made the first hire, the sequencing matters: when a route can carry a second person, what to look for, and how to run the first ninety days is the piece to read before this one.