Product Quality Review (PQR / APR)
A Product Quality Review is the periodic, product-by-product examination of whether a manufacturing process actually stayed in control over a defined window — usually a year. It exists because control is a claim that has to be re-checked against the accumulated evidence: hundreds of batch records, deviations, changes, complaints, and stability results that individually passed but collectively may reveal a drift no single batch showed. Done as intended, the PQR is where a subtle downward trend gets caught before it becomes an out-of-specification result, a rejected batch, or a recall. Done as a formality, it is a template filled in after the fact that documents a year without examining it. ICH Q10 places product quality review among the tools a pharmaceutical quality system uses to verify the ongoing state of control.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 21 LINKSThe Product Quality Review is the annual look-back meant to catch a trend before it becomes a recall — a QMS and GMP element (PQR and APR are one idea, two names) whose value is aggregating the year, not transcribing it.
06 · QUALITY MATURITY — PRODUCT QUALITY REVIEW (PQR / APR), REACTIVE TO ADAPTIVE
The annual review is a template filled in after the fact with a boilerplate "state of control maintained" conclusion that drives no action.
A PQR procedure and schedule exist, but the review lists data without interpreting it and contract-manufactured history is omitted.
The review aggregates testing, deviations, changes, complaints, and stability into real trends and reaches conclusions that drive CAPA and change.
The PQR reads continued-process-verification data to judge whether the process is still validated, focusing scrutiny where risk is highest.
Review findings feed management review as a portfolio health signal; a consistent period and cadence let trends compound across cycles.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 3
Derived from the 3 standards SPEQ maps to this subject, across 2 regulatory bodies: FDA, ICH.
RECORDS & OBJECTIVE EVIDENCE
- A PQR/APR report per product for a consistent, defined review period
- Aggregated testing trends, deviations, changes, complaints, returns, and recalls
- Stability-study outcomes and the qualification/validation status of the equipment
- A quality/technical agreement defining who compiles the review across sites
- Conclusions and resulting actions (CAPA, change control) with quality-unit ownership
COMMON INSPECTION FINDINGS
- A review that lists data without interpreting it (copy-paste conclusion)
- A boilerplate "state of control maintained" conclusion driving no action
- Contract-manufactured batches omitted from the product's review
- Inconsistent review periods preventing year-over-year trend comparison
- Adverse trends identified but never translated into an action
PQR and APR — one concept, two regulatory names
The vocabulary confuses newcomers, so it is worth settling. **Product Quality Review (PQR)** is the term used in EU GMP; **Annual Product Review (APR)** is the term from the US, rooted in 21 CFR 211.180(e), which requires a written record of each drug product reviewed at least annually to determine the need for changes to specifications or manufacturing/control procedures. **ICH Q7** carries the same expectation for active pharmaceutical ingredients under regular quality reviews. They are not three different obligations; they are one discipline — a periodic evidence-based review of a product’s quality history — expressed in three regulatory dialects. A global operation reconciles them into a single review that satisfies each, rather than running parallel paperwork.
The shared purpose across all three is explicit in the US wording: the review is not documentation for its own sake but a decision input — does the accumulated year of evidence indicate that specifications, processes, or controls should change? A PQR that reaches no conclusions and drives no actions has missed the point of the exercise.
What a real review actually examines
A substantive PQR pulls together the strands of a product’s year that are managed separately day to day: the results and trends of critical in-process and finished-product testing; all deviations, non-conformances, and their investigations; every change made to process, equipment, specification, or supplier and whether it performed as intended; rejected and reworked batches; returns, complaints, and recalls; the outcome of stability studies and any adverse trends; the status of qualification and validation for the equipment and utilities involved; and the performance of the material suppliers feeding the product. The value is in the *aggregation*: a single deviation is an incident, but the same deviation appearing across the review period is a signal about the process.
This is where the PQR connects to **continued process verification** — the ongoing-monitoring stage of the process-validation lifecycle. The PQR is the periodic checkpoint that reads the accumulated monitoring data and asks whether the process is still operating as validated. It is also risk-informed: quality risk management shapes which parameters and trends deserve the closest scrutiny, so the review concentrates on what actually threatens quality rather than treating every data series as equally important.
Timing, ownership, and the contract-manufacture complication
A PQR is bounded by a defined review period — conventionally annual, though a product’s risk, volume, and change history can justify a different cadence — and it is owned by the quality unit, which is responsible for the review reaching real conclusions rather than the production function marking its own homework. The review period should be consistent year over year so trends can be compared across cycles rather than reset each time, and a product made in low volume or on an infrequent campaign still owes a review even when a full year yields few batches.
The relationship becomes genuinely harder when manufacture is split across parties. Where a marketing-authorisation holder uses a contract manufacturer, or a product moves through multiple sites, no single party holds all the data the review needs — the CMO has the batch and deviation history, the MAH holds the complaint, stability, and returns picture, and neither review is complete alone. This is precisely why the **quality/technical agreement** must specify who compiles the PQR, what data each party supplies and by when, and how the MAH reviews and takes ownership of the conclusions. A PQR that silently omits the contract-manufactured half of a product’s history is a review of half the evidence — and it is a recurring inspection finding at exactly these interfaces.
The failure mode: the copy-paste review
The characteristic weakness inspectors find is the PQR that lists data without interpreting it — pages of tables, batch counts, and deviation numbers transcribed from the systems of record with a boilerplate "the process remained in a state of control" conclusion that would read identically regardless of what the numbers said. A review that cannot fail is a review that verifies nothing. The tell is a conclusion that does not engage with the data beneath it, or a review whose findings never translate into a single action, CAPA, or change.
A genuine review does the analytical work: it looks for trends across batches, not just pass/fail per batch; it asks whether recurring minor deviations point to a systemic weakness; it connects a slow shift in an assay result to a supplier change made mid-year; and it produces conclusions and, where warranted, actions. Those actions close the loop through the quality system — a trend becomes a CAPA, a needed adjustment becomes a change control, a supply pattern becomes a supplier-qualification action — and the review’s outputs feed management review, where leadership sees which products are healthy and which are drifting. The PQR is only as valuable as the honesty of the analysis and the reality of the actions it drives.
FREQUENTLY ASKED
What is the difference between a PQR and an APR?
None in substance. Product Quality Review (PQR) is the EU GMP term and Annual Product Review (APR) is the US term rooted in 21 CFR 211.180(e); ICH Q7 carries the same expectation for active pharmaceutical ingredients. They are one discipline — a periodic, evidence-based review of a product’s quality history — expressed in different regulatory dialects, and a global operation reconciles them into a single review rather than running parallel paperwork.
What does a Product Quality Review examine?
The aggregated quality history of a product over the review period: testing results and trends, deviations and investigations, changes and their outcomes, rejected and reworked batches, returns, complaints and recalls, stability data, the qualification/validation status of the equipment involved, and supplier performance. The value is in aggregation — a single deviation is an incident, but the same deviation recurring across the year is a signal about the process.
How is the PQR related to process validation?
The PQR is the periodic checkpoint that reads the data produced by continued process verification — the ongoing-monitoring third stage of the process-validation lifecycle — and asks whether the process is still operating as validated. It is where accumulated monitoring evidence is interpreted rather than merely collected.
What makes a PQR inadequate?
Listing data without interpreting it. The classic failing review transcribes batch counts and deviation numbers and appends a boilerplate "state of control was maintained" conclusion that would read identically whatever the data showed. A review that cannot fail verifies nothing; a real one analyses trends across batches and produces conclusions and actions that close the loop through CAPA, change control, and management review.