Knowella

Repeat Failure Review

Reviews an asset that has failed the same way more than once. Raised on the second failure carrying the same code. Carried out by reliability with maintenance. A repeat failure means the last repair treated the symptom.

KnowMaintainReviewMNT-017Pinned in navigation
Completed by
Carried out by reliability with maintenance
Raised
At the review interval, and after any trigger event

Summary

In short

  • A repeat failure review is a review used in KnowMaintain that reviews an asset that has failed the same way more than once. It is built against ISO 14224 and forms part of the Reliability and Predictive Maintenance programme.
  • Raised on the second failure carrying the same code. Carried out by reliability with maintenance.
  • The template holds 47 fields across 5 sections, with failure history repeating for each entry.
  • ISO is international Organization for Standardization. A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.
  • It connects to the rest of the library: links Asset, Failure Modes; feeds RCA.

What it is

What it is

What is a repeat failure review?

A repeat failure review is a review used in KnowMaintain that reviews an asset that has failed the same way more than once. It is built against ISO 14224 and forms part of the Reliability and Predictive Maintenance programme.

When is a repeat failure review completed?

A repeat failure review is completed at the review interval, and after any trigger event. Raised on the second failure carrying the same code.

When to use it

When to use it, and when not to

This review 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 review covers has occurred, or is about to
  • A new record is needed; each one gets its own ID in the form RFR-2026-000
  • You are running the Reliability and Predictive Maintenance programme and this is one of its steps
  • A linked record needs this one to exist: links asset, failure modes; feeds rca

Not for

  • Equipment Failure Report, which records that an asset has failed and stopped or degraded production.
  • Failure Mode Record, which records how an asset failed, using standard failure mode codes rather than free text.
  • Repair Record, which records what was actually done to fix the asset, including parts replaced and settings changed.
  • Anything outside KnowMaintain, which belongs in the workspace that owns that process

Standards

What it is built against

ISOInternational Organization for Standardization

A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.

FAQ

Frequently asked questions

What is the repeat failure review template based on?+

It is built against ISO 14224. ISO is international Organization for Standardization. A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.

What sections does the repeat failure review contain?+

There are 5 sections: header, failure history, pattern analysis, root cause, cost of repetition. Together they hold 47 fields, 31 of which are required.

How often is a repeat failure review raised?+

A new record is raised at the review interval, and after any trigger event. Each one is given an ID in the form RFR-2026-000, so it can be traced and referenced from other records.

Which programme does the repeat failure review belong to?+

It is part of Reliability and Predictive Maintenance. Intervals set by failure behaviour rather than by the calendar.

Can the repeat failure review 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.

KnowMaintain

Holds the repeat failure review library against your registers, routes each record to its owner, and keeps the evidence trail together.

Ella

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 KnowMaintainasset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.

Meet KnowMaintain

Sources

Sources

  • ISO — International Organization for Standardization

KnowMaintain

Also in Breakdowns

6Browse the whole library
Record

Equipment Failure Report

Records that an asset has failed and stopped or degraded production. Raised at the moment of failure. Completed by the operator or technician. Carries a case ID that runs through repair, cause analysis and prevention.

Record

Failure Mode Record

Records how an asset failed, using standard failure mode codes rather than free text. Completed by the technician after repair. Coded, so patterns can be seen across hundreds of failures rather than read one at a time.

Record

Repair Record

Records what was actually done to fix the asset, including parts replaced and settings changed. Completed at repair. Carried out by the technician. Builds the asset history that makes the next failure faster to diagnose.

Record

Temporary Repair Record

Records a repair that is not permanent, with an expiry date and a plan for the proper fix. Raised whenever a temporary fix is made. Approved by the maintenance manager. Temporary repairs that nobody tracks are how equipment quietly becomes unsafe.

Record

Production Impact Record

Records what the failure cost in lost output, scrap and late orders. Completed by production after the event. Gives maintenance the business case for prevention, in the language finance responds to.

Record

Breakdown Debrief

A short review straight after a significant breakdown, capturing what happened and what would have helped. Run within 24 hours. Led by the maintenance supervisor with everyone involved. Fast and informal, and often catches things a formal investigation misses.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.