The conclusion is the only part of the PQR most readers will see, and it is the part inspectors compare with the body. When the body reports nine deviations with the same cause, an adverse stability trend and a supplier at the edge of specification, and the conclusion says 'the process is in a state of control and no actions are required', the finding is not about the conclusion. It is about whether the site's quality system can be trusted to evaluate its own data. This guide is about writing conclusions that match the evidence and actions that go somewhere.
The conclusion answers three questions
Paragraph 1.10 defines the objectives: consistency of the process, appropriateness of specifications, trends, and improvements. The conclusion should answer them one at a time, in words that could only apply to this product in this period.
- Consistency: state whether the critical parameters were stable and capable, name any that were not, and name the cause where known. 'The process was consistent for all critical parameters except tablet hardness, which showed a downward shift from batch 24-030 attributed to the change of lubricant supplier (CC-24-041); capability remains acceptable at Ppk 1.4 and the shift is being monitored under action 3.'
- Specifications: state whether the finished product and starting material specifications remain appropriate, and name any that do not. 'The in-process limit for blend uniformity RSD generated seven deviations, none of which affected finished product content uniformity; the limit is tighter than the process requires and a change control to widen it within the registered range is action 4.'
- Improvements: list what will change. If the answer is nothing, say what was considered and why nothing is needed, because 'no actions' with no reasoning reads as 'nobody looked'.
From finding to action
Paragraph 1.11 requires the manufacturer and the MAH to evaluate the results and assess 'whether corrective and preventive action or any revalidation should be undertaken'. ICH Q7 2.51 says the same for APIs and adds that the reasons for the action should be documented and the actions completed 'in a timely and effective manner'. So every action in the PQR needs a stated reason (the finding it addresses), an owner, a due date, and a route into a system that tracks it: CAPA, change control, the validation master plan, the supplier management programme, or the specification review process. An action that lives only in the PQR action table is not tracked, because nobody opens the PQR again until next year.
- Findings about recurring deviations become CAPA, with the PQR referenced as the source.
- Findings about specifications or limits become change controls, and where the specification is registered, a variation assessed by regulatory affairs.
- Findings about drift or capability become monitoring actions under ongoing process verification, or, if the process has moved outside its validated state, a revalidation decision.
- Findings about suppliers become supplier management actions: audit, requalification or a second source.
- Findings about qualification or agreements become engineering or contracts actions with dates.
Revalidation: when the PQR should say it
EU GMP Annex 15 expects the validated state to be maintained and reviewed, and the PQR is one of the places where the evidence is gathered. If a critical parameter shows a sustained shift that the site cannot explain, or capability has fallen below the site's threshold, or a change has been made whose effect on the process has not been demonstrated, the honest conclusion is that the validated state is in question and a documented assessment is needed. The PQR does not perform the revalidation. It raises the question and records the decision. Sites that never raise it, on any product, in any year, invite the inspector to raise it for them.
Feeding management review
ICH Q10 section 3.2.4 lists 'periodic quality reviews' among the inputs to management review of process performance and product quality, and section 4.1 requires management review of the pharmaceutical quality system itself. The PQR is therefore not complete when it is signed; it is complete when its conclusions have been presented to the people who can authorise resources and its actions have been accepted into the management review action log. The practical mechanism: a one-page PQR summary per product or group, tabled at the quality management review, listing the three answers and the actions, with a column for status at the next meeting. Paragraph 1.11 also requires that the effectiveness of the procedures for managing PQR actions is verified during self-inspection; put it on the self-inspection checklist.
Feeding ongoing process verification
EU GMP Annex 15, section 5.28 onwards, describes ongoing process verification as the monitoring of product quality throughout the lifecycle 'to ensure that a state of control is maintained', with the relevant process trends evaluated, the extent and frequency of the verification reviewed periodically and adjusted as process understanding improves, and statistical tools used where appropriate to support conclusions about variability and capability (5.30). ICH Q8 (R2) describes the same idea as maintaining the design space through lifecycle management, and ICH Q10 section 3.2.1 calls it the process performance and product quality monitoring system. The PQR is the annual checkpoint of that programme. In a mature system, the PQR does not generate the trending; it summarises trending that has been running all year and confirms that the OPV plan (which parameters, which charts, which rules, which review frequency) is still the right one. The conclusion should say whether the OPV plan is to change. Annex 15 5.31 makes the link explicit: ongoing process verification 'should be used throughout the product lifecycle to support the validated status of the product as documented in the Product Quality Review', with incremental changes over time considered and the need for additional actions, such as enhanced sampling, assessed.
Sign-off
The QP responsible for certification, together with the MAH, must ensure the review is timely and accurate (1.11). That means the QP reads it, and the signature page should say what each signature means: author (compiled the data and drafted the evaluation), reviewer (checked the data against source), head of QA (approved the conclusions and actions), QP (confirmed the review supports continued certification), MAH representative where different (evaluated the review on behalf of the MAH). Dates on the signature page in the wrong order, or a QP signature dated before the trending was done, are findings in their own right.
Module 5 of the course rebuilds a weak conclusion against its own body, writes the action table, and drafts the management review summary from it.