Most incident reports describe a fall in one sentence: worker lost balance, sustained injury, case closed pending corrective action. That sentence is accurate and almost useless. It tells you what happened without telling you anything that would stop it happening again — to someone else, on a different shift, doing a different task that shares the same underlying gap.
This article opens a series built around one real investigation — the details of the equipment, task, and setting have been changed so the case can’t be traced back to any specific site or organisation, but the causation chain itself is exactly as investigated. It’s one of the clearer examples of why Tripod Beta exists as a methodology, rather than a more familiar tool like 5 Whys or a Fishbone diagram.
The Scenario
A vendor’s technician was tightening a mounting bolt on a pump coupling at a processing plant. To reach both sides of the coupling, he climbed onto a support ledge, working alone at ground level while the rest of the crew was occupied installing a different pump unit nearby. Holding a wrench in one hand, he let go of the structure with the other to step back — but stepped back instead of stepping down, lost his one point of contact, and fell. On the way down, he struck a spare pump component that had been left on the floor nearby for convenience. He sustained a serious back injury and a fractured rib. Had the fall gone slightly differently, the potential outcome was serious internal injury, possibly fatal.
Why This Is an “Event,” Not Just an Incident
In Tripod Beta terms, every incident is built from at least one Trio: an Agent, an Object, and an Event. The Agent is whatever carries the potential to cause harm — here, the loss of balance and the fall itself. The Object is what’s vulnerable to it — the technician. The Event is the change of state that results when the Agent acts on the Object: the fall and the impact injury.
This distinction matters more than it looks. “The technician climbed onto the ledge” is not an Event — it’s an action, a Substandard Act in Tripod Beta’s terms. “The technician fell and struck the component below” is an Event: something occurred, a state changed, and it’s the direct result of the Agent’s release. Confusing an action for an Event is one of the most common structural errors in an investigation, and it usually happens because “climbing onto the ledge” feels like the natural place to start the story. It isn’t. It’s one step in a much longer chain that an investigation has to trace, not assume.
Why One Incident Gets Ten Layers of Analysis
A report that stops at “worker fell while working at height” has described the Event and nothing else. What actually determines whether this happens again is everything behind it: which barriers were supposed to prevent or catch this, why each one failed in the moment, what situational and psychological context made each failure feel reasonable at the time, and — the layer most investigations skip — which management system failures allowed those conditions to exist in the first place.
This particular case surfaced six failed barriers, five distinct preconditions, and four separate Basic Risk Factors (BRF) — Tripod Beta’s classification for the type of management system gap behind each underlying cause. None of the four pointed at the technician’s judgment on the day. All four pointed at decisions made well before he climbed onto that ledge: how the job was engineered, how the risk assessment was built, how the work was resourced, and whether anyone checked if the person assigned could physically do the task as described.
That’s the shape a proper investigation actually takes — not a single root cause, but a chain of findings at increasing distance from the moment of the fall, each one pointing at a different fix, owned by a different part of the organisation.
What This Series Covers
Over the coming weeks, this series will walk through each layer of that chain: the barriers that failed, the preconditions that explain why, and each of the four Basic Risk Factor findings in turn — including the confusion between a Risk Assessment and a Job Hazard Analysis that ran through part of this investigation, and how a properly scoped Bowtie diagram could have caught several of these gaps before the job ever started.
The Practical Starting Point
Before any of the deeper layers matter, the discipline that separates a real investigation from a compliance exercise is refusing to stop at the first plausible explanation. “He lost his balance” is true. It is not the finding. The finding is everywhere the investigation is willing to keep asking why — and that’s exactly what the rest of this series traces, one layer at a time.
Want your investigation team building causation chains like this — not just describing what happened? Cikgu Barrier’s Tripod Beta Incident Investigation programme is Malaysia’s only accredited Tripod Beta training, teaching HSE teams and investigation leads the full methodology from Trio construction to Underlying Cause. Available in-house and as a public workshop across Malaysia.