Product Update - May 11, 2026

Inspection Cycles — recurring inspection periods with automated team notifications

Admins can now create named inspection cycles tied to a specific template and date range — monthly, quarterly, annual, or a custom window. Activating a cycle dispatches notifications to the relevant team members so everyone knows the inspection period has started. A dashboard view tracks how many inspections are completed, pending, or overdue within the cycle, and cycles can be configured to close automatically when the end date passes or when every linked inspection is finished.

This solves a common problem for safety and compliance teams: ad-hoc inspections can happen without anyone knowing the program is behind schedule. Cycles make the inspection calendar explicit, auditable, and tied to real completion data rather than just checklists.

Use case: A facilities manager sets up a quarterly fire-equipment inspection cycle for all three office locations. When the cycle activates, every assigned inspector receives a notification and the dashboard shows real-time completion progress across all sites.

Available in: Inspections → Cycles

---

Inspection Review Workflow — multi-stage approval before an inspection is finalized

Inspections can now be submitted for review after completion, routing them through one or more designated reviewer levels before the record is locked. Reviewers see the full inspection with a review panel showing which stage is pending; they can approve to advance to the next level or reject with a required comment that sends the inspection back to the inspector for rework. The final approval closes and locks the inspection. If a workflow has multiple levels, the panel shows the current step and total step count so reviewers always know where they are in the process.

This adds a quality control layer for organizations where a single inspector's judgment is not sufficient for compliance or liability purposes — common in EHS, regulated manufacturing, and food safety environments where a supervisor or safety officer must sign off on findings before they count as closed.

Use case: A food-safety auditor completes a kitchen inspection and submits it. The shift supervisor reviews the findings, rejects two line items that need photo evidence, and the auditor resubmits. The supervisor approves the revised inspection, and the record is automatically locked and timestamped.

Available in: Inspections → Inspection record → Review panel