ICH Q9(R1): Quality Risk Management
A practical guide to pharmaceutical quality risk decisions, from defining the question and examining evidence to evaluating controls and reviewing new information.

On this page · 12 sections
- 1What ICH Q9(R1) means for pharmaceutical quality decisions
- 2Guidance, regional obligations and the limits of applicability
- 3How QRM differs from assessment, FMEA, CQAs and data integrity
- 4Run the QRM lifecycle from question to control
- 5Scale formality and challenge subjectivity without losing scientific discipline
- 6Build an evidence base that makes uncertainty visible
- 7Make risk-based decisions and record residual-risk acceptance
- 8Worked cases: packaging changes, supplier uncertainty and ineffective controls
- 9Connect QRM with the quality system and validation
- 10Recover when evidence, controls or implementation assumptions fail
- 11Document decisions, communicate risk and trigger meaningful review
- 12Implementation checklist: test whether the risk decision is usable
How does ICH Q9 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What ICH Q9(R1) means for pharmaceutical quality decisions
ICH Q9(R1) is an international pharmaceutical guideline describing a systematic process for assessing, controlling, communicating and reviewing risks to medicinal-product quality across the product lifecycle, as described in ICH Q9(R1), section 4.
Two ideas anchor the whole method. First, ICH Q9(R1) says the evaluation of risk to quality should be based on scientific knowledge and "ultimately link to the protection of the patient", so a risk score is only meaningful when it traces back to a credible patient or product-quality consequence. Second, the guideline defines risk as "the combination of the probability of occurrence of harm and the severity of that harm"; teams estimate both, and sometimes detectability, before deciding whether a control is proportionate.
For practical pharmaceutical risk discussions, the useful starting point is a decision rather than a score. The questions explored below are an operational reading aid, not an additional prescribed framework:
- What could go wrong?
- What evidence supports the assessment?
- Which controls address the risk?
- Who makes the decision?
- What would prompt reconsideration?
For pharmaceutical quality decisions, R1 discusses how formality can reflect a decision’s importance, uncertainty and complexity. It also recommends managing and minimizing subjectivity to support scientifically robust risk-based decision-making. These themes help frame how much structure a discussion needs and how its conclusions are challenged.
The comparison with neighbouring terms below sets the boundary: this article follows the overall QRM process. Detailed data-integrity risk assessment and critical quality attribute identification remain outside its scope; they are not substitutes for the broader decision process.
02Guidance, regional obligations and the limits of applicability
For medicinal products in jurisdictions applying ICH guidance, ICH Q9(R1), section 6 explains that appropriate QRM does not remove industry’s obligation to comply with regulatory requirements. Treat it as pharmaceutical guidance, not a standalone statute.
Use this screening table before choosing a QRM procedure. Each row prompts a current regional and product-specific scope check; it does not imply equivalent adoption status or effective dates.
| Jurisdiction and product | Regional text to consult | Applicability question | Decision to document |
|---|---|---|---|
| EU/EEA medicinal products | Current EudraLex Volume 4 text | Which GMP parts and annexes cover this product and activity? | Applicable scope and regional Q9 implementation. |
| US human drugs | Current FDA Q9 guidance and relevant regulations; screen 21 CFR 211. | Which GMP provisions cover this operation, and how is Q9 implemented? | Regulatory basis, guidance role and product-specific exclusions. |
| Japanese medicinal products | Current MHLW/PMDA Q9 implementation texts and applicable GMP texts. | Which current provisions and guidance cover this product and site? | Regional implementation and product-specific GMP scope. |
Keep binding requirements, guidance, local procedures and proposed software support separate in the applicability record. Identify the legal basis, the guidance informing interpretation, and the procedure translating decisions into site practice. Define any proposed software role separately; retain human review and approval.
Food, supplement, device and chemical manufacturers can consider QRM’s analytical approach, but should establish their own sector’s governing obligations independently. Method transfer is not regulatory equivalence. For operational implementation, continue with quality-system integration and risk-based validation.
03How QRM differs from assessment, FMEA, CQAs and data integrity
These distinctions reflect common pharmaceutical operational usage, not formal definitions from other standards. They separate the management process from its analytical activities, tools, records and organisational setting.
| Term | Operational role | Typical output | Boundary |
|---|---|---|---|
| QRM | Management process | Risk decisions, controls and reviews | Broader than assessment |
| Risk assessment | Analytical activity | Identified hazards and evaluated risks | Informs decisions; does not implement controls |
| FMEA | Failure-mode analysis tool | Failure modes, effects and priorities | One method, not the lifecycle |
| Risk register | Record structure | Risks, owners, actions and status | Tracks decisions; does not justify them |
| Critical quality attribute (CQA) | Product attribute | Attribute with a quality-relevant limit or range | What needs control, not an assessment method |
| Data-integrity risk assessment | Specialised assessment | Data vulnerabilities and proposed controls | Focuses on data trustworthiness |
| Pharmaceutical quality system | Organisational system | Governance, procedures and oversight | Uses QRM; is not synonymous with it |
For pharmaceutical organisations using international ICH guidance, ICH Q10, section 1.6 identifies knowledge management and QRM as enablers of effective implementation.
For medicinal-product QRM under international ICH guidance, ICH Q9(R1), section 5 presents recognised tools and internal procedures as available approaches—not FMEA alone. Sterile-process assessment is a specialist application, not a separate management framework. For connecting hazards to supporting knowledge, see the evidence and uncertainty model below.
04Run the QRM lifecycle from question to control
Start with the decision, not the tool. For a proposed pharmaceutical packaging change, the question might be whether mix-up risk is adequately controlled before implementation. An FMEA is one way to examine that question; completing it is not the decision.
The workflow below is an illustrative implementation aid, not a mandatory sequence or template. Roles are locally assigned accountable owners; they need not perform every task themselves.
Question → knowledge → hazards → analysis and evaluation → control comparison → decision → implementation → review ↺ knowledge or analysis. Communication runs alongside every stage.
| Stage | Input | Accountable role | Useful output |
|---|---|---|---|
| Define question and scope | Proposed change | Decision owner | Decision boundary and affected operations |
| Assemble knowledge | Process data and experience | Technical lead | Evidence summary and gaps |
| Identify hazards | Process steps and failure history | Process owner | Hazards linked to potential harm |
| Analyse and evaluate | Hazards, evidence, evaluation criteria | Assessment lead | Risk judgments and uncertainties |
| Compare controls | Risk judgments and alternatives | Control owner | Options and expected effects |
| Record decision | Control comparison | Authorised decision maker | Rationale and residual-risk disposition |
| Implement actions | Approved actions | Implementation owner | Completed changes and effectiveness evidence |
| Review changes | Effectiveness evidence and new knowledge | Risk owner | Confirmed decision or reopened assessment |
For medicinal-product QRM under international ICH guidance, ICH Q9(R1), section 4.1 recommends including experts from appropriate areas when teams are formed. In this example, select expertise in packaging identification and line operation because those activities determine the failure pathways being assessed.
For medicinal-product QRM under international ICH guidance, ICH Q9(R1), section 4 describes decisions to return to a previous step for further information or adjust risk models. Practically, uncertain inspection performance sends the team back to evidence gathering rather than directly to acceptance.
At handoffs, share unresolved questions, changed assumptions and action ownership with affected operators and decision makers. Route approved modifications through change control. Keep detailed record content and review triggers in documentation and risk review.
- Frame the QuestionDefine product, process, decision owner and boundaries.
- Gather KnowledgeConnect hazards to evidence, assumptions and gaps.
- Assess the riskAnalyse harm and evaluate against stated criteria.
- Select controlsCompare options and evaluate residual risk.
- Record the decisionDocument rationale and accountable human approval.
- Implement and checkAssign actions and evaluate control effectiveness.
- Review and learnReassess after changes, signals or ineffective controls.
05Scale formality and challenge subjectivity without losing scientific discipline
For medicinal-product QRM under international ICH guidance, ICH Q9(R1), section 5.1 describes formality as a continuum, not a choice between formal and informal assessment. The practical question is how much structure will make this particular decision dependable—not which template produces the longest report.
For medicinal-product QRM, international ICH guidance identifies uncertainty, importance and complexity as considerations that can call for greater formality. It also recommends against using resource constraints to justify lower formality.
Translate formality into observable choices
In pharmaceutical workshop practice, teams can scale analytical structure, participation and documentation separately. A familiar, bounded issue may suit a focused discussion and concise rationale. An unfamiliar issue with interacting failure paths may benefit from explicit comparison of alternatives, broader technical participation and a more detailed record of assumptions. Report length alone is a poor test of reasoning quality.
For example, in supplier risk management, missing knowledge about a supplier’s process can justify additional technical input rather than simply adding more scoring categories. Record why the chosen approach fits the uncertainty and decision at hand.
Challenge subjectivity before seeking agreement
For medicinal-product QRM under international ICH guidance, ICH Q9(R1), section 5.3 describes controlling subjectivity through attention to bias and assumptions, appropriate use of QRM tools, and relevant data and knowledge.
Practical facilitation controls—not a mandated scoring methodology—include:
- Define the decision question and boundaries before scoring, so participants assess the same situation.
- Anchor rating descriptions in observable conditions rather than adjectives that each participant interprets differently.
- Separate supporting evidence from assumptions; identify which assumptions could change the conclusion.
- Invite independent initial judgments before group discussion to reduce anchoring on the first speaker’s view.
- Record unresolved disagreement and the evidence needed to resolve it, rather than treating silence as agreement.
Voting or averaging ratings is not a substitute for investigating disagreement. Different ratings may reflect different process assumptions or knowledge gaps rather than different risk tolerances. Preserve that distinction in the quality risk register. When disagreement exposes a control that is not executed as assumed, use the failure modes and recovery approach.
06Build an evidence base that makes uncertainty visible
For medicinal-product risk-based decisions under international ICH guidance, ICH Q9(R1), section 5.2 emphasises the importance of ensuring the integrity of the data used. Here, the practical question is whether trustworthy evidence actually supports the hazard scenario being assessed—not how to conduct a separate data-integrity risk assessment.
A practical evidence map groups process knowledge, development or validation results, relevant deviations, complaints, supplier information and control-effectiveness observations by hazard scenario. For each item, record provenance, version, applicability, limitations and contradictory findings. Check whether the product, equipment, operating conditions and period represented match the decision. A successful validation result under different conditions may offer context without establishing control effectiveness here.
- Observation: what a test, record or direct inspection actually showed.
- Inference: what the team concludes from those observations, with its reasoning.
- Unresolved assumption: what the decision depends on but the evidence has not established; identify how it will be checked.
Keep contrary findings visible beside supporting results. Apply the approach to formality and uncertainty covered above when deciding how much additional investigation is useful.
Illustrative record design
Assessment → hazard scenario ↔ evidence item → decision → control review → assessment.
In this proposed vendor-neutral data model, an assessment contains hazard scenarios; each scenario links to evidence supporting or challenging a decision. Control reviews return effectiveness observations to the assessment. Use stable identifiers and version-specific evidence references so source changes do not erase the basis of an earlier decision. This is a suggested structure for traceability, not a mandatory schema or a software capability statement.
Risk Assessment
Defines scope and decision context.
- assessment_id
- product_id
- risk_question
- scope
- owner
- formality_rationale
Hazard Scenario
Links potential harm, uncertainty and supporting evidence.
- scenario_id
- assessment_id
- hazard
- potential_harm
- uncertainty
- evidence_refs
Evidence Item
Preserves provenance, applicability and known limitations.
- evidence_id
- source_ref
- version
- applicability
- limitations
- reviewed_by
Risk Decision
Records evaluation, reasoning and human acceptance.
- decision_id
- scenario_id
- evaluation_basis
- residual_risk
- decision_rationale
- approved_by
Control review
Tracks implementation, effectiveness evidence and subsequent learning.
- control_id
- decision_id
- action_owner
- control_status
- effectiveness_evidence
- review_trigger
07Make risk-based decisions and record residual-risk acceptance
For medicinal-product QRM under international ICH guidance, ICH Q9(R1), section 5.2 includes decisions about residual-risk acceptability after controls, alongside communication and review of the QRM activity and its outputs. The decision therefore extends beyond choosing a control.
For medicinal-product QRM, that international guidance describes a spectrum of decision structure: more structured approaches formally compare available alternatives and relevant factors; less structured approaches draw principally on existing knowledge. These are not fixed categories assigning a particular method to every decision.
For medicinal-product QRM under international ICH guidance, section 5.1 recommends basing risk scores, ratings and assessments on appropriate evidence, science and knowledge. In practical scoring systems, ordinal ratings express ordered categories, not measured event probabilities. A lower rating alone does not demonstrate that a control works or establish that remaining risk is acceptable.
A useful practical decision record contains:
- Alternatives considered and the criteria used to compare them.
- Supporting evidence, its limitations and residual uncertainty.
- The selected option and rationale for accepting the remaining risk.
- A named human decision-maker, acceptance conditions and circumstances for reconsideration.
For example, in supplier risk management, the rationale can explain why available evidence supports acceptance despite a remaining knowledge gap, rather than merely reporting a favourable score.
As a practical governance distinction, risk acceptance is not batch disposition or release. A calculation or software workflow does not grant release authority; separately authorised people make those decisions using the applicable evidence, including the batch record. The worked decisions below illustrate how alternatives and uncertainty shape the acceptance rationale.
08Worked cases: packaging changes, supplier uncertainty and ineffective controls
These hypothetical pharmaceutical cases illustrate qualitative reasoning, not reported manufacturing outcomes. Each selected action depends on the stated assumptions; none establishes a universal assessment level, acceptance threshold or batch-disposition rule.
Packaging change: familiar work, specific misidentification hazard
Assumptions and unit: The assessment unit is a packaging-change event. Artwork changes, but the product-contact system and equipment remain unchanged. The decision question is whether documentary review alone adequately addresses the possibility of using the wrong artwork.
Evidence and alternatives: Compare approved artwork differences, component identifiers, obsolete-stock handling and experience with comparable changes. Relevant experience supports a focused assessment rather than reopening unchanged equipment questions. However, document approval does not establish which component reaches the line. Compare documentary review alone with documentary review plus verification at the point of use.
Selected action and review trigger: In this scenario, the team records in change control its choice to add a line-side check against the approved artwork revision. The rationale targets component misidentification, not general confidence in packaging operations. A revision mismatch or unexpected obsolete stock triggers reconsideration.
Supplier change: uncertainty determines the next action
Assumptions and unit: The unit is the supplier-material combination. Supplier history is limited, and a material's particle-size behaviour during blending is uncertain. The decision question is whether there is an adequate basis to introduce that material into the process.
Evidence and alternatives: Review available characterisation, sampling representativeness and existing knowledge connecting particle size with blend performance. An absence of recorded failures offers little reassurance when experience is sparse. Compare proceeding on assumed equivalence with obtaining targeted characterisation and process-relevant evaluation.
Selected action and review trigger: The team defers the change pending evidence addressing that uncertainty. Receipt of the characterisation results triggers reassessment, not automatic acceptance. The decision record identifies the unresolved question and who will judge whether the new evidence answers it.
Control effectiveness: new evidence reopens an accepted decision
Assumptions and unit: A damaged sieve challenges a previously accepted foreign-particle control. The unit is the transfer stage and batches processed since the last documented intact-screen check. The decision question is whether the original control rationale still supports those batches and future operation.
Evidence and alternatives: Trace inspection records, maintenance history and material routes back to the original assessment. Compare replacement alone with investigating the damage mechanism and revising integrity checks. Reconsider scenarios involving undetected damage and potentially affected material.
Selected action and review trigger: The team selects investigation and revised checks, leaving batch disposition to authorised human review. A controlled evaluation of the revised check's ability to detect representative damage tests effectiveness. Failure of that evaluation or recurrence returns the decision to the QRM decision loop.
09Connect QRM with the quality system and validation
For medicinal-product quality systems using international ICH guidance, ICH Q9(R1), section 6 recommends integrating quality risk management into existing operations and documenting it appropriately. In practice, this means connecting risk decisions to operational records rather than maintaining an isolated assessment.
Common pharmaceutical quality-system handoffs include:
- Change control supplies the proposed change and implementation boundary: affected products, equipment, processes and operating conditions.
- Validation supplies relevant demonstrations and their limitations. Compare tested conditions with the conditions assumed in the risk decision.
- Deviations and complaints supply new signals that may challenge assumed failure frequencies, consequences or control performance.
- CAPA supplies assigned actions and effectiveness findings, distinguishing completion of an action from evidence that it controls the identified risk.
- Knowledge management preserves the resulting learning, including revised assumptions and the reasoning behind accepted or rejected options.
A useful feedback loop returns implementation findings to the assessment owner. If validation demonstrates performance only within a narrower operating range, compare that range with the proposed implementation boundary before treating the control as established. Local procedures determine responsibilities and records.
For software-supported record organisation and workflow tracking, consider shared identifiers, explicit version references, action ownership and linked evidence as design choices—not assumed product features or proof of compliance. Scientific evaluation, interpretation of limitations and approval remain human responsibilities. Use the implementation checklist to test whether each handoff carries enough information for the next decision.
10Recover when evidence, controls or implementation assumptions fail
An assessment can remain approved while its operational basis changes. The following practice-based checks help identify when a decision needs reopening rather than administrative closure.
| Failure | Observable signal | Immediate response | Recovery evidence |
|---|---|---|---|
| Obsolete source versions | Assessment cites superseded specifications | Check changes affecting the decision | Version comparison and impact conclusion |
| Controls implemented differently | Observed setup differs from assessed design | Contain the mismatch through local procedures | Implementation verification and revised assessment |
| Missing action ownership | Open action has no accountable owner | Assign ownership and escalation | Accepted responsibility and completion evidence |
| Contradictory records | Execution records conflict with control assumptions | Investigate; retain both records | Reconciled chronology and supported conclusion |
| Effectiveness check does not support closure | Failure recurs or results remain inconclusive | Keep the action open; reconsider controls | Relevant results supporting effectiveness |
A practical recovery sequence is to identify the decision affected, prevent continued reliance on the invalid assumption, and determine product and process impact through local procedures, including the deviation process where appropriate. Obtain relevant evidence, then reassess the decision with the responsible decision-makers. Distinguish evidence that an action was completed from evidence that its control works.
Preserve the original rationale and explain what changed, why, and how it affects the conclusion; do not silently overwrite it. Keep recovery within the applicable regional and product scope, using local procedures for disposition and escalation.
11Document decisions, communicate risk and trigger meaningful review
Use the data model introduced above as a connected decision record, not a second assessment template. In the quality risk register, keep scope and participants linked to evidence references and assumptions. Connect the selected method and evaluation criteria to the decision rationale, then connect controls to accountable owners and review triggers. This makes the reasoning traceable without copying supporting reports into every record.
As practical communication choices, tailor the message to its recipient:
- Action owners need the control, completion expectations and evidence that will demonstrate implementation.
- Decision-makers need the rationale, remaining uncertainty and matters requiring their approval.
- People affected by a changed control need the revised working instructions, when they apply and how to report difficulties.
For medicinal-product QRM under international ICH guidance, ICH Q9(R1), section 4.6 recommends basing review frequency on the level of risk.
In practice, distinguish scheduled review from event-triggered reconsideration. A scheduled review checks whether the decision still holds at a planned point. A changed process entering change control, contradictory evidence, an ineffective control or a relevant new quality signal can prompt reconsideration before that point.
Compare new knowledge with the original acceptance rationale. Record whether the conclusion remains justified, changes or needs further evidence, together with the reason and any follow-up owner. An unchanged conclusion still benefits from a documented explanation.
12Implementation checklist: test whether the risk decision is usable
Use these practical self-review questions before approving or implementing a pharmaceutical risk decision. They are an implementation aid, not certification criteria.
- Bound the question: does it identify the decision, process boundaries and exclusions?
- Identify applicability: are the product, lifecycle stage and relevant jurisdictions named?
- Record the formality rationale: does the chosen approach reflect uncertainty, complexity and decision importance?
- Trace conclusions: is each material conclusion connected to evidence or an explicit assumption?
- Compare alternatives: are credible options and reasons for rejecting them recorded?
- Assign controls: are owners, implementation actions and effectiveness checks clear?
- Name decision authority: is responsibility for approval and residual-risk acceptance explicit?
- Test review triggers: do they identify observable changes, who monitors them and who reopens the assessment?
Keep unresolved gaps visible in the decision record or quality risk register, with owners and next actions. A completed form is not proof of adequate risk management.
Return to the purpose of pharmaceutical QRM for the acceptance test: can a qualified colleague understand why the decision was made, execute the actions and identify what new information would change it?
Frequently asked questions
Q.Does ICH Q9(R1) prescribe a single risk-scoring method, or can a qualitative assessment be appropriate?+
A qualitative assessment can be appropriate; numerical scoring is not the only practical way to explain a risk decision. For pharmaceutical quality across ICH regions, ICH Q9(R1) section 5.2 describes less structured approaches using existing knowledge. In practice, a qualitative assessment works best when the hazard, potential harm, supporting knowledge and control rationale are explicit. For risk-based validation, explain why the selected checks address the failure mechanism rather than treating a risk label as the justification.
Q.Can a lower-formality assessment use a short record, and what reasoning still needs to be clear?+
A short record can be a useful practical format when it preserves the reasoning behind the decision. For pharmaceutical quality across ICH regions, ICH Q9(R1) section 5.1 recommends robust risk management regardless of formality. A concise entry in the quality management system can identify the decision, hazard, evidence, uncertainty, controls, responsible reviewer and review trigger. Explain why the chosen depth is adequate; merely marking an assessment as low risk does not communicate that reasoning.
Q.What should a team do when the available evidence is sparse, contradictory or drawn from a [different process](/glossary/process-validation)?+
Treat the uncertainty as part of the decision, not as an empty field to fill with an optimistic estimate. For pharmaceutical quality across ICH regions, ICH Q9(R1) section 5.1 identifies uncertainty, importance and complexity as factors that may warrant greater formality. As practical steps, distinguish observations from assumptions, examine whether borrowed evidence transfers to the actual operating conditions, and identify what information could change the conclusion. In supplier risk management, investigate relevant differences before relying on another supplier’s history.
Q.How should conflicting expert judgments be resolved without averaging away the disagreement?+
First identify whether experts disagree about facts, assumptions, failure mechanisms or acceptable consequences. For pharmaceutical quality across ICH regions, ICH Q9(R1) section 4.1 recommends that decision makers manage and minimise subjectivity. A practical approach is to record competing explanations, identify evidence that could distinguish them and test whether either would change the controls. If disagreement remains, document the decision owner’s rationale and unresolved uncertainty. Escalate material resource or authority issues through management review, rather than converting disagreement into an unexplained average.
Q.Does a lower calculated risk score justify leaving an applicable regulatory obligation unmet?+
No. For pharmaceutical quality across ICH regions, the ICH Q9(R1) introduction explains that quality risk management does not remove industry’s obligation to comply with regulatory requirements. As a practical decision structure, separate applicable obligations from choices about how to manage risk. A score can help compare control options; it is not evidence that an obligation has disappeared. When assessing cGMP issues, identify the applicable obligation independently before using the assessment to evaluate proposed corrective actions.
Q.Is accepting residual risk the same decision as approving a [batch for release](/glossary/batch-record)?+
No. Operationally, residual-risk acceptance addresses whether the remaining risk is acceptable after controls; batch disposition addresses a particular batch. Keep their scope and approval records distinct. For pharmaceutical quality across ICH regions, ICH Q9(R1) section 5.2 includes residual-risk acceptability among risk-management decisions. In a practical quality assurance workflow, the assessment informs the authorised person’s batch decision alongside batch-specific evidence. A signed assessment or favourable score is not, by itself, a batch-release approval.
Q.When should an existing risk assessment be reopened rather than reused for a new decision?+
As practical review triggers, consider changed materials, equipment, operating conditions, intended use, failure history or evidence about control effectiveness. Compare the new decision with the original assessment’s scope and assumptions before carrying its conclusion forward. For pharmaceutical quality across ICH regions, ICH Q9(R1) section 4 describes decisions that return to earlier steps for further information or model adjustment. Findings from APR / PQR can prompt that comparison. Record whether the new information changes the hazard analysis, controls or acceptance rationale.
Q.Can food, supplement, device or chemical manufacturers use the approach while respecting their own product and jurisdiction boundaries?+
Yes—as a cross-sector practice, teams can adapt hazard identification, control evaluation and review without treating pharmaceutical guidance as their governing rulebook. International pharmaceutical guidance ICH Q9(R1) section 2 describes its scope as pharmaceutical quality. For another sector, start with the product, intended use, market and applicable framework, then adapt terminology and decision criteria. Device teams can separately consider ISO 14971 for its general medical-device risk-management purpose. Borrow the reasoning structure, not an assumption of regulatory equivalence.
Primary sources
Explore this topic
ICH Q9 sits inside 3 overlapping topic clusters in our glossary. Every neighbour is one click away.
Drug-product cGMP rules, ICH Q-series, and the regulators that enforce them.
ICH Q8/Q11/Q12 toolkit — Quality by Design, design space, control strategy, CPV and lifecycle management.
URS-through-PQ lifecycle, GAMP 5 categorisation and CSA's modern alternative.
Want to see how ICH Q9 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
