Quality & InspectionFree worksheetPDF, Excel, Word exportManufacturing

FMEA Recommended Actions Tracker Worksheet

An FMEA is only as good as the actions that follow it. This tracker keeps each recommended action, owner and due date next to the before and after ratings, so you can show risk really went down.

Download:
Failure modeRecommended actionOwnerDue dateStatusS beforeO beforeD beforeRPN beforeS afterO afterD afterRPN afterRPN reduction
240
72
168
252
108
144
120
16
104
150
54
96
Total RPN before
762
Total RPN after
250
Total reduction
512
Overall RPN reduction
67.2%

Re-score only after the action is implemented and verified. Severity normally changes only if the design or process is changed to remove the effect. Check your own action rules; many customers now require Action Priority rather than RPN thresholds.

Turn FMEA actions into ERP change orders

Optional: we can link actions to ECOs and control plan revisions in your ERP.

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

How to use the tracker

Copy each high-priority failure mode from your FMEA, write the action in specific terms and assign a named owner with a due date. Enter the original S, O and D, then enter the planned or actual new ratings once the action is done. The sheet calculates RPN before, RPN after and the reduction. Update status weekly in your quality meeting.

  • One action per row
  • Use verbs and measurable results
  • Never re-score before verification
  • Export for management review

How RPN is calculated

RPN is severity times occurrence times detection, each on a 1 to 10 scale, giving a value from 1 to 1000. Prevention actions reduce occurrence; detection actions reduce detection rating. Severity drops only when the failure effect itself is designed out. The tracker shows RPN reduction so you can compare actions, but RPN alone can mislead because different combinations produce the same product.

RPN versus Action Priority

The AIAG-VDA FMEA handbook replaced RPN thresholds with Action Priority (high, medium, low), which weights severity first. A failure with severity 9 and low occurrence can matter more than a mid-severity item with the same RPN. Use this tracker for the arithmetic and your Action Priority table for deciding which items need action first.

Common mistakes

Closing an action without evidence is the most common failure. Attach the work instruction, gauge study or control plan revision that proves the change. Another mistake is lowering detection by adding inspection when prevention was possible. Finally, avoid actions such as retrain operator without a documented method to verify effectiveness.

Frequently Asked Questions

When can I change the severity rating?

Only when the failure effect changes, for example by a design change or by removing the hazard. Detection and prevention controls do not reduce severity. Many teams lock severity unless engineering confirms a real change.

Is a lower RPN always better evidence?

It is useful, but not sufficient. A drop must be backed by verified controls and, ideally, by data such as lower scrap or better capability. Also check severity first, since a high-severity item may need action even at a low RPN.

How often should we review actions?

Weekly or biweekly during launch, monthly afterward. Overdue items should be escalated to the process owner. Keep closed actions in the file as evidence for audits.

Can I use this with Action Priority?

Yes. Add your AP level in the action text or a separate note, and use the RPN columns for comparison. The sheet does not replace your customer-specific AP table.

If actions should flow into ERP change orders and control plans, Netray can wire that in. Ask for a short review.