Process FMEA Review Audit

It checks whether the PFMEA is complete, current, and internally consistent. The audit walks through document control, failure mode analysis, risk rating validation, action tracking, and the final review outcome. It is designed to surface deficiencies such as missing process steps, weak cause statements, incorrect RPN math, and open actions without owners.

Use it during PFMEA creation, scheduled management review, process changes, customer complaint follow-up, and before launching a new product or process. It is also useful after a control plan update or a process deviation that suggests the PFMEA may be stale. If the process has not changed and the document is already under formal review cadence, the audit can be lighter but should still confirm closure of open items.

A cross-functional reviewer is best, typically quality, manufacturing, engineering, and operations with process knowledge. The person running the audit should understand the process flow, the control plan, and the organization’s severity, occurrence, and detection ranking rules. For special characteristics or customer-specific requirements, include the relevant process owner or quality lead.

The right cadence depends on process risk and change frequency, but it should be reviewed whenever the process, product, equipment, or controls change. Many teams also schedule periodic reviews to confirm the PFMEA still matches the current process flow and that action items are closed. A stale PFMEA is a common non-conformance because it no longer reflects actual risk or controls.

Yes, it supports the core expectations behind structured PFMEA review: clear process scope, failure mode logic, cause and effect linkage, risk evaluation, and action follow-up. It is also compatible with quality management system practices under ISO 9001:2015 because it helps verify documented information, risk-based thinking, and corrective action tracking. You can customize the ranking language to match your internal or customer-required method.

Common misses include failure modes written as vague symptoms instead of process-step-specific conditions, causes that are not tied to the failure mode, and controls that are listed but not actually capable of detecting or preventing the issue. Teams also miss incorrect RPN calculations, outdated revision references, and action items that were closed without evidence. Another frequent problem is forgetting to update the PFMEA after a process change or customer complaint.

Yes, the template is meant to be adapted to your organization’s approved severity, occurrence, and detection scales and your action threshold rules. You can also add customer-specific special characteristics, plant-specific approval steps, or links to your control plan and process flow diagram. Keep the ranking definitions consistent so reviewers do not score the same risk differently from one audit to the next.

An ad-hoc review often misses traceability because comments are discussed verbally and not checked against the document structure. This template forces a repeatable walk-through of scope, ratings, actions, and closure evidence, which makes findings easier to assign and track. It also helps prevent the common problem of a PFMEA that looks reviewed but still contains outdated or unsupported entries.

Attach whatever proves the action was implemented and is working, such as revised work instructions, updated control plan entries, training records, inspection results, or photos of the changed process condition. If the action changes detection or prevention, include evidence that the new control is in place and linked to the relevant failure mode. Closure should not rely on a status update alone.