Almost every incident investigation produces recommendations. Almost none of them prevent the next incident. This is not an exaggeration. It is a pattern visible in virtually every corrective action register in Malaysian industry: a set of specific responses to the incident that just occurred, closed within 90 days, and filed — while the management conditions that produced that incident continue unchanged.
The Incident-Specific Response: Why It Fails
An incident-specific recommendation addresses the specific conditions of the specific incident: this machine, this location, this team, this moment. Examples: “Install additional guarding on Machine B3.” “Retrain the three technicians involved.” “Repair the lighting at Pump Station 7.” These are not wrong — they are often necessary. But they are insufficient as primary corrective actions for incidents caused by management system failures, because they do not address those failures. They address the symptoms.
Two years from now, a different machine in a different area with a different team will develop the same guarding gap — because the management system that allowed Machine B3 to operate without adequate guarding has not been changed.
The Quality Test for Investigation Recommendations
Apply this test: if this recommendation had been implemented ten years ago — before this site, this machine, this team — would it have prevented this incident? An incident-specific recommendation fails this test. A systems-level recommendation passes it. A recommendation that changes the management condition that produced the failure will prevent any future incident produced by that condition.
Three Levels of Recommendation: An Example
An incident: inadequate machine guarding caused a contact injury. The guarding standard had not been reviewed since commissioning fifteen years ago. No system existed to trigger guarding reviews when equipment was modified.
Level 1: Incident-Specific Response
“Install additional guarding on Machine B3.” Addresses this machine. Does not address the fifteen-year-old standard or the absence of a review system.
Level 2: Broader Incident Response
“Review machine guarding on all similar equipment against current standards.” Addresses this class. Does not address the management system that allowed standards to age without review.
Level 3: Systems-Level Recommendation
“Implement a machine guarding standards management system that: (a) defines applicable standards for each equipment category, (b) triggers a review whenever equipment is modified or standards are revised, and (c) requires independent verification before equipment returns to service after modification.” This changes the management condition. A facility that implements it will not have an unreviewed guarding standard in 2041.
Why Malaysian Investigations Produce Incident-Specific Recommendations
Investigation methodology. Most sites use tools not designed to trace causation to the management system level. Without reaching that level, investigations cannot produce systemic recommendations.
Closing pressure. DOSH timelines and management pressure create incentives for recommendations achievable quickly. Systems-level changes take longer and are harder to define as closed.
Accountability avoidance. A systems-level recommendation implies a management system failed, implicating the people responsible. Incident-specific recommendations attribute the incident to a physical condition or individual behaviour — safer for the investigator.
The Regulatory Context Under OSHA 2022
OSHA 2022 strengthens DOSH’s authority to assess whether corrective actions following serious incidents are adequate, and creates personal liability for directors and managers when oversight failures are identified. A corrective action register full of incident-specific responses is not evidence that the management condition has been addressed. It is evidence that the incident has been responded to.
Develop the Investigation Capability to Produce Systemic Recommendations
Producing systems-level recommendations requires investigations that reach the systems level — methodology that does not allow the investigation to close at a plausible immediate cause, but requires it to trace the causation chain to the management system failure that produced that cause.
Cikgu Barrier’s Incident Investigation Basics builds structured investigation methodology that reaches beyond the individual to the system. For the most rigorous framework available, Tripod Beta Incident Investigation is the standard.