Why Records Appear Not Assessed or Pending

In OrviQ, compliance and assurance states reflect proven evaluation history. This guide explains why certain items may display non-terminal states.

---

1. "Not Assessed" on Control Effectiveness

• Why it occurs: The control is registered, but no formal testing procedure or assessment campaign has been recorded for the active period.
• How to resolve: Conduct an operating effectiveness test in Controls & Assurance > Assessments (/assess).

2. "Unassessed" on Requirement Determination

• Why it occurs: The requirement is in scope, but a compliance officer has not yet formally evaluated the mapped controls and evidence to record a verdict.
• How to resolve: Open the Requirement Workspace (/requirements), review mapped controls, and click Save Determination.

3. "Expired" or "Expiring Soon" on Evidence

• Why it occurs: The evidence item's validity date has passed or is within 30 days of expiry.
• How to resolve: Upload updated proof (e.g., current year configuration export or recent test report) and link it to the control.