Quality & InspectionFree templatePDF, Excel, Word exportManufacturing

FMEA Lessons Learned and Carry-Over Review Template

An FMEA should change whenever reality surprises you. This template records field failures, line-by-line FMEA updates and the check across similar products, so the lessons actually reach the next program.

Fill in

Live preview
Download:

FMEA Lessons Learned and Carry-Over Review Template

FMEA Lessons Learned Record

Company: Acme Precision Ltd Reference: LL-2026-017 Date: 2026-11-10 FMEA document: PFMEA-0412 rev C Owner: A. Rao

1. Event

Customer reported 14 pumps with seal leakage traced to bore oversize at OP20.

2. Was it in the FMEA

Yes, rated too low

Occurrence was rated 3 based on old tooling. New insert grade wears faster.

3. Updates required

OP20 bore oversize: raise occurrence to 5, add tool life counter, update control plan frequency.

4. Other products and processes to check

Housing family B, lines 3 and 5.

5. Update checklist

ItemDoneDateInitials
PFMEA lines revised
Control plan revised
Work instruction updated
Special characteristics register updated
Similar FMEAs reviewed for same cause
Rating scale or template improved

Approvals

Owner / Date
Quality manager / Date
Process owner / Date

Starting point for your own procedure. Link each record to the CAPA or 8D that triggered it, if one exists.

Trigger FMEA reviews from ERP returns

Optional: we can flag returns and NCRs that should prompt an FMEA update.

Optional. The tool and every export work without this. No spam.

How to use the template

Complete one record per significant event, such as a customer return, internal escape, audit finding or near miss. State whether the failure was in the FMEA and, if it was, why it was rated too low. List the exact FMEA and control plan lines to change and every other product that shares the cause. Export to PDF or Word and file it with the FMEA revision.

  • Reference the CAPA or 8D number
  • Be specific about which lines change
  • Check sibling products
  • Close the checklist before approving

Why the FMEA missed it

There are only three possible answers: the failure was not identified, it was identified but the occurrence or detection rating was wrong, or the control was assumed effective but was not. Each answer leads to a different fix: broaden the brainstorm, correct the evidence behind ratings, or validate the control. Recording the reason builds a pattern over time.

Carry-over and living FMEAs

A living FMEA is updated after changes in process, equipment, material, supplier or field data. Carry-over from an earlier part saves time but only if the team reviews what differs. The review checklist in this template prompts the common gaps: control plan, work instruction, characteristics register and sibling FMEAs.

Common mistakes

Filing the lesson without changing the FMEA is the most frequent problem. Another is fixing only the part that failed, leaving identical risks on the next line. Finally, do not blame the team in the record; focus on the system gap that allowed the escape.

Frequently Asked Questions

When should we write one?

After any customer complaint, internal escape of consequence, audit finding or process change that affects risk. Many plants also run a quarterly review of scrap and returns against the FMEA.

Is it the same as a CAPA?

No. A CAPA fixes the cause of a specific problem. This record makes sure the FMEA and related documents learn from it. They should reference each other.

Who owns it?

The FMEA owner, usually a process or quality engineer. The quality manager approves, and the process owner confirms the control plan and work instructions have changed.

Do customers ask for this?

Some customer-specific requirements call for FMEA updates after field issues, and auditors look for evidence that FMEAs are living documents. Check your own customer requirements.

If returns and NCRs sit in your ERP, Netray can trigger these reviews automatically. Ask for a short review.