FMEA Recommended Action Closure: Evidence, Re-Rating, and Audit-Ready Documentation

The auditor scrolls down to row 47 of a PFMEA, points to a recommended action marked “Closed — 03/14”, and asks one question: how do you know it worked? If the answer is a calendar invite from the action review meeting and a checkbox in a tracking spreadsheet, the audit finding writes itself. Closure under AIAG-VDA is a verified reduction in S/O/D ratings backed by evidence stored where the next person can find it. This post walks through the closure record practitioners build during the action, not the day before the audit.

What FMEA Action Closure Means Under AIAG-VDA

The AIAG-VDA 7-step process treats Step 7 (Results Documentation) as the close-out gate, not a clerical wrap-up. The standard requires the team to re-rate severity, occurrence, and detection after the action is implemented and to document the reasoning behind any change. A closed action is one where (1) the implementation is verified by evidence the auditor can review, (2) S/O/D ratings have been re-evaluated honestly, and (3) the connected artifacts — process flow diagram, control plan, work instructions — reflect the new state.

What auditors look for in IATF 16949 surveillance audits and customer audits is consistent: an action with closure date, an evidence trail tied to that action, a re-rate with justification, and downstream documents that match. When any of those four are missing or stale, the action is “closed” only on paper.

Step 1: Define Closure Criteria When You Assign the Action

The most common closure failure starts before the action is implemented: the recommended action is written as a task list rather than a verified outcome. Compare these two:

• Task-shaped: “Install poka-yoke sensor on station 30 to detect missing torque-converter washer.”
• Outcome-shaped: “Station 30 sensor verified to detect missing washer with zero escape rate over a 30-day production run; integration to PLC reaction plan confirmed by fault injection test.”

The outcome-shaped version is the closure criterion. It tells the action owner what evidence will close the loop and gives the auditor a checkable claim. Write it into the recommended action field at assignment time; don’t backfill it after the work is done.

For severity-driven actions on critical characteristics, the closure criterion typically references a capability study, a fault-injection result, or a documented design change. For occurrence-driven actions, the criterion usually references a Cpk improvement (1.33 minimum, 1.67 for critical characteristics) or a defect-rate trend over a defined sample. For detection-driven actions, the criterion references a measurement system analysis (GR&R) on the new gauge or a verification run on the new inspection method.

Step 2: Collect Evidence as the Action Progresses

Treat evidence collection as part of the action work, not a closeout chore. By the time the action is ready to close, the file should already exist. Common evidence types by action category:

Store the evidence in the QMS (or whatever document control system the auditor will be looking in). File-share links die with reorgs; embedded photos in spreadsheets get stripped on export. The closure record needs a stable reference path.

Step 3: Re-Rate S/O/D Honestly

Re-rating is where closure discipline lives or dies. Three rules from practice:

• Severity rarely changes. Severity describes the consequence of the failure mode at the customer or end-user level. Adding controls doesn’t change what happens when the failure occurs; it changes how often or whether it reaches the customer. Severity drops only when a design change eliminates or reduces the consequence (e.g., a redundant circuit so a single-point loss of function becomes degraded function instead). If your recommended action is a process control or inspection, severity stays where it was.
• Occurrence reduces only with cause-side evidence. Lower occurrence means the cause is less likely. That requires data: a Cpk that improved, a defect rate that dropped over a defined production volume, a poka-yoke that prevents the cause from arising. “We added a check” is not occurrence evidence — it’s detection.
• Detection reduces only when the new control demonstrably catches the failure. Manual 100% visual inspection is rarely better than D=5; humans miss defects at predictable rates. Automated inspection with a verified algorithm and test images can earn D=2–3, but only with a documented validation. Don’t move detection from 7 to 3 because you wrote “added 100% inspection” in the action column.

For a deeper look at how revised ratings affect priority — particularly for severity 9–10 items where AP can stay High even after detection improvements — see the post on interpreting FMEA results when high RPN doesn’t indicate the biggest risk. The action priority and RPN calculator handles the AIAG-VDA AP lookup once you have the revised ratings.

Step 4: Build the Closure Record

The closure record is the artifact the auditor reviews. Six fields, in this order, are what carries water in practice:

Some teams add a seventh field: a sustainment date six or twelve months out for re-checking the action’s effectiveness. This catches the failure mode where an error-proof gets bypassed, a gauge drifts, or a procedure decays.

Step 5: Update Connected Artifacts

An action that changes a process step but leaves the process flow diagram, control plan, and work instructions on the old version creates audit findings on three different documents. The closure isn’t complete until the linked documents reflect the change.

• Process Flow Diagram: add or revise the operation step, update operation numbers if needed
• Control Plan: update the control method, frequency, sample size, gauge, and reaction plan for the affected characteristic
• Work Instructions / Standardized Work: revise the SOP if operator behavior changed
• Special Characteristics designation: if the action introduced a new CC or SC, flag it on the FMEA and propagate to the control plan and operator visual aids

The PFD-PFMEA-Control Plan trio drifts faster than any other set of quality documents. The post on keeping the PFD, PFMEA, and Control Plan in sync covers the maintenance discipline that prevents this drift.

FMEA Closure Failures Auditors Find

From practitioner experience and IATF surveillance audit findings, the recurring closure failures are:

1. Action marked closed, no evidence file. The closure tracker says completed; the QMS has no associated record. Easy finding.
2. Re-rated occurrence with no data. Occurrence dropped from 6 to 3 with no Cpk study, no defect-rate data, no statistical justification.
3. Severity reduced without a design change. Severity went from 8 to 5 because “the new control catches it” — the auditor will note that controls don’t change severity.
4. Connected control plan unchanged. FMEA shows new prevention control; control plan still references the old detection control. Trio drift.
5. No reviewer sign-off. The re-rate was applied by whoever updated the spreadsheet; no quality engineer reviewed the justification.
6. Severity 9–10 item with reduced AP from a detection-only action. AIAG-VDA AP logic keeps severity 9–10 items at High AP regardless of detection improvements. If your AP dropped from H to M with only a detection-side action, the AP table was misapplied.

When Re-Rating Doesn’t Reduce Risk

Sometimes the action runs to completion, the evidence is collected, and the AP still doesn’t move. That’s a real outcome — not a failure of the closure process. Common cases:

• Inspection added to a severity 8 item: AP often stays Medium or High because AIAG-VDA prefers prevention for severity-7-and-above failure modes
• Operator training as the only action: training-only changes typically don’t move occurrence below the 6–7 range without a verification mechanism
• Procedure change without measurement: no Cpk delta, no occurrence reduction

When this happens, the closure record should document what the action achieved (e.g., “detection rating improved from 7 to 5; occurrence and severity unchanged”) and feed back into the action plan: a follow-up action focused on prevention or design change is the right next step. For framing the next action under capacity constraints, see prioritizing FMEA actions when resources are limited.

Closure as a Continuous Discipline

The closure record is the artifact, but the discipline is the practice of writing closure criteria into the action at assignment, collecting evidence as the work progresses, and re-rating with the same scrutiny as the original rating. Teams that treat closure as a one-time event before the audit produce file-stuffer FMEAs. Teams that treat it as continuous quality management produce living documents — and audit findings drop accordingly.

The AIAG & VDA FMEA Handbook covers the closure documentation requirements in Step 7; the ASQ FMEA reference aligns with the same closure-and-verification model.