Some words carry more organisational weight than they should. “Light work” is one of them. It’s rarely defined precisely, it’s applied by whoever is scoping the job on the day, and once it’s attached to a task, it quietly shapes every downstream decision about resourcing, supervision, and risk assessment depth — often without anyone consciously deciding that a lower standard of scrutiny is appropriate.
This article continues a series built around one real investigation, with equipment, task, and setting fictionalised for confidentiality. It examines two distinct Tripod Beta Basic Risk Factor findings — Organisation and Incompatible Goals — that both trace back to the same “light work” label, and explains why they’re classified separately even though they share a root cause.
The Organisation Finding
Organisation was the largest category of finding in this investigation by volume, and the pattern was consistent rather than isolated. The task was repeatedly normalised as “light works, therefore not dangerous” at multiple points across the causation chain — not a single lapse but a recurring framing. There was a heavy, repeated reliance on the equipment vendor’s own competence as a substitute for independent verification. The vendor’s own technical representative wasn’t present during the risk assessment’s development. The risk assessment itself was built on a previous, similar job’s understanding plus some additional scope, rather than on the specific method statement actually submitted for this job. The consultant preparing the risk assessment didn’t have access to the reference document the method statement pointed to. And the risk assessment was only finalised shortly before the vendor team mobilised to site — leaving little practical room for it to be challenged or revised before work began.
Individually, each of these looks like a minor scheduling or resourcing gap. Stacked together, they describe an organisation whose risk assessment process functions, procedurally, as a formality to complete before mobilisation — rather than a genuine, adequately resourced check on whether the plan actually accounts for the real conditions of the job.
The Incompatible Goals Finding
Incompatible Goals is a different Basic Risk Factor, describing a different mechanism: two legitimate organisational priorities working against each other, with no process forcing a resolution between them. In this case, it showed up at the instruction level rather than the process level. Risk was accepted for a technician working alone, in a congested and noisy area, without anyone explicitly weighing the consequences if something went wrong. Instructions for the task were given without factoring in the risks specific to that particular environment.
The same “light work” label runs through both findings, but the mechanism differs. Organisation describes a broken process — the risk assessment development itself is structurally under-resourced and rushed. Incompatible Goals describes a broken reconciliation — an instruction was issued without anyone checking whether “get this done, it’s minor work” actually matched the physical conditions the task required.
Why the Distinction Matters for the Fix
Treating this as one undifferentiated finding — “there was a poor safety culture around this task” — would be accurate in spirit and useless in practice. Two separate root causes require two separate corrective actions, owned by two different parts of the organisation. The Organisation finding calls for redesigning how risk assessments are resourced, scheduled, and validated against source documents — a process-level fix, likely owned well above the individual site. The Incompatible Goals finding calls for a mechanism that catches conflicts between a task’s stated priority level and its actual physical demands before instructions are issued — closer to the point of task assignment, and potentially owned by a site supervisor or planning lead.
Collapsing both into “safety culture” hands the fix to nobody specific, which in practice means neither gets addressed, and the label “light work” continues doing the same quiet damage on the next job it gets applied to.
The Practical Question
Pick any task at your site currently labelled “light,” “routine,” or “low risk,” and trace how that label was assigned. If nobody can point to a specific process that reviewed the label against the task’s actual physical demands, and nobody can point to a specific check that reconciled the resulting instruction against real site conditions, you likely have both findings sitting in the same place this investigation found them — just waiting for an incident to surface them.
Want your investigation team able to separate a broken process from a broken instruction, and route each finding to the right fix? Cikgu Barrier’s Tripod Beta Incident Investigation programme teaches the full range of Basic Risk Factors, including Organisation and Incompatible Goals, with the classification discipline to keep them distinct. Available in-house and as a public workshop across Malaysia.