Guide
ICH Q7: API GMP From the Starting Material to the Final API
ICH Q7 is the global GMP standard for Active Pharmaceutical Ingredients, harmonised across FDA, EMA, PMDA and adopted as the reference by PIC/S and most other regulators. It is the rulebook every API manufacturer and every finished-dose manufacturer's supplier-qualification programme depends on. The text dates to 2000 but FDA, EMA and PIC/S have continued to sharpen interpretation through Q&As, warning letters, and inspection patterns — particularly around the 'API starting material' boundary, change control over critical steps, and supplier oversight of contract manufacturers and intermediates. This guide walks through the twenty sections, the API starting material decision, the inspection patterns that produce findings in 2026, and a practical readiness path. It is written for QA leads, qualified persons, process development managers and supplier quality teams at API manufacturers and at finished-dose manufacturers qualifying API sources.
Start free trial Free trial, no credit card, onboard in days, not months.
The API starting material decision: where Q7 starts to apply
Section 1 (and the FDA/EMA/PMDA Q7 Q&A) defines the point at which an API starting material enters the synthesis — and that point determines where full Q7 GMP applies. The decision is a documented justification involving the synthesis route, the chemistry, the impurity carry-over potential, the steps remaining to the API, and the manufacturer's commercial control. Inspectors challenge the starting-material designation as a default question — designating a material 'too late' in the route is the most efficient way to shrink the GMP scope, and regulators know it. The 2018 ICH Q7 Q&A and the EMA Reflection Paper on requirements for the selection and justification of starting materials are the references the conversation will turn on.
Quality Management (Section 2) and the role of the quality unit
Section 2 places overall responsibility for quality on a quality unit (or units) that is independent of production, with defined authority to release or reject APIs, intermediates and materials, to approve specifications and master batch records, to investigate quality issues, and to ensure the validation of critical processes. The independence question — does the quality unit report to operations, does it have the resources and authority to discharge its duties — is the question Section 2 audits live or die on. Warning letters to API manufacturers cite quality-unit failures repeatedly, often where the head of quality reports into operations or where quality has no veto on shipment.
Process Equipment (Section 5) and Documentation (Section 6)
Section 5 covers design and construction, equipment maintenance and cleaning, calibration, computerised systems. Section 6 covers documentation and records — the master batch production record, the actual batch production record, laboratory control records, batch production record review, complaint files. Cleaning validation under Section 5 is the perennial finding area for multi-product API plants — campaign length, worst-case product, MACO calculations, and the analytical sensitivity to detect the worst-case residue are all live inspection topics. Documentation issues under Section 6 are second only to data integrity in modern API warning letters.
Production and In-Process Controls (Section 8) and the critical-step concept
Section 8 introduces the concept of critical process steps — steps that have a significant impact on the quality of the API and that therefore warrant tighter controls, more rigorous change control, and explicit validation. Most Q7 implementations name critical steps in the master batch record but then treat all steps identically — defeating the point. Inspectors test by asking 'which steps are critical, why, and what control distinguishes them from non-critical steps'. A defensible answer requires the criticality assessment, the rationale, and the differential controls actually present at the critical step.
Change Control (Section 13) and validation lifecycle
Section 13 requires a formal change control system for changes to raw materials, specifications, analytical methods, facilities, support systems, equipment, processing steps, labelling and packaging materials, computer software. Changes affecting an API's quality, safety or efficacy may also require regulatory filing. The Q7 expectation is that change control is integrated with validation — a change to a critical step triggers a revalidation assessment, not just a paper change. Section 12 (Validation) sets the validation expectations: prospective validation as the default for commercial API processes, concurrent validation in defined circumstances, retrospective validation rarely and only with strong justification, ongoing process monitoring tied to the lifecycle.
Rejection and Reuse of Materials (Section 14) and supplier oversight (Section 7)
Section 14 covers rejection, reprocessing, reworking, recovery of materials and solvents, returns. Section 7 (Materials Management) covers receipt and quarantine, sampling and testing, storage, re-evaluation. The supplier oversight expectation extends to contract manufacturers and to material suppliers — the API manufacturer is responsible for the quality of contracted activities and must qualify suppliers proportionate to risk. Section 16 (Contract Manufacturers including Laboratories) makes the contractor-quality-agreement expectation explicit. Warning letters in 2025 hit hard on situations where the API manufacturer outsourced a step and treated it as 'the contractor's GMP' — Q7 puts the responsibility back on the contract giver.
Section 19: APIs for Use in Clinical Trials, and Section 20: Glossary
Section 19 sets a proportionate framework for APIs intended for use in clinical trials — many full-commercial controls scale down with clear caveats, but quality unit oversight, traceability and impurity control remain. A common 2026 problem: companies stretching Section 19 flexibility into late-phase manufacture intended for pivotal trials or for first commercial production, where regulators expect full Section 8 through 17 controls to be operating. Section 20 is the glossary — the definitions of API, API starting material, batch, critical, impurity, intermediate, validation that the rest of the standard hangs on. Misuse of a defined term in the master batch record is the easiest way to lose an inspection thread.
A 90-day readiness path
Days 1 to 15: gap assessment against Sections 2, 6, 8, 12, 13, 16 and (if relevant) 19; check API starting-material justifications; assess critical-step differential controls; assess data integrity per laboratory and per production system. Days 16 to 45: close the highest-impact gaps — typically critical-step controls, change-control-to-revalidation linkage, supplier oversight evidence; refresh OOS workflow. Days 46 to 70: cleaning validation per product matrix; quality unit independence review; internal audit covering all relevant sections. Days 71 to 90: management review; mock inspection focused on the opening conversation (quality unit independence, starting-material justification, data integrity); pre-inspection logistics.
Where this lives in V5 Ultimate
The clauses above aren't theoretical — every one maps to a shipped module and an industry profile. Jump to the parts of the product that turn this guide into evidence on a Monday morning.
Modules that do the work
Quality management
Q7 sections anchored in a Q10-aligned PQS.
API batch records
Critical-step controls structurally enforced per batch.
Deviations, OOS & CAPA
Investigations integrated with change control and validation.
Supplier & contractor oversight
Section 7 and Section 16 evidence in one record per contractor.
Document control
Starting-material justifications and master batch records under control.
Compliance self-assessment
Score the API GMP programme against Q7 by section.
Industries this hits hardest
Frequently asked
Is ICH Q7 the same as 21 CFR 211 for APIs?
21 CFR 211 covers finished pharmaceuticals; ICH Q7 covers active pharmaceutical ingredients. FDA accepts ICH Q7 as the GMP standard for APIs intended for use in finished pharmaceuticals, and uses Q7 as the inspection reference for API facilities. EMA and PMDA likewise apply Q7. The two standards are designed to be complementary, not duplicative.
Does Q7 apply to biotech APIs?
Q7 applies to the GMP elements common to APIs of chemical and biotech origin, with the qualification that biotech APIs (recombinant proteins, monoclonal antibodies, vaccines) carry additional process-specific controls covered by ICH Q5A through Q5E and by the EU Annex 2 (biological active substances and medicinal products). The base Q7 framework still applies; the biotech-specific Annexes layer on top.
What is the API starting material exactly?
Q7 defines it as the raw material, intermediate or API used in the production of an API that is incorporated as a significant structural fragment into the structure of the API. The designation is a documented justification involving synthesis route, chemistry, impurity profile, commercial control and remaining steps to the API. The Q7 Q&A and the EMA Reflection Paper give worked examples. Misdesignation — pulling the starting material too late in the route — is one of the most-cited findings in API inspections.
How does Q7 interact with ICH Q9 and Q10?
Q9 (Quality Risk Management) and Q10 (Pharmaceutical Quality System) layer over Q7. A modern Q7 implementation runs the PQS under Q10, uses Q9 to make risk-based decisions across the Q7 sections (criticality assessment, supplier risk, change classification), and integrates Q12 (Lifecycle Management) for post-approval changes. Treating Q7 as a standalone is technically possible but loses the modernisation that EMA, FDA and PMDA all expect.
See it on your shop floor.
Free trial, no credit card, onboard in days, not months.