The short answer
When a pool tech calls in sick, the job is to keep that day's stops covered. Reassign them across your remaining techs or take them yourself, tell the affected customers about any timing change, and keep proof of service on every visit. Route software that moves stops between techs in a few taps turns a scramble into a five-minute fix.
This is a business problem, not a backyard one. You run a pool service company, a tech is out for the day, and a full route of customers still expects their pools serviced. The water doesn't pause because someone has the flu, so the question is how you cover that day's stops without dropping accounts or burning your other techs out.
How smoothly this goes comes down to one thing: how easily you can move stops from the sick tech to someone else. Here is how to cover a route when a tech is out, how to reassign stops between technicians, when to push a stop versus skip it, how to keep customers in the loop, and how to make the next sick day a non-event.
At a glance
Key takeaways
- Start from the sick tech's stop list, not the tech: reassign that day's pools across your other techs and yourself based on who's working nearby and who has room.
- Spread the extra stops across two or three people rather than dumping a full extra route on one tech, so no one finishes after dark.
- Push low-risk stops to the next day before you skip any; a pool serviced a day late is fine, a pool skipped for a week turns green.
- Keep at-risk pools on schedule: heavy-use, summer-heat, algae-prone, and commercial pools should hold their slot.
- Tell only the affected customers about a timing change before service day, then let an automatic service summary prove the visit happened.
- Make sure the covering tech can see each pool's gate code, equipment, and quirks, so they aren't walking in blind.
- Keep routes in a shared system and cross-train your techs, so a sick day is a five-minute reshuffle instead of a morning of phone calls.
How do I cover a pool route when a tech is out?
Cover the route by reassigning the sick tech's stops to the people you still have on the road that day: your other techs, and yourself if you carry a route. Start from the day's stop list, not from the tech. Pull up everything that was assigned to the person who called in, then decide where each stop goes based on who is already working nearby and how much room is left in their day.
The math is about capacity, not goodwill. A tech already running a full day can't simply absorb another eighteen pools, so before you pile stops onto someone, look at how full each tech's day already is. Spread the extra stops across two or three people instead of dumping them on one, and the day stays doable. The closer the sick tech's route sits to your other routes, the easier this is, which is one more reason tight, geographic routes pay off when something goes wrong.
How do I reassign stops between technicians?
Reassign stops by moving them onto another tech's route for the day and re-ordering that day so the new stops fall in driving sequence. On paper this means crossing names off one sheet, writing them onto another, and hoping the second tech can read where the new stops fit. In software built to reassign stops between techs, it's drag-and-drop: you move the sick tech's stops onto whoever is covering, the route reorders, and that tech opens an updated day on their phone without a single phone call.
Keep three things in mind as you move stops. First, group by geography, so a covering tech isn't sent across town for one orphaned pool. Second, watch the clock, because a covered route that runs past dark just trades one problem for another. Third, make sure the covering tech can see the pool's details, the gate code, the equipment, the dog in the backyard, so they aren't walking in blind. Good route software carries all of that with the stop, so reassigning a pool hands over the full picture, not just an address.
Push stops to another day before you skip them
Push stops before you skip them. A pool that gets serviced a day late is fine; a pool that gets skipped entirely for a week is how you get a green pool, an angry customer, and a callback. So when one tech being out means there genuinely aren't enough hours to cover every stop, move the lowest-risk pools to the next day rather than dropping them.
Decide what moves by risk, not by convenience. A shaded pool with light use and balanced water last visit can wait a day without trouble. A heavily-used pool in peak summer heat, a pool that was already fighting algae, or a commercial pool under health-department rules should hold its slot, because those are the ones that turn into a real problem if they're missed. Pushing a handful of low-risk stops to tomorrow and keeping the at-risk ones on schedule is almost always better than trying to cram a day-and-a-half of work into one day and rushing every test.
Tell only affected customers, before they notice the change
Tell customers about a timing change before they notice it, and only the ones actually affected. A pool owner rarely cares which tech shows up, but they do notice if their regular Wednesday service slides to Thursday, especially if they leave a gate unlocked or a dog inside on service day. A short heads-up, by text or email, that says "your service is moving to tomorrow this week" prevents the "did anyone come?" call before it happens.
Then let the proof of service do the rest. When the covering tech completes the visit and logs what they tested and dosed, an automatic service summary tells the customer the pool was handled, even though a different name was on the truck. That record is what keeps a reassigned visit from feeling like a dropped one. Most customers never think twice about a one-day shift as long as they can see the work got done and the water is right.
How do I keep one sick day from becoming a crisis?
Take a real example. You run a two-tech shop servicing 180 pools across Gilbert and Chandler, and at 6am on Wednesday one tech texts that he's down with the flu. That's 18 stops with no one assigned. If your routes live in software, you open his day, drag the stops onto the other tech and yourself, and both updated routes are live on phones before the trucks roll. The whole thing takes five minutes. If those routes live on paper or in the sick tech's head, the same morning becomes an hour of phone calls and a real chance some pool gets missed.
The difference isn't luck, it's setup. Keep every route in a system both you and your techs can see and edit, not in one person's notebook. Cross-train so any tech can run any route from the stop details on their phone, which gets easier when you're already managing multiple technicians in one place. And build a little slack into the week so a covered day doesn't push everyone past their limit. Do that, and a sick tech is a five-minute reshuffle instead of a fire drill.
FAQ
Frequently asked questions
Can I reassign a route to another technician for just one day?
Yes, and for a sick day that's usually the right move. You don't need to permanently change who owns a route to cover a single day. Reassign the affected stops to whoever is covering, just for that day, and switch them back when the regular tech returns. The cleanest way is to move the stops onto the covering tech's day so they show up in the right driving order, rather than handing over a separate list to juggle. With route software this is a few seconds of dragging stops, and the covering tech sees the updated day on their phone. The key is that it's temporary and visible: everyone can see who's covering what today, and nothing gets lost when the regular tech comes back tomorrow.
Should I service the pools myself when a tech calls in sick?
If you still carry a route or know the work, covering some stops yourself is often the fastest fix, but spread the load rather than taking all of it. Most small pool service owners are one bad morning away from being back on the truck anyway, so picking up part of a sick tech's route is normal. The smarter play is to split the orphaned stops between yourself and your other working techs by geography, so no single person, including you, ends up with an impossible day. Take the stops that sit closest to where you already need to be. If you're a true solo operator with no one else, your only levers are pushing low-risk stops to tomorrow and keeping the at-risk pools on today's schedule.
Is it okay to skip a pool service visit when I'm short-staffed?
Skipping entirely should be the last resort, behind reassigning and pushing to another day. A single missed week, especially in summer, is enough for chlorine to crash and algae to take hold, which means a green-pool callback that costs you far more time than the visit would have. If a tech being out genuinely leaves you without the hours to cover everything, move the lowest-risk pools to the next day instead of cancelling them. Reserve any true skip for pools that are low-use, were perfectly balanced last visit, and aren't under any service guarantee or health-department requirement. And if you do skip or push a stop, tell that customer proactively. A heads-up about a one-day delay is a non-event; silence that they discover as a green pool is how you lose the account.
How do I tell customers their pool service is running late?
Send a short, proactive message to only the affected customers before their normal service day, by text or email. Keep it simple: their service is moving to a specific day this week, and you'll have it handled. You don't need to explain that a tech is sick or apologize at length. What customers actually want is to not be surprised, especially the ones who unlock a gate or keep a dog in on service day. Reaching out before they notice prevents the "did anyone even come?" call. After the covering tech finishes, an automatic service summary showing what was tested and dosed closes the loop and proves the pool was handled, even with a different tech on the job. Most people don't think twice about a one-day shift when they can see the work got done.
How can I prepare so a sick day doesn't wreck my routes?
Set up three things before you ever need them. First, keep every route in a system both you and your techs can see and edit, not in one tech's head or a paper sheet, so anyone can pick up anyone's stops. Second, cross-train your techs so any of them can run any route from the pool details, gate codes, and equipment notes attached to each stop on their phone. Third, build a little slack into the weekly schedule so a covered day doesn't push a tech past their limit. With those in place, covering a sick tech is a quick reshuffle: open the missing day, spread its stops across whoever's working, and the updated routes are live on phones in minutes. The operators who panic on a sick day are almost always the ones whose routes only existed in the absent person's memory.
Should I hire a backup pool technician for sick days?
For most small operations a dedicated backup tech isn't worth a full-time wage, but having someone you can call helps. The more practical insurance is cross-training and shared routes, so your existing crew can absorb a missing day between them without anyone new. As you grow past two or three techs, a little built-in capacity, routes that run slightly under their ceiling, gives you natural slack to cover absences without scrambling. Some owners keep a part-time or on-call tech for peak season, when a sick day during the summer rush hurts most. The honest answer is that good route setup covers the occasional sick day far more cheaply than a backup hire; reserve the extra body for when your pool count makes a single absence genuinely impossible to absorb.
