When you need it
Use during design or operational review when a system's credible failures need structured examination. Revisit after configuration changes or experience reveals a previously unrecognized mechanism or dependency.
XLSX /
AI tools and documents for engineering and project management.
Failure Mode and Effects Review
Trace credible failure modes through local and system effects to existing controls and improvement actions.
How to use this templateThis Excel template contains prepared working sheets and completion notes on a separate sheet. Enter your project data and review the completed workbook before use.
This editable workbook helps you organise project information. Check any included formulas, assumptions and results before use; it does not replace professional review.
The form prepares a separate brief; it does not fill the Word or Excel file.
Read product descriptions in your language. The Word and Excel template files are in English.
Only selected pages are shown. This is not the complete template. The full editable Word or Excel file is supplied with purchase.
Learning
How to use this template
What it helps you decide
The review traces how loss of a function can affect the wider system. It tests whether existing controls address the actual failure chain and directs improvement without relying on unexplained numerical rankings.
How to complete it
- Define analysis boundaries and operating modes from the functional breakdown. Enter Function and Failure mode separately so the required service and its loss remain clear.
- Record Cause / evidence and Local / system effect as distinct links. Compare Existing control with actual effectiveness evidence and identify Control limitations.
- Set Proposed action and Review basis using the owner's approved method. Preserve uncertain mechanisms and obtain specialist review rather than treating a default score as risk acceptance.
Who prepares and reviews it
A reliability or systems engineer facilitates preparation with design, operations and maintenance specialists. Relevant safety experts review serious effects; the asset owner approves the method and actions within the applicable project authority.
A mistake to avoid
Combining cause, failure mode and consequence into one vague phrase prevents the team from identifying which control interrupts the chain and which gap remains unresolved.
Illustrative example
Illustrative example: a cooling system review examines loss of flow from a failed pump. The team distinguishes pump stoppage, possible causes and effects on connected equipment, then checks whether the listed alarm actually detects the condition. The owner decides what control verification or improvement is required.
Document contents
- Document control and decision owner
- Evidence, scope and applicability
- Analysis boundary
- Failure chain
- Controls and detectability
- Action prioritization
- Open points, competent review and decision
Required inputs
- Project / asset identity, assessment date, scope and authorized decision owner
- Verified source documents with exact revision and record locators
- System functional breakdown and boundaries
- Design and operating information
- Failure history and manufacturer evidence
- Approved analysis criteria and competent participants
Practical tools.
Professional judgment.
Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.
Prepare project brief