Compliance Register

The Compliance Register is an ELCA-style (Environmental Legal Compliance Assessment) log: every finding pairs an observation with the specific legal requirement it's assessed against, a compliance verdict, and — where needed — a corrective action, owner and due date.

An environmental audit finding is only actionable if it's clear exactly which legal requirement it relates to and what a "compliant" verdict actually means for that requirement. Structuring every record as observation-plus-legal-requirement-plus-verdict, rather than a free-text audit note, keeps that link explicit for every finding, not just the ones someone remembered to cross-reference.

Each finding is categorised (Air Quality, Water Management, Waste Management, Hazardous Substances, Energy & GHG, Fauna & Flora, Fire Protection, International Laws, or General), records the observation and the legal requirement it's assessed against, and carries a compliance verdict: compliant, non-compliant, query-non-compliant, observation, or fyi. A finding also has its own open/closed status, separate from the compliance verdict — a non-compliant finding stays open until its corrective action is complete, then moves to closed, while the verdict itself (non-compliant) remains part of the historical record.

The list page shows every finding with its category, compliance verdict, and open/closed status, filterable and sortable by due date, compliance status, or status. The detail page shows the full finding; create and edit forms share the same fields.

• Category — required. One of Air Quality, Water Management, Waste Management, Hazardous Substances, Energy & GHG, Fauna & Flora, Fire Protection, International Laws, General.
• Observation — required. What was observed.
• Legal requirement — required. The specific legal requirement this observation is assessed against.
• Compliance status — required. One of compliant, non-compliant, query-non-compliant, observation, fyi.
• Recommendation — optional. The corrective action recommended, if any.
• Responsible person — required. Who owns following up on this finding.
• Due date — required. When the corrective action is due.
• Status — open or closed. Independent of the compliance verdict.

Creating or editing a finding requires category, observation, legal requirement, compliance status, responsible person, and due date; the recommendation field is optional (findings verdicted compliant/fyi often won't need one).

Closing a finding is a direct status edit — there's no separate sign-off step or notification triggered by it in the current version of the product. A finding's compliance status has no automated effect on other registers such as Metrics Log or the Legal Register; relate them manually where they cover the same underlying requirement.

What's the difference between "non-compliant" and "query-non-compliant"? Both are compliance-status verdicts; query-non-compliant is for a finding where non-compliance is suspected but not yet confirmed — use non-compliant once it is.