Our Safety Score Formula, Published
Every competitor shows a safety score. None of them publish how it is computed. Here is ours, with the arithmetic, so you can check every point.
Why publish it at all?
A safety score you cannot explain is a number you cannot defend. When a subcontractor asks why they are a D, the answer should be a list of events, not a shrug at a black box.
So we publish the formula. If you are comparing us with another vendor, ask them for theirs in writing.
The formula
Severity weight
Low 1, medium 3, high 6, critical 12
Per concern
Duration multiplier
1 + minutes ÷ 10, capped at 30 minutes
1× to 4×
Penalty
Severity weight × duration multiplier, per event
Summed
Exposure
Person-hours observed ÷ 10, at least 1
Per period
Score
100 − total penalty ÷ exposure, between 0 and 100
A ≥ 90 · B ≥ 80 · C ≥ 70 · D ≥ 60
The score ranks; the KPIs and the event list report.
A worked example
An emergency exit is blocked for 30 minutes on a quiet night shift. That is a critical event: 12 × 4.0 = 48 points. The night shift observed 16 person-hours, so exposure is 1.6, and the shift scores 100 − 48 ÷ 1.6 = 70, a C.
The same 30-minute block on a busy day shift with 120 person-hours costs 48 ÷ 12 = 4 points. The shift scores 96, an A.
- Night shift70score
- Day shift96score
The penalty is the same. The exposure is not.
That is deliberate. The score ranks shifts, sites and owners against each other fairly. The blocked minutes and the event list are what you report, because a 30-minute blocked exit is a 30-minute blocked exit on any shift.
Where the points went
Category scores use the whole site's exposure, so the deductions add up to the site total. That lets the dashboard say things like: your site is a B, and 9 of the 13 points you lost are Emergency Readiness.
Frequently Asked Questions
The formula is the same for every customer so scores can be compared. What you control is which concerns are switched on, the zones they run on and their thresholds.
So one very long block cannot swamp a month of scores. The blocked-minutes KPI has no cap and counts every minute.
No. A supervisor can mark an event as a false alarm with a reason, and it is excluded from the score.
COM8 Engineering
Computer Vision & Platform
Engineers behind the edge box, the detection pipeline and the COM8 Vision dashboard.
A safety score you can defend
Put COM8 Vision on the cameras you already have.
Book a pilotAlready a customer? Log in
