The commercial pool log that checks itself

Most state and local pool codes require operators to keep pool operation records available for inspection, prescribing what you record and how long you keep it. Commercial Pool Log captures every required reading with a tamper-resistant timestamp and generates a printable Monthly Operating Report in a familiar daily-operations layout. As with any recordkeeping method, confirm specifics with your local health department.

Sanitizer readings (free and combined chlorine, or bromine), pH, water temperature, and clarity checks — testing frequency varies by state and pool type, but whirlpools typically need several tests a day while standard pools need opening plus peak-load tests, plus weekly alkalinity and cyanuric-acid tests where applicable. Backwashes, breakpoint chlorination, contamination incidents and closures belong in the record too. Commercial Pool Log builds this checklist per pool automatically for supported states; every other state can log the same fields on its own schedule.

For supported states, the field turns yellow or red as the tech types, with the legal range and the code citation printed under it — a closure-level reading (say, free chlorine below minimum, or pH too high) logs a closure event and keeps the pool flagged CLOSED until a passing reopen-verification reading is recorded. Other states log the same reading without automatic grading until we've verified that state's specific thresholds.

It varies by state — commonly a year or more. Commercial Pool Log retains every account's records indefinitely by default regardless of state — the database itself blocks hard deletes, so your retention obligation is handled automatically. Confirm your own state's specific requirement with your health department.

Any state can create an account, add locations and pools, log readings, run operational checks, record incidents, and generate monthly reports and CSV exports today. Automatic legal-range validation and citations are fully modeled for a growing list of states — we don't fabricate thresholds for states we haven't verified, so unsupported states get full recordkeeping now while we add validated rule sets over time.