Usage Examples
- The NIR method is PAT, so its model maintenance plan belongs in the control strategy, not in a standalone lab SOP.
- We are running PAT for feedforward control only; we are not claiming real-time release testing in this filing.
- If the PAT probe drops out mid-run, the contingency testing plan is what keeps the batch releasable.
What is Process Analytical Technology (PAT)?
Process Analytical Technology is a system for designing, analyzing and controlling pharmaceutical manufacturing through measurements taken during processing rather than after it, so quality is assured by in-process control instead of end-product testing alone.
Process Analytical Technology exists because end-product testing samples a batch after every chance to influence it has passed. 21 CFR 211.165(a) still demands a laboratory determination of conformance to final specifications before release, and a failure there is a rejected batch, not a corrected one. PAT moves the measurement into the process, while the process can still respond.
Process Analytical Technology covers the whole measurement-to-action chain: the in-line, on-line or at-line analyzer, the model that converts a signal into a quality attribute, the feedforward or feedback control it triggers, and the maintenance that keeps that model valid. PAT stops short of the release decision. Releasing on process data is real-time release testing, a separate ICH Q8 concept that PAT can support but does not itself confer.
Process Analytical Technology is applied as an element of the control strategy, which ICH Q8(R2) defines as a planned set of controls derived from product and process understanding. ICH Q13 calls PAT well-suited to continuous manufacturing, citing in-line UV flow cells, near-infrared for blend uniformity, and on-line HPLC for reaction conversion. PAT measurement points belong on the process flow diagram in the dossier, alongside the critical steps where process controls are conducted.
Not to be confused with
- Real-time release testing (RTRT)
- RTRT is a release decision made from process data; PAT is the measurement and control system that can feed it. ICH Q13 states RTRT is not a regulatory requirement, so running PAT without claiming RTRT is a normal, filable configuration.
- Quality by Design (QbD)
- QbD is the development approach, defined by predefined objectives and product and process understanding. PAT is one tool used inside it. ICH Q8(R2)'s enhanced-approach comparison lists "PAT tools utilised" as a characteristic of QbD, not as its definition.
- In-process controls under 21 CFR 211.110
- the CFR requires written in-process controls and tests for every batch regardless of technology. PAT is one way to satisfy that; a manual sample pulled to a QC lab is another, and it is equally compliant.
- Continuous manufacturing
- CM is a manufacturing mode in which material is continuously fed in, transformed and removed. PAT is a measurement and control approach. ICH Q13 pairs them because CM needs real-time signal, but batch processes use PAT too.
PAT itself is not mandated. These are the obligations that govern it once you use it.
What you must do
- 1Establish written procedures describing the in-process controls and tests conducted on appropriate samples of in-process materials of each batch; PAT can satisfy this obligation but does not remove it21 CFR 211.110(a)
- 2Perform an appropriate laboratory determination of satisfactory conformance to final specifications, including identity and strength of each active ingredient, before releasing a batch21 CFR 211.165(a)
- 3Scope the PAT system to include the analyzer, the model and the resulting control action, because ICH defines PAT as a system for designing, analyzing and controlling manufacturing through timely measurements, not as an instrumentICH Q8(R2) Part I Glossary
- 4Support any real-time release claim with process data comprising a valid combination of measured material attributes and process controls, not with the analyzer output aloneICH Q8(R2) Annex Glossary
- 5Describe the associated reference test method whenever RTRT is proposed, and do not assume RTRT is expected of youICH Q13 Section 4.2
- 6Include alternative or additional quality controls in the proposed control strategy to mitigate the risk of data lapses, such as recalibrating an NIR probe mid-runICH Q13 Section 4.2
Common mistakes
Treating the analyzer as the deliverable
Teams qualify an NIR probe and call PAT done. ICH defines PAT as a system spanning measurement, model and control action, so a probe with no control response and no model maintenance plan generates data nobody acts on and a reviewer cannot credit as a control.
Assuming PAT automatically buys real-time release
RTRT is a separate claim carrying its own dossier burden: reference test method, model justification and sampling strategy, contingency plans. ICH Q13 says plainly that RTRT is not a regulatory requirement, and asserting an RTRT approach you have not justified invites a deficiency on the entire control strategy.
No plan for when the measurement stops
ICH Q13 expects the control strategy to include alternative or additional quality controls for data lapses, and names probe recalibration as the example. Probes drift and fail. Without a pre-agreed contingency test, a short data gap converts a running batch into an investigation and potentially diverted material.
When This Matters
- The NIR method is PAT, so its model maintenance plan belongs in the control strategy, not in a standalone lab SOP.
- We are running PAT for feedforward control only; we are not claiming real-time release testing in this filing.
- If the PAT probe drops out mid-run, the contingency testing plan is what keeps the batch releasable.
Frequently Asked Questions
No. PAT is optional. 21 CFR 211.110(a) requires written procedures describing in-process controls and tests on samples of in-process materials of each batch, but it does not specify the measurement technology. ICH Q13 states that real-time release testing, PAT's usual payoff, is not a regulatory requirement for continuous manufacturing implementation.
Related Use Cases
- Pharma Use Cases
Cut NDA and sNDA prep time by 60% with AI-assisted drafting and automated readiness checks
- Biotech Use Cases
Compress IND prep from 8-12 weeks to under 3 weeks with AI-assisted drafting and validation
- CMC Workflows
Track ICH quality guidelines automatically and get alerts when changes impact your products
- Quality/QA Workflows
Track GxP regulation changes and enforcement trends
