Assurance / How the score works
How the score works
Seven measures, weighted to 100, then caps. Qyro admins edit the model; customers see the explanation.
Score = Σ ( weight × result ) then apply caps
Measures
| Measure | Weight | Result is | From | AI Triage Platform | Lost |
|---|---|---|---|---|---|
| Documents | Share of in-scope documents approved and inside their review date | 6 | −14 | ||
| Hazards controlled | Share of hazards with an approved control and no overdue review | 15 | 0 | ||
| Plan items live | Share of plan items with a live, in-date way of knowing | 6 | −9 | ||
| Evidence in date | Share of required evidence present and unexpired; −50% weight inside 30 days of expiry | 7 | −8 | ||
| Work on time | Share of CAPAs, workflow steps and tasks not overdue; CAPAs count double | 12 | −3 | ||
| Training | Share of required training complete for each person’s role | 10 | 0 | ||
| Incidents handled | Share of incidents meeting each step’s deadline | 8 | −2 |
Caps and rules
Untriaged incident past its deadlineScore capped at 50On
CAPA overdue by 30 days or moreScore capped at 70On
Expired certificate shown in a Trust Portal−5 pointsOn
Measure with nothing in scopeIts weight is shared across the othersOn
Versions
v1.3 · draftIncidents weight 10 → 12 · preview: average −1.4 across customersDraft
v1.2 · live since 1 OctAdded the portal certificate ruleLive
v1.1Retired 1 OctRetired