Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics -> Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
SOP Plug-and-play starting point Quality Assurance

SOP: Quality Risk Management Process and Tool Selection

A plug-and-play SOP for running a quality risk management assessment end to end under ICH Q9(R1): proportionality tiers, how to pick FMEA, FTA, HACCP, or risk ranking, the four QRM phases, sign-off authority by risk level, and a filled specimen.

Document type: SOP

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This is a ready-to-use SOP. It governs how a quality risk management (QRM) assessment gets run, from the decision that one is needed through to a closed, accepted, and reviewed outcome. It does not replace the tool-specific worksheets (an FMEA worksheet, a HACCP CCP determination, a risk register); it is the procedure that tells a team which tool to reach for and how to carry the assessment through all four ICH Q9(R1) phases so the result is defensible. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it.

Document control header

FieldEntry
Document titleQuality Risk Management Process and Tool Selection
Document number<<FILL: SOP-ID, e.g. SOP-QA-009>>
Version<<FILL: version, e.g. 1.0>>
Effective date<<FILL: effective date>>
Supersedes<<FILL: prior version or "New">>
Document owner<<FILL: role, e.g. Head of Quality Assurance>>
Applies to<<FILL: sites / departments in scope>>

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> identifies when a formal quality risk assessment is needed, selects a method proportionate to the decision, runs the assessment through identification, analysis, and evaluation, decides on risk control, communicates the outcome, and sets a review trigger. It exists so that risk-based decisions across the site, validation scope, deviation depth, supplier tiering, change acceptability, follow one consistent, auditable process rather than a different improvised process each time.

2. Scope

This procedure applies to any GxP decision that depends on a judgment about risk to product quality, patient safety, or data integrity, across development, technology transfer, commercial manufacturing, and discontinuation. It covers both the fully documented, cross-functional assessments (FMEA, FTA, HACCP, risk ranking) and the shorter documented risk discussions used for low-impact decisions. It does not define the technical content of any single tool’s worksheet, those are governed by the tool-specific templates referenced in section 5.3, or the criteria for when a risk assessment is mandatory for a particular activity type, which is set by <<FILL: SOP-ID or policy reference for QRM triggers, e.g. change control, deviation management>>.

3. Responsibilities

RoleResponsibility
Risk ownerRequests or is assigned the assessment, provides technical input, drives risk-reduction actions to closure, and holds the residual risk once accepted.
FacilitatorRuns the assessment session, keeps scoring anchored to the defined scales, prevents one voice from dominating, and is not the person who owns the outcome.
Subject matter expertsProvide failure modes, causes, hazards, and the basis for scores from their functional area.
Quality AssuranceConfirms the method and tier are appropriate, approves the scoring rationale, and holds sign-off authority for risk acceptance per section 6.
Management / quality councilReceives escalated high risks, resources risk-reduction actions, and accepts residual risk that remains high after mitigation where that authority is required.

4. Definitions

  • Hazard: anything that could act as a source of harm.
  • Harm: injury to health, including harm that flows from a product losing quality or from the product not being available.
  • Risk: how likely harm is to occur, taken together with how bad that harm would be. Not probability alone.
  • Severity, occurrence, detectability: the three dimensions scored in most GxP risk tools; detectability is inverted (a high score means harder to detect).
  • Residual risk: whatever risk remains once controls and mitigations are in place.
  • Risk acceptance: a deliberate, documented decision by a person with the authority to do so, to live with the residual risk.
  • Proportionality: the ICH Q9(R1) principle that the effort, formality, and documentation applied to a risk decision should match the significance of that decision, not be fixed at one level for everything.

5. Procedure

5.1 Set the proportionality tier

Before choosing a tool, classify the decision into a tier. Use the table below as the default; document any deviation from it with a stated rationale.

TierTypical decisionMinimum expectation
1, low impactMinor SOP wording change, non-critical label update, a scheduling or non-GxP tool changeA short documented discussion between the process owner and QA; conclusion and rationale in the change or deviation record itself
2, moderate impactConfiguration change to a non-release system, a new supplier for a non-critical material, a moderate deviation with a plausible bounded causeRisk ranking and filtering, or a short-form FMEA scoped to the affected steps only
3, high impactNew GxP system supporting release decisions, a change to a sterilizing or aseptic step, a recurring critical deviation, establishing established conditions for a filingFull FMEA, FTA, or HACCP with a cross-functional panel, following the rest of this procedure in full

