Look at a sample of incident investigation reports from Malaysian workplaces and a pattern emerges quickly: most of them have two real sections. What happened, and what the company is doing about it. Everything else is formatting. That’s not because investigators are careless — it’s because the standard report template most companies use was never designed to hold more than that.
A report that actually functions as an investigation — one that holds up to scrutiny, prevents a repeat, and gives DOSH or a client audit something credible to review — needs five distinct sections, not two.
Section 1: Immediate Facts and Actions
This is the section almost every report gets right, because it’s the most intuitive to write. What happened, who was involved, what was done in the first hours — containment, first aid, securing the scene, initial notifications. It’s factual, time-sensitive, and rarely contested.
Section 2: Sequence of Events
A factual timeline, built from evidence and statements, with no interpretation yet layered on top. This section establishes what occurred, in order — separate from why it occurred, which comes next. Conflating the two too early is one of the most common ways an investigation’s conclusions get shaped before the evidence is fully gathered.
Section 3: Causation Analysis
This is the section most reports either skip or collapse into two words: operator error. Done properly, causation analysis works backwards from the event — through the barrier that should have stopped it, to the substandard act or condition that let it through, to the underlying cause that explains why the barrier wasn’t there or didn’t hold in the first place.
That underlying cause is usually where the real finding sits, and it’s almost always a management system gap rather than an individual failure — a Basic Risk Factor (BRF) in Tripod Beta terminology, covering categories like inadequate procedures, unclear organisational authority, or a training programme that was never updated against the actual range of conditions a job produces. A report that stops at “the operator made an error” has described the Substandard Act. It hasn’t explained anything.
Section 4: Recommendations With an Owner and a Date
“Retrain staff” as a bullet point, with no name attached and no deadline, is not a recommendation an investigation can be held accountable to — it’s a wish. A recommendation that survives a follow-up audit specifies who owns it, by when, and how completion will be verified.
Section 5: Dissemination
This is the section that’s missing most often, and its absence is usually why the same failure quietly repeats somewhere else in the same company. A proper investigation doesn’t just close the file on the one asset, line, or crew where the incident happened — it checks whether the same underlying cause exists anywhere else in the operation, and pushes the finding out to every area where it applies.
Without this step, a technically accurate report can still leave a company exposed. The bearing spec that failed on one line is often the same spec running on three others. The training gap that caused one operator’s error usually exists for every operator trained under the same programme. Section 5 is what turns an accurate finding into an organisational fix.
Why This Matters Beyond the Report Itself
Under Malaysian OSH law, the quality of an investigation isn’t just an internal management concern — DOSH’s expectations for notifiable incidents go beyond confirming that an investigation occurred, to assessing whether it was conducted credibly. A report that stops at section 2 or 3, with no verified recommendations and no dissemination step, is a weaker position to be in if that investigation is ever reviewed externally.
The Practical Check
Pull your last completed investigation report and check it against these five sections. Most companies find they have solid coverage on sections 1 and 2, partial coverage on 3, and little to nothing on 4 and 5. That gap — not a lack of effort, but a lack of structure — is usually the real reason the same type of incident finds its way back onto the same site.
Want your investigation team writing reports that actually reach section 3, 4, and 5 — 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 causation-chain methodology from event to underlying cause. Available in-house and as a public workshop across Malaysia.