FMEA Action Closure Checklist (Free, PDF/Excel)

0%

0 of 34 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Action definition

The action is written as a specific, measurable change, not 'improve' or 'be more careful'CRITICALThe action targets a named cause or failure mode on a specific FMEA lineCRITICALAn owner is named, with a person rather than a departmentA target date is set and agreed with the ownerThe action type is clear: prevention, detection, or design changeHigh severity lines have an action even when the ratings are below thresholdManagement has resources approved for the action

Implementation evidence

The change is implemented, not just planned or in a purchase requestCRITICALEvidence is attached: drawing, work instruction, photo, change record or test reportCRITICALRelated engineering change or document revision is releasedTooling, fixtures or software changes are validated on the lineOperators and setters have been trained on the new methodGauges or sensors added are calibrated and in the calibration systemSupplier-facing changes are communicated and acknowledged

Effectiveness verification

A trial, run-at-rate or capability study confirms the change worksCRITICALDetection controls are challenged with known bad samples or master partsCRITICALProcess capability or defect data supports the new occurrence ratingNo new failure mode was introduced by the changeVerification covers all shifts and lines that run the processResults are reviewed by someone independent of the action ownerPilot data period is long enough for the failure rate being claimed

Re-rating

Severity is not lowered unless the design or effect actually changedCRITICALNew occurrence rating is justified by prevention evidence, not by hopeNew detection rating is justified by demonstrated detection capabilityThe original ratings and date are kept for historyAction priority or RPN is recalculated and compared with the targetLines still above target are kept open with a new action

Documents and linkage

FMEA revision level and date are updatedCRITICALControl plan reflects the new or changed controlsCRITICALProcess flow diagram and work instructions are consistent with the changeRelated FMEAs on similar parts or lines are checked for the same causeLessons learned are added to the failure mode libraryCustomer approval is obtained where the contract requires notificationThe action status is closed in the tracker with the closing date and approver

Any unchecked critical item means the action should not be closed. A high count of unchecked non-critical items suggests the action is implemented but not yet embedded.

Track FMEA actions alongside ERP change records

Optional: a short review of how actions and change records could be shown together from your existing systems.

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

How to use the checklist

Work through it per action, not per FMEA. Start with the definition: an action that cannot be verified cannot be closed. Then check implementation evidence, effectiveness verification, re-rating and linkage. Critical items are the ones auditors and customers ask about first. Print or export it and attach it to the action record, or use it in the FMEA review meeting to test each closure live.

Why re-rating needs discipline

The easiest way to improve an RPN is to lower the numbers. Severity should not change unless the design or the effect has changed, as it describes the consequence, not the likelihood. Occurrence falls only if a prevention control acts on the cause, and detection improves only if a control demonstrably catches the failure mode. The AIAG and VDA handbook asks teams to assess the effectiveness of actions and to document the results in the optimization step, so keep evidence together with the revised ratings.

Common mistakes

Closing actions on the target date rather than on evidence is the usual failure. Others include updating the FMEA but not the control plan, forgetting to retrain night shift and lowering severity because a detection control was added. A further trap is applying the fix to one line while the same process runs on three other lines.

Do not close actions based on intent or a purchase order
Challenge new detection controls with known bad parts
Check every line and shift that runs the process
Update the control plan in the same change

Frequently Asked Questions

When can an FMEA action be closed?

When the change is implemented, evidence is attached, effectiveness is verified, ratings are re-assessed honestly and the control plan and related documents match. A completed task alone is not enough to close an action.

Can I lower severity after an action?

Only if the design or the effect itself changed, for example by removing a hazard. Adding a control that reduces occurrence or improves detection does not change severity, because severity describes the effect of the failure if it occurs.

How do I verify a new detection control?

Challenge it with known bad samples or master parts, ideally at the limit of acceptable and unacceptable, and record that it rejects them reliably. A control that has never been shown to catch the failure mode should not earn a low detection rating.

Who should approve action closure?

Someone independent of the action owner, commonly the quality engineer or FMEA team leader. For customer-controlled characteristics, the customer may also need to approve changes under the contract or quality agreement.

If actions, change records and inspection data are in your ERP, Netray can help show closure evidence alongside each FMEA line, with read-only access to your records.

Talk to an Expert Explore More Free Tools

Related Tools

Quality & Inspection

More Quality & Inspection tools

See all

FMEA Recommended Action Closure Checklist: Verify Before You Re-Rate