Phosphates are where the pool industry's sales pressure and its actual chemistry pull in opposite directions. A handheld meter reads a scary number, a product is sitting on the truck, and the path of least resistance is to dose it and move on. Sometimes that is the right call. Often it is treating a symptom that was never going to cause a problem.
The job is knowing the difference, because the wrong instinct costs you either way. Over-treat and you burn product and customer trust. Ignore a reading that actually matters and you are back next week fighting an algae bloom on your own dime.
What phosphates are and where they come from
Phosphates are dissolved nutrients. They are not directly harmful to swimmers and they do not throw off your sanitizer reading. What they do is feed algae. Algae need phosphates the way a lawn needs fertilizer, so the theory is simple: starve the water of phosphates and algae cannot get a foothold.
The reality is messier, because phosphates pour into a pool from a dozen sources you cannot fully control:
- Fill water. Many municipal supplies add orthophosphate to protect their pipes from corrosion. You are importing phosphates every time you top off.
- Lawn and landscape runoff. Fertilizer from the yard washes in with rain and irrigation overspray.
- Decaying organics. Leaves, pollen, and bather waste break down into phosphates over a season.
- Some sequestrants and stain treatments. Certain metal-control and scale products are phosphate-based and will spike your reading the day you add them.
Why a high reading is not an automatic bloom
Here is the part the meter does not tell you: algae need phosphates, but phosphates do not cause algae on their own. Algae also need a sanitizer gap. A pool running solid free chlorine relative to its CYA will not bloom at 1,000 ppb of phosphates. A pool that keeps drifting low on chlorine will bloom at 200 ppb.
So the first question when you see a high phosphate number is not "which remover do I use?" It is "is my sanitizer actually holding?" If chlorine is stable and proportional to CYA, a high phosphate reading is a watch item, not an emergency. If chlorine keeps crashing, phosphates are the gasoline, but the low sanitizer is the match.
The mental model: phosphates are fuel. Sanitizer is the fire suppression. You can have a tank of fuel sitting safely as long as nothing is lighting it. Fix the sanitizer first, then decide whether the fuel is worth removing.
When to treat
Reach for a phosphate remover when the reading is high and one of these is true:
- You cannot keep chlorine stable. If a pool fights you on sanitizer week after week and phosphates are above ~500 ppb, knocking them down removes the fuel while you sort out the real cause.
- Salt pools with output strain. A salt cell working overtime against a heavy phosphate load ages faster. On chlorine generators, keeping phosphates in check is partly cell-life insurance.
- Recurring seasonal blooms. A pool that greens up the same week every spring, despite decent chemistry, is a candidate for a preventive treatment ahead of the warm-up.
- Post green-to-clean. After you clear a bloom, the dead algae dump a fresh load of phosphates. Treating then helps stop the rebound.
When to leave it alone
- Chlorine is rock solid. Stable sanitizer and clear water at a high phosphate number is not a problem to spend a customer's money on.
- You just added a phosphate-based sequestrant. The reading is high because you put it there on purpose. Removing it undoes the stain or metal control you were paying for.
- Your fill water is the source and the pool is fine. Chasing a number that refills every top-off is a treadmill. Manage the sanitizer instead.
How to treat without overshooting
Phosphate removers are lanthanum-based. They bind phosphates into a precipitate the filter then catches. The practical notes that save you a callback:
- Test and record the starting number so you can show the customer the before and after.
- Dose to the product's rate for the actual reading, not a blanket pour. Over-dosing clouds the water and loads the filter for no extra benefit.
- Run the filter continuously for 24 to 48 hours after treatment. The remover only works if the precipitate gets captured.
- Expect a pressure rise and plan the filter clean. On a cartridge or DE system, a heavy treatment can mean a rinse the next visit.
- Re-test the following week. If the number is back up and chlorine is fine, the source is ongoing (usually fill water) and the answer is management, not repeated dosing.
How to bill it so it does not feel like an upsell
Phosphate treatment is a legitimate add-on, but customers have been burned by it being sold as a cure-all. Frame it the way you would frame any honest recommendation:
- Tie it to a visible problem they already know about ("your pool greens up every April"), not an abstract number.
- Bill product at cost plus a fair markup, plus the filter clean if the treatment triggers one. Itemize it so the invoice is not a mystery.
- Log the before and after readings on the service record. A customer who can see the number drop does not feel sold; they feel served.
That last point is where logging earns its keep. If your chemistry history lives in one place per pool, the phosphate trend, the chlorine stability, and the treatment all sit on one timeline, and the recommendation explains itself.
Bottom line
- Phosphates are algae fuel, not an algae cause. Stable sanitizer beats a low phosphate number every time.
- Treat when you cannot hold chlorine, on strained salt pools, on recurring seasonal bloomers, and after a green-to-clean.
- Leave it alone when chlorine is solid, when you added a phosphate-based product on purpose, or when the only source is fill water and the pool is clear.
- Dose to the reading, run the filter, plan the clean, and log the before and after so the bill explains itself.