Compliance position
Compliance was treated as a prerequisite workstream, not a late-stage reporting add-on — the product direction assumed the system should be compliance-tight before broader workflow expansion. That work (Phase 3) is now complete.Implemented compliance work
- chemistry threshold evaluation with closure-required outputs
- Illinois-specific defaults and closure behavior
- manual closure incidents
- evidence uploads and corrective actions
- scheduled closures kept separate from compliance incidents
- facility status, timeline, and exception-ledger views (including a closure-vs-scheduled split)
- print-friendly compliance pages
- IDPH-oriented reporting support
- inspection packet builder
- daily/weekly compliance digest email
- reopen attestation/sign-off workflow
- policy/SOP document library and jurisdiction checklist templates
Also implemented since Phase 3
- preventive maintenance scheduling (Phase 3B)
- custom form templates with conditional logic and versioning (Phase 4)
- form submissions, scheduling, approvals, file/signature capture, and completed-form exports (Phase 5)
- corrections: a reason-required, permission-gated edit flow with a before/after audit trail, applied to chemical records, maintenance logs, and decided form submissions
Current roadmap shape
Phase 6 — Public Form Links
- public, unauthenticated token-based submission routes
- public submission safeguards
- notification recipients wired to actually send email
- offline PWA drafts
- Phase 6 end-to-end verification
Phase 7 — Multi-Organization Accounts
- many-to-many organization membership + active-organization session concept
- self-service signup and org creation
- email invite flow
- org switcher UI
- rework of org-scoped permission/session plumbing to resolve from active membership
Later themes
- native mobile-app exploration