Pull ten Job Hazard Analyses from almost any Malaysian worksite and a pattern shows up quickly: a meaningful number of them could be swapped between two completely different tasks without anyone noticing. “Wear appropriate PPE. Follow the SOP. Use proper tools and equipment.” These control measures aren’t wrong, exactly. They’re just so generic they could apply to nearly any job on site — which means they apply, in any useful sense, to none of them.
This article continues a series built around one real investigation, with equipment, task, and setting fictionalised for confidentiality. The finding at the centre of this article falls under Tripod Beta’s Procedure Basic Risk Factor: a management-system-level gap in how a controlling document was written, not a one-off situational condition.
What the Investigation Found
The control measures inside the Job Hazard Analysis for this task were too generic. They didn’t capture the components that actually mattered for this specific job — the physical reach required to access both sides of the component being worked on, or the fact that ground-level positioning wouldn’t be sufficient to complete the task as scoped. A JHA that should have specified a working platform, or a two-person team, or a defined maximum-reach limit, instead offered language broad enough to apply to almost any maintenance task on the site.
Why “Generic” Isn’t a Minor Flaw
A JHA that reads the same for a twenty-minute bolt-tightening job as it does for a task requiring a working platform and a rigging plan isn’t a document that’s slightly under-detailed. It’s a document that has stopped doing the one thing a JHA exists to do: translate a general hazard awareness into task-specific controls that someone executing the work can actually act on.
The practical consequence shows up exactly where it did in this case. When a control measure is vague enough to be technically satisfied without addressing the real hazard, the person doing the work has to fill in the missing specificity themselves — improvising a solution to a problem the JHA should have already solved. That improvisation is where preconditions like “normal practice” and “light work” framing take root, because nobody above the technician’s level has actually specified what “doing this safely” requires for this particular task.
Where This Finding Sits in the Causation Chain
It’s worth being precise about the level at which this finding sits, because it’s a common point of confusion. A generic JHA is not, on its own, a Precondition — it’s not a situational or psychological state affecting a specific individual on a specific day. It’s a finding about a management process: how the document was developed, reviewed, and approved before the job ever started. That makes it an Underlying Cause, categorised under the Procedure BRF, and it means the fix has to happen at the level of how JHAs get written and reviewed generally — not through a one-time correction to this single document.
Why This Keeps Happening Even With a JHA Process in Place
Most sites already have a JHA requirement, a template, and a sign-off step. The gap this case exposes isn’t the absence of a process — it’s a review step that checks whether a JHA exists and is signed, without checking whether its content is actually specific to the task it’s meant to cover. A JHA can satisfy every procedural requirement on a checklist and still fail to describe a single real hazard particular to the job in front of it.
What a Genuine Fix Looks Like
Closing this gap doesn’t mean writing longer JHAs. It means building a review step that asks a narrower question: could this exact document be reused, unchanged, for a materially different task? If the honest answer is yes, the JHA hasn’t captured what makes this task specific, and it needs task-level detail before it’s approved — physical access requirements, minimum crew size, equipment-specific handling notes — not more general safety language.
The Practical Check
Take your site’s JHA for the most physically demanding routine task you have, and compare it against the JHA for one of your simplest routine tasks. If the control-measure sections read almost identically, that’s the same gap this investigation found — and it’s usually invisible until an investigation goes looking for it specifically.
Want your team writing JHAs and risk assessments specific enough to actually control the hazard, not just satisfy a template? Cikgu Barrier’s HIRARC Training Malaysia programme teaches practical, task-specific risk assessment that holds up to real scrutiny, not just an audit checklist. Available in-house, public workshop, and virtual delivery.