FMEA Step-by-Step

Failure Mode and Effects Analysis (FMEA) is one of the most widely used risk assessment methods in GMP systems.

It is used to:

• identify potential failures

• evaluate risk impact

• prioritize mitigation efforts

• support risk-based decisions

FMEA is especially useful when organizations need structured evaluation of:

• process failures

• equipment risks

• contamination pathways

• human error potential

• control effectiveness

When applied correctly, FMEA helps organizations prioritize attention before failures occur.

What FMEA Is

FMEA is a structured method used to evaluate:

• how a process or system can fail

• what impact those failures may have

• how effectively failures can be detected or controlled

The method evaluates potential failure modes using three common elements:

• severity

• likelihood (or occurrence)

• detectability

These elements are then used to support prioritization of risk.

FMEA does not eliminate risk.
It supports consistent and traceable evaluation of risk.

FMEA Is Not a Scoring Exercise Alone

FMEA is often reduced to completion of scoring tables.

This weakens the method.

The purpose of FMEA is not to generate numbers.
The purpose is to:

• identify meaningful failure pathways

• evaluate effectiveness of controls

• support better decisions

When scoring becomes the primary objective:

• teams focus on numbers rather than failures

• assumptions replace process understanding

• mitigation becomes superficial

Effective FMEA depends on quality of analysis, not scoring complexity.

Step 1 — Define the Scope Clearly

FMEA begins with defining the scope.

The assessment should clearly identify:

• the process or system being evaluated

• assessment boundaries

• assumptions

• intended use of the assessment

Poorly defined scope creates:

• inconsistent scoring

• missing failure modes

• unclear mitigation ownership

Scope should remain narrow enough to support meaningful analysis while broad enough to capture relevant interactions.

Step 2 — Identify Failure Modes

Failure modes describe how a process, system, or activity could fail.

Examples include:

• incorrect parameter settings

• contamination events

• incomplete data review

• equipment malfunction

• operator error

Failure modes should reflect realistic operational conditions rather than theoretical possibilities alone.

Weak failure mode identification leads to weak downstream analysis.

Cross-functional involvement is often necessary to ensure realistic identification of failure pathways.

Step 3 — Evaluate Severity

Severity evaluates the impact if the failure occurs.

Severity should consider impact to:

• patient safety

• product quality

• data integrity

• compliance status

Severity should reflect consequence, not probability.

A common failure occurs when severity is reduced because occurrence is considered unlikely.

This weakens risk prioritization.

Severity should remain linked to impact rather than assumptions about likelihood.

Step 4 — Evaluate Occurrence

Occurrence evaluates how likely the failure is to happen.

Evaluation should consider:

• historical performance

• process capability

• known variability

• operational complexity

Occurrence scoring should be supported by available data whenever possible.

Assumed or arbitrary occurrence scoring weakens defensibility and creates inconsistent prioritization.

Step 5 — Evaluate Detectability

Detectability evaluates how effectively existing controls can identify the failure before impact occurs.

This includes evaluation of:

• monitoring systems

• alarms

• review activities

• automated controls

• operator checks

Detectability should reflect actual detection capability, not assumed control effectiveness.

A control that exists but consistently fails to identify problems should not receive strong detectability scoring.

Detectability should reflect realistic control performance.

Step 6 — Prioritize Risk

Organizations commonly prioritize FMEA outcomes using:

• Risk Priority Numbers (RPN)

• risk matrices

• predefined escalation thresholds

Prioritization should support decisions regarding:

• mitigation

• escalation

• additional review

• monitoring expectations

Prioritization systems should remain aligned with defined acceptance criteria and escalation thresholds.

Scoring only becomes meaningful when linked to defined decision pathways.

Step 7 — Define Mitigation Actions

Mitigation actions should address:

• reduction of severity where possible

• reduction of occurrence

• improvement of detectability

Mitigation should remain proportional to:

• actual impact

• uncertainty

• operational feasibility

Superficial mitigations that do not meaningfully reduce risk weaken the effectiveness of the assessment.

Step 8 — Reassess Residual Risk

After mitigation, residual risk should be reassessed.

Organizations should evaluate whether:

• controls are effective

• remaining exposure is acceptable

• escalation is still required

• uncertainty remains significant

Residual risk acceptance should remain traceable and justified.

Mitigation does not automatically justify acceptance of remaining exposure.

Common Failures in FMEA

Recurring weaknesses include:

• scoring without process understanding

• inconsistent scoring logic

• unrealistic detectability assumptions

• excessive focus on RPN values

• failure to reassess after changes

• mitigation actions disconnected from actual failure modes

These failures reduce FMEA to a documentation exercise rather than a decision-support tool.

How Inspectors Evaluate FMEA

They assess whether:

• failure modes are realistic

• scoring logic is consistent

• controls reflect actual operations

• mitigation actions are meaningful

• reassessment occurs after changes

A common concern arises when FMEA documents appear complete, but operational decisions do not reflect the assessment.

This indicates weak integration between QRM and operational systems.

Relationship to Lifecycle Governance

FMEA should remain subject to ongoing review.

Assessments may require reassessment when:

• process changes occur

• deviations trend upward

• controls fail

• operational understanding evolves

Risk assessments should evolve with system knowledge over time.

What Good Looks Like

Effective FMEA systems demonstrate:

• realistic failure mode identification

• consistent scoring logic

• meaningful mitigation actions

• traceable reassessment of residual risk

• alignment between assessment and operations

In these systems:

• prioritization remains defensible

• controls remain proportional

• risk decisions remain explainable

FMEA functions as a decision-support framework, not merely a scoring exercise.

Regulatory Perspective

Regulators do not expect mathematically perfect FMEA systems.
They expect structured and defensible reasoning.

Effective FMEA should demonstrate that organizations can:

• identify meaningful failure pathways

• evaluate controls realistically

• prioritize risks proportionally

• reassess decisions when operational understanding changes

During inspection, weak FMEA systems often become visible when documented risks do not align with actual process behavior, recurring deviations, or control effectiveness.