Equipment Failure Investigation (RCFA) Report Template
A failure that is fixed but not understood tends to come back. This root cause failure analysis (RCFA) template gives you a one-to-two page report for significant breakdowns: what failed, what it cost, what happened, why, and what will change. Fill it in and export it as PDF or Word.
Fill in
Equipment Failure Investigation (RCFA) Report Template
Equipment Failure Investigation Report
Site: Northfield Plant 2 Report number: RCFA-2026-014 Report date: 2026-10-20 Investigation lead: A. Maintenance Supervisor
1. Asset and failure summary
Asset: PMP-204 Cooling water pump Failure date and time: 2026-10-14 03:40 Failure mode: External leakage Downtime (hours): 9.5
2. Impact
Line 3 stopped for 9.5 hours. No injuries. Estimated repair cost 4,800 including seal kit and labour.
3. Sequence of events
03:40 low pressure alarm. 03:55 operator stopped pump. 04:30 technician found seal leaking. 11:00 seal replaced and pump restarted.
4. Cause analysis (5 Whys)
| Step | Question and answer |
|---|---|
| Why 1 | The mechanical seal leaked and the pump lost pressure. |
| Why 2 | The seal faces were scored. |
| Why 3 | The pump ran dry for a short time during a suction valve closure. |
| Why 4 | The suction valve was closed during a changeover without a pump interlock. |
5. Root cause statement
No interlock or procedure step prevents the pump from running with the suction valve closed.
6. Evidence reviewed
| Evidence | Source | Finding |
|---|---|---|
| Failed part inspection | ||
| Maintenance history | ||
| Operating data and alarms | ||
| Procedures and training |
7. Corrective and preventive actions
| No. | Action | Type (correct or prevent) | Owner | Due date | Status |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 |
8. Effectiveness check
How and when will we confirm the actions worked?
________________________________
Approvals
Edit the examples before use. A 5 Whys chain is a starting method: for complex or safety-related failures, add a cause-and-effect diagram, a fault tree or a team review. Keep the report focused on systems and conditions, not on blaming individuals.
Failure history from your ERP
Optional: we can talk about pulling repeat-failure lists from your ERP work orders to decide which events to investigate.
Optional. The tool and every export work without this. No spam.
How to use the template
Complete the summary and impact within a day while the facts are fresh, then gather the timeline from operators, alarm logs and the work order. Run the cause analysis with the people who know the machine, ask why until you reach a condition you can act on, and write the root cause as a statement of a system gap rather than a person. Finally assign actions with owners and dates and set a check on whether they worked.
- Triggers: safety events, long downtime, repeat failures, high cost
- Preserve the failed part before it is thrown away
- Interview shift staff separately
- Close the report only when actions are verified
The method behind it
The 5 Whys technique asks why repeatedly until the answer is a cause you can control. It is quick and works well for single-chain problems. Failures often have several contributing causes, so check whether each answer is supported by evidence, and branch when it is not. Distinguish the physical cause (seal faces scored), the human or procedural cause (no interlock or step) and the latent cause (design or management system).
Actions that hold
Weak actions are retraining and reminders alone. Stronger ones change the equipment or the process: an interlock, a design change, a PM task, a standard work step or a spares decision. Record both a correction (fix the immediate damage) and prevention (stop the root cause). Link the work order, the PM change and any engineering change number to the report so the history is traceable in the CMMS or ERP.
Common mistakes
Stopping at operator error is the biggest mistake: ask why the system allowed the error. Others include investigating every minor stop, which exhausts the team, and writing actions with no owner or date. Avoid vague root causes such as lack of maintenance. Finally, share lessons with sites that have the same equipment.
Frequently Asked Questions
When should we do a formal RCFA?
Set triggers in advance, such as any safety event, downtime above a set number of hours, a repeat failure of the same mode within a period, or cost above a limit. Trigger rules stop the team from either investigating everything or nothing.
Is 5 Whys enough?
For simple, single-path failures it is often enough. For complex events, add a cause-and-effect diagram or fault tree and involve the people who know the equipment. If the 5 Whys ends at a person, keep asking why the system let it happen.
What is a good root cause statement?
It names a condition or system gap that you can change, and that if removed would have prevented the failure. For example, no interlock prevents the pump running with the suction closed. Avoid vague wording and personal blame.
How long should the report be?
One to two pages is enough for most events. The value is in the actions and the follow-up. Attach photos, trend charts and the work order rather than writing long descriptions.
If you want failure investigations linked to the work orders and equipment history in your ERP, we can show how that works read-only on your own data.
Related Tools
5 Whys Root Cause Analysis Template
Document a problem, the chain of five whys, the root cause and countermeasures in a format you can print or share.
Maintenance & ReliabilityISO 14224 Failure Mode Codes Reference
A searchable table of the three-letter failure mode codes used in ISO 14224 reliability data collection, with plain-English meanings and typical equipment.
Maintenance & ReliabilityMTBF and MTTR From a Failure Log Python Script Generator
Name the columns in your CSV export and get a pandas script that works out MTBF, MTTR, failure count and availability for each asset.
Maintenance & ReliabilityMaintenance and Reliability Maturity Assessment
Ten questions covering work management, preventive maintenance, spares, data and root cause practice, with a score and practical next steps.
More Maintenance & Reliability tools
See all- MTBF and MTTR Worksheet
- TPM Autonomous Maintenance CIL Standard Template
- TPM Autonomous Maintenance Standard Template
- TPM Pillars and Autonomous Maintenance 7 Steps Reference
- Preventive Maintenance Schedule Template
- Maintenance Work Order Template
- Inherent vs Operational Availability Calculator (MTBF, MTTR)
- Spare Parts Criticality Scoring Worksheet
- Maintenance Backlog Calculator (Weeks of Work and Crew Size)