History is the immutable record of every task completion, work-order closure, and SOP publish in your account. It is built to satisfy two needs: day-to-day shift handoffs, and formal compliance audits.
Open History
From the left navigation click History. The default view shows the current Facility for the last 7 days. Every row is one completion event with author, timestamp, attached notes, readings, and photos.
Filtering
Filters are stacked along the top:
- Facility — defaults to current; switch to "All facilities" if you have access.
- Date range — calendar picker, with presets for 7d / 30d / 90d / Year-to-date.
- Type — Daily task, Weekly task, Monthly task, Work order, SOP publish.
- User — narrow to a single tech.
- Task / SOP — pick a specific task or SOP.
- Search — free-text across title, notes, and comments.
Each filter updates the URL, so the result set is shareable.
Reading a row
Click any row to expand it. You will see:
- The task or work-order title and ID.
- The cadence and the due window.
- All field values captured (readings, pass/fail, notes).
- Attached photos with timestamps and SHA-256 hashes.
- Any comments or status transitions on the underlying work order.
- Who logged the entry, from which IP (admin-only).
Edits and corrections
Edits to historical entries are tightly controlled:
- A Technician can correct their own entry for 24 hours after completion. The original value is preserved with a "before" / "after" diff visible to admins.
- An Admin can correct any entry for 24 hours. Beyond 24 hours, only Manual correction entries are allowed — these add a new row tagged as a correction without overwriting the original.
This rule is what makes History audit-grade. Every change is visible.
Exporting for an audit
From the top right of History, click Export → Compliance bundle. The bundle is a ZIP containing:
- A CSV of every filtered row with all fields.
- A
photos/folder with the attached images at original resolution. - A
sops/folder with the SOPs in effect during the filtered range (and a diff between versions). - A
manifest.jsonwith SHA-256 hashes for every file so the bundle's integrity can be verified after delivery.
The export honours your role-based access — you can only export what you can see.
Common audit recipes
- Last 12 months of water sampling at Facility 3: filter by Facility=Facility 3, Task=Water sampling, Range=Last 365 days → Export Compliance bundle.
- Every overdue task in Q1: filter by Range=Q1, then sort by Status: Overdue → Export CSV.
- All SOP changes during 2026: Type=SOP publish, Range=Year-to-date → Export.
Tips
- Bookmark common audit filter URLs and share them with the compliance team.
- Run a dry-run export each quarter to catch missing readings before the real audit asks for them.
- Compliance bundles are large — generate them off-peak and use the email-when-ready option for big ranges.
FAQ
Can I delete an entry? No. Even Super Admins can only soft-hide an entry for confidentiality reasons; the existence of the entry remains visible.
Can I add a missing entry after the fact? Yes — Admins create a Manual correction entry with the actual time of the work in the body. The entry is tagged so audits know it was backfilled.
Does the compliance bundle include redactions? Not yet. For redacted exports, generate the bundle and run your redaction step before delivering.