PROTOCOLREFERENCE OUTLINE

PACMP & Change-Classification Protocol

Post-Approval Change Management Protocol that pre-defines a change, its studies and pre-agreed acceptance criteria, and the resulting reporting category — the enhanced-approach mechanism for lowering a change from a prior-approval supplement to a notification. Aligned to ICH Q12, ICH Q10, and ICH Q9(R1).

What a template is not

A template is a document baseline to adapt inside your own quality system. SPEQ does not approve, validate, or take responsibility for what you issue from it, and using one is not evidence of compliance.

CHECKING ACCESS

Checking your Professional access…

REGULATIONS MAPPED
ICH Q12ICH Q10ICH Q9(R1)21 CFR 314.70
DOCUMENT TYPE
Protocol
LAST UPDATED
August 2026
PURPOSE

A protocol that pre-defines a specific change, the studies and pre-agreed acceptance criteria that will evaluate it, and the reporting category sought — the mechanism for agreeing the approach with a regulator before the change is made, so execution can be reported at a lower category. Its weak point is acceptance criteria written loosely enough to pass anything, which removes the reason the protocol earned its category.

What's Inside

✓Protocol identification and the Established Conditions the change touches, named rather than described loosely
✓Current versus proposed condition stated parameter by parameter, so the scope cannot drift later
✓Change-classification decision carrying both the default category and the target category being sought
✓Risk assessment under ICH Q9(R1) sizing the studies to the risk rather than to habit
✓Studies, tests and pre-defined acceptance criteria written so that a result can genuinely fail them
✓Reporting-category justification per market, since categories are jurisdiction-specific and never assumed equivalent
✓Implementation, effectiveness check and the lifecycle position of the protocol once it is used

How to Use It

1Identify the change precisely and name every Established Condition it touches; a vague scope makes the agreed category unusable.
2State current and proposed conditions parameter by parameter rather than as a narrative of the intent.
3Work the classification to both a default and a target category, and say why the reduction is justified.
4Size the studies from the ICH Q9(R1) assessment; a protocol carrying more testing than the risk warrants will not be repeated.
5Write acceptance criteria a result can actually fail — criteria loose enough to pass anything forfeit the category you sought.
6Justify the category separately for each market in scope, then run the effectiveness check after the change is executed.
DOCUMENT CONTENTS

The full section structure of this template — every section and sub-section, so you can use it as a baseline for your own site document.

—Document Control
› Document Information› Approval Signatures› Revision History› Distribution List
1Protocol Purpose, Scope, and Regulatory Basis
2Change Description and Established Conditions Affected
› Description of the proposed change
3Change-Classification Decision
4Risk Assessment (ICH Q9(R1))
5Studies, Tests, and Pre-Defined Acceptance Criteria
6Reporting-Category Justification
7Implementation, Effectiveness Check, and Lifecycle
8Approvals
REGULATORY CONTEXT

ICH Q12 provides the Established Conditions and post-approval change management protocol framework; the protocol rests on an effective pharmaceutical quality system under ICH Q10 and a proportionate assessment under ICH Q9(R1). Reporting categories remain jurisdiction-specific — 21 CFR 314.70 in the United States, EU variation types elsewhere — so each market in scope is cited to its own instrument and never assumed equivalent. Whether a regulator accepts the target category is its decision, not the protocol’s; the protocol only makes the case reviewable.

MAPPED STANDARDS
ICH Q12ICH Q10ICH Q9(R1)21 CFR 314.70
Browse the standards catalog →