A Tier 1 decision does not need to proceed past this step; record the conclusion and stop. Tier 2 and Tier 3 continue to section 5.2.

5.2 Select the method

Work through these questions in order. Stop at the first one that applies.

Are you comparing many dissimilar items to decide where resources go, rather than analyzing one process in depth?
↓
Yes → risk ranking and filtering. No → continue.
↓
Is there one specific step where a control must hold, and losing it makes the hazard unrecoverable downstream (for example a sterilizing filtration or terminal sterilization step)?
↓
Yes → HACCP-style hazard analysis and CCP determination. No → continue.
↓
Do the failure modes interact, or does the undesired event need a combination of conditions to occur?
↓
Yes → fault tree analysis. No → continue.
↓
Can you list the process or system steps and analyze each one for failure modes independently?
↓
Yes → FMEA / FMECA, the default for Tier 2 and Tier 3 decisions. No → run a preliminary hazard analysis or a structured what-if first to map the hazards, then return to this question.

Record the method chosen and the reason in the assessment header. Q9(R1) does not mandate a particular tool; it names FMEA, FMECA, FTA, HACCP, HAZOP, PHA, and risk ranking and filtering as examples and leaves the choice to the team, provided the choice and its rationale are documented.

5.3 Assemble the team and set the boundary

  1. Name a facilitator who does not own the decision the assessment will inform.
  2. Name the risk owner and at least one subject matter expert from each function closest to the failure mode or hazard, not only the function requesting the assessment.
  3. Write down the scope and boundary before scoring: which process steps, systems, or unit operations are in and which are explicitly out.
  4. Pull the tool-specific template that matches the method chosen in 5.2 (<<FILL: internal template references>>, or use /templates/assessment-validation-risk-fmea for a computerized-system FMEA and /templates/worksheet-haccp-ccp-determination for a CCP determination) and agree the scoring scales and, where the method uses RPN, the action thresholds, before scoring begins.

5.4 Phase 1: risk assessment

  1. Identify. List the hazards or failure modes, with their causes.
  2. Analyze. Score each item against the pre-agreed scales. Record the basis for each score, what data or experience it rests on, in a notes column; a score with no stated basis is treated as a placeholder, not a finding.
  3. Evaluate. Compare the scored items against the criteria set in advance (an RPN band, a risk class, a CCP decision). Flag any item where severity alone warrants attention regardless of the combined score.

5.5 Phase 2: risk control

  1. For every item above the acceptance threshold, or flagged on severity, decide and record whether to reduce the risk, accept it as is, or accept it with monitoring.
  2. Where risk reduction is chosen, name the specific mitigation, whether it is a technical control (a system lock, an interlock, an automated check) or a procedural control (an SOP, a second review), and who owns it.
  3. Re-score the residual risk after the mitigation is verified in place, not merely planned. A mitigation credited before it is verified is not a mitigation yet.
  4. Accept the residual risk at the authority level set in section 6.

5.6 Phase 3: risk communication

  1. Share the assessment, including items that were not actioned and why, with the risk owner, QA, and the process or system owners affected.
  2. Where the outcome changes a downstream decision (validation scope, review frequency, change acceptability, investigation depth), name that decision explicitly in the assessment so the link is traceable later.
  3. Route high-tier outcomes to management review per <<FILL: SOP-ID for management review>>.

5.7 Phase 4: risk review

  1. Set a review trigger at the time of approval: a stated calendar cadence for Tier 3 assessments (<<FILL: e.g. annually>>) and, for every tier, a trigger on any relevant change, recurring finding, or new knowledge about the hazard.
  2. A review record states what was reconsidered and why the conclusion did or did not change; “reviewed, no change” with no supporting statement is not sufficient.
  3. Log the assessment, its residual risk, its owner, and its review trigger in the site quality risk register (/templates/register-quality-risk or <<FILL: internal register reference>>) so it is visible as a living record, not an archived file.

6. Sign-off authority for risk acceptance

