Quality & InspectionFree templatePDF, Excel, Word exportDiscrete Manufacturing

FMEA Recommended Action Closure Report Template

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.

Fill in

Live preview
Download:

FMEA Recommended Action Closure Report Template

FMEA Recommended Action Closure Report

Company: Acme Precision Ltd FMEA: PFMEA-0457 Rev C Part or process: Housing 48213, Op 40 bore finishing Completion date: 2026-10-20 Status: Closed

Failure mode and cause

Failure mode: Bore diameter oversize Cause addressed: Tool wear not detected between gauge checks

Action taken

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

Owner: J. Rivera, Process Engineering

Rating change

ItemSeverity / Occurrence / Detection
Previous8 / 6 / 7
Revised8 / 3 / 3

Evidence of effectiveness

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.

Documents updated

DocumentUpdated (Y/N)Revision
Process flow diagram
Control plan
Work instruction
Gauge or test method
Training record

Approvals

Action owner / Date
FMEA facilitator / Date
Quality manager / Date

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.

FMEA actions inside your ERP

Optional discussion on tracking FMEA actions alongside change and quality records.

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

How to use the template

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

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.

  • 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

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

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.

Frequently Asked Questions

When can I lower an occurrence rating?

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?

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?

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?

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

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