Compliance Score Changed

Overview

AIQ-CMP-001 is an informational marker, not an error: it fires whenever a framework's assurance percentage changes since it was last viewed. It exists so nobody mistakes a moved score for a data problem when it is actually the platform doing its job.

Common causes

• A new finding pushed a control from PASS to PARTIAL or FAIL.
• Evidence for a control went stale past its cadence, moving it toward EVIDENCE GAP.
• An exception expired and the control reverted to its raw evaluated state.
• A scope change added or removed assets, sites or controls from the framework calculation.

Trace the change

1. Open the control's observation history to see the exact state transition and timestamp.
2. Open Change Intelligence for the same period to see if a configuration or asset change coincides with the score movement.
3. If the change came from an expired exception, check the exception's owner and renewal status.

When to escalate

Escalate only if the observation history shows a state change with no corresponding evidence event, which would indicate a calculation issue rather than a real-world change. In nearly all cases the history explains the movement directly.

Related reading

• AIQ-CMP-001Assurance score changed
  A control moved state, changing the framework assurance percentage.

• Evidence-First Assurance Model
  Universal controls, evidence mapped to many frameworks, and why missing evidence is not failure.
• Control States
  PASS, PARTIAL, FAIL, EVIDENCE GAP, NOT APPLICABLE and EXCEPTION — precise definitions.
• Evidence Timeline
  Reading control history: PARTIAL → PASS storylines and confidence over time.