Overview
Every industrial user location now carries a compliance status — Compliant or Non-Compliant — worked out by the system rather than set by hand. It answers one question: does this location have any open violations?
Nonconformances now carry a lifecycle status of their own. Violations move through Open, In Progress and Closed automatically as responses are issued and their requirements are met. Exceptions are simpler: they are Open until an authority user closes them by hand.
Before You Begin
Compliance status is computed from all violations in the system regardless of when they were created. When this feature deploys, every location's compliance status is instantly computed based on its current violations.
How Compliance Status Is Decided
A location is Non-Compliant when it has at least one violation that is Open or In Progress. It is Compliant when all violations are closed, or no violations exist at all. Exceptions do not affect compliance status.
The status is re-derived whenever something happens that could change it — a violation is created, a response is issued, a requirement is met. It is not a field anyone edits.
Where Compliance Status Appears
On the location page — as a status chip in the summary card.
On the Industrial Users list — as the Status column, which leads the table. The column previously headed Status (whether the location itself is active) is now headed Active.
In the industrial user's portal — the same chip on their location summary, so they see the same standing you do.
📝 Note The Status column can be searched and filtered like any other, and it is included in exports.
The Violation Lifecycle
A violation's status follows what has been done about it. Nobody sets it directly.
Status | What it means |
Open | The violation has been created and no response has been issued for it. |
In Progress | A response has been issued, and it carries requirements that have not all been met yet. |
Closed | Every response covering the violation is complete and all of its requirements have been met. |
A violation created with no response starts Open. Issuing a response that carries requirements moves it to In Progress. When those requirements are met the response completes, the violation moves to Closed, and the location's compliance status is worked out again. A response carrying no requirements takes the violation straight from Open to Closed, because there is nothing outstanding to wait for.
Each violation is independent. Closing one does not close another at the same location, and the location stays Non-Compliant while any violation remains Open or In Progress.
Closing an Exception
Exceptions are informational findings that do not affect compliance status. They have no In Progress state and no automatic path to Closed. Only authority users can close exceptions. Portal users can see exceptions but cannot close them.
You can close exceptions from three places:
On a nonconformance's own page, using Close.
On a report's Nonconformances tab, in the Exceptions section — either Close All in the section header, or Close from an individual row's menu.
On the Exceptions tab of the Violations page, by selecting rows and using the bulk Close.
In each case a Close Exceptions window asks you to confirm, offers a Notes (optional) field, and closes with the Close button. Anything you type in Notes is kept on the nonconformance.
⚠️ Warning Closing an exception is permanent and cannot be undone. The window says so, and a closed exception is locked from further edits.
📝 Note Only Open exceptions can be closed, so only those rows offer the action.
Reading the Violations Page
The program-wide list is the Violations page. It has Violations, Exceptions and All tabs, each showing a count of its open items, and a Status column showing each record's lifecycle status. The list covers the whole working set rather than open items alone.
Nonconformances associated with retracted reports are removed from this list.
On a Report's Nonconformances Tab
The tab is split in two:
Violations at the top, with the selection checkboxes and Add Response behavior it already had. Responses are only created against violations.
Exceptions below it, collapsed by default, with a count beside the heading. Expanding it shows the exceptions and their Close actions.
📝 Note If a report has no exceptions, the Exceptions section is not shown at all.
What the Industrial User Sees
In the portal, an industrial user sees their location's compliance chip and a single Reports table covering both their sample reports and any reports an enforcement document requires of them. Scheduled and past-due items open the form for them to complete and submit.
Portal users can see exceptions but cannot close them — the Close actions are not shown to them.
FAQ
Q: My location says Non-Compliant but I have closed everything. Why?
A: Compliance looks at violations only, and only at those that are Open or In Progress. Check the location's violations rather than its exceptions — one still open anywhere on the location keeps it Non-Compliant.
Q: Can I set a location to Compliant myself?
A: No. The status is derived from the location's violations. Creating a violation makes a location Non-Compliant. Responding to all violations and fulfilling their requirements is what returns a location to Compliant.
Q: Open exceptions are not making my location Non-Compliant. Is that wrong?
A: No, that is how it works. Exceptions are informational and do not affect compliance status.
Q: Why can't I close this exception?
A: Only Open exceptions can be closed. One that is already closed stays closed — closing is permanent. Portal users cannot close exceptions at all.
Q: I closed an exception by mistake.
A: It cannot be reopened, and the record is locked. Contact Support if the record needs correcting.
Q: Why did my Status column change to Active?
A: The Status column now carries your locations' compliance status. The column that previously showed whether a location is active is now headed Active.
Q: A violation is Closed but the report still shows a problem. Why?
A: Closed means every response covering that violation is complete and its requirements were met. It does not remove the nonconformance from the record — the history stays.
Related articles
Tracking Required Submittals
Understanding Nonconformances on Sample Reports