Dashboards & KPIs
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Glossary Term
APQR
The yearly look-back that proves a product's process and quality stayed in control.
The Annual Product Quality Review pulls a year of batch, deviation, change, and complaint data into one verdict: is this product's process still consistent and its specifications still appropriate?
On this page
What an APQR is
The Annual Product Quality Review (APQR) — called the Product Quality Review (PQR) in EU GMP — is a periodic (normally yearly) review of all batches and quality data for a product, conducted to confirm the consistency of the existing process, the appropriateness of current specifications, and to identify opportunities for product and process improvement.
It is required by 21 CFR 211.180(e) in the US and EU GMP Chapter 1 (§1.10) in Europe — and while the two texts differ in detail, the intent converges: look back across a year of manufacturing for one product and ask whether it is still in control. A typical APQR pulls together batch records and yields, starting-material and packaging-material data, in-process and finished-product results and trends, out-of-specification and out-of-trend results, deviations and their investigations, changes made (and whether they had the intended effect), returns/complaints/recalls, stability data, the adequacy of corrective actions, and the qualification/validation status of relevant equipment, utilities, and the analytical methods — plus, in the EU, the status of technical agreements.
The output is a documented review with conclusions and, where the data warrants, recommended actions — process improvements, specification revisits, revalidation triggers, or CAPAs. It is a controlled document in its own right, reviewed and approved by quality.
APQR vs management review
An APQR is product-specific and data-heavy — one product, a year of batches, deep into the numbers. Management review is system-level and periodic — the whole QMS, for leadership. APQR findings are a natural input to management review, but they are different reviews with different scopes and audiences. Conflating them — a management review that name-checks products instead of a real per-product data review — is a finding.
Why the APQR is mostly a data-gathering problem
The hard part of an APQR is rarely the analysis — it is assembling a year of data scattered across batch records, the deviation log, the change register, the OOS system, the stability programme, and the complaint file. Teams routinely spend more effort compiling the review than interpreting it, and the compilation is where errors creep in: a deviation missed because it lived in a different system, a change whose effectiveness was never checked, a trend invisible because the data was never brought together.
Inspectors probe exactly these seams. They check that the APQR was actually performed on schedule (a late or skipped review is a finding), that it genuinely covers the required elements rather than a template walk-through, that it identifies adverse trends rather than smoothing them away, and — critically — that the actions it recommends were actually carried out. An APQR that flags a recurring deviation and recommends a CAPA that never happened is worse than one that missed it.
When the underlying records are connected — deviations linked to batches, changes linked to products and their effectiveness checks, CAPAs linked to their triggers — the APQR becomes a query rather than an archaeology project, and the trends it surfaces are trustworthy because the data ties together. When they are scattered across disconnected systems, the review is only as complete as the person compiling it remembered to include.
Where the APQR requirement lives
- 21 CFR 211.180(e) — the US requirement: written records reviewed annually to evaluate quality standards and determine the need for changes to specifications or procedures
- EU GMP Chapter 1, §1.10 — the EU Product Quality Review: the explicit list of elements (materials, in-process/finished results, failed batches, deviations, changes, stability, returns/complaints/recalls, CAPAs, qualification status, technical agreements)
- ICH Q10 — the pharmaceutical quality system; the APQR is a continual-improvement and process-performance mechanism within it
- ICH Q7 — for active pharmaceutical ingredients, the equivalent annual quality review of APIs
- EU GMP Chapter 7 — outsourced activities; where manufacturing is contracted, the PQR responsibilities are shared and must be defined in the technical agreement
- WHO TRS guidance — the global reference for jurisdictions modelling their product-review requirements
Running an APQR that holds up
A defensible APQR is built continuously, not assembled in a panic at year-end. The pattern that works:
Define scope and period per product. One review per product (or product family where justified), covering a defined twelve-month period, with the required elements enumerated so nothing is silently dropped.
Pull the data from the systems of record. Batch results and yields, in-process and release data with trends, OOS/OOT events, deviations and their investigations, changes and their effectiveness checks, stability results, complaints/returns/recalls, and qualification/validation status. The quality of the review depends entirely on the completeness of this pull.
Analyse, don't just list. The value is in the trending and the cross-element view — does a cluster of deviations correlate with a change? Is a specification consistently met by a wide margin (revisit it) or barely (investigate)? Are stability trends consistent with the registered shelf life? A list of data is not a review.
Conclude and act. Document conclusions, raise CAPAs or revalidation triggers where warranted, and — the part inspectors verify — close those actions. Feed the significant findings into management review.
The discipline that makes this sustainable is connected records: if deviations, changes, and results already carry product and batch context, the annual pull is a filter, not a reconstruction.
What strong APQR programs share
APQR programs that pass inspection and actually drive improvement share these controls:
The recommendation that was never carried out
An APQR that correctly identifies an adverse trend and recommends an action is only as good as the action's completion. The most damaging APQR finding is not a missed trend — it is a documented recommendation that was never executed, because it proves the review is a paperwork exercise rather than a control. Tracked, closed actions are what make the APQR real.
- A scheduled, tracked review calendar — every product reviewed on time; late reviews flagged before they become findings
- A defined element checklist — the §1.10 / 211.180(e) elements enumerated so coverage is complete and consistent
- Connected source data — deviations, changes, OOS, complaints, and results carrying product/batch context for a clean annual pull
- Genuine trending — data analysed across batches and elements, adverse trends identified rather than smoothed
- Change-effectiveness review — changes made in the period assessed for whether they achieved the intended effect
- Documented conclusions and actions — recommendations recorded as tracked CAPAs or revalidation triggers
- Action closure — the actions the APQR recommends actually completed and evidenced
- Management-review linkage — significant APQR findings fed into the system-level review
- Contract-manufacturing agreements — shared PQR responsibilities defined where manufacturing is outsourced
How Complere supports the APQR
Complere does not auto-generate a finished APQR document — the review, the trending interpretation, and the conclusions are quality judgement, and a platform that claimed to write your product quality review would be overselling. What Complere removes is the compile problem, which is where most of the APQR effort and most of the risk actually sit.
Deviations, CAPAs, changes, OOS events, complaints, and quality events are captured as connected records linked to product and batch context in CAPA & Deviations and the related modules — so the annual data pull for a product is a filtered query rather than a hunt across disconnected systems. Dashboards & KPIs surface the trends an APQR reports on — deviation patterns, CAPA status and aging, change throughput — across the review period. Changes carry their context through change control, so the “did this change have its intended effect” question has a traceable answer. The review document itself is a controlled document, reviewed and approved with electronic signatures, and the actions it raises become tracked CAPAs that can be driven — and proven — to closure. Significant findings feed naturally into management review.
The division is clean: the analysis, the trending interpretation, and the conclusions stay yours; the data assembly, the trend visibility, and the action tracking — the parts that consume the time and create the gaps — are where Complere helps.
Frequently asked questions
Common questions about APQR sourced from regulatory references and inspection patterns.
What is an APQR (or PQR)?
The Annual Product Quality Review (APQR), called the Product Quality Review (PQR) in EU GMP, is a periodic review of all batches and quality data for a product, confirming process consistency, the appropriateness of current specifications, and opportunities for improvement. It is required by 21 CFR 211.180(e) and EU GMP Chapter 1.
What does an APQR cover?
Typically: batch records and yields, starting-material and packaging data, in-process and finished-product results and trends, OOS and OOT results, deviations and investigations, changes made, returns/complaints/recalls, stability data, and the status of qualification/validation and technical agreements - for one product over the review period.
How is an APQR different from management review?
An APQR is product-specific and data-heavy (one product, a year of batches). Management review is system-level and periodic (the whole QMS, for leadership). APQR findings are a natural input to management review, but they are different reviews with different scopes.
Does Complere generate the APQR document?
No - the review and its conclusions are quality judgement. What Complere removes is the compile problem: deviations, CAPAs, changes, OOS events, and complaints captured as connected records linked to product and batch context, with dashboards surfacing the trends. The analysis stays yours; the data assembly is where Complere helps.
Continue Exploring
Explore related topics, modules, and compliance resources for a deeper understanding of your quality system.
See the records an APQR compiles, connected in one system
Walk through the modules and workflows that address this area inside a controlled, validation-ready quality system.