This is a ready-to-use ICH Q12 post-approval change management protocol (PACMP), the tool that lets a company agree in advance with a health authority on how a specific future change will be made and assessed, so the eventual implementation can go through a reduced reporting category. Replace every <<FILL: ...>> placeholder with your own specifics. A worked specimen for an analytical method replacement follows. Verify each cited regulation against the current source before you rely on it.
Approval page
| Field | Entry |
|---|---|
| Protocol title | <<FILL: description of the planned change>> |
| Protocol number | <<FILL: PACMP-ID>> |
| Version | <<FILL: version>> |
| Product(s) covered | <<FILL>> |
| Scope | <<FILL: single change / broader protocol covering a defined category of changes>> |
| Applicable region(s) | <<FILL>> |
| Prepared by | <<FILL: name, role>> |
| Approved by (internal) | <<FILL: Regulatory Affairs CMC lead, QA head>> |
1. Objective
Pre-agree with <<FILL: health authority>> the studies, predefined acceptance criteria, and reporting category for <<FILL: description of the planned change>>, so that once the change is executed and the criteria are met, it can be implemented and reported through a reduced category rather than filed and reviewed cold.
2. Scope
This protocol covers <<FILL: exactly what is bounded: one specific change, or a defined category of related changes across one or more products>>. It does not cover <<FILL: state explicitly what is out of scope, to prevent scope creep at execution>>.
3. Background and justification for the reduced category
<<FILL: why this change is a good candidate for pre-agreement, e.g. platform experience with similar changes, existing process/product knowledge, the risk-based rationale for why a reduced category is appropriate once the acceptance criteria are met.>>
4. Established condition affected
| Established condition | Current registered value/form | PLCM reference | Reporting category without this protocol | Proposed category with this protocol |
|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
5. Risk assessment (ICH Q9(R1))
| CQA potentially affected | Mechanism of potential impact | Severity | Probability | Detectability by the proposed studies | Overall risk rating |
|---|---|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
6. Studies and predefined acceptance criteria
Every criterion must be objectively pass/fail. Write each one as if a different, uninvolved reviewer will judge the result with no additional context.
| Study | Method / design | Acceptance criterion | Rationale for the criterion |
|---|---|---|---|
<<FILL>> | <<FILL>> | <<FILL: numeric, unambiguous>> | <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
7. Proposed reporting category on execution
If every study in section 6 meets its predefined acceptance criterion, the change will be implemented and reported through: <<FILL: reporting category, e.g. notification / annual report / CBE-30 / Type IA/IB>>.
8. Condition for reverting to a higher category
If any result falls outside the predefined acceptance criteria: <<FILL: state the fallback, e.g. the change is not implemented under this protocol; the sponsor investigates the deviation and either revises the approach and re-executes, or files the change under the standard reporting category with the full data package.>>
9. Execution and reporting procedure
- Confirm this protocol is approved and in effect for the region of intended implementation.
- Execute the studies in section 6 exactly as written; do not substitute a different design without amending the protocol first.
- Compare each result to its predefined acceptance criterion. Record pass/fail for each.
- If all criteria are met, prepare the implementation report and submit through the category in section 7.
- If any criterion is not met, follow section 8; do not implement the change under this protocol.
- Update the PLCM document to record execution, outcome, and the category used.
10. Acceptance criteria for this protocol (protocol-level, not study-level)
- Every study in section 6 has a criterion that is unambiguous pass/fail.
- The risk assessment in section 5 credibly links the proposed studies to the CQAs at risk; the studies would actually detect an adverse effect if one occurred.
- The reporting category in section 7 is justified by the strength of the studies and the risk rating in section 5.
- Section 8 states a real fallback, not a placeholder.
11. References
ICH Q12, Technical and Regulatory Considerations for Pharmaceutical Product Lifecycle Management, Annex II (PACMP example). ICH Q9(R1), Quality Risk Management. US FDA guidance and 21 CFR 314.70 / 601.12 (comparability protocol practice, for US filings). Applicable regional PACMP guidance for other filing regions.
Confirm the current version and clause numbers of each reference before issue.
12. Deviation handling
Any deviation from the studies as written in section 6 (different lot, different site, different analyst pool than specified) is documented, assessed for whether it invalidates the pre-agreement, and escalated to Regulatory Affairs before the implementation report is prepared. A material deviation from the approved protocol design means the pre-agreement no longer covers what was actually done.
13. Summary and conclusion (completed at execution)
<<FILL: on execution, state the outcome of every study against its criterion, whether the change was implemented, and through which category.>>
14. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL>> | Initial protocol, submitted for authority agreement. |
15. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Regulatory affairs (CMC) | <<FILL>> | ||
| Analytical / QC (if applicable) | <<FILL>> | ||
| Quality assurance | <<FILL>> | ||
| Health authority approval reference | <<FILL: agreement letter / approved supplement number>> |
Filled specimen
The following shows an illustrative PACMP for replacing a compendial finished-product assay method with a validated UPLC alternative. Values are illustrative.
Section 6, studies and criteria:
| Study | Method / design | Acceptance criterion | Rationale |
|---|---|---|---|
| Accuracy (spike recovery) | Three spike levels, triplicate | Mean recovery 98.0-102.0% at each level | Confirms the new method quantifies correctly across the reportable range |
| Repeatability precision | Six replicate preparations, one analyst, one day | RSD <= 2.0% | Confirms method precision is fit for release testing |
| Specificity | Forced-degradation samples analyzed by both methods | No interference at the analyte retention time from known degradants or excipients | Confirms the new method separates the analyte from everything it must be distinguished from |
| Method comparison | Twelve representative production batches analyzed by both methods in parallel | Mean difference between methods within +/- 2.0% | Demonstrates the new method agrees with the currently validated method across real product variability |
Section 7: “If every study passes, the change is implemented and reported through a notification, consistent with the reduced category pre-agreed for a demonstrated-equivalent method replacement.”
Section 13, completed at execution: “All four studies met their predefined acceptance criteria (accuracy 99.1/100.2/99.8% at the three spike levels; repeatability RSD 0.7%; specificity confirmed, no interference; method comparison mean difference +0.6% across 12 batches). The method was implemented on <<FILL: date>> and reported via notification per the agreed category.”
Common inspection findings this protocol prevents
- A “PACMP” on file whose acceptance criteria are too vague for a reviewer to judge pass or fail objectively.
- Execution using a different study design than the one the authority actually approved, with no amendment or deviation record.
- Implementation proceeding despite a failed criterion, treated informally rather than through the section 8 fallback.
- No record showing execution occurred, or the PLCM never updated to reflect it.
How to adapt this protocol
- Scope section 2 tightly: a protocol that tries to cover too much is harder to get agreed and harder to execute cleanly.
- Write section 6 criteria that are demanding enough to protect the product and achievable enough that a credible change can actually meet them; both failure directions defeat the protocol’s purpose.
- Confirm the reporting category in section 7 against your target region’s actual PACMP practice before submission.
- On execution, follow section 9 exactly; any deviation goes through section 12 before you touch section 13.
- Update the linked PLCM document immediately on execution so the two documents never drift apart.