A readiness verdict only means something when the required capability is explicit. Set the people, roles, competencies and assets that a station or watch must have before comparing them with live evidence.
Requirements can inherit from organisation to country, contract, site and station or watch. Define minimum counts and classify each requirement as critical or advisory. Personnel, role competence, medical and fitness currency, licences, vehicles and equipment assurance can all contribute. Local changes have a clear scope rather than silently rewriting a global rule.
Decisions retain their context
Publishing a new profile version preserves the historical rule under which an earlier verdict or override was made. Compare required with actual, name the first failure and the affected response capability, then record the authorised decision. A critical failure is Not ready regardless of high percentages; advisory failures can degrade capability.
No profile, no assumed pass
Missing evidence cannot satisfy a requirement. When no profile exists, the answer is unknown rather than Ready. Show the gap and a suggested remedial response in the working view so the accountable person can resolve or escalate it without mistaking a score for a verdict.
Being clear about what this does and does not mean
Evidence over averages
Percentages support inspection of evidence; they never override a critical rule.
Accountable configuration
The organisation defines its minimums; the platform does not certify that those minimums meet a legal standard.
Questions worth asking of your own operation
Which critical requirements vary between your sites?
Can you reconstruct the rule that applied to a past decision?
What does your team see when a profile has not been configured?