A pool chemical log is the most boring document in the business until the day you need it. A customer's child gets red eyes after a swim, a plaster finish starts etching, or a new tech insists the pool was fine when he left. On that day, either you have a record of what was tested and added at every visit, or you have a guess. This post covers what to write down at each stop, how to keep techs consistent about it, and how the log turns from a chore into something that saves you money and arguments.
The readings that belong on every visit
At minimum, test and record free chlorine and pH every visit. Those two numbers change week to week and drive most of your chemical decisions. Total alkalinity should be recorded at least every visit where you adjust pH, because it controls how stubborn the pH is. Cyanuric acid (stabilizer) and calcium hardness move slowly, so many companies test them monthly, but they still belong in the log when tested. Salt pools add a salt reading, and some companies record water temperature and filter pressure too.
Commonly cited targets are free chlorine around 1 to 3 ppm (higher in stabilized outdoor pools), pH around 7.4 to 7.6, and total alkalinity around 80 to 120 ppm. Your local health code, the surface type and your own experience may shift those numbers. The point of the log is not to prove the water hit a textbook number, it is to show you tested and responded sensibly.
Record what you added, not just what you found
A reading without the treatment is half a record. If the log says pH was 8.0 and nothing else, nobody knows whether the tech fixed it. Every visit should list each product added and the amount: so many pounds of shock, so many ounces of muriatic acid, tablets added to the feeder, bags of salt.
This matters for three reasons. Safety, because a customer complaint about irritation is easier to answer when you can show exactly what went in and when. Cost, because you cannot price a pool correctly without knowing how much product it uses. And training, because a supervisor reviewing logs can see when a tech is dumping in too much acid or under-dosing chlorine to save time. In the crew app, the tech picks the product and enters the amount along with the readings, so the visit carries both halves of the story in the pool chemical log.
Make the log fast enough that techs actually fill it in
The most common reason chemical logs fail is that they take too long. A tech running 16 stops a day in July will skip anything that feels like paperwork. So make it quick: the same fields in the same order at every pool, the products they actually carry already in a list, and no typing beyond the numbers.
Set the expectation plainly. A stop is not done until the readings and the chemicals added are in. Spot-check logs weekly at first. If a tech logs pH 7.5 and free chlorine 3.0 at every single pool for two weeks, he is not testing. Real water varies, and real logs show it. A short conversation early saves a long problem later. When techs see that the office actually reads the logs, and uses them to back the tech up when a customer complains, the logs get better on their own.
Use the history to spot problems before they show
One week's reading tells you what to add today. Twelve weeks of readings tell you what is going on with the pool. A pool that needs more chlorine every week as summer goes on may have climbing stabilizer, which is a sign to test CYA and plan a partial drain. A pool where pH climbs fast every week may have high alkalinity or a new plaster finish still curing. A sudden jump in chlorine demand can point to a leak bringing in fresh water, or an algae problem starting in the filter.
When the history lives on the property instead of in a binder in someone's truck, any tech can look at the last few visits before testing. That is how a substitute can service a pool for the first time and still make the same calls the regular tech would. It is also how the office can answer "why is my bill higher this month" with a straight answer.
Send customers the results
Most homeowners never see what happens at their pool. They see clear water and a bill. That is fine until a competitor offers a lower price, and then the customer has no idea what they would lose by switching. Sharing the readings and a photo after each visit shows the work.
After a completed stop, the customer can get an alert with the tech's notes and photos, and they can see their service history in the customer app. Keep the note human: "Brushed and vacuumed, pH was a little high so I added acid, filter pressure is creeping up so we should clean it next month." That one sentence explains the visit, justifies the price, and plants a filter clean. Our post on proof of service covers the rest of that picture.
Keep the records long enough to matter
Some states and local health departments have rules about chemical records for commercial pools, and some insurers ask how you document treatments. Rules for residential service vary widely, so check with your state and your insurance agent about what you should keep and for how long. Even where nothing is required, keep at least a few seasons of history. Disputes about a plaster finish or a liner can surface long after the visit.
The easiest way to keep records is to never have them on paper. A log entered at the pool, attached to the property and the date, does not get rained on, lost under a seat or thrown away when a tech quits. When you price a pool, the same log tells you what it really costs to service, which is where chemical cost tracking picks up.
Ready to Run a Tighter Pool Service Operation?
IndustryBossPro gives you everything in this guide โ and every other tool your business needs โ from $59/month.