The ICH Q10 management review is the moment when senior management stops delegating quality and actually governs it: a periodic, documented review of process performance, product quality and the Pharmaceutical Quality System (PQS) itself. It is not a box-ticking exercise: it is what authorities use to judge whether leadership knows its risks and acts on them. In this guide we look at exactly what the ICH Q10 guideline requires, the two review levels it defines (sections 3.2.4 and 4.1), the expected inputs and outputs, a ready-to-adapt model agenda and the findings inspectors raise most often.
What the ICH Q10 management review is
ICH Q10 dedicates a specific section (2.6) to management review, defining it as a direct responsibility of senior management: leadership must govern the PQS through periodic reviews to assure its continuing suitability and effectiveness. EU GMP mirrors the concept: Chapter 1 of EudraLex Volume 4 (para. 1.6, in operation since 31 January 2013) explicitly requires a “periodic management review, with the involvement of senior management” of the operation of the quality system, to identify opportunities for continual improvement of products, processes and the system itself.
Two practical consequences are often underestimated. First: the management review cannot be fully delegated to QA; senior management must actively take part, and the minutes must prove it. Second: the review must produce decisions and resources, not just observations. A review that never allocates resources and never adjusts objectives looks, to an inspector, like a paper exercise.
The two review levels defined by ICH Q10
ICH Q10 distinguishes two complementary reviews, which in practice can be separate meetings or distinct parts of the same meeting:
- Section 3.2.4 — Management review of process performance and product quality: the “operational” level, one of the four PQS elements together with the process performance and product quality monitoring system, the CAPA system and change management. It looks at data: trends, batches, complaints, deviations.
- Section 4.1 — Management review of the Pharmaceutical Quality System: the “system” level. It assesses whether the PQS as a whole achieves its quality objectives and remains adequate, including against organisational changes, acquisitions or new regulations.
Many companies merge the two levels into a single annual meeting: acceptable, provided both perspectives are recognisable in the inputs and in the minutes. ICH Q10 does not prescribe a frequency: it must be defined internally based on the site's risk and complexity, and then followed with discipline.
Topics like this one — PQS governance, quality metrics, inspector expectations — are the bread and butter of The Pragmatic GMP, our free weekly newsletter: one concrete, no-fluff email a week for people working in QA, QC and manufacturing. Subscribe and take your site's management review one step further.
The inputs: what must reach the meeting
ICH Q10 lists precise inputs for each level. For the review of process performance and product quality (3.2.4):
- results of regulatory inspections, audits and other assessments, and commitments made to authorities;
- periodic quality reviews (PQR/APR), including customer satisfaction measures such as complaints and recalls;
- conclusions of process and product monitoring;
- effectiveness of implemented changes, including those arising from CAPA;
- follow-up actions from previous management reviews.
For the review of the PQS (4.1), the inputs shift to the system itself: measurement of achievement of quality objectives and performance indicators of the system's processes, such as the timeliness and quality of complaint, deviation, CAPA and change-control handling, feedback on outsourced activities, self-assessments and external assessments (inspections and customer audits).
The outputs: decisions, not observations
The expected outputs of the operational review (3.2.4) are improvements to manufacturing processes and products, provision, training or realignment of resources, and the capture and dissemination of knowledge (knowledge management, one of Q10's two enablers together with quality risk management). From the system review (section 4.3) the expected outcomes are improvements to the PQS and its processes, allocation or reallocation of resources and personnel training, revisions to the quality policy and quality objectives, and timely documentation and communication of results, including escalation to top management.
Model agenda and comparison of the two levels
The table summarises how to set up the two reviews in practice; adapt it to the size of your site.
| Aspect | 3.2.4 review (process/product) | 4.1 review (PQS system) |
|---|---|---|
| Focus | Process trends, batch quality, complaints, deviations, CAPA | Overall PQS effectiveness and quality objectives |
| Main inputs | PQR, monitoring, inspection outcomes, change effectiveness | Quality-process KPIs, self-inspections, outsourcing, external audits |
| Typical outputs | Process and product improvements, resources, knowledge sharing | Revised quality policy and objectives, resources, training |
| Participants | Site leadership, QA, production, QC, engineering | Senior management, QA, owners of PQS processes |
| Frequency (practice) | More frequent (e.g. quarterly/six-monthly) | Typically annual, or upon significant changes |
A seven-point model agenda: (1) status of actions from the previous review; (2) quality KPIs and their trends; (3) PQR summary and product signals; (4) deviations, CAPA and changes: volumes, timelines, effectiveness; (5) audit and inspection outcomes, internal and external; (6) emerging risks and outsourced activities; (7) decisions: resources, objectives, action plan with owners and due dates.
The findings inspectors raise most often
- Absent senior management: the review exists but leadership does not attend, or the minutes give no evidence of it.
- Incomplete inputs: outsourcing, regulatory commitments or follow-up from previous reviews are missing.
- No traceable decisions: descriptive minutes, with no actions, owners or due dates.
- The loop is never closed: agreed actions are not verified at the next review.
- Declared frequency not respected: the SOP promises a cadence the site does not keep.
A good self-assessment test: take the minutes of the last two years and ask whether an external reader, from those documents alone, would understand the site's three main problems and what leadership decided to fix them. If the answer is no, the review produces paper, not governance — and that is exactly what an inspector will note.
GuideGxP recommendation
Treat the management review as a process, not a meeting: a dedicated SOP with mandatory inputs, a standard data package prepared by QA, minutes with decisions and actions tracked in the CAPA or change-control system, and systematic verification of follow-up at the opening of the next review. Explicitly link outputs to resources: in an audit, it is the most convincing signal that the PQS is genuinely governed.
To master the whole ICH Q series — from Q8 to Q12, with Q9(R1), Q10 and readiness for the new Q1 — take a look at our guide Quality Guidelines ICH Q: what is actually applicable, with a ready-to-use Excel/Word toolkit.
