ICH Q7 clause 8: Production and in-process controls
The 28 audit questions covering clause 8, each with the objective evidence to request, the nonconformities most often raised against it and what to sample. Part of the free ICH Q7 API GMP audit checklist, which holds 350 items across 18 clauses.
All 28 questions for clause 8
Open any row for its objective evidence, common nonconformities and auditor tips. You can check items off as you go. This browser remembers your progress across all 18 clauses of this checklist.
§8 Production and in-process controls
8.10 Are raw materials weighed and measured under controlled procedures, with appropriate accuracy and traceability?
- Weighing SOPs with technique details
- Calibrated balance records
- Balance accuracy appropriate for quantities weighed
- Weighing area environmental controls
- Container identification during weighing
- Second-person verification of critical weighings
- Weighing records in batch records
- Training on weighing technique
- Balances not calibrated or wrong accuracy range
- Weighing in uncontrolled environment
- Container identification lost during weighing
- No verification of weights for critical materials
- Contamination from shared weighing equipment
- Tare weight verification not documented for re-used dispensing containers
Weighing and measuring operations are critical quality control points. Issues include: wrong material charged (identity confusion), wrong quantity (weighing error), contamination during weighing (from environment or weighing equipment), weighing equipment inaccuracy. Controls: calibrated balances appropriate for the quantity range, dedicated weighing area with environmental controls, clear container identification, independent verification of weighed quantities.
8.11 Is each material verified against the batch record (identity, quantity) before being added to the batch?
- Batch records showing material verification checkpoints
- Second-person witness signatures for critical operations
- Barcode/RFID verification systems
- Expiry date checks documented
- Material release status checks
- Label vs batch record cross-reference
- Error-catch incidents showing system effectiveness
- Training on verification procedures
- Material verification not documented in batch records
- Witness requirement bypassed
- No electronic verification despite availability
- Expired materials used
- Quarantined materials charged to batches
- Material lot number mismatch between batch record and warehouse release ticket
This is a key error prevention control. Before adding a material to the batch, production verifies: (1) the material label matches what the batch record requires, (2) the quantity weighed matches the batch record requirement, (3) the material is within its retest/expiry period, (4) the material is released (not quarantined). For critical operations, an independent witness or electronic verification provides additional assurance.
8.12 Are actual yields compared against expected yields at appropriate steps, with significant deviations investigated?
- Expected yield ranges in master production instructions
- Actual yield calculations in batch records
- Yield deviation investigation records
- Yield trending over multiple batches
- Yield comparison at critical steps
- Investigation SOP for yield deviations
- Yield impact assessment on quality
- Statistical yield control charts
- Yield ranges not established or too wide to be meaningful
- Low yields not investigated
- Yield only calculated at final step
- No trending of yield data
- Yield deviations closed without root cause
- Abnormally high yields not investigated for potential contamination or incomplete drying
Yield is a sensitive indicator of process problems. Significantly low yields may indicate lost material (spills, equipment hangups), incomplete reactions, or wrong reagent additions. High yields may indicate under-reaction products or contamination. Expected yield ranges (typically 90-110% for well-established processes) should be set based on historical data. Deviations trigger investigation, especially at critical steps where yield correlates with quality.
8.13 Are critical process parameters monitored and documented during production?
- CPP list for each process with ranges
- Monitoring frequency defined for each CPP
- Batch records showing CPP data at required intervals
- Automated monitoring system logs
- CPP excursion investigation records
- Validation reports establishing CPP ranges
- Alarm system for CPP excursions
- CPP trending and process capability data
- CPPs not monitored at defined frequency
- Paper-based monitoring missing excursions
- Ranges not based on validation data
- Excursions not investigated
- CPP data not in batch records
- DCS alarm limits not aligned with validated CPP operating ranges
CPPs (temperature, pH, pressure, agitation, addition rates, reaction time) must be monitored continuously or at frequent intervals during production. Modern practice uses automated DCS/PLC systems that log parameters continuously and alarm on excursions. Paper-based monitoring at defined intervals is acceptable but risks missing transient excursions. All CPP data becomes part of the batch record.
8.14 Are in-process materials tested and found acceptable before proceeding to the next significant step where required?
- In-process control SOP
- IPC acceptance criteria in master batch records
- IPC results in batch records
- Sampling point diagrams
- IPC method references (validated methods)
- IPC failure investigation procedures
- Disposition of in-process material on IPC failure
- IPC trending by process step
- No in-process controls for critical transitions
- IPC acceptance criteria not defined
- IPC results not recorded
- IPC failures not acted upon
- Process proceeds despite failed IPC
- IPC sampling points not representative of bulk batch composition
In-process testing (IPC) verifies that the batch is progressing correctly before committing to expensive downstream steps. Example: testing for reaction completion before workup, testing particle size before drying, testing moisture before final packaging. Each IPC has: sampling point, test method, acceptance criteria, disposition procedure if out-of-spec. IPC procedures must be QA-approved.
8.15 Are production deviations documented, with critical deviations investigated and resolved?
- Deviation management SOP
- Deviation records with investigation
- Classification of deviations (minor, major, critical)
- Associated batch impact assessment
- Root cause analysis documentation
- CAPA records linked to deviations
- Deviation trending reports
- QA review and approval of deviation closures
- Deviations closed without root cause analysis
- Associated batch assessment skipped
- Recurring deviations without effective CAPA
- Critical deviations handled as minor
- Deviations not linked to batch records
- Deviation trending not reviewed during annual product quality review
Production deviations are unplanned departures from approved procedures or specifications. Every deviation must be documented and evaluated, with critical deviations investigated thoroughly. The investigation scope must extend to 'associated batches' — other batches potentially affected by the same cause (same equipment, same material lot, same time period). Root cause analysis is mandatory, and CAPA must prevent recurrence.
8.16 Are process changes evaluated through change control before implementation?
- Change control SOP covering process changes
- Change request forms with impact assessments
- QA approval of process changes
- Pre-implementation risk assessment
- Post-implementation effectiveness review
- Revalidation records for significant changes
- Change control log
- Classification of changes (minor/major/critical)
- Process changes made without change control
- Impact assessments superficial or missing
- QA bypass in change approval
- No post-implementation verification
- Revalidation skipped for significant changes
- Stability assessment not included in change evaluation for CPP modifications
Planned process changes must go through change control, not informally. Even minor changes can have unexpected effects (e.g., supplier substitution affecting impurity profile). The change control process must: document the change, assess impact on quality, require QA approval, implement the change with verification, and evaluate results. Significant changes trigger revalidation of affected process steps.
8.17 Are critical processing steps witnessed or independently verified?
- Witnessed step identification in master batch records
- Witness signatures in batch records
- Electronic verification systems for critical steps
- Witnessing SOP
- Witness training and qualification
- Critical step list with rationale
- Verification step timing documented
- Witness responsibility matrix
- Critical steps not witnessed
- Witnessing backdated after the step
- Same person performing and witnessing
- Electronic verification bypassed
- Critical steps not identified in batch records
- Witness personnel lacking qualification for the specific operation being verified
Witnessed operations prevent single-person errors on critical steps. Typical critical steps requiring witnessing: charging of starting materials, addition of catalysts/critical reagents, final product isolation, sampling for release testing. Electronic verification (barcode confirmation, automated metering) can replace physical witnessing. The witness signature or electronic verification must be in the batch record at the specific step.
8.20 Where appropriate, are time limits established for the completion of production steps?
- Time limits in master batch records where applicable
- Batch records showing actual times vs limits
- Deviation records for time limit exceedances
- Process understanding documentation supporting time limits
- Time limit justification (where no limits)
- Parameter-based vs time-based control rationale
- Time limit trending
- Product quality vs hold time data
- Time limits specified but not enforced
- Extended hold times without documentation
- No time limits on time-sensitive steps
- Deviations from time limits not investigated
- Time limits based on convenience rather than quality impact
- Production scheduling routinely exceeding validated inter-step hold times
Time limits constrain process steps to prevent quality issues from extended durations (e.g., extended reaction times causing over-reaction, extended hold times allowing degradation, extended drying causing loss of a volatile component). Not all steps need time limits — parameter-based control may be more appropriate (e.g., reaction until IPC shows completion). Where time limits exist, they must be enforced and deviations investigated.
8.21 Are deviations from established time limits documented and evaluated for quality impact?
- Time limit deviation records
- Impact assessment for time deviations
- Additional testing results where required
- Root cause analysis for time deviations
- Disposition decisions with scientific justification
- CAPA for recurring time deviations
- Trending of time deviations
- QA review of time deviation impact
- Time deviations closed without impact assessment
- Additional testing not performed when warranted
- Recurring time deviations without process change
- Disposition decisions without scientific basis
- No trending of time deviations
- Degradation product formation not assessed after extended reaction hold times
Time limit deviations follow the standard deviation process but with specific focus on time-related degradation risks. Example: if a time limit exists for cooling after a reaction, and cooling takes too long, the investigation must assess whether the extended time at elevated temperature caused degradation, additional impurity formation, or crystal form changes. Investigation may require additional testing beyond routine release testing.
8.30 Are there written procedures for in-process monitoring and control of critical parameters?
- In-process monitoring SOPs
- IPC specifications in master batch records
- Sampling frequency defined for each IPC
- Sample size specifications
- Acceptance criteria documented
- Failure handling procedures
- Decision trees for OOS IPC results
- Training records on IPC procedures
- IPC procedures missing or incomplete
- No defined acceptance criteria
- Failure handling not specified
- Sample sizes insufficient for test requirements
- OOS IPC results handled inconsistently
- Decision trees for out-of-specification IPC results not documented
In-process monitoring procedures must be specific and documented. They define what to measure, how often, how much sample, what results are acceptable, and what to do if results fail. Failure handling is particularly important — there must be a clear decision tree: halt process, additional testing, investigate, adjust, continue, or reject. These decisions must be documented and authorized by QA for critical steps.
8.31 Are in-process controls and their acceptance criteria defined for parameters that affect quality?
- IPC specifications with scientific justification
- Validation data supporting acceptance criteria
- IPC test method references
- Tightness of IPC limits vs specification
- Process understanding documents
- IPC method validation
- Acceptance criteria traceability to CQAs
- Periodic IPC review
- IPC criteria without scientific justification
- IPC limits tighter/looser than validation supports
- IPC methods not validated
- IPCs not targeting CQA-impacting parameters
- Arbitrary acceptance criteria
- IPC acceptance criteria not updated after process validation or technology transfer changes
IPC selection must target parameters that affect downstream quality. Common IPCs: pH of buffered solutions, reaction completion (HPLC or TLC), moisture content (Karl Fischer), particle size (laser diffraction), appearance (visual), density (specific gravity). Acceptance criteria should be derived from process understanding and validation data — not arbitrary. Tighter limits prevent downstream issues; looser limits risk quality impact.
8.32 Are in-process control specifications reviewed and approved by the quality unit?
- QA signatures on IPC specifications
- QA approval records for IPC changes
- Change control records for IPC modifications
- QA review criteria for IPC approval
- IPC specification version control
- QA training on IPC review
- IPC approval workflow
- Periodic QA audit of IPC program
- IPCs in use without QA approval
- IPC changes without change control
- Production setting own IPCs
- QA approval perfunctory (rubber stamp)
- IPC revisions untracked
- Temporary IPC modifications during troubleshooting not managed through deviation system
QA approval ensures that production doesn't unilaterally set its own acceptance criteria. QA's scientific review is independent and product-quality focused. Any changes to IPCs (tightening, loosening, adding, removing, method changes) require QA re-approval through change control. This prevents drift in controls that could compromise quality.
8.33 Are out-of-specification in-process materials segregated and dispositioned under control?
- In-process material quarantine procedures
- OOS in-process material records
- Disposition decisions documented
- Reprocessing records for OOS materials
- Reworking records for OOS materials
- QA approval of disposition
- Rejected material tracking
- Linkage to Section 14 procedures
- OOS in-process materials used without justification
- No clear quarantine of failed materials
- Reprocessing without QA approval
- Reworking done without validation
- Disposition decisions not recorded
- Rejected intermediate impurity profile not evaluated before reprocessing decision
Out-of-specification in-process materials must be segregated to prevent accidental use. Quarantine procedures apply the same as for raw materials. Disposition options include: reprocessing (repeating established steps), reworking (using a different step), destruction, or use as a different product. Each disposition requires QA approval and documentation per Section 14.
8.34 Is completion of significant process steps confirmed by testing where it cannot be assessed visually?
- Completion test specifications for critical steps
- Batch records showing completion testing
- HPLC methods for reaction monitoring
- Acceptance criteria for completion
- Decision procedures for incomplete reactions
- Method validation for completion methods
- Turnaround time for completion testing
- Correlation between completion data and final API quality
- Process steps proceeded without completion verification
- Completion methods not validated
- Long delays between completion testing and next step
- No correlation between IPC and final quality
- Completion criteria not scientifically justified
- Analytical turnaround time for completion tests causing unnecessary process delays
Some process steps can't be visually assessed for completion — chemical testing is required. Common examples: HPLC to confirm reaction completion, TLC for quick spot checks, NMR for functional group transformations, chiral HPLC for stereoselectivity. Testing must occur BEFORE the next step to avoid wasting subsequent steps on incomplete material. Results are documented in batch records.
8.35 Are residuals carried over from prior steps controlled so they do not adversely affect quality?
- Residual material specifications at critical steps
- Toxicological assessments (genotoxic, heavy metal)
- Washing/purification effectiveness data
- Residual testing IPCs
- ICH M7 assessment for genotoxic impurities
- ICH Q3D assessment for elemental impurities
- Carryover calculations
- Purification step validation
- No monitoring of residuals from earlier steps
- Genotoxic impurities not assessed per ICH M7
- Elemental impurities not assessed per ICH Q3D
- Carryover assumed rather than measured
- Purification steps not validated for residual removal
- Catalyst residue limits not established based on toxicological evaluation
Residual materials from earlier steps can contaminate intermediates and APIs. Controls include: washing steps, drying steps, crystallization for purification, distillation for solvent removal, chromatography for impurity removal. IPCs should monitor residuals that could affect final quality, especially toxic components (genotoxics per ICH M7, heavy metals per ICH Q3D). Limits are set based on toxicological assessment.
8.36 Is cleaning between same-product batches and between different products controlled and, where required, validated?
- Between-batch cleaning validation for same product
- Campaign length validation
- Visual inspection criteria
- Periodic comprehensive cleaning schedule
- Residue accumulation studies
- Campaign end cleaning verification
- Dedicated equipment cleaning approach
- Visual clean SOPs
- No validation of between-batch cleaning
- Indefinite campaign lengths without residue assessment
- Visual clean only without periodic verification
- No residue accumulation data
- Cleaning approach for dedicated vs non-dedicated equipment not differentiated
- Degradation product accumulation not monitored across consecutive batch campaigns
Same-product cleaning between batches has different requirements than product-changeover cleaning. For dedicated equipment making the same API, some residue buildup is acceptable if it doesn't accumulate to levels affecting quality. Between-batch cleaning may be simpler (rinse + visual) with periodic comprehensive cleaning. Validation demonstrates that the approach maintains quality across a campaign.
8.40 Is the combining of fractions of a single batch for further processing controlled and documented?
- Definition of blending in site procedures
- SOP distinguishing combining from blending
- Batch records reflecting single-batch combining
- Blending SOP for true blending operations
- Training on blending definitions
- Process documentation showing within-batch combining as normal
- Historical data on combining practices
- QA review of combining vs blending classification
- Misclassification of combining as blending (unnecessary burden)
- Misclassification of blending as combining (inadequate control)
- No clear definition of blending in procedures
- Within-batch combining treated as requiring full blending validation
- Separate-batch blending treated as routine combining
- Blending rationale not documented in batch records for regulatory traceability
This clause distinguishes two concepts often confused: (1) combining fractions of a single batch into a homogeneous whole — this is normal production, not blending, and (2) combining separate batches into a larger lot — this is blending and requires specific controls. The definitions are important because they trigger different documentation and validation requirements. Most within-batch combining is acceptable as normal production.
8.41 Is blending prohibited as a means of bringing out-of-specification material into compliance?
- Blending SOP prohibiting OOS batch blending
- Individual batch release records before blending
- Blending records showing all component batches passed
- QA approval of blending operations
- Training on blending prohibitions
- Internal audit verification of blending compliance
- Blending investigation procedures
- Batch release criteria for blend components
- Failed batches blended to meet specifications
- Blending without individual batch release first
- Specifications met only after blending
- Blending used as routine rescue for production problems
- No QA verification of component batch status before blending
- Borderline-passing batches systematically selected for blending to improve average assay
This is an absolute prohibition — using blending to 'average out' failed batches is a serious compliance violation. Every batch entering a blend must individually meet all applicable specifications. Blending can be used to: create larger lots for convenience, homogenize subtle batch-to-batch variation within specification, or combine batches for downstream processing. It cannot be used to rescue failed batches.
8.42 Are blending processes validated to demonstrate homogeneity of the resulting blend?
- Blending validation protocols and reports
- Homogeneity test data across blend locations
- Sampling plans for blend validation
- Blend stability data
- Validated blend size limits
- Number of blending operations validated
- Blending equipment qualification
- Periodic revalidation
- Blending without validation
- Homogeneity assumed rather than demonstrated
- Blend size not validated
- No blend stability assessment
- Single-point sampling for homogeneity verification
- Blending equipment not qualified for the validated blend size range
Blending validation proves that the physical mixing actually produces a uniform result. Validation tests include: sampling from multiple locations within the blended material, analyzing for key quality attributes, and demonstrating that results are similar across all sample locations. Validation also determines acceptable blend sizes (too large may not mix well, too small loses the benefit of blending) and assesses blend stability.
8.43 Do blending records provide full traceability to the individual batches that make up the blend?
- Blending batch records
- Component batch traceability
- Blend composition documented
- Blending equipment records
- Resulting blend batch numbering
- QA review of blending records
- Linkage between blend batch and component batches in inventory
- Investigation capability from blend to components
- Blending records missing component details
- Traceability broken at blending step
- Blend batch numbers not distinguished from component batches
- No QA review of blending records
- Quantities not recorded
- Component batch manufacturing dates not captured in blend batch record
Blended batches need their own batch records showing the composition. Key information: identity and batch number of each component, quantity of each, date and time of blending, equipment used, blending operator, resulting blend batch number, and any IPC results on the blend. This creates a clear audit trail from blend back to individual components, enabling impact assessment if problems arise later.
8.44 Are critical physical attributes of blends tested where they affect quality?
- Physical attribute specifications for blends
- Blend test results in batch records
- Particle size distribution data
- Bulk density measurements
- Moisture content results
- Content uniformity data across blend locations
- Test method references for blend testing
- Acceptance criteria for physical attributes
- Blends not tested for physical attributes
- Test methods not validated
- Acceptance criteria not defined
- Single-point sampling for blend uniformity
- Physical attributes specified but not measured
- Particle size distribution not verified after blending of lots with different milling histories
Blending is often used to achieve uniform physical properties, so testing must verify success. Common tests: particle size distribution (laser diffraction), bulk/tap density (for flow properties), moisture content (Karl Fischer), homogeneity via content uniformity (multi-point HPLC assay). Tests selected based on which physical properties matter for the API's intended use.
8.45 Is the expiry or retest date of a blended batch based on the oldest component?
- Blending SOP specifying expiry calculation
- Blend batch records with component manufacturing dates
- Blend expiry dates calculated from oldest component
- Quality unit verification of blend expiry
- Training on blend expiry rules
- Customer labeling reflecting conservative expiry
- Blend stability data supporting expiry
- Batch record showing expiry calculation
- Blend expiry based on blending date instead of oldest component
- Blend expiry extended beyond oldest component expiry
- Mixed component ages not tracked in blend records
- No verification of expiry calculation
- Blend shipped with expiry exceeding oldest component
- Customer CoA showing blend retest date calculated from blending date rather than oldest batch
This is a conservative rule to protect patients. Since the blend contains material as old as its oldest component, the expiry must match that oldest material. You cannot 'reset' the clock by blending old material with new — the old material is still present and still aging. This rule sometimes makes blending unattractive from a shelf-life perspective, which is by design.
8.46 Are the homogeneity and impurity profile of blends confirmed to meet specifications?
- Impurity profile testing on blends
- Comparison of blend profile to components
- Impurity profile specifications for blends
- Investigation of unexpected impurity changes
- Testing method for impurity profiling
- Historical blend impurity data
- Trending of blend vs component impurities
- QA review of blend impurity data
- Blend impurity profile not tested
- No comparison to component profiles
- Unexpected blend impurities not investigated
- Impurity profile spec only for individual batches, not blends
- Blending without understanding impurity interactions
- New impurity peaks in blend chromatogram not identified or qualified
Blending typically averages impurity levels across components, but unexpected interactions can occur — e.g., if one component has a high level of a reactive impurity, it could react with components of another batch during blending. Testing the blended material's impurity profile confirms no unexpected changes. For blends with diverse component sources, comparison to individual component profiles is particularly important.
8.47 Must blends meet the same specifications that apply to the individual component batches?
- Release testing of blended batches
- Full specification testing on blends
- QA approval of blend release
- Reduced testing justification where applied
- Blend release records
- Blend test results vs specifications
- Blend release procedure
- Blend quality vs component quality comparison
- Reduced testing of blends without validation
- Blend release without full testing
- Blend treated as continuation of component batches
- No QA release of blend as new batch
- Blend shipped without complete testing package
- Blend certificate of analysis not reflecting all specification tests performed
Blending doesn't reduce testing obligations. The blend must meet all specifications that individual components had to meet. This prevents using blending as a way to skip testing. Some efficiencies are possible with validation — e.g., reduced testing if statistical sampling from the blend is equivalent to testing each component. But the default is full testing of the blend as a new batch.
8.50 Is the carryover of residual material between same-product batches controlled to acceptable levels?
- Campaign length validation
- Same-product carryover assessment
- Impurity accumulation studies
- Microbial carryover assessment
- Periodic comprehensive cleaning records
- Campaign end cleaning procedures
- Risk assessment for same-product carryover
- Historical data on impurity profile stability across campaigns
- Unlimited campaign length without assessment
- No impurity accumulation monitoring
- Microbial growth on equipment between batches
- Same-product carryover treated as having no limits
- No periodic comprehensive cleaning
- Carryover material not assessed for stability-related degradation between batch turnovers
Unlike cross-product carryover, same-product carryover is sometimes acceptable and even beneficial (avoiding material waste). However, controls must ensure that: (1) degradation products don't accumulate beyond limits, (2) microbial contamination doesn't grow, (3) impurity profile remains within specifications. This requires campaign length validation and periodic comprehensive cleaning. Not all same-product carryover is acceptable — depends on stability and growth characteristics.
8.51 Are contamination-control measures in place addressing personnel, equipment, environment, and materials?
- Contamination control risk assessment
- Contamination control procedures
- Dedicated equipment for high-risk products
- Environmental controls (HVAC, pressurization)
- Cross-contamination prevention measures
- Personnel flow controls
- Gowning procedures
- Training on contamination prevention
- No contamination risk assessment
- Shared equipment for high-risk products (e.g., hormones, beta-lactams)
- Inadequate environmental controls
- Personnel flow not controlled
- Gowning inconsistent or inappropriate
- Contamination control strategy not updated after introduction of new product types
Contamination can come from many sources: personnel, equipment, environment, materials, cross-contamination. Controls must address each source. Risk assessment identifies highest risks and prioritizes controls. Typical controls: dedicated facilities for high-risk products (e.g., beta-lactams), air handling for cross-contamination prevention, gowning for personnel contamination, closed systems for sensitive products.
8.52 Is the effectiveness of contamination controls monitored at appropriate intervals?
- Environmental monitoring program
- Microbial and particulate monitoring data
- Cleaning verification testing results
- Finished API testing for contamination
- Monitoring frequency justification
- Trending of monitoring data
- Investigation of excursions
- Risk-based monitoring plan
- No contamination monitoring program
- Monitoring frequency not risk-based
- Excursions not investigated
- Monitoring data not trended
- No correlation between monitoring and product quality
- Surface swab results showing persistent exceedance of action limits without CAPA
Monitoring confirms that contamination controls are effective. Typical monitoring includes: environmental microbial monitoring (air samples, surface swabs, personnel gloves), particulate monitoring for clean areas, cleaning verification at product changeovers, periodic testing of finished APIs for expected contaminants (e.g., cleaning agents). Monitoring frequency is risk-based — more frequent for high-risk, less for low-risk.
Each item shows its evidence, common nonconformities and auditor tips. The clause index has the PDF of all 350 items, formatted for a clipboard.
The rest of the ICH Q7 API GMP audit checklist
350 items across 18 clauses. Back to the clause index.