Residual risk levelWho may accept
LowRisk owner, with QA concurrence recorded on the assessment
MediumQA approval required in addition to the risk owner
HighManagement or quality council approval required, with a written rationale; a High residual risk is never closed by simply re-rating it lower without a documented basis

7. Acceptance criteria

  • The proportionality tier and the method chosen are both stated and consistent with sections 5.1 and 5.2.
  • The team is cross-functional for any Tier 2 or Tier 3 assessment; no assessment above Tier 1 is signed by a single author.
  • Every score has a recorded basis; every item above threshold, or flagged on severity, has a documented decision.
  • Residual risk is re-scored only after the mitigation is verified, and is accepted at the authority level in section 6.
  • A review trigger is set and the outcome is logged in the quality risk register.

8. Records generated

  • The completed assessment (FMEA worksheet, HACCP CCP determination, risk ranking table, or documented risk discussion for Tier 1).
  • The risk register entry.
  • The review record at each triggered or scheduled review.

9. References

ICH Q9(R1), Quality Risk Management (Step 4, 18 January 2023). ICH Q10, Pharmaceutical Quality System, quality risk management enabler. 21 CFR Part 211 (current good manufacturing practice for finished pharmaceuticals), the underlying process and quality controls QRM decisions support. EU GMP Chapter 1 (Pharmaceutical Quality System) and the quality risk management principles applied across the GMP chapters and annexes.

Confirm the current version of each reference before issue.

10. Revision history

VersionDateAuthorSummary of change
<<FILL: 1.0>><<FILL: date>><<FILL: author>>Initial issue.

11. Approvals

RoleNameSignatureDate
Author<<FILL>>
Reviewer (QA)<<FILL>>
Approver (Quality Head)<<FILL>>

Filled specimen

The following shows a Tier 3 assessment run through the procedure for an example biologics fill-finish site, so you can see the level of detail expected. The company, system, and numbers are illustrative; replace them with your own.

Trigger: a proposed change to introduce an automated stopper-height sensor at the stoppering station, replacing a purely visual in-process check.

StepEntry
Tier (5.1)Tier 3, change affects a container closure integrity control on a sterile product
Method chosen (5.2)FMEA, because the change affects one process with steps that can be listed and scored independently; not HACCP because the question is a design change to an existing control, not identification of which step needs one
Team (5.3)Facilitator: CSV lead. Risk owner: Manufacturing engineering. SMEs: QA microbiologist, automation engineer, line operator lead
ScopeStoppering station only, from stopper feed to crimp-station handoff; upstream compounding and filling excluded
Assessment outcome (5.4-5.5)Failure mode “sensor false-accept on a partially seated stopper,” Severity 9, Occurrence 2, Detectability 3, RPN 54. Mitigation: dual detection (height sensor plus a downstream vision check before crimping), sensor calibration added to the periodic instrument program. Residual RPN 9x1x2=18, accepted by QA per section 6 (Medium band)
Communication (5.6)Shared with QA, manufacturing, and automation; change control CC-2026-0417 references this assessment directly; validation test plan updated to include a forced-fail challenge of the sensor
Review trigger (5.7)Annual review, plus trigger on any stoppering-station deviation or sensor alarm-rate trend
Register entryLogged as QR-2026-031 in the site quality risk register

Common inspection findings this SOP prevents

  • A team runs a full FMEA for a decision that plainly did not need one, or skips any documented assessment for a decision that clearly did, because no tier framework exists to decide which.
  • Different teams pick different tools for the same type of decision with no consistent rationale, so risk assessments across the site are not comparable.
  • A residual risk is re-scored lower with no verification that the mitigation actually works, so the “after” number is aspirational.
  • A high residual risk is accepted by the project team instead of the authority level in section 6.
  • An assessment sits in a file and never reaches the quality risk register, so it is invisible to anyone reviewing site risk posture.

How to adapt this SOP

  1. Set your document number, owner, and effective date in the header.
  2. Point section 2’s cross-reference to your real change control, deviation, and QRM-trigger procedures.
  3. If your site already has a validated risk register or an FMEA template, name it directly in sections 5.3, 5.7, and 8 rather than the generic references given here.
  4. Adjust the proportionality tiers and the sign-off authority table to your organization’s actual delegation of authority.
  5. Confirm every regulation in section 9 against the current published version before issue.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.