FMEA Recommended Action Tracking Report Template
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.
Fill in
FMEA Recommended Action Tracking Report Template
FMEA Recommended Action Report
Company: Acme Precision Ltd FMEA: PFMEA-0412 Rev C Part or process: Housing 48213, Op 40 bore finish FMEA line: Line 17 Report date: 2026-10-20
Risk being addressed
Failure mode: Bore diameter oversize Cause: Insert wear not detected between checks Action type: Prevention
Recommended action
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.
Owner: J. Rivera, Process Engineer Target date: 2026-11-30 Status: In progress
Verification evidence
Capability study on 50 consecutive parts, Cpk target 1.67. Probe challenged with master rings at both limits.
Ratings before and after
| Rating | Before | After | Basis for change |
|---|---|---|---|
| Severity | 8 | 8 | Unchanged unless the effect or design changed |
| Occurrence | 5 | 3 | Prevention evidence, capability or defect data |
| Detection | 6 | 3 | Demonstrated detection capability |
Linked documents updated
| Document | Updated (Y/N) | Revision | Date |
|---|---|---|---|
| FMEA | |||
| Control plan | |||
| Process flow diagram | |||
| Work instruction | |||
| Gauge or calibration record |
Approvals
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.
Generate action reports from your ERP records
Optional: a short review of how change and quality records could be turned into these reports automatically.
Optional. The tool and every export work without this. No spam.
How to use the template
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
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.
- 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
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.
Frequently Asked Questions
Does this replace the FMEA sheet?
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?
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?
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?
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.
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.
Related Tools
FMEA Recommended Action Closure Checklist
A checklist to confirm an FMEA action is implemented, verified with evidence, re-rated honestly and carried into controls and documents before it is closed.
Developer ToolsFMEA Risk Ranking SQL Query Generator
Generates ANSI-style SQL for an FMEA table: open high-risk lines, overdue actions, risk roll-up by process step and a cumulative Pareto of RPN.
Quality & InspectionFMEA Prevention and Detection Controls Reference
A searchable list of common prevention and detection controls, with what each addresses and where it falls short, for use when completing FMEA and control plan columns.
Quality & InspectionFMEA Process Maturity Assessment
Ten questions that score how well your organisation runs FMEA, from team and scope to rating discipline, action closure and linkage to the control plan.
More Quality & Inspection tools
See all- SAP QM Process Capability Cp Cpk Calculator
- SAP QM Lot Rejection Rate, PPM and Sigma Level Calculator
- SAP QM Gauge R&R Study Calculator
- SAP QM Cp and Cpk Capability Calculator
- Job Shop Material Certification Log Worksheet
- Job Shop First Piece Inspection Sign-Off Template
- Job Shop Scrap and Rework Cost Calculator
- Master Data Audit Sample Size Calculator
- Data Quality Sigma Level Calculator