How to use this document
Copy the template below into your quality system. Replace every <<FILL: ...>> placeholder with your company, system, and process specifics, then route it through your own document control, review, and approval. The filled specimen shows one worked example; adapt the numbers and scope to your operation and verify each cited regulation or standard against the current source before you rely on it.
This is a generic, originally worded starting point. It contains no confidential, proprietary, or employer material, it is drafted with AI assistance and reviewed, it is not legal or compliance advice, and adopting it does not by itself create or prove compliance. See the Disclaimer and Terms.
This is a ready-to-use form for deciding and documenting a protocol amendment during a PPQ campaign, a planned, approved change to the protocol itself, as distinct from a deviation, an unplanned departure from an unchanged protocol. Complete it whenever an issue would recur on every remaining batch unless the protocol itself changes. Replace every <<FILL: ...>> placeholder with your own specifics and route it through your normal document control, review, and approval before the next batch runs under the changed version. A worked filled specimen follows.
1. Purpose
This form documents the decision to amend an active PPQ protocol mid-campaign: the specific change, the data showing the original approach would not hold for every remaining batch, and the effect of the change on batches already run and on any concurrent-release strategy in use.
2. Scope
3. The deviation-versus-amendment test
4. Responsibilities
5. Basis for the change
6. Effect on the campaign
7. Approvals
8. References
See the paired article, PPQ readiness: the prerequisites that decide success before batch one, for the reasoning behind the deviation-versus-amendment distinction.
The paired PPQ deviation criticality pre-classification plan, for the framework this form’s test in section 3 distinguishes itself from.
The paired PPQ acceptance criteria and concurrent release basis, where this amendment pauses an active concurrent-release strategy.
9. Revision history
Filled specimen
Extract for an example three-batch PPQ campaign for a lyophilized biologic, acceptance criteria set as tighter provisional in-process limits during PPQ per the campaign’s acceptance-criteria basis, no concurrent release in use.
The deviation-versus-amendment test: after batch one, an in-process conductivity limit set during PPQ protocol drafting was exceeded by a small margin with no CQA impact, classified Major per the deviation criticality plan and investigated. The root cause, a buffer preparation specification that did not account for seasonal water conductivity variation at the manufacturing site, would recur on batch two and batch three under the same buffer specification, so this was recognized as an amendment question, not a batch-by-batch deviation pattern.
Basis for the change: Deviation investigation DEV-2026-0391’s root cause and three months of incoming water-quality data supported widening the buffer preparation specification’s conductivity range with no effect on the downstream CQA, confirmed by Manufacturing Science against existing process characterization data. Proposed change: widen the buffer preparation conductivity specification in the protocol’s in-process control table, with no change to the downstream CQA acceptance criteria.
Effect on the campaign: batch one’s data remains valid and still counts toward the three-batch campaign, since the amendment corrects an in-process specification, not the CQA or batch-count basis itself, and batch one’s CQA results were unaffected by the exceeded in-process limit. Concurrent release was not in use, so no pause was triggered. The amendment took effect for batch two forward, approved by Validation, Manufacturing Science, and QA before batch two started; Regulatory Affairs confirmed the change did not require an update to the BLA’s CMC section ahead of filing, since it was documented as a resolved in-process specification refinement within the already-planned process validation strategy.
- A protocol design flaw investigated and closed as a fresh deviation on each successive batch, with the same underlying flaw left unaddressed for the next batch in line.
- A protocol changed mid-campaign with no documented rationale connecting the change to specific investigation data.
- A concurrent-release strategy continuing to release batches with no assessment of whether a mid-campaign protocol change affects batches already released.
- No stated decision on whether batches run under the prior protocol version still count toward the campaign’s batch count.
- Work the test in section 3 honestly before drafting anything further; if the issue would not recur on every remaining batch, this is a deviation, not an amendment, and this form does not apply.
- Cite the specific investigation or trend data behind the change in section 5; a change with no data behind it is not a defensible amendment.
- State explicitly in section 6 whether already-run batches still count toward the campaign; never leave this implied.
- If the campaign relies on concurrent release, treat the amendment as an automatic pause trigger until its impact on already-released batches is assessed.
