What this is
What is a root cause failure analysis trigger?
What is a root cause failure analysis trigger?
It is a screening record, not the investigation itself. It scores a failure's safety, food safety, environmental and cost consequence, checks whether it is a repeat, and produces a decision on how much investigation effort the event actually warrants. The full investigation, if one is needed, happens in a separate RCA record.
How is it different from a root cause analysis?
A root cause analysis works out why a failure happened. This trigger decides whether that work is justified in the first place, and if so, at what depth — a quick debrief, a 5 Why, a full RCA, or a cross-functional RCA with external support. Skipping the trigger means the depth decision is made informally, by whoever is standing nearest the failed asset.
Why does the trigger score potential outcome as well as actual outcome?
Because a failure that caused no harm can still have been one step away from a serious one. The Potential For Much Worse Outcome field exists precisely so that a near-miss with high potential consequence doesn't screen itself out just because nothing bad happened this time.
Scope
When is a root cause failure analysis trigger required?
This record is a single screening step in the Reliability and Predictive Maintenance programme. Using it to do the investigation itself, or to track a failure mode's history over time, produces records that are hard to report on later.
Use this template when
- A significant failure has just occurred and no screening decision exists for it yet
- A new record is needed; each one gets its own ID in the form RCFT-2026-000
- You are running the Reliability and Predictive Maintenance programme and this trigger is one of its steps
- A linked record needs this one to exist first — it links the Case and, where warranted, triggers the RCA
- An MTBF Review or condition-monitoring alert has flagged a deteriorating trend that needs a screening call
Do not use it for
- Equipment FMEA, which works through how an asset could fail, what the effect would be and how likely it is to be detected, before any failure has happened.
- Reliability Centred Maintenance Study, which decides the ongoing maintenance strategy for a failure mode, not whether one specific event needs investigating.
- MTBF Review, which reviews the trend in failure frequency over a period, rather than screening a single event against it.
- Bad Actor Report, which tracks an asset or failure mode with a poor repeat history over time, once that pattern is established.
- Anything outside KnowMaintain, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 14224 requirements does this satisfy?
ISO 14224 sets the taxonomy failure data must fit into, but it does not set the threshold for when a failure earns an investigation — that judgement is what this trigger formalises against the standard's structure.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 14224 | Failure events must be classifiable against a specific asset and equipment taxonomy before they are recorded as reliability data. | Header |
| ISO 14224 | Consequence severity — safety, environmental and production — must be scored before a decision is made on investigation depth. | Screening criteria |
| ISO 14224 | Repeat failures and their occurrence frequency must be captured against the asset, not assessed as a one-off event. | Screening criteria |
| ISO 14224 | Potential consequence, not only realised consequence, must inform the failure's criticality classification. | Screening criteria |
| ISO 14224 | Any related reliability review that identified a deteriorating trend must be cross-referenced against the triggering event. | Related records |
| ISO 14224 | The investigation method chosen must be proportionate to the scored consequence and assigned to a named lead. | Decision |
| ISO 14224 | The rationale for the investigation level, including a decision that none is required, must be recorded and approved. | Decision |
What it does not cover
- A screening score with no rationale text, which leaves the next reviewer no way to tell whether 'None required' was a judgement call or a shortcut.
- A Repeat Failure flag that contradicts the Occurrences In 12 Months count, which undermines every other score entered on the same form.
- An Investigation Level of Full RCA with no Method Required selected, which hands the lead a mandate but no technique to carry it out.
- A Critical-rated asset with Total Cost Of Failure left blank, which removes half the evidence the threshold decision is supposed to weigh.
- A closed trigger with no Maintenance Manager signature, which leaves the screening decision unowned if it is challenged later.
Global
Root Cause Failure Analysis Trigger requirements by country
The screening decision this record makes sits alongside, not instead of, whatever statutory investigation duty already applies to the event.
ISO 14224
Defines the taxonomy and failure-mode vocabulary reliability data must use, but leaves the investigation-trigger threshold to the operator.
The standard will not tell you when to investigate — that judgement call is what this template exists to formalise.
RIDDOR 2013, regulation 4 (dangerous occurrences)
Certain failure types — pressure system failure, lifting equipment collapse, specified dangerous occurrences — carry a mandatory reporting duty regardless of what this screening decides.
A 'none required' outcome here does not excuse a RIDDOR report if the event qualifies; the two obligations run in parallel, not in sequence.
OSHA 29 CFR 1910.119(m)
Facilities covered by process safety management must investigate incidents with, or with the potential for, a catastrophic release within 48 hours of occurrence.
For covered processes, that 48-hour clock starts regardless of the score this form produces — the trigger can add rigour, but it cannot replace the statutory duty.
How to complete it
How to complete a root cause failure analysis trigger, step by step
Filling in every field is mechanical. The judgement calls below are what decide whether the screening decision holds up when someone re-reads it after the next failure.
This is a near-miss judgement, not a description of what happened. A short, cheap outage on a critical asset can still score high here if a slightly different failure mode would have stopped the whole line — the field exists to stop severity being judged only by luck.
This distinguishes a control that failed from a situation where no control existed at all. The two point to very different investigation depths, and conflating them is how a genuine control failure gets waved through as unavoidable wear.
5 Why suits a single, fairly obvious causal chain. Fishbone and fault tree suit failures with several plausible contributing factors. ICAM and TapRooT are proportionate when the failure touches organisational or systemic factors, not just a component. Picking by habit rather than by what is genuinely unclear wastes the escalation the screening just earned.
The rationale field is free text and unscored, which makes it easy to skip. It is also the only place that explains, months later, why a failure that later turned out to matter was screened out at the time — and whether that reasoning still holds.
What auditors find
Most common root cause failure analysis trigger findings
Patterns worth checking before a screening decision is treated as settled.
| Finding | Clause | What fixes it |
|---|---|---|
| Downtime Hours is filled in but Total Cost Of Failure is left blank on an asset rated Critical. | ISO 14224 | Require a cost estimate, even a rough order of magnitude, whenever Asset Criticality is Critical — cost is half the trigger threshold. |
| Repeat Failure is marked 'No' while Occurrences In 12 Months shows three or more. | ISO 14224 | Cross-check the occurrence count against the repeat-failure flag before the screening score is accepted. |
| Investigation Level is set to 'None required' with no text entered in Rationale For Level Chosen. | ISO 14224 | Make the rationale field mandatory whenever the level is None required or Quick debrief — that is exactly the outcome an audit will ask about. |
| Method Required is left blank after Full RCA or Cross functional RCA has been chosen. | ISO 14224 | Force a method selection once the investigation level reaches Full RCA, so the assigned lead isn't improvising a technique on day one. |
| MTBF Review ID is never populated even when the trigger clearly follows a deteriorating trend review. | ISO 14224 | Surface the asset's open reliability alerts automatically at the point of raising, rather than relying on the raiser to remember the reference. |
| Safety and Food Safety Consequence are both scored 'None' with no cross-check against any linked incident or product hold record. | ISO 14224 | Validate consequence scores against linked incident and hold records before the screening total is finalised. |
Case in point
Case in point: the bearing that scored itself out of an investigation
A conveyor bearing failed in the filling area, causing twenty minutes of downtime. Safety Consequence was scored None, Downtime Hours was low, and Repeat Failure was marked No because nobody checked the asset's history — this was, in fact, the third bearing failure on that conveyor in eight months. Investigation Level came out as 'None required'.
The fourth failure took the line down for a full shift and triggered a proper RCA, which found the same misalignment fault each time. Three screening decisions had each been individually defensible and collectively wrong, because the Occurrences In 12 Months field was never populated against the asset's actual record.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- MNT-053
- Archetype
- Record
- Record ID
- RCFT-2026-000
- Scoring
- Investigation level
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 14224
- Links
- Links Case; triggers RCA
- Tags
- Reliability, Investigation
- Sections
- 4
- Fields
- 34
- Follow up fields
- 0
- Repeating sections
- 0
- Links out
- 6
Header
13 fieldsTrigger ID*
Auto sequence. Format RCFT-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Asset*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Match The Effort To The Consequence
Investigating a failed light fitting for a day and a bearing that stopped the line for twenty minutes is the wrong way round. This decides which failures get real analysis.
Case ID*
Thread key
Failure Report ID
Links to MNT-013 Case ID
Screening criteria
11 fieldsSafety Consequence*
- None4 pts
- First aid3 pts
- Lost time1 pt
- Fatality potential0 pts
Food Safety Consequence*
- None4 pts
- Minor3 pts
- Product hold1 pt
- Recall potential0 pts
Environmental Consequence*
- None4 pts
- Minor3 pts
- Reportable1 pt
- Major release0 pts
Downtime Hours*
Total Cost Of Failure
Asset Criticality*
Repeat Failure*
- No3 pts
- Yes0 pts
Occurrences In 12 Months
Failure Was Unexpected*
- No2 pts
- Yes0 pts
Existing Controls Should Have Prevented It*
- No2 pts
- Yes0 pts
Potential For Much Worse Outcome*
Same reasoning as safety incidents. Investigate on potential, not just on what happened.
- No3 pts
- Yes0 pts
Related records
1 fieldMTBF Review ID
The review that flagged the deteriorating trend.
Links to MNT-051 Review ID
Decision
9 fieldsInvestigation Level*
None, quick debrief, 5 Why, full RCA or cross functional RCA with external support.
- None required3 pts
- Quick debrief2 pts
- 5 Why2 pts
- Full RCA1 pt
- Cross functional RCA0 pts
Method Required
Lead Assigned
Debrief ID
Links to MNT-019 Debrief ID
RCA ID
Links to FDN-013 RCA ID
Target Completion
Rationale For Level Chosen
Maintenance Manager*
Signature*
MNT-053 · record IDs look like RCFT-2026-000 · Links Case; triggers RCA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping the screening honest — checking repeat history, chasing the rationale field, matching method to consequence — is the work that actually slips.
Holds the trigger against the asset's full failure history, so Repeat Failure and Occurrences In 12 Months are never left to memory.
Cross-checks Safety Consequence and Potential For Much Worse Outcome against any linked incident record before a screening total is accepted.
Flags Food Safety Consequence scores that disagree with an open product hold, so a screening decision never quietly undercuts a food safety event.
Coordinates the crew across these workspaces, rolls open triggers and their rationale into one view, and holds every write for your approval before it touches a record.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Root Cause Failure Analysis Trigger definitions and key terms
- RCFT
- Root Cause Failure Analysis Trigger — this template's own record type, the screening step that decides whether a failure gets investigated at all.
- ICAM
- Incident Cause Analysis Method — a structured investigation technique for tracing organisational and system factors behind a failure, not just its immediate cause.
- TapRooT
- A proprietary root cause investigation methodology built around a fixed set of causal factor categories, often specified for major incident investigations.
- Bad actor
- An asset or failure mode with a repeat history bad enough to warrant its own tracking record, rather than a one-off investigation.
- MTBF
- Mean Time Between Failures — the reliability metric an MTBF Review tracks; a deteriorating MTBF trend is one of the events that can trigger this screening.
FAQ
Frequently asked questions about root cause failure analysis trigger
Does a 'none required' outcome still need to be recorded?+
Yes. The screening decision, including a decision not to investigate, is the record. Without it there is no evidence the failure was ever assessed against the criteria, only that nothing visible followed it.
What happens if the screening score and the chosen investigation level disagree?+
The score is a guide, not an automatic outcome — Investigation Level is a separate field the maintenance manager sets deliberately. Where the two disagree, the Rationale For Level Chosen field should explain why the manager overrode the score.
Who can change the Investigation Level once it is set?+
In practice this sits with the maintenance manager, who also provides the sign-off signature. Changing it after the fact should leave a trail, since the level chosen determines who gets assigned and how much time they are given.
Does this template replace the RCA itself?+
No. It decides whether an RCA — or a lighter method such as a 5 Why or debrief — is warranted, and at what level. The investigation itself is carried out and recorded separately, referenced back here by its RCA ID.
How does a repeat failure change the screening outcome?+
A repeat failure scores lower on the Repeat Failure field, which pushes the outcome toward a deeper investigation level, because a recurring pattern is exactly what a one-off screening decision is prone to miss.
What if the failure turns out worse than first scored?+
The screening record isn't locked once consequences develop further — Status can move back to In progress and the consequence fields revisited, since a delayed food safety hold or a secondary failure changes the basis the original decision was made on.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Reliability and Predictive Maintenance
Root Cause Analysis
Finds out why something happened rather than who was involved
Equipment Failure Report
Records that an asset has failed and stopped or degraded production
Failure Mode Record
Records how an asset failed, using standard failure mode codes rather than free text
Repair Record
Records what was actually done to fix the asset, including parts replaced and settings changed
Temporary Repair Record
Records a repair that is not permanent, with an expiry date and a plan for the proper fix
Repeat Failure Review
Reviews an asset that has failed the same way more than once
More in Reliability
Equipment FMEA
Works through how an asset could fail, what the effect would be and how likely it is to be detected
Reliability Centred Maintenance Study
Decides the right maintenance strategy for each failure mode, from run to failure through to condition monitoring
MTBF Review
Reviews mean time between failures for an asset or asset class over a period
PM Optimization Review
Reviews whether preventive tasks are set at the right frequency, using actual failure and finding data
Spares Criticality Review
Decides which spare parts must be held on site based on lead time and asset criticality
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 14224 — Collection and exchange of reliability and maintenance data for equipment
- RIDDOR 2013 — Reporting of Injuries, Diseases and Dangerous Occurrences Regulations, reg. 4
- OSHA 29 CFR 1910.119(m) — Process safety management, incident investigation
- ISO 9001 cl.10.2 — Nonconformity and corrective action
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.