1) Why incident investigation is a mandatory pillar of safety
No safety system is perfect from day one. The difference between a weak organization and a mature organization is not whether incidents occur—but how the organization responds after an incident.
- Hide – blame – move on → the incident will return, often with more severe consequences.
- Investigate thoroughly – fix the system – improve continuously → every incident becomes a lesson that makes the site safer.
For a Project Manager (PM), investigation is not about finding someone to blame. It is about preventing recurrence, protecting people, protecting the project, and protecting the PM’s professional credibility.
2) Five non-negotiable principles for PMs
Before launching an investigation, PMs must align on these five core principles:
- Human safety is the absolute priority — investigation must never interfere with rescue or medical response.
- No premature personal blame — evaluate system factors first.
- Facts must be evidence-based — not assumptions or emotions.
- Investigate near-misses like real accidents — outcomes often depend on “one second”.
- Investigation without improvement is meaningless — the end goal is system change.
3) Task 1 — Secure the scene for investigation
3.1 When must PMs activate scene preservation?
PMs must instruct scene preservation when any of the following occur (minor or major):
- Workplace injury, technical incident, equipment failure with injury potential.
- Collapse, tip-over, falling objects, slipping, fire, electric shock, asphyxiation, lifting incidents.
- Near-miss with potential for severe consequences.
3.2 How to secure the scene properly
- Isolate the incident area within an allowed scope.
- Do not move equipment/evidence unless required for rescue.
- Restrict access to unauthorized persons; control entry/exit.
- Record the time of incident and scene conditions (lighting, weather, shift, etc.).
Note: Securing the scene does not mean “freezing the entire site”. Preserve only the elements directly linked to the incident.
4) Task 2 — Collect objective, complete information
After ensuring safety and stabilizing the scene, the PM must organize data collection under the principle: complete – accurate – objective – timely.
4.1 Mandatory information groups
- Scene data: photos/videos; equipment condition; positions of people/materials/structures; abnormal traces.
- People data: statements from involved persons; witness accounts; shift/working hours; fatigue indicators (if any).
- System records: JSA for the task; issued PTW; training records; applicable procedures/technical instructions; supervision logs.
4.2 The PM’s role during data collection
The PM does not replace HSE, but remains accountable for investigation output:
- Ensure collection is complete — no cherry-picking “convenient” facts.
- Protect psychological safety of reporters; do not pressure anyone to “admit fault”.
- Control timeline — long delays cause data loss and reduce improvement effectiveness.
5) Task 3 — Root cause analysis
This is the core of Pillar 5. Many organizations fail because they stop at surface-level conclusions. PMs must ensure the team reaches root causes that explain: “Why did it happen?” and “What prevents it from happening again?”
5.1 Common mistakes PMs must avoid
- “The worker was careless.”
- “They were overconfident.”
- “They didn’t comply.”
5.2 Do it right: separate two cause groups
A) System causes (always evaluate first):
- Was the JSA missing steps, hazards, or controls?
- Were controls realistic in actual execution—or “paper compliance”?
- Was training delivered to the right people, for the right job, at the right time?
- Was supervision sufficient and timely? Were there “supervision gaps”?
- Was PTW implemented in substance, not formality?
B) Individual execution causes (within system context):
- Was the worker trained adequately before the task?
- Did they work outside authorized scope or use incorrect methods?
- Were schedule/time pressures pushing people to skip safety steps?
INDUSVINA principle: Individual errors often reflect deeper system gaps. Fixing the system is the sustainable way to reduce incidents.
6) Task 4 — Update the system after investigation
Investigation only matters if it leads to change. After identifying root causes, the PM must drive system updates toward: better procedures – stronger forms – more practical training – tighter supervision.
6.1 Update procedures & forms
- Adjust method statements / work procedures.
- Update JSA for similar tasks; add missing control steps.
- Revise PTW conditions if applicable.
6.2 Update training
- Add new lessons (case study) into training content.
- Retrain relevant crews; verify understanding and correct practice.
- Reinforce items that were previously skipped or misunderstood.
6.3 Update the supervision plan
- Increase inspection frequency for high-risk work.
- Adjust supervision assignments—especially during shift change or schedule acceleration.
- Add new control checklists aligned to root causes.
7) Task 5 — Share lessons learned & prevent recurrence
A mistake is truly corrected only when the whole team learns from it. PMs should share lessons under this principle: short – clear – no shaming – prevention focused.
- Run a toolbox talk: Incident → Causes → New controls.
- No naming-and-shaming; never create fear of near-miss reporting.
- Reinforce: “Report early to protect your teammates and yourself.”
8) INDUSVINA mindset: “Safety tuition”
INDUSVINA treats every incident as “tuition” paid by the company—through time, costs, reputation, and sometimes human health.
That is why INDUSVINA rejects vague “general lessons learned”. We require: evidence – root causes – corrective actions – preventive actions – effectiveness tracking.
9) Conclusion for Project Directors
For PMs, incident investigation is not a side task. It protects people, protects schedule, and protects professional credibility. A strong PM is not someone with “no incidents”, but someone whose system becomes safer after every incident.
Implementation tip: Apply Pillar 5 as a mandatory post-incident flow after every accident/near-miss: secure the scene → collect evidence → analyze root causes → update JSA/PTW/training → share lessons learned.
