SOP: Management Review of the Pharmaceutical Quality System

This is a ready-to-use SOP that governs how management review of the pharmaceutical quality system (PQS) is planned, run, and closed. It is the procedure the Quality Management Review Meeting Record points back to as its governing document. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows. Verify each cited regulation against the current source before you rely on it.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> conducts periodic management review of the pharmaceutical quality system so that senior management examines the system’s performance on a defined schedule, renders a documented conclusion on its effectiveness, commits the resources the data shows are needed, and drives every resulting action to verified closure.

2. Scope

This procedure applies to <<FILL: site(s) / business unit(s)>> and covers the full review hierarchy: any tier or operational quality review that feeds it, the site or business-unit executive management review, and, where applicable, the regional or corporate/global quality council review it rolls up to. It does not itself define individual system procedures (deviations, CAPA, change control); those are governed by their own SOPs and referenced here only as inputs.

3. Responsibilities

4. Definitions

• Management review: a structured, periodic evaluation of the PQS by senior management, with documented inputs, decisions, and follow-up actions, per ICH Q10 and (where applicable) ISO 13485:2016 section 5.6.
• Effectiveness verdict: senior management’s documented conclusion on whether the PQS is effective, conditionally effective, or not effective for the period reviewed.
• Escalation pyramid: the tiered structure (tier/shift meeting, operational quality review, site executive management review, and, where applicable, regional or global quality council) through which unresolved issues and decisions travel up and down.
• Action tracker: the continuously maintained log of every action arising from any tier of review, with a single named owner, a due date, and a link to the objective evidence of closure.

5. Procedure

5.1 Set and publish the schedule

1. Define the review interval for each tier in the escalation pyramid applicable to your organization (for example: monthly operational review, quarterly executive management review, semi-annual global quality council) and state the basis for the chosen interval.
2. Publish the year’s review dates in advance and define quorum for the executive management review in this procedure, for example “the review cannot proceed without the site head and the Head of Quality present.”
3. Define the trigger and process for an out-of-cycle review following a major event (a critical recall, a serious inspection finding, a significant data integrity signal).

5.2 Collect and curate the inputs

1. At a fixed point before each review (recommended: 3 to 4 weeks before an executive review), the coordinator pulls each standing input listed in section 6 from its source system against a single, stated data cutoff date.
2. Apply the same metric definitions every period, and across every site if the organization is multi-site, so trends and cross-site rollups are genuinely comparable.
3. Functional leads convert raw metrics into a short narrative: the number, whether it is in or out of tolerance, the trend, the likely cause, and a proposed action where warranted.
4. Distribute the pre-read package at least <<FILL: number>> business days before the meeting.

5.3 Run the review

1. Open with the status of every action from the previous review; this item is never skipped.
2. Walk each standing input as a trend with interpretation, not a raw count.
3. The chair drives every issue raised to one of two exits: accepted-and-tracked-elsewhere, or a new action with a single named owner and a due date.
4. Where the data indicates the system is under-resourced, the chair makes or defers, explicitly and on the record, a resourcing decision.
5. Close with senior management’s explicit effectiveness verdict: effective, conditionally effective, or not effective, stated as a sentence, not implied by silence.

5.4 Act on the effectiveness verdict

1. Effective. Proceed on the standard cadence; track any named exceptions as standard actions.
2. Conditionally effective. Assign a resourced remediation plan with a committed re-assessment date for the affected area; consider a shortened review interval for that area until it returns to effective.
3. Not effective. Escalate to corporate/regional/global quality the same cycle; assign an executive owner; assess whether the gap triggers a health-authority notification obligation under the organization’s regulatory commitments; increase review frequency for the affected system until it recovers.

5.5 Record, cascade, and track

1. Complete the management review record within <<FILL: number>> business days; the chair and Head of Quality sign it.
2. Load every new action into the action tracker (see the companion Management Review Action Tracker) the same day, with owner, due date, and a link back to this meeting.
3. Cascade decisions and resource commitments down to the functions responsible for executing them, and escalate unresolved items up the pyramid per section 5.1.
4. Confirm previously “approved” resource commitments actually materialized (a requisition filed, a system procured); an approved-but-unactioned commitment is itself an input to the next review.

6. Standing inputs (the agenda)

At minimum, every review draws on: process performance and product quality trends; deviations and investigations; CAPA status and effectiveness; complaints; change control status; internal, supplier, and regulatory audit/inspection outcomes; supplier and vendor quality; recalls and field actions; regulatory intelligence and commitments; training and resource adequacy; customer/patient feedback and post-market or pharmacovigilance signals where relevant; the status of every prior action; and progress against quality objectives.

7. Acceptance criteria

• The review is held on the interval this SOP defines, with any slip documented and justified.
• Senior management, named and present, chairs the review; a review without them present is not compliant with this procedure.
• Every standing input in section 6 is addressed, presented as a trend with interpretation and a stated data cutoff.
• Every prior action’s status is reviewed first, and every new action carries a single named owner and a due date.
• A documented effectiveness verdict is recorded every time, with the corresponding action from section 5.4 taken where the verdict is not simply “effective.”
• The action tracker reconciles to the record; no action exists in one and not the other.

8. Records generated

• Quality Management Review Meeting Record (see the paired Record template).
• Management Review Action Tracker (see the paired Log template).
• Pre-read data package and source-system extracts referenced by the record.

9. References

ICH Q10, Pharmaceutical Quality System, section 3.2.4 (management review of process performance and product quality). ICH Q9(R1), Quality Risk Management (risk-based prioritization of review inputs). EudraLex Volume 4, Chapter 1, Pharmaceutical Quality System. ISO 13485:2016, section 5.6 (management review), where a device or combination-product quality system is in scope. 21 CFR Part 820 harmonized with ISO 13485 (QMSR), effective 2 February 2026, where combination products are in scope.

Confirm the current version and clause numbers of each reference before issue.

10. Revision history

11. Approvals

Filled specimen: schedule and quorum definition

The following shows the schedule and quorum section completed for an example site, so you can see the level of specificity expected. The company and names are illustrative.

Common inspection findings this SOP prevents

• No defined interval in procedure, so a missed or delayed review has nothing to be measured against.
• Quorum undefined, so a review “happens” without senior management ever actually attending.
• Standing inputs left to whoever remembers to bring them, so a required category quietly disappears from the record.
• No defined trigger for an out-of-cycle review, so a major event waits for the next scheduled quarter.
• No procedural link between the effectiveness verdict and a concrete next step, so “not effective” and “effective” carry the same consequences in practice.

How to adapt this SOP

1. Set your document number, owner, and effective date in the header.
2. Map section 5.1’s escalation pyramid to your real organizational tiers; a single-site company can delete the regional/global layer.
3. Confirm the standing input list in section 6 against your actual source systems and add any local inputs (product quality review, process monitoring, stability signals).
4. Point sections 8 and 5.5 at your real record and action-tracker documents.
5. Confirm every regulation in section 9 against the current published version before issue.