From failed checklist item to verified resolution — without leaving the platform.

How it works

A failed checklist item creates a violation. When a checklist run is submitted with failed items, the platform auto-generates one violation per failure. Each violation is pre-populated with: the failed item text, the linked regulatory citation, the risk level, the assignee (defaults to compliance manager for the facility), the source (with linkage back to the checklist run and inspection).

A violation gets corrective actions. From the violation detail, you create one or more corrective actions. The platform suggests templates based on the violation type — for example, an inventory discrepancy violation suggests "Inventory Reconciliation" with subtasks for physical count, state-system reconciliation, written documentation, track-and-trace adjustment, and staff retraining.

Subtasks track real work. Every corrective action has an ordered subtask checklist. Each subtask is checked off by the person who did it; the system records who and when. No more "marked complete" actions where the work was actually half done.

Verification is mandatory. When the assignee marks a corrective action as ready for review, a different user has to verify it before it can be closed. Same person can't sign off on their own work. Enforced server-side.

Linked evidence. Documents, photos, and files attached to the corrective action live in the document vault, linked to the action, the violation, and the facility. Nothing lives in someone's email.

Built for a real inspection record

Every status change, every note, every document attachment generates an audit log entry. When you have to defend your remediation history to a state agency, the timeline is right there — accurate, complete, attributed.