IPCIn-Process Control
In-Process Controls (IPCs) are the tests, checks and measurements taken on product or process during manufacturing to confirm the batch is performing inside its validated control strategy. Pulled correctly they are the difference between catching a deviation in real time and discovering it at finished-product release; pulled badly they become a paperwork ritual that adds cost without protecting quality.
On this page · 9 sections
- 1What an IPC Is — and What It Is Not
- 2The Regulations That Require IPCs
- 3Where IPCs Live in the Process Flow
- 4Designing the IPC Plan (the Risk-Based Way)
- 5Sampling Plans, Acceptance Criteria and Statistical Rigour
- 6When an IPC Fails — OOS, OOT and the Real-Time Decision
- 7Real-Time IPCs, PAT and the Continuous-Verification Future
- 8Common IPC Failures in FDA 483s
- 9How V5 Handles In-Process Controls
How does IPC 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 an IPC Is — and What It Is Not
An In-Process Control (IPC) is a test, check or measurement taken on the product or the process during manufacturing — between the receipt of starting materials and the release of the finished batch — to confirm the batch is performing inside its validated control strategy. The defining word is product. An IPC asks 'is the material we are making what it needs to be at this point in the process?' That distinguishes it from an in-process verification (IPV), which asks 'did the operator perform the step the way the procedure required?' and from finished-product release testing, which asks 'is the final batch within spec?'
The categories overlap in everyday speech but separate cleanly in a well-designed batch record. The IPV proves the dispense happened with the right material, the right scale and the right witness. The IPC proves the blend that resulted from that dispense has the assay, blend uniformity and moisture content the process needs at that point. Both are required; both live in the BMR; neither substitutes for the other.
02The Regulations That Require IPCs
Every major regulated-manufacturing framework requires in-process testing, even where the phrase 'in-process control' is not used. The common requirement is that the manufacturer has identified the critical points in the process, defined what must be measured at each, set the acceptance criteria in advance, and documented the result before the batch progresses past that point.
| Framework | Citation | What is required |
|---|---|---|
| FDA drug cGMP | 21 CFR 211.110 | Written procedures for in-process sampling, with specifications and rejection criteria |
| FDA drug cGMP | 21 CFR 211.160 | Laboratory controls including in-process testing established in advance |
| FDA supplements | 21 CFR 111.70(c) | Specifications for in-process production at points, steps, or stages where control is needed |
| FDA devices | 21 CFR 820.80(c) | Acceptance activities to ensure in-process product meets specified requirements |
| FDA food | 21 CFR 117 Subpart C | Preventive controls including process controls with monitoring at established frequencies |
| EU GMP | Volume 4 Part I Ch.6 | In-process controls performed at appropriate stages of production |
| ICH Q7 (APIs) | Section 8.30 | In-process testing performed and the results recorded for batch evidence |
| ICH Q10 | Section 3.2.3 | In-process monitoring as part of the manufacturing control strategy |
| ISO 13485:2016 | Clause 8.2.5 | Monitoring and measurement of product at appropriate stages |
Two themes unite the citations. First, the IPC plan is required to exist in writing before the batch starts — not derived from inspector questions after a deviation. Second, the criteria for acceptance must be established in advance: 'we will measure assay at the granulation step and accept 95.0–105.0% on a single sample' is an IPC; 'we measure assay sometimes' is not.
03Where IPCs Live in the Process Flow
IPCs cluster at the points where a deviation, if missed, will be costly or impossible to correct downstream. The exact list depends on the process, but the design principle is universal: place an IPC immediately before a step that locks the batch into a state the next step cannot undo.
Solid-dose pharmaceutical (tablet) example
- Dispensing: tare-verified weights, material identity scan (this is an IPV with a paired IPC for assay-adjusted charge calculation).
- Granulation: granulation endpoint (torque, power, particle size), loss-on-drying after drying.
- Blending: blend uniformity by stratified sampling, sieve analysis, bulk density.
- Compression: average and individual tablet weight, hardness, thickness, friability, disintegration.
- Coating: weight gain, dissolution after coating, visual defects.
- Packaging: fill count, leak test, label verification, lot/expiry print check.
Biologic example
- Cell expansion: viable cell density, viability, glucose, lactate, dissolved oxygen, pH.
- Harvest: turbidity, titer by quick assay.
- Purification: A280 protein concentration, conductivity at chromatography pool, bioburden after every open step.
- Fill-finish: pre-fill bioburden, post-fill weight check, container-closure integrity test (CCIT).
Food / dietary supplement example
- Receiving: identity verification, moisture for hygroscopic ingredients, gluten screen for allergen-free claims.
- Mixing: assay or actives uniformity, moisture, microbial bioburden screen.
- Encapsulation/tableting: fill weight, content uniformity, disintegration.
- Packaging: torque on closures, fill count, label and 2D-barcode print verification.
04Designing the IPC Plan (the Risk-Based Way)
ICH Q9 risk-management thinking has moved IPC design away from 'we test everything we can' to 'we test what controls a CQA that has no other line of defence.' The modern IPC plan is the output of a process-knowledge exercise: each critical quality attribute is mapped to the process parameters that influence it, each parameter is rated for criticality and detectability, and IPCs are placed where a critical parameter is not already controlled by a validated engineering control or upstream qualification.
- List every CQA for the product (assay, uniformity, dissolution, sterility, identity, appearance).
- For each CQA, list the CPPs that influence it — from a fishbone or a DoE.
- Rate each CPP for severity, probability and detectability under current controls.
- Where current controls are weak, place an IPC at the point where the parameter manifests.
- Set acceptance criteria from the design space (ICH Q8), not from historical averages.
- Define the sampling plan: how many, how often, how stratified.
- Define what happens when the IPC fails (hold, abort, investigate, regrade).
- Validate the IPC method and the sampling plan against ICH Q2 and USP <1010>.
05Sampling Plans, Acceptance Criteria and Statistical Rigour
An IPC result is only as good as the sample that produced it. Two sampling errors dominate FDA observations: insufficient sample size to detect the variation present in the batch, and non-stratified sampling that systematically misses parts of the batch. Both are statistical, not procedural, problems — and both are addressable by an honest sampling-plan design.
Sample size
For attributes data (pass/fail) the AQL framework in ANSI/ASQ Z1.4 gives defensible plans. For variables data (assay, weight, hardness) the sample size is driven by the required confidence and the expected process variation; for blend uniformity, USP <905> and the 2003 PQRI draft drive 10 or more stratified samples at top/middle/bottom of the blender.
Stratified sampling
Pulling 10 tablets from the same chute is not a sample of the batch — it is a sample of the chute. Stratified sampling pulls at start/middle/end of the run, from multiple ports of the blender, from each filling head of a multi-head packager, to give the batch-level inference the IPC is supposed to provide.
Acceptance limits vs action limits
Acceptance limits define pass/fail. Action limits sit tighter and trigger investigation or process adjustment before the batch fails. Modern IPC plans operate on both: action limits drive real-time control, acceptance limits drive disposition.
| Pattern | Acceptance limit | Action limit | What happens on action breach |
|---|---|---|---|
| Tablet weight (compression) | ± 7.5% of mean | ± 5% of mean | Press adjusted; sample re-pulled |
| Granulation LOD | 1.5–3.0% | 1.8–2.7% | Dry time adjusted in the next sub-lot |
| Blend uniformity (RSD) | ≤ 5% | ≤ 3.5% | Mixing time extended; resample |
| Bioburden post-filtration | ≤ 10 CFU / 100 mL | ≤ 2 CFU / 100 mL | Investigation initiated, line halted on second breach |
06When an IPC Fails — OOS, OOT and the Real-Time Decision
An IPC outside its acceptance limit is an out-of-specification (OOS) result and triggers FDA's 2006 OOS Guidance investigation pathway, even though the IPC is not a release test. An IPC inside its acceptance limit but outside its historical control-chart envelope is an out-of-trend (OOT) result and triggers the OOT investigation. Both pathways must be defined in advance; both must distinguish lab error from manufacturing-process error before deciding the batch fate.
- Pause: the next step cannot start while the IPC is under investigation.
- Lab-error check: re-pull, re-test by the same analyst, then by a second analyst.
- If lab-error confirmed: invalidate the original result, document, proceed with second result.
- If lab-error not confirmed: open formal investigation, treat result as valid, determine manufacturing root cause.
- Disposition: continue (with rework if needed), reject, or escalate to MRB for use-as-is justification.
07Real-Time IPCs, PAT and the Continuous-Verification Future
The traditional IPC is a sample pulled by an operator, walked to a lab, analysed, and returned as a number an hour later. PAT (Process Analytical Technology, FDA 2004) replaced this round trip for many parameters with in-line or at-line sensors that produce the IPC result inside seconds: NIR for blend uniformity, Raman for content uniformity, in-line LOD probes for granulation endpoint, on-line UV-Vis for column elution profiles. The advantage is not faster paperwork — it is feedback control: the process can be adjusted while it is still on, before the next sub-lot is in trouble.
PAT-based IPCs change the batch-record evidence: instead of a single number from a single sample, the BMR carries the continuous data stream that informed the in-line decision. The validation effort is heavier (ICH Q2 for the method, ICH Q14 for analytical-procedure development, GAMP 5 for the system) but the inspection story is simpler: the evidence is the process, not a sample of the process.
08Common IPC Failures in FDA 483s
- IPC pulled but not recorded contemporaneously — the value handwritten on a glove and copied into the BMR an hour later.
- Sampling plan written for a smaller batch size than the one running; not re-validated when scale changed.
- Acceptance limits 'updated' silently to match drifting historical data, with no change control or risk reassessment.
- IPC investigation closed without ruling out manufacturing root cause when the lab cause could not be confirmed.
- Stratified sampling defined in the SOP but not honoured on the floor (operator pulls a convenience sample at one location).
- IPC method not requalified after instrument or reagent change.
- IPC results trended in a spreadsheet that is not subject to Part 11 audit trail.
- No defined action on action-limit breach — the action limit was decorative.
- IPC values backdated when the original record was 'lost'.
09How V5 Handles In-Process Controls
In V5 the IPC plan is a property of the MMR, not of the operator memory or the local lab spreadsheet. When the MMR is approved, V5 generates the sampling schedule, attaches the acceptance and action limits to each IPC step, and binds each step to the LIMS test method. At execution time the batch record forces the IPC to be entered before the next step can begin — and the data flows automatically into the SPC chart, the CPV dataset and the deviation system if it breaches.
- Acceptance and action limits come from the validated control strategy, not from a free-text field.
- Sampling location, time and sample size are mandatory at recording, not optional.
- PAT and at-line instrument readings stream into the BMR with full provenance.
- OOS/OOT investigations open automatically with linked evidence (raw data, instrument log, prior trend).
- Trending dashboards are role-scoped: production sees real-time, QA sees trend, regulators see audit trail.
- Method requalification triggers raise change-controls before the IPC can be used on a new batch.
Frequently asked questions
Q.What is the difference between an IPC and a release test?+
An IPC tests product or process state during manufacturing to inform the next step; a release test confirms the finished batch meets its specification before distribution. The same parameter can appear in both — assay measured in-process and again at release — but the decision the data drives is different.
Q.Does every IPC failure require an OOS investigation?+
Yes when the failure is on an established specification. The 2006 OOS Guidance applies to in-process specifications, not just finished product. The investigation can be brief if lab error is confirmed, but it cannot be skipped.
Q.Can PAT replace traditional IPCs?+
Yes, where the PAT method is validated against the reference method under ICH Q2 and the model is maintained under ICH Q14. Real-time release testing under EMA / FDA guidance allows the PAT result to replace the conventional in-process and even release test where the validation supports it.
Q.Who owns the IPC plan — manufacturing or quality?+
Both. Quality owns the specifications and acceptance criteria; manufacturing owns the execution and the sampling. The MMR is the single document where both signatures live, and changes require both functions to re-approve under change control.
Q.How do IPCs feed continued process verification (CPV)?+
Each IPC result writes to the CPV dataset along with the batch identifier, the process parameter values at the sample point, and the operator/instrument provenance. The SPC chart for the IPC is the live continued-verification artefact under ICH Q10 §3.2.3.
Q.What's the smallest defensible IPC plan?+
One IPC per CQA, placed at the step where that CQA first manifests, with statistically defensible sampling and pre-set acceptance and action limits. Anything smaller leaves a CQA un-controlled; anything larger should justify its cost against the risk reduction it provides.
Primary sources
- 21 CFR 211.110 — Sampling and testing of in-process materials and drug products
- 21 CFR 211.160 — General requirements (laboratory controls)
- 21 CFR 111.70 — Specifications (dietary supplements)
- 21 CFR 820.80 — Receiving, in-process, and finished device acceptance
- ICH Q7 §8 — Production and in-process controls (APIs)
- ICH Q8(R2) — Pharmaceutical Development (control strategy)
- ICH Q10 — Pharmaceutical Quality System
- USP <1010> — Analytical data — interpretation and treatment
Further reading
- In-Process Verification (IPV)Distinct from IPC: IPV confirms a step happened; IPC tests what the step produced.
- Critical Process Parameter (CPP)IPCs typically monitor a CPP or the CQA it controls.
- Critical Quality Attribute (CQA)The product attribute the IPC is protecting.
- Control StrategyIPCs are the in-line layer of the ICH Q10 control strategy.
- SPCTrended IPC data feeds the SPC charts used in continued process verification.
- Out-of-Specification (OOS)An IPC result outside its limit triggers an OOS or OOT investigation.
- Out-of-Trend (OOT)Trending IPCs catches drift before it crosses spec.
- BMREvery IPC result lands in the BMR as part of the batch evidence.
Want to see how IPC could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.