What The Health Score Means
Operational Health measures how well the verified outcomes meet the stated requirements. A higher score means stronger compliance with those checks. A lower score means more confirmed exceptions within the evidence assessed.
It is not a revenue-loss estimate or proof that all business operations are healthy. CRM evidence may not capture work performed outside the system.
How It Is Calculated
- Control score: passed requirement outcomes divided by passed plus failed outcomes, expressed out of 100.
- Domain score: the equal-weight average of its scored requirement controls.
- Overall score: the equal-weight average of the domains with a supported score.
The same obligation is not counted twice. Not-applicable checks and review indicators do not become automatic failures or passes in the requirement score.
Why Evidence Coverage Matters
Evidence coverage shows how much of the applicable requirement evidence supports a definite outcome. Unverified results are excluded from the health calculation and remain visible as gaps. A score of 90 with low coverage does not provide the same confidence as 90 with broad coverage.
If no verified requirement outcomes exist, a meaningful health score cannot be calculated. A technical collection failure must be resolved rather than represented as poor operating performance.
Read High Scores In Context
- Governance: a complete recorded baseline can score 100 for baseline completeness. That does not certify the configuration is correct.
- Reporting Readiness: satisfied scored requirements do not remove separate source-traceability indicators or evidence gaps.