STANDARD CHECKER

Readings against ASHRAE 188 —
each one checked, each clause cited.

Enter your cooling tower water management plan and upload your reading log. One request returns every finding: values out of range, readings overdue, records missing — each one pointing at the standard clause or plan section that requires it.

Check a cooling tower See pricing

How Coolcheck works — readings in, findings out, each with a clause citation YOUR LOG (CSV) 2026-01-15,Tower 1,pH,7.2 2026-01-22,Tower 1,pH,8.9 COMPARE AGAINST §8.3 ASHRAE 188 pH 6.5 – 8.5 §5.2.1 30 days OUT OF RANGE? 8.9 exceeds max 8.5 FINDINGS OUT-OF-RANGE §8.3 OVERDUE 41 days OVERDUE §5.2.1 MISSING No records Download CSV Your readings → CSV input Checked against plan + ASHRAE 188 defaults Findings with clause citations
01 TOOL / WHAT IT DOES

Each reading checked against ASHRAE 188, each clause cited.

ASHRAE Standard 188 and the CDC Legionella Control Toolkit define control limits, monitoring frequencies, and corrective actions for cooling tower water management plans. Coolcheck compares every reading you took against those published values — or against your own plan parameters if they differ from the defaults.

A finding is named, valued, and sourced. Out-of-range. Overdue. Missing. Every one carries the clause or plan section that creates the requirement. No health verdict, no alarm — just the standard's own language, applied to your numbers.

Check a cooling tower

02 DIAGNOSTIC / HOW IT WORKS

Three steps: enter, upload, review.

§8.3
Enter your plan parameters. Control limits per parameter — pH, conductivity, biocide, temperature — and monitoring frequency. Leave a field blank to use the ASHRAE 188 default (published in the standard and the CDC toolkit).
CSV
Upload your reading log. Export from your cooling tower spreadsheet as CSV. Columns: date (YYYY-MM-DD), location, parameter, value, unit. The tool parses every row and compares it.
§5.2.1
Review the findings. A table of out-of-range values, overdue readings, and missing parameters — each with the clause reference. Download as CSV. No data is stored. No account needed.

This is not a compliance record, not a lab result, and not legal or medical advice. Findings are comparisons of your readings against your plan parameters and ASHRAE 188 defaults. A tool that misses a lapse is worse than a spreadsheet because the spreadsheet does not claim to be watching.


03 STANDARD / PARAMETERS CHECKED

Published control limits for every common parameter — or your own.

The tool applies ASHRAE 188 default control limits and monitoring frequencies for the four parameters every water management plan tracks. Use them as-is or override any value with your plan's own limits.

pH 6.5 — 8.5
Control range. Every 7 days.
ASHRAE 188 §8.3
Conductivity ≤ 1800 µS/cm
Upper limit only. Every 7 days.
ASHRAE 188 §8.3
Biocide 0.5 — 5.0 mg/L
Control range. Every 7 days.
ASHRAE 188 §8.3
Temperature ≤ 38 °C
Upper limit only. Every 7 days.
ASHRAE 188 §8.3

Culture (dip-slide) sampling: every 30 days per ASHRAE 188 §5.2.1. The standard does not set control limits for culture — your plan must define what action level triggers a response.

If your plan specifies a different limit or frequency, enter it in the tool. The tool uses your values where supplied; defaults are labelled "default from ASHRAE 188".


04 ACCESS / WHAT IT COSTS

Free for any cooling tower you manage.

This tool is free to use. No account needed, no data stored. Your readings arrive in one request, we compare them against ASHRAE 188 or your plan, and the findings — and nothing else — leave in the response.

A Pro tier ($5.00/check) is planned but not yet available. It would add: save tower profiles with your plan parameters, compliance rollup across multiple towers at one site, and a history of past check results. These features require accounts and persistent storage — not part of the current architecture. See pricing for details.


05 SCOPE / WHAT IT WILL NOT DO

A compliance tool that misses a lapse is worse than a spreadsheet.

These limitations are structural, not temporary. We state them here and on the tool page because an honest gap is information and a hidden one is not.

  • No email, reminders, or alerts. There is no email sender in this fleet. Overdue findings are for your reference — you must act on them yourself.
  • No BMS, CMMS, or LIMS integration. CSV is the only input format. If your building management system or lab reports cannot export CSV, this tool cannot read them.
  • No storage. Every request is processed independently. Nothing is saved server-side. Refresh the page and you start fresh.
  • No accounts, no login, no saved history. There is no way to store readings, revisit past checks, or compare across months.
  • Not a compliance record. The tool checks arithmetic and dates against a standard. It does not issue findings that satisfy an inspector's documentation requirement. Always consult your water management plan and a qualified EHS professional.

If your plan does not specify a control limit for a parameter, the tool uses the ASHRAE 188 default and labels it as such. If the standard itself does not set a limit (culture is one example), the tool says so rather than inventing one.


06 TRUST / THE STANDARD IT CITES

Every finding cites the clause that requires it.

ASHRAE Standard 188 — Legionellosis: Risk Management for Building Water Systems — is the framework that defines what a water management plan must contain: control locations, control limits, monitoring frequencies, corrective actions, and documentation. The CDC Legionella Control Toolkit provides the recommended numerical values.

Coolcheck does not interpret these standards. It compares your readings against the published numbers and dates. Each finding message names the clause: "ASHRAE 188 §8.3" or "default from ASHRAE 188 §5.2.1". You can verify every citation against the published text.

The tool does not parse or interpret the standard — it holds published numbers and applies them to the values you submit. If the standard does not settle a frequency (e.g., culture action levels), the tool says so rather than inferring one.