The short answer
A per-visit pool service checklist covers water testing for free chlorine, pH, and total alkalinity, then skimming, brushing, and vacuuming, emptying the skimmer and pump baskets, checking filter pressure and equipment, and writing a dated note on what was done and what to watch. Run the same steps in the same order at every stop.
The point of a checklist isn't to tell an experienced tech how to clean a pool. It's to make sure every pool gets the same service no matter who shows up, so a customer never notices that Tuesday's tech skips the pump basket or forgets to test alkalinity. On a one-person operation that discipline lives in your head. The moment you add a second or third tech, it has to live somewhere everyone can see it.
Below is the standard set of tasks that belongs on a pool service checklist for a routine stop: what to test, what to clean, which baskets and equipment to check, roughly how long it should take, and why the note at the end matters as much as the work.
At a glance
Key takeaways
- Run the same checklist in the same order at every stop so a customer gets identical service no matter which tech shows up.
- Test free chlorine and pH every visit and log the numbers - free chlorine 1-4 ppm, pH 7.4-7.6, alkalinity 80-120 ppm - not "looked fine."
- Skim, brush the walls and waterline, and empty both the skimmer and pump baskets every visit; vacuum when the pool needs it.
- Check filter pressure every stop and backwash or clean the filter when it climbs 8-10 PSI above its clean baseline, not on a fixed schedule.
- End every visit with a specific dated note on what you tested, what you added, and what to watch - that note is what protects you in a dispute.
- Cap a standard residential stop around 20-25 minutes; the checklist keeps a tech from lingering or quietly cutting corners.
- Put the checklist where the whole crew runs it the same way - a route that depends on one person's memory doesn't scale.
The tasks that belong on every stop
A routine pool service visit breaks into five groups of tasks, and a good checklist puts all five in a fixed order so nothing gets skipped when a tech is moving fast. Water quality comes first because everything else is downstream of it, then the physical cleaning, then the baskets and flow, then a quick equipment scan, and finally the note. A typical residential stop that hits all five runs about 20-25 minutes once the route is tight and the tech knows the pool.
The checklist is the same whether a pool sits on a weekly or biweekly route; what changes is how much correcting each visit needs, not which boxes exist. Getting the list identical across techs is the whole game, and it's a lot easier when the same list is built into the route each tech runs every stop on a set route from, instead of a laminated card that half the crew has lost.
| Task group | What the tech does at every visit |
|---|---|
| Water quality | Test free chlorine, pH, and total alkalinity; add chemicals to bring readings into range |
| Cleaning | Skim the surface, brush walls, steps, and waterline, vacuum or confirm the cleaner is working |
| Baskets & flow | Empty the skimmer basket and pump basket, check the water level and refill if low |
| Equipment | Read the filter pressure, look over the pump and heater, confirm the system is circulating |
| Documentation | Log the readings and any chemicals added, write a dated note, flag anything to watch |
Water testing: the readings to log every time
Test at least free chlorine and pH on every single visit, and total alkalinity most visits, because those three move fastest and drive almost every water problem you'll get called about. Free chlorine should sit around 1-4 ppm, pH between 7.4 and 7.6, and total alkalinity in the 80-120 ppm range. A pool that drifts out of those bands is the one that turns cloudy or green between visits and generates the complaint call.
The checklist should say which readings get logged, not just "test the water," so every visit produces the same record. Free chlorine and pH are the every-visit minimum; a fuller panel with calcium hardness and cyanuric acid can run weekly or when something looks off. The exact set of readings to log at each visit is worth standardizing once and holding the whole crew to, because inconsistent testing is where most between-tech quality gaps start. Logging the numbers also means you can prove what the water was doing if a customer disputes a green pool later.
The cleaning tasks that can't be skipped
Skim, brush, and empty the baskets on every visit; vacuum when the pool needs it. Skimming pulls floating debris before it sinks, brushing the walls, steps, and waterline knocks off the algae film that a chlorine reading alone won't catch, and emptying the skimmer and pump baskets keeps water actually moving through the system. A full-bottom vacuum isn't always needed weekly, but a quick pass on visible debris usually is.
The basket step is the one techs skip when they're behind, and it's the one that causes the most trouble. A packed pump basket chokes circulation, which drops the filter's effectiveness and lets chlorine sit unmixed, so the pool you "treated" still goes cloudy by the weekend. Put "empty both baskets" on the checklist as its own line, not folded into cleaning, so it gets checked off deliberately. On a pool under heavy tree cover you may be pulling a full skimmer basket every visit through the fall.
Equipment and filter checks take under a minute
End the physical work with a 30-second equipment scan: read the filter pressure gauge, glance at the pump and heater, and confirm water is circulating and returning to the pool. The single most useful number here is filter pressure. Backwash a sand or DE filter, or clean a cartridge, when the gauge climbs 8-10 PSI above its clean baseline, not on a fixed calendar, because a clogged filter stops doing its job long before the water looks dirty.
The equipment scan is also how you catch problems before the customer does. A pump that's louder than usual, a heater throwing an error, a small leak at a union: these get noted and flagged, not fixed on the spot. Repairs aren't part of a routine service stop, so the checklist's job is to make sure the tech looked and wrote down what they saw. A three-tech shop that notes equipment issues every visit turns a surprise "my heater died" call into a scheduled repair the operator saw coming a week earlier.
The note is part of the checklist, not an afterthought
The last item on every checklist is a specific, dated note: what you tested, what you added, and anything the customer or the next tech needs to know. "Stopped by, everything looked fine" is not a note. "FC 1.2, added 2 lb cal-hypo, brushed heavy algae on north wall, watch it next visit" is. That level of detail is what protects you when a customer claims the pool was neglected, and it's what lets any tech pick up a route cold.
This is where a paper checklist falls down and a per-visit digital record pays off. In PoolBoss, the tech checks off the tasks and logs the readings on the phone at the pool, and those entries become the visit record automatically - so the office can see that every stop was completed and can turn the checklist into a service record the customer receives. The proof that a stop happened is the logged checklist and readings, not a GPS ping; a completed, timestamped record is what actually answers "did my pool get serviced this week."
One checklist, every tech, every stop
The reason to standardize is that a checklist is only worth anything if the whole crew runs it the same way. Take a three-tech shop running about 140 pools across Gilbert and Chandler. The owner wants a customer to get identical service whether their regular tech or a fill-in shows up, so nobody can tell who came. A shared checklist - test, skim, brush, baskets, filter pressure, note - capped around 25 minutes a stop makes that possible, and the office can see the completed checklist for every visit.
Getting there is less about the list and more about where it lives. A checklist built into the route means a new hire runs the exact same steps on day one as your best tech, and you can see at a glance which stops were finished. That consistency is also what lets you add pools without quality slipping, which is the whole point of building the route the checklist runs on deliberately in the first place. A route that depends on one person's memory doesn't scale; a checklist every tech runs the same way does.
FAQ
Frequently asked questions
How often should I backwash the filter?
Backwash when the filter pressure gauge reads about 8-10 PSI above its clean baseline, not on a set weekly schedule. Every filter has a normal pressure right after it's cleaned; as it traps debris, pressure rises and flow drops, and once it's 8-10 PSI over that baseline it's no longer filtering effectively. That's the signal to backwash a sand or DE filter or hose off a cartridge. Backwashing too often just wastes water and, on a sand filter, actually hurts filtration because a slightly dirty bed filters finer than a freshly cleaned one. So the checklist item isn't "backwash" - it's "read the pressure," and the reading tells you whether today is the day. Write the clean baseline down for each pool so any tech knows the trigger point.
Do I need to test the water at every single visit?
Yes - test free chlorine and pH at every visit without exception, because those two move the fastest and drive most water problems. Free chlorine can crash in a day or two in Sunbelt summer heat, and pH drifts constantly, so skipping a test is how a clear pool turns green before the next stop. Total alkalinity is worth testing most visits since it buffers pH. A fuller panel - calcium hardness, cyanuric acid, and salt on a saltwater pool - doesn't need to run every single time; weekly or when a reading looks off is enough for those slower-moving numbers. The rule of thumb: the faster a level changes, the more often you test it. Log every reading you take so the visit produces a consistent record and you can see trends over time rather than guessing.
Should I send the customer the checklist or a service report?
Yes - sending a short per-visit summary is one of the cheapest ways to cut "did you actually come" calls and show the value you deliver. Most residential customers never see the pool get serviced because they're at work, so a report with the date, the readings, what you added, and a note turns invisible work into something they can point to. It also protects you: if a customer later claims the pool was neglected, a string of dated reports with real readings settles it fast. You don't need to send a wall of data - the tested levels, any chemicals added, and one line of notes is plenty. The easiest version is automatic, generated from the checklist the tech already completed at the pool, so it costs the office no extra time per visit.
Is the checklist different for weekly versus biweekly service?
No - the task list is the same; what changes is how much correcting each visit needs. Whether you service a pool weekly or every two weeks, the tech still tests, skims, brushes, empties the baskets, checks the equipment, and writes a note. On a biweekly pool, though, more happens between visits: chlorine has more time to fall, debris has longer to accumulate, and algae has a bigger head start, so expect to dose more heavily and brush harder to recover each time. That's also why biweekly service is a harder sell in peak summer heat, when a pool can go green in the gap. Keep the checklist identical so the record stays consistent, but price and schedule biweekly accounts knowing each visit is doing roughly twice the catch-up work.
How long should a standard pool service stop take?
A routine residential stop that covers the full checklist runs about 20-25 minutes once the route is tight and the tech knows the pool. That includes testing, skimming, brushing, emptying both baskets, a quick equipment scan, and the note. A first visit to an unfamiliar pool, or one that's been neglected, takes longer, and a large commercial pool or one under heavy tree cover will run over. If a tech is consistently finishing standard stops in under 10 minutes, that's usually a sign steps are getting skipped, not that they're fast. Use the time as a sanity check, not a stopwatch: the goal is every checklist item done, and 20-25 minutes is roughly what that takes on a typical backyard pool in good shape.
What should I do if I find a problem outside the checklist, like a broken pump?
Note it, flag it to the office, and follow up separately - a repair is not part of a routine service stop. The checklist's job is to make sure the tech looked at the equipment and wrote down what they saw, so an equipment issue gets caught early instead of becoming an emergency call. When you spot a loud pump, a heater error, or a leak, record it in the visit note with enough detail that the operator can decide whether it needs a scheduled repair visit or a call to the customer. Don't try to squeeze a repair into a route stop; it blows up the day's schedule and usually needs parts you don't have on the truck. Catching problems on the routine visit and handling them as their own job is exactly how a good checklist earns its place.
