What is ICAM?

ICAM stands for Incident Cause Analysis Method. It is a structured incident investigation methodology designed to move past “what happened” and surface the full set of contributing factors that created the conditions for an event, including human factors and systemic organizational issues.

A few practical characteristics define ICAM in the field:

• It is explicitly non-blame oriented. The intent is learning and prevention, not liability assignment.

• It uses structured evidence collection (commonly via PEEPO) and then a disciplined analysis workflow.

• It organizes causal learning into a consistent set of “buckets,” which makes trend analysis and cross-site learning far easier than narrative-only investigations.

This structure is one of ICAM’s biggest advantages: it forces investigation teams to test whether they are treating an incident as a system outcome (defenses, context, management systems), not a single-point failure.

ICAM has a particularly strong footprint in Australia. It was operationalized and scaled through major Australia-linked industries and institutions, especially resources and high-risk operations.

How Haven supports ICAM-based investigations

You can leverage Haven inside an ICAM program by treating ICAM as the investigation governance frame and using Haven as the execution engine that accelerates evidence capture, strengthens causal logic, and improves corrective action quality and learning loops.

Below is a practical mapping that keeps ICAM intact while upgrading throughput, consistency, and defensibility.

Step 1: Define the event, scope, and “what happened”

ICAM intent: Establish a clean event description, boundaries, and an agreed timeline before causal analysis.

How Haven helps

• Haven guides structured witness interviews so you get comparable statements across roles (operator, supervisor, maintenance, contractor). It extracts facts, reconstructs sequences, and flags inconsistencies to resolve early.

• Haven drafts the initial event narrative in ICAM style, anchored to evidence, not interpretation.

• Output artifacts: timeline, event description, evidence register, interview summaries.

Practical ICAM benefit: faster convergence on a single “facts first” timeline, less rework later.

Step 2: Build and stress test the timeline

ICAM intent: Create a defensible sequence of actions, conditions, and defenses.

How Haven helps

• Haven ingests the documents that typically slow down ICAM teams (SOPs, permits, JHAs, maintenance history, training records, telemetry, photos) and links them to timeline points.

• It highlights missing evidence and recommends the next best document or question to close gaps.

• Output artifacts: timeline with citations to source documents, gaps list, and potential inconsistencies between the evidence assets.

Practical ICAM benefit: fewer “timeline debates” because the thread is traceable to source material.

Step 3: Identify “Absent or Failed Defenses”

ICAM intent: Find barrier failures and degradations.

How Haven helps

• Haven RCA methodologies map each timeline inflection to the expected defense layer: engineering controls, admin controls, verification steps, supervision checks, maintenance controls.

• It can propose root causes using structured methods including Fishbone (6Ms), or through its Multithreaded RCA approach. 

• Output artifacts: defense inventory, failed defense statements, control gap candidates.

Practical ICAM benefit: defense analysis becomes systematic, not anecdotal.

Step 4: Identify “Individual or Team Actions” without stopping there

ICAM intent: Capture actions and decisions as inputs to the system, not endpoints.

How Haven helps

• Haven produces action level clarity (who did what, when, with what information and constraints).

• Haven frames actions as “decision points under conditions,” which is the bridge to task conditions and organizational factors.

• Output artifacts: contributing condition hypotheses.

Practical ICAM benefit: you reduce “human error” language and increase causal precision.

Step 5: Identify “Task or Environmental Conditions”

ICAM intent: Surface local conditions shaping performance.

How Haven helps

• Haven extracts and normalizes condition signals across sources (fatigue indicators, staffing levels, shift handovers, time pressure, equipment state, environmental factors, layout constraints).

• It cross checks conditions against procedures and work plans to detect mismatches.

• Output artifacts: task condition list tied to evidence, condition to action linkages.

Practical ICAM benefit: conditions stop being a generic list and become evidenced causal drivers.

Step 6: Identify “Organizational Factors” with specificity

ICAM intent: Find upstream management system breakdowns that are fixable.

How Haven helps

• Haven suggests likely organizational factor domains based on observed patterns, such as change management, training system design, procurement specs, maintenance strategy, contractor governance, permit to work design, supervision capacity, risk assessment quality.

• It prompts for the missing upstream evidence needed to validate each factor, so you do not overreach.

• Output artifacts: organizational factor statements written as control failures (policy, workflow, verification, resourcing, governance), each anchored to concrete evidence.

Practical ICAM benefit: you get fewer vague findings and more “this workflow step failed” conclusions.

Step 7: Corrective actions that align with the Hierarchy of Controls

ICAM intent: Actions that address the causal level, not just symptoms.

How Haven helps

• Haven proposes corrective actions explicitly mapped to the failed defense or organizational factor, and ranks options by expected risk reduction, effort, and time to implement.

• It can enforce “ICAM quality gates” on actions: owner, due date, verification method, leading indicator, and a measurable effectiveness test.

• Output artifacts: CAPA set aligned to causal findings, verification plan, leading indicator plan.

Practical ICAM benefit: stronger CAPA quality and less “train and remind” defaulting.

Step 8: Learn, trend, and prevent, not just close the case

ICAM intent: Feed systemic learning back into the organization.

How Haven helps

• Haven racks corrective action completion and, more importantly, effectiveness. It flags recurring themes across investigations even when incident types differ.

• It can produce early warning signals by correlating small precursor patterns (control degradations, documentation gaps, permit defects) with later serious events.

• Output artifacts: theme heatmaps, recurring organizational factor dashboard, corrective action effectiveness reports.

Practical ICAM benefit: ICAM becomes a learning system, not a compliance report generator.

Conclusion: Haven supercharges your ICAM investigations

The biggest step changes of using Haven to power ICAM investigations are:

• Faster, higher quality witness capture with fewer contradictions

• Evidence synthesis and document cross referencing at scale 

• More actionable organizational factor statements 

• Corrective action effectiveness tracking and recurring pattern detection 

ICAM is a proven methodology. To execute it well, teams need consistent evidence capture, disciplined analysis, high quality write-ups, and action follow-through. This is where Haven can materially strengthen the workflow.