Three things that get called monitoring
The word covers a lot of ground. It is worth separating what a vendor might mean when they say it.
- A technician tests the water on each visit. This is a snapshot: the chemistry at 10 am on Tuesday. It says nothing about Wednesday through Monday.
- A controller at the pool reads the water continuously and doses to setpoint. This is automation. The pool is being managed between visits, not just checked on them.
- Software collects the controller's readings, keeps them, and turns them into decisions. This is real-time monitoring in the sense that matters: someone, or something, is watching every pool all the time and knows which one needs a person today.
All three are useful. Only the second and third change what happens to the water between visits.
What a controller reads
The controller at every pool we service is a PoolCop, a commercial automation unit installed at the equipment pad. It has probes in the water and sensors on the equipment, and it reads:
- pH, continuously, and feeds acid to hold the setpoint.
- ORP, oxidation-reduction potential, which is the sanitizer's actual strength in the water rather than a chlorine concentration. A pool at 750 millivolts is sanitizing; a pool at 600 is not, whatever the chlorine reading says. The controller feeds chlorine to hold the ORP setpoint.
- Filter pressure, which tells it when the filter needs a backwash and, over weeks, whether the filter is losing efficiency.
- Flow and pump state, which tell it whether the pool is circulating at all.
- Water temperature, and the state of the fill valve, the heater, and any feature pumps it controls.
What it does not read is worth knowing too. Free chlorine as a ppm number, alkalinity, calcium, and stabilizer are lab tests. The controller manages the water from pH and ORP; the lab test on each visit verifies it and sets the rest.
What dosing to setpoint means
A pool without a controller is dosed for the week: the technician adds enough chlorine on Tuesday to last until the next visit, which means the pool is over-chlorinated on Tuesday and under-chlorinated on Sunday. A controller doses for the hour. When two hundred swimmers arrive on Saturday and the ORP drops, it feeds. When they leave, it stops. The water is in range on Saturday afternoon and on Tuesday morning. That is the single biggest difference automation makes, and it is why we put a controller on every pool.
What software adds
A controller does its job at one pool. Software does its job across all of them. PoolSense Intelligence, our own platform, takes every reading from every controller and does four things with it.
It keeps the readings. Every one, from the day the pool went on. The controller itself does not store history; without software, a reading not captured is gone. The record is what answers an inspector's question and what tells the next technician what this pool did last August.
It scores each pool. A health score from the pool's own readings: sanitation, equipment, stability, balance. One number that says how the pool is doing, and a breakdown that says why.
It ranks what needs attention. An attention board that puts every pool in order: what needs intervention now, what is developing, what is worth watching. The operations team reviews it every morning and builds the day's routes from it. A pool that is fine does not get a visit it does not need; a pool that is drifting gets one before the residents notice.
It projects and grades itself. Free chlorine, alkalinity, and stabilizer are projected forward from the last lab test using the controller's feed data and the weather. Every SpinTouch test at the next visit grades the projection, and the platform shows its own accuracy for each pool rather than hiding it. When the model is wrong, we know, and so does the board if they ask.
It also meters the autofill and flags water loss the weather cannot explain, keeps the log book the inspector reads, and runs the guest page residents can open to see whether the water is in range.
Questions to ask any vendor
- Is there a controller at the pool, and what does it read? If the answer is a test strip, the pool is not monitored between visits.
- Does it dose to setpoint, or does it just report?
- Where do the readings go, and how long are they kept? Ask to see last month's readings for a pool they service.
- Who looks at the data, and how often? Every morning is the right answer. When something breaks is the wrong one.
- How is a lab test used? It should verify the probes and set the parts of the chemistry the probes cannot see, not replace them.
- Can the board see it? A vendor confident in the data will show it to you.
Real-time monitoring is not a feature to add to pool service. It is a different way of running a pool, in which the decision about what to do at a pool is made from what the pool is actually doing. The visible work still has to be done, and done well. The invisible work is what keeps the pool open on Saturday. See what it would show for your pool.