Summary
In short
- A cause code register is a register used in General that holds the standard list of cause codes used in investigations, covering failed defences, human actions, task conditions and organisational factors. It is built against ICAM, Reason model and forms part of the Master Data and Foundations programme.
- Set up once and reviewed yearly. Managed by the safety or quality lead.
- The template holds 11 fields across 3 sections.
- ICAM is incident Cause Analysis Method. An investigation method separating absent or failed defences, individual actions, task conditions and organisational factors.
- It connects to the rest of the library: used by Root Cause Analysis.
What it is
What it is
What is a cause code register?
A cause code register is a register used in General that holds the standard list of cause codes used in investigations, covering failed defences, human actions, task conditions and organisational factors. It is built against ICAM, Reason model and forms part of the Master Data and Foundations programme.
When is a cause code register completed?
A cause code register is completed once at set up, then whenever an entry is added, changed or retired. Set up once and reviewed yearly.
When to use it
When to use it, and when not to
This register is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use it for
- The event or activity this register covers has occurred, or is about to
- The workspace is being set up, or the register needs an entry added or retired
- You are running the Master Data and Foundations programme and this is one of its steps
- A linked record needs this one to exist: used by root cause analysis
Not for
- Site and Location Register, which holds every site, building, area and zone your organisation operates.
- Asset Register, which holds every piece of equipment, machine, vehicle and tool you track.
- Worker Profile, which holds a record for each worker, including role, department, site and start date.
- Anything outside General, which belongs in the workspace that owns that process
Standards
What it is built against
ICAMIncident Cause Analysis Method
An investigation method separating absent or failed defences, individual actions, task conditions and organisational factors.
Reason modelReason organisational accident model
The model behind latent conditions, active failures and defences in depth.
ReasonReason organisational accident model
James Reason's model of how organisational conditions align to allow an accident.
FAQ
Frequently asked questions
What is the cause code register template based on?+
It is built against ICAM, Reason model. ICAM is incident Cause Analysis Method. An investigation method separating absent or failed defences, individual actions, task conditions and organisational factors. Reason model is reason organisational accident model. The model behind latent conditions, active failures and defences in depth.
What sections does the cause code register contain?+
There are 3 sections: identification, definition, governance. Together they hold 11 fields, 6 of which are required.
How many cause code register records should we have?+
This is a singleton. One record per workspace, set up once and maintained, rather than one per event. Other templates refer back to it.
Which programme does the cause code register belong to?+
It is part of Master Data and Foundations. One place for each thing, so a change updates everywhere rather than in eight lists.
Can the cause code register template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.
The agents
What the agents do with it
The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.
Holds the cause code register library against your registers, routes each record to its owner, and keeps the evidence trail together.
Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.
This template lives in General — control tower. The orchestration layer. Registries and engines every other workspace reads from.
Meet General→Sources
Sources
- ICAM — Incident Cause Analysis Method
- Reason model — Reason organisational accident model
- Reason — Reason organisational accident model