WorkflowQuality Operations & CAPA

Quality Risk Management (ICH Q9)

Quality risk management that reads each new investigation, change and CAPA for the control it breaks, moves the score with its source, and waits for the risk owner to accept.

See one granulation FMEA move after an investigation ↓
Watch with transcript →
The problem

The alarm stopped sounding, and the risk file still calls it low

An FMEA is written by a cross-functional team, approved, then reviewed on a calendar, often by re-scoring the table from memory. Deviations, investigations, changes and CAPAs arrive in between, and each form's tick box asks whether a risk assessment is impacted; the investigator answers from what they remember of the file.

The assumptions sit in the current controls column, where nobody can search them. An investigation finds that a software update widened an alarm limit, yet the failure modes scored low because of that alarm keep their scores, and so does the sister machine. The inspector compares the risk file with the deviation log and finds the gap first.

Built forQA risk management leadsRisk ownersQA headsSite quality heads

The Problem Today

Risk files are re-scored on a calendar from memory, so a control that stopped working still holds its risks low.

2005
Year ICH Q9 first asked for risk review after investigations published

Compared from memory today

  • Deviations
  • Root causes
  • Changes
  • Risk files
  • Scores follow the roomTwo reviewers can read the same evidence and score it far apart
  • Sister lines hear lateAnother granulator keeps the same widened alarm and its low score

The Solution

  1. Each event read for the control it breaksDeviations, investigations, changes and CAPAs, against every assessment
  2. The pin moves with its passageSeverity, occurrence or detection, citing the record and the scale step
  3. A challenger tests the draftFinds what else leaned on the control and corrects over-scoring
  4. Owner accepts, QA reopens the fileQA checks every decision; reviewers score blind before the review

Built-in controls

  • No score moves until the risk owner accepts it
  • A high risk is accepted by the QA head, with an end
  • Only manufacturing and quality records are read

What You Get

A closed investigation now reaches each risk file that leaned on the failed control, at each plant.

  • Risk files that match the logInspectors and client auditors read one story in both
  • New risk owners score like veteransPast rulings shown; a learned rule waits for the QA head
  • One library of failure modesControls and assumptions shared across products, lines and plants
Features

Quality risk management features on one granulation FMEA, event by event

A root cause is approved: a software update widened the high-torque alarm on a wet granulator. The risk owner, the QA risk lead and the QA head carry the plant's granulation FMEA from that finding to a reopened file.

demoThe CDMO, its plants, clients, people, records and scores are sample data.

  1. 01Risk map

    FMEA risk map with each failure mode as a pin and its last-review trail

    • Each failure mode a pin. Severity and occurrence place it, its detection score is written on it, and a dotted trail shows where the last review left it.
    • The control each score rests on. Opening a pin shows the assumption behind its score, so the risk owner sees which control a new finding would break.
  2. 02Event reader

    Investigation root causes read for the assumptions they break

    • Root cause read against the file. The event reader finds two broken assumptions, a widened alarm and a seal changed only by the calendar, each tied to its passage.
    • Every living assessment searched. The assessment finder looks for the same assumptions in every plant's files, computerized-system assessments included, instead of the one the form named.
    • Plan, sources and confidence shown. Each agent lays out its plan, the passages behind its finding and a confidence, so QA audits the reasoning behind a proposal.
  3. 03Proposed move

    Detection rescored from alarm to batch record review, with its scale step

    • Occurrence from the batch count. Occurrence moves only with the events and the batches behind them, read against the plant's own frequency scale.
    • Detection from where it was found. An excursion the alarm missed and batch record review caught is scored at that step of the detection scale.
  4. 04Challenger

    A challenger asks which other failure modes leaned on the same control

    • One finding reaches each failure mode. Asked what else relied on the failed alarm, the score mover brings two more failure modes into the read.
    • The agents' own over-scoring caught. A loss-on-drying check at the end of drying still finds an over-wet granule, so the draft detection score comes down a step.
    • Points a person must answer. A point the agents cannot settle, such as an earlier risk acceptance, blocks sending to QA until a person flags or answers it.
  5. 05Owner decision

    Risk owner accepts or rejects each move only after reading its sources

    • One move at a time. A move's choices open only after its passages have been on screen, and the next move starts once the last is read.
    • A reason code on each decision. Accept or reject carries its reason, so the file says why each score changed or stayed where it was.
    • Rejections reach QA as well. The QA risk lead sees rejected moves beside accepted ones, and a rejected move to high also needs the QA head.
  6. 06Accepted moves

    Accepted moves land on the risk assessment, and its bands change with them

    • Pins move only on acceptance. The over-granulation pin lands in the high band once the risk owner accepts, and the file's band counts follow.
    • Basis rewritten where the score holds. Where no event supports an occurrence move, the score stays and its basis is rewritten from the tested batches.
  7. 07Elsewhere

    The same broken assumption found in other FMEAs, systems and plants

    • Sister granulator and control software. Another product's FMEA and the process-control system assessment rest on the same controls, and the QA risk lead adds them to the review or sends them to their owners.
    • Each plant rules on its own file. A file at another plant is kept on watch or disputed by that plant's site quality head, with the evidence in front of them.
  8. 08QA check

    QA risk lead checks every decision and signs the FMEA reopening

    • Maker and checker differ. The QA risk lead opens each decision and agrees or sends it back with a reason, and nobody checks their own work.
    • Signed with its meaning. The reopening carries the signer's own credentials and a stated meaning, and the cross-functional review is set.
    • Client notice held for the QA head. The quality agreement's notice to the client waits for the QA head's high-risk acceptance, then the QA risk lead reads it and sends it.
  9. 09What-if

    Interim controls and CAPA actions rehearsed before any score returns

    • Where each pin would land. The planner plays forward a supervisor's torque check, the restored alarm limit and the CAPA's effectiveness check, one scenario at a time.
    • The interim control, recorded. The risk owner records the chosen containment check, and the QA head's acceptance of the high risk names it with an end date.

Each moved score has an owner who decides it and a QA lead who checks it

The risk owner rules on each move, QA checks the ruling, the QA head accepts what stays high, and other plants decide on their own files.

QA risk management leads

Run the quality risk management program and check each moved score

  • Every new event read against every assessment
  • Each decision to check, rejections included
  • An evidence export ready for an inspection
Risk owners

Own process FMEAs and decide each proposed move on their files

  • The passage and scale step behind a move
  • How similar evidence was scored before
  • Interim controls rehearsed before proposing one
QA heads

Accept high risks for a set time and approve learned rules

  • No high risk accepted without a signature
  • Learned rules held for the QA head's approval
  • Rejected moves to high for countersignature
Site quality heads

Decide on their plant's assessments when another plant's finding reaches them

  • The other plant's evidence before deciding
  • Keep on watch or dispute, with a reason
  • No file reopened from outside their plant

A widened alarm limit sat behind three failure modes in one FMEA

An alarm that could no longer sound

A software update widened the high-torque limit, the change control never compared it with the validated value, and the file still scored detection on that alarm.

Two more failure modes on that alarm

Granule density used it as prevention and the over-wet granule as in-step detection; the challenger's question brought both into the read.

Detection the agents over-scored

The loss-on-drying limit at the end of drying still catches an over-wet granule, so the draft score was revised down a step.

The sister granulator's file

Another product's FMEA on the sister granulator rests on the same widened alarm, and joins the same cross-functional review.

The challenger plays the ICH Q9 reviewer against the score mover's draft

Each one reads plant and QA records alone, puts a source behind each proposal, and leaves each decision to a named role.

Event reader

Reads each deviation, investigation, change and CAPA for the assumptions it breaks or confirms.

  • Moves no score
Assessment finder

Finds each assessment, at any plant, whose controls, frequencies or severity basis rest on that assumption.

  • Puts another plant's file in a review only through its site quality head
Score mover

Proposes the moved severity, occurrence or detection with the scale definition and the passage.

  • Leaves the pin where it is until the risk owner accepts
  • Moves occurrence only with events and a batch count
Challenger

Plays the ICH Q9 reviewer and the inspector, testing the agents' own scores as hard as anyone's.

  • Removes no proposal
  • Holds sending until a person answers or flags each point
Risk memory

Shows how this risk owner and QA scored similar evidence before, and proposes rules from their rulings.

  • Its proposed rules wait for the QA head's signature
What-if planner

Plays forward interim controls and CAPA actions to show where each pin would land.

  • Lowers no score before its evidence exists
Review drafter

Drafts the reopening record, the review agenda and the invitations to reviewers.

  • Sends nothing before the QA risk lead signs
More screens

Reviewers score blind, and a wide spread is discussed before anyone agrees

Behind the map sit the records an inspector asks for next, and the place where subjectivity is measured.

Root cause passages each move citesThe investigation's root causes and contributing factor, rendered from the record with each cited passage highlighted; a citation on any screen opens here.
Every living assessment, by plant and status260 living risk assessments across four plants with band, last and next review, owner and status; the overdue periodic reviews stand out in red.
The process FMEA as an inspector reads itThe risk question, the scales from the procedure and each failure mode with the control its score rests on; rows the agents touched carry the alarm finding.
Blind pre-scores, and the spread between reviewersInvited reviewers score before they can see anyone else's score; a past review shows each reviewer's occurrence score and the one spread that was discussed.
Past rulings, and a rule waiting for the QA headHow risk owners, QA and a review panel ruled on similar evidence, and the rules learned from them; the proposed rule stays idle until the QA head signs it.
The reopening, the QA checks and the owner's decisions, in orderThe reopening, the QA checks and the risk owner's decisions in time order, each with reason, meaning and session; the evidence pack exports as CSV.

demoSample data, from the working solution.

A high risk is accepted only by the QA head, and only until the review

Reopening the assessmentThe QA risk lead checks each decision, rejections included, and signs the reopening with a stated meaning.
Accepting a high riskOnly the QA head signs a high risk accepted until the review, with its interim control and an end.
Whether a held batch may be usedThe assistant gives no answer about a held batch and names the QA disposition lead, who decides.
Turning a ruling into a ruleA rule learned from past rulings changes the next read only when the QA head has signed it.

Questions QA teams ask about quality risk management

What is quality risk management?

ICH Q9 defines quality risk management as a systematic process for the assessment, control, communication and review of risks to product quality across the lifecycle. Here each assessment stays current: agents read new deviations, investigations, changes and CAPAs against it, and the risk owner decides each proposed move.

When does ICH Q9 expect a risk review?

After new knowledge and experience, from planned or unplanned events such as root causes from failure investigations, at a frequency set by the level of risk. The review may reconsider earlier risk acceptance decisions, which is why the challenger flags them for the QA head.

What did ICH Q9(R1) add for risk assessment teams?

Formality as a spectrum, risk-based decision-making, managing and minimizing subjectivity, and product availability risks. Blind pre-scores, with the spread between reviewers shown and discussed, answer the subjectivity section with data.

How does a process FMEA score move here?

Only on the plant's own scales. Occurrence needs the events and the batch count behind them, and detection follows the step where the failure was actually found. The score mover cites both, and the challenger checks every occurrence move against that rule.

Which records does the solution read?

Deviations, investigations, change controls, CAPAs, batch records, historian trends, maintenance records, configuration exports, procedures and validation reports, each read against the assessments that rest on it.

How does a CDMO tell a client when its product's risk moves to high?

The client's quality agreement sets the notice; it states the move and its interim control, waits for the QA head's high-risk acceptance, and goes out once the QA risk lead has read it.

Bring the risk file
nobody has reopened.

Send one FMEA with the deviations, changes and CAPAs since its last review, and we will show which scores they move.