Tool V10 · Free

Safety Assurance Map

A risk register that lists hazards and a rating is a list, not assurance. What makes a risk acceptable is the barriers between the hazard and the harm, and whether each one is really in place. Enter the hazards, rate them before and after controls, and name the barriers on both sides of the top event. Each barrier is tagged to the SMS element that manages it and the functional area it sits in, so the map shows where assurance is evidenced and where it is only intended.

Step 1

How much risk is tolerable?

Risk is rated likelihood (1 to 5) times severity (1 to 5). The cut-offs below are a common 5×5 convention, not a regulatory limit: set the tolerability your own SMS and Accountable Manager have adopted.

Acceptable up to a score of

At or below this, no action beyond monitoring.

Tolerable with mitigation up to

Above this the risk is intolerable until reduced.

Likelihood: 5 frequent, 4 occasional, 3 remote, 2 improbable, 1 extremely improbable. Severity: 5 catastrophic, 4 hazardous, 3 major, 2 minor, 1 negligible.

Step 2

The hazards and their barriers

Each hazard has a top event, the thing that goes wrong. Preventive barriers stand between the threats and the top event. Recovery barriers stand between the top event and the consequences. A barrier counts as evidence only when its status is In place.

Start from a common hazard

Where the risk stands

—

Add a hazard.

Risk matrix (after controls)

Findings

Which SMS elements the barriers evidence

Bow-tie view

Have JK build the register your Authority will test.

A hazard log tied to your operation, barrier owners and evidence, a safety-performance indicator set, and a management-of-change route that keeps the register alive after certification.

No email app? · info@aviationhubkenya.org

An organiser for your own judgements, not an SMS and not an assessment of one. The ratings, barriers and statuses are what you enter; the tool does not verify them. SMS elements follow the ICAO Annex 19 framework (four components, twelve elements) and functional areas use the IOSA section names as a neutral index; mapping to IS-BAO, BARS or an Authority's own checklist is a separate exercise. A barrier is tagged to the element that manages or evidences it, which is a working convention, not a clause-by-clause compliance mapping. Everything you enter stays in this browser.