Skip to main content
This page explains the current compliance behavior and the near-term direction of the platform.

​
Current compliance features

Implemented today:
  • audit logging foundation
  • chemistry status evaluation
  • Illinois-based chemical defaults in the seed configuration
  • closure-threshold support for configured chemical fields
  • closure warning messaging on affected chemical record detail pages
  • comment and history support on chemical records
  • manual closure incidents with reopen/resolve flow
  • evidence attachments and corrective actions
  • scheduled closures kept separate from compliance incidents
  • facility-status, exception-ledger, and timeline views
  • inspection packet builder (/compliance/packet)
  • inspector-ready exception reporting with a closure-vs-scheduled split
  • daily/weekly compliance digest email
  • reopen attestation/sign-off workflow
  • policy/SOP document library and jurisdiction checklist templates (/compliance/library)

​
Illinois water quality defaults

The seeded demo chemical profile uses Illinois-oriented defaults based on 77 Ill. Admin. Code 820. Examples:
  • free chlorine ideal 1.0 to 4.0 ppm
  • free chlorine closure below 0.5 ppm
  • total chlorine closure above 5.0 ppm
  • pH closure below 6.8 or above 8.0
  • cyanuric acid alert above 100 ppm
These are defaults, not forced values. Each pool profile can be adjusted.

​
What’s still on the roadmap

Compliance reporting itself is feature-complete. What’s still ahead is outside the compliance module specifically: public, unauthenticated form submission links and multi-organization accounts. See Roadmap.
1

Log the reading

Log the chemical record accurately.
2

Review status

Review the status on the detail page.
3

Open a closure incident if needed

If the record shows closure_required, open or review the linked closure incident.
4

Document follow-up

Add notes, evidence, and corrective actions inside the incident record.
5

Use scheduled closures for planned downtime

Use scheduled closures only for planned downtime such as holidays or maintenance windows.
6

Preserve records

Preserve records rather than deleting them unless necessary.

​
Current compliance workflow highlights

  • closure incidents are manual and can optionally reference a chemical record
  • resolution requires attestation, not a structured retest workflow
  • comments act as the incident notes thread, including any follow-up readings
  • evidence uploads cover photos, PDFs, SOPs, and handwritten sheets
  • corrective actions are structured follow-up tasks inside the incident

​
Scheduled closures vs. compliance closures

The roadmap distinguishes:
  • scheduled closures Examples: weekends, holidays, facility days off
  • compliance closures Examples: closure-threshold chemistry or visibility failures
That separation is important so planned downtime is not mixed with health or regulatory incidents.