# FMEA Lessons Learned and Carry-Over Review Template

> Source: https://netray.co/tools/fmea-lessons-learned-carryover-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A structured document to capture what escaped, why the FMEA missed it and which lines and controls need updating.

## Category

quality

## Industry

Manufacturing

## Audience

- Quality engineer
- Reliability engineer
- Program manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Reference

**Key:** ref

**Type:** text

**Default:** LL-2026-017

#### Date

**Key:** date

**Type:** date

**Default:** 2026-11-10

#### FMEA document

**Key:** fmea_id

**Type:** text

**Default:** PFMEA-0412 rev C

#### What happened

**Key:** event

**Type:** textarea

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

#### Was the failure in the FMEA

**Key:** missed

**Type:** select

**Options:**

- Yes, rated correctly
- Yes, rated too low
- No, not identified

**Default:** Yes, rated too low

#### Why the FMEA missed it

**Key:** why

**Type:** textarea

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

#### FMEA and control plan lines to update

**Key:** changes

**Type:** textarea

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

#### Other parts or lines affected

**Key:** scope

**Type:** textarea

**Default:** Housing family B, lines 3 and 5.

#### Owner

**Key:** owner

**Type:** text

**Default:** A. Rao

**Blocks:**

#### FMEA Lessons Learned Record

**Body:** Company: {{company}}
Reference: {{ref}}
Date: {{date}}
FMEA document: {{fmea_id}}
Owner: {{owner}}

#### 1. Event

**Body:** {{event}}

#### 2. Was it in the FMEA

**Body:** {{missed}}

{{why}}

#### 3. Updates required

**Body:** {{changes}}

#### 4. Other products and processes to check

**Body:** {{scope}}

#### 5. Update checklist

**Table:**

**Columns:**

- Item
- Done
- Date
- Initials

**Rows:**

**0:** PFMEA lines revised

**0:** Control plan revised

**0:** Work instruction updated

**0:** Special characteristics register updated

**0:** Similar FMEAs reviewed for same cause

**0:** Rating scale or template improved

#### Approvals

**Signatures:**

- Owner
- Quality manager
- Process owner

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

## Content

**Intro:** 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.

**Sections:**

#### How to use the template

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

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

**Faq:**

#### When should we write one?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

fmea lessons learned template, fmea carry over review, fmea update after field failure, lessons learned form quality, fmea living document review, fmea revision record, escape analysis template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json