[Answer] What is SIF?

Credit: Pop & Zebra/Unsplash

Understanding SIF (Serious Injury & Fatality) Investigating incidents, near-misses and hazardous conditions takes considerable time and effort. 

Does everyone have the time and resources to investigate every incident in depth? And is it worth it?

Here’s an excerpt from an article published in ShipNerd, explaining the same.

Heinrich’s triangle

Historically, many have followed Heinrich’s triangle. Although the numbers used in Heinrich’s triangle are contested, the concept remains valued by many safety experts. 

Tackling near-missed

The rationale is if we tackle all the many near-misses and minor accidents, then this will avoid that major injury or fatality that sits at the top of the triangle.

Prevent big incident

However, how to prevent that big incident from occurring? Consider that your efforts should focus only on those incidents with a high potential for harmful outcomes.

What is SIF?

According to human factors consultancy Dekra, SIFs have plateaued or increased while the more minor injuries have continuously declined. Their studies identified that one of the main reasons for this is that the causal factors behind SIFs are often different from those for less serious injuries.

They also found that the potential for serious injury is low for the majority (around 80%) of non‑SIF injuries. As such, not all minor incidents can result in major incidents.

Defining SIFs

Defining a fatality is of course straightforward, but what constitutes a “serious injury”

In general terms, it can considerably be a life‑threatening or life‑altering work‑related injury or illness.

It gets trickier when trying to determine whether an event has “SIF Potential”

Specifically, this is when the incident could have reasonably resulted in a fatality or serious injury had any of the circumstances or protective measures changed, or if luck hadn’t played its part in reducing the severity of tIn other words, could a fatality or life-altering or life-threatening injury/illness reasonably have resulted?

Methods to determine SIF Potential

There are two recognized methods to help determine whether an incident has SIF Potential:

1.“Judgment‑Based Narrative Review” – 

This is a subjective approach. It relies on the professional judgment of safety managers and investigators to assess whether the event could have resulted in a SIF.

2.“Event‑based Decision Tree Classification” – 

This uses the characteristics of the incident or near-miss to classify a situation as having SIF potential. 


Safety reporting and measuring ‘safety’ can be a contentious issue.

Some in the “you can’t manage what you don’t measure” camp argue that recording injury rates are important management information and allows the identification of problem areas.

Others may argue that metrics such as lost time incidents (LTIs) are not indicative of performance and can create a culture where people are discouraged from reporting.

Rate of actual SIF events

Recording actual SIF events may not in itself be a useful indicator of safety performance as incidents are, thankfully, infrequent. 

What may be more useful is the rate of actual SIF events plus those events with SIF potential – in other words, the exposures that resulted in an actual fatality or serious injury plus those that could have but did not.

Safety initiatives

Knowing which types of incidents have SIF potential can help you identify and formulate safety initiatives that target both these types of events and the underlying issues behind them.

Dekra say that when companies rely solely on recordable injury rates as the primary measure of safety performance (a common practice) they lose sight of crucial data underlying SIFs. 

This ends up with safety initiatives that are put in place to help reduce low SIF potential incidents for no other reason than because they occur more frequently. 

It is then mistakenly believed 

that their actions are addressing the likelihood of all injury types.

Did you subscribe to our newsletter?

It’s free! Click here to subscribe!

Source: ShipNerd