# FMEA Recommended Action Tracking Report Template

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

## Short answer

A fill-in report that records one FMEA recommended action with owner, due date, verification evidence, before and after ratings, and sign-off.

## Category

quality

## Audience

- Quality engineer
- Process engineer
- Quality manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### FMEA number and revision

**Key:** fmea_id

**Type:** text

**Default:** PFMEA-0412 Rev C

#### Part or process

**Key:** item

**Type:** text

**Default:** Housing 48213, Op 40 bore finish

#### FMEA line reference

**Key:** line

**Type:** text

**Default:** Line 17

#### Failure mode

**Key:** failure_mode

**Type:** text

**Default:** Bore diameter oversize

#### Cause addressed

**Key:** cause

**Type:** text

**Default:** Insert wear not detected between checks

#### Action type

**Key:** action_type

**Type:** select

**Options:**

- Prevention
- Detection
- Design change
- Prevention and detection

**Default:** Prevention

#### Recommended action

**Key:** action

**Type:** textarea

**Default:** Add tool life counter to the program so the insert changes every 250 parts, and add in-process probe check of the bore every 25 parts.

#### Action owner

**Key:** owner

**Type:** text

**Default:** J. Rivera, Process Engineer

#### Target date

**Key:** target

**Type:** date

**Default:** 2026-11-30

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- In progress
- Implemented, awaiting verification
- Verified and closed
- Cancelled

**Default:** In progress

#### Verification evidence

**Key:** evidence

**Type:** textarea

**Default:** Capability study on 50 consecutive parts, Cpk target 1.67. Probe challenged with master rings at both limits.

#### Severity before

**Key:** s_old

**Type:** number

**Default:** 8

#### Occurrence before

**Key:** o_old

**Type:** number

**Default:** 5

#### Detection before

**Key:** d_old

**Type:** number

**Default:** 6

#### Occurrence after

**Key:** o_new

**Type:** number

**Default:** 3

#### Detection after

**Key:** d_new

**Type:** number

**Default:** 3

#### Report date

**Key:** date

**Type:** date

**Default:** 2026-10-20

**Blocks:**

#### FMEA Recommended Action Report

**Body:** Company: {{company}}
FMEA: {{fmea_id}}
Part or process: {{item}}
FMEA line: {{line}}
Report date: {{date}}

#### Risk being addressed

**Body:** Failure mode: {{failure_mode}}
Cause: {{cause}}
Action type: {{action_type}}

#### Recommended action

**Body:** {{action}}

Owner: {{owner}}
Target date: {{target}}
Status: {{status}}

#### Verification evidence

**Body:** {{evidence}}

#### Ratings before and after

**Table:**

**Columns:**

- Rating
- Before
- After
- Basis for change

**Rows:**

**0:** Severity

**1:** {{s_old}}

**2:** {{s_old}}

**3:** Unchanged unless the effect or design changed

**0:** Occurrence

**1:** {{o_old}}

**2:** {{o_new}}

**3:** Prevention evidence, capability or defect data

**0:** Detection

**1:** {{d_old}}

**2:** {{d_new}}

**3:** Demonstrated detection capability

#### Linked documents updated

**Table:**

**Columns:**

- Document
- Updated (Y/N)
- Revision
- Date

**Rows:**

**0:** FMEA

**0:** Control plan

**0:** Process flow diagram

**0:** Work instruction

**0:** Gauge or calibration record

#### Approvals

**Signatures:**

- Action owner
- FMEA team leader
- Quality manager

**Notes:** Severity is shown as unchanged by default because adding a control does not change the effect of a failure. If severity genuinely changes, record why in the basis column. This is a general format, not a customer-specific or AIAG form.

## Content

**Intro:** A long FMEA sheet is a poor place to track what happened to one action. This template gives each recommended action a one-page record: what risk it addresses, who owns it, what evidence shows it worked, how the ratings changed and which documents were updated.

**Sections:**

#### How to use the template

**Body:** Fill one report per FMEA action. Identify the FMEA, revision and line, then copy the failure mode and cause so the report stands alone. Write the action as a specific change with an owner and target date. When the action is complete, add the evidence, enter the new occurrence and detection ratings, record which linked documents were updated and obtain sign-offs. Export to PDF or Word and attach it to the FMEA record or the change file.

#### What good evidence looks like

**Body:** Evidence should match the claim. A lower occurrence rating needs prevention evidence, such as a capability study, defect data over a meaningful period or proof that an error-proofing device blocks the failure. A better detection rating needs proof that a control rejects bad parts, for example a challenge test with known nonconforming samples. Photos, change records, revised work instructions and calibration certificates all help. Avoid evidence that only shows the action was started.

**Bullets:**

- Capability or defect data for occurrence changes
- Challenge test results for detection changes
- Released drawing, work instruction or program revision
- Training records for the people affected

#### Keeping the documents aligned

**Body:** The FMEA, the control plan and the process flow should describe the same process. The table in the report lists the documents to confirm after every closed action. The AIAG and VDA approach expects FMEA results to be documented and communicated, and customer audits often compare the control plan line by line with the FMEA. Where the action touches a customer-approved characteristic, check whether a notification or approval is required before the change goes live.

**Cta:** If your actions and engineering changes live in your ERP or QMS, Netray can discuss ways to generate these reports from existing records with read-only access.

**Faq:**

#### Does this replace the FMEA sheet?

**Answer:** No. It supports the FMEA by recording the detail of one action. The FMEA still holds the failure chains and ratings, and should show the action, its status and the revised ratings once the action is verified.

#### Why is severity unchanged by default?

**Answer:** Severity describes the effect of the failure if it occurs. Adding a prevention or detection control does not make the effect less serious, so only a design change that removes or reduces the effect justifies a lower severity.

#### Can I use this for customer-specific forms?

**Answer:** Use it as an internal record. Some customers require their own action format or portal entry, and you should follow those, using this report as supporting evidence.

#### How many reports do I need?

**Answer:** One per recommended action. For a long FMEA, start with the highest severity and highest action priority lines, and keep the reports with the revision history of the FMEA.

## Search terms

fmea action plan template, fmea recommended action template, fmea action tracking sheet, fmea action report format, fmea corrective action form, fmea action status report, fmea action log excel, fmea follow up form

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