# FMEA Recommended Action Closure Report Template

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

## Short answer

A fill-in document to close out an FMEA recommended action with evidence, revised ratings, control plan updates and sign-off.

## Category

quality

## Industry

Discrete Manufacturing

## Audience

- Quality engineer
- Process engineer
- FMEA facilitator

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### FMEA document number

**Key:** fmea_id

**Type:** text

**Default:** PFMEA-0457 Rev C

#### Part or process

**Key:** part

**Type:** text

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

#### Failure mode

**Key:** failure_mode

**Type:** text

**Default:** Bore diameter oversize

#### Cause addressed

**Key:** cause

**Type:** text

**Default:** Tool wear not detected between gauge checks

#### Action taken

**Key:** action

**Type:** textarea

**Default:** Installed in-process air gauge with automatic tool offset and stop on out-of-limit.

#### Action owner

**Key:** owner

**Type:** text

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

#### Completion date

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Previous S / O / D

**Key:** old_sod

**Type:** text

**Default:** 8 / 6 / 7

#### Revised S / O / D

**Key:** new_sod

**Type:** text

**Default:** 8 / 3 / 3

#### Evidence of effectiveness

**Key:** evidence

**Type:** textarea

**Default:** 30-day run of 4,200 parts, Cpk 1.72, no out-of-limit parts shipped. Challenge test: 10 of 10 seeded oversize parts stopped.

#### Status

**Key:** status

**Type:** select

**Options:**

- Open
- Implemented, verifying
- Closed
- Cancelled

**Default:** Closed

**Blocks:**

#### FMEA Recommended Action Closure Report

**Body:** Company: {{company}}
FMEA: {{fmea_id}}
Part or process: {{part}}
Completion date: {{date}}
Status: {{status}}

#### Failure mode and cause

**Body:** Failure mode: {{failure_mode}}
Cause addressed: {{cause}}

#### Action taken

**Body:** {{action}}

Owner: {{owner}}

#### Rating change

**Table:**

**Columns:**

- Item
- Severity / Occurrence / Detection

**Rows:**

**0:** Previous

**1:** {{old_sod}}

**0:** Revised

**1:** {{new_sod}}

#### Evidence of effectiveness

**Body:** {{evidence}}

#### Documents updated

**Table:**

**Columns:**

- Document
- Updated (Y/N)
- Revision

**Rows:**

**0:** Process flow diagram

**0:** Control plan

**0:** Work instruction

**0:** Gauge or test method

**0:** Training record

#### Approvals

**Signatures:**

- Action owner
- FMEA facilitator
- Quality manager

**Notes:** A starting point for internal use. Adapt to your quality system and customer requirements. Revised ratings should be entered into the FMEA only after the evidence is reviewed.

## Content

**Intro:** An FMEA action is not finished when the work is done; it is finished when the evidence supports the new ratings. This template records that evidence in one page.

**Sections:**

#### How to use the template

**Body:** Fill the fields for the FMEA row you are closing: the failure mode, the cause, what was done and who owned it. Enter the previous and revised ratings and describe the evidence that supports them. Choose a status, then export to PDF or Word and attach it to the FMEA record. One report per action keeps the audit trail clear.

#### What good evidence looks like

**Body:** Evidence should be measurable and independent of opinion: capability data, a challenge test with seeded defects, trial results or a validation report. State sample size and period. For detection actions, a gauge study or challenge test shows real effectiveness. For prevention actions, data over enough production to show a changed occurrence is more convincing than a design review alone.

**Bullets:**

- Link to data files or report numbers, not just a summary.
- Record any residual risk the action does not remove.

#### Closing the loop with other documents

**Body:** An action usually changes more than the FMEA. The process flow, the control plan, work instructions, gauges and training may all need updating. The table in the template lists them so none are forgotten. Customers working to IATF 16949 and AS9100 expect the FMEA, control plan and operating instructions to stay consistent.

#### Common mistakes

**Body:** Closing actions on completion of the task rather than on proof of effect is the most common problem. Others include lowering ratings without data, leaving the control plan unchanged and failing to record who verified the result. Review open actions regularly so they do not age silently.

**Cta:** Netray can help connect FMEA actions to change orders and quality records in your ERP so closure status is visible without manual chasing.

**Faq:**

#### When can I lower an occurrence rating?

**Answer:** When data from the changed process shows reduced frequency, or a proven prevention control addresses the cause. A plan to improve is not enough.

#### Should severity change?

**Answer:** Rarely. Only if the design or process change alters the effect on the customer or next operation. Controls normally affect occurrence or detection.

#### Does every action need a report?

**Answer:** Practices differ. Many sites require closure evidence at least for high-severity or high-priority items. Follow your procedure and customer requirements.

#### Can I attach it to a change order?

**Answer:** Yes. Export to PDF and attach it to the engineering change or corrective action record so the evidence is linked.

## Search terms

fmea action closure template, fmea recommended action report, fmea action tracking form, fmea revised rating evidence, fmea action completion document, pfmea action status report, fmea review sign off form, fmea action plan template

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