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 risk assessment for evaluating, at every change that could touch a container closure seal, whether the existing CCIT method validation and its acceptance criteria still apply. Attach it to the relevant change control record. Replace every <<FILL: ...>> placeholder with your own specifics and route it through your normal document control, review, and approval. A worked filled specimen follows. Verify each cited reference against the current source before you rely on it.
1. Purpose
This assessment determines whether a proposed change invalidates any part of the existing CCIT validation package, the method’s demonstrated sensitivity, the positive control basis, the seal quality acceptance range, or the maximum allowable leakage limit (MALL) itself, and defines the action required before the change is implemented.
2. Scope
3. Responsibilities
4. Change classification
Classify the change against the categories below. More than one applicable row widens the scope of follow-up work required.
5. Impact evaluation
6. Conclusion and required action
7. References
USP General Chapter <1207>, Package Integrity Evaluation, General Considerations.
USP General Chapter <1207.1>, Package Integrity Testing in the Container-Closure System.
USP General Chapter <1207.3>, Package Seal Quality Test Technologies.
See the paired article, Building a container closure integrity program under USP <1207>, for the underlying method-selection and revalidation-trigger logic this assessment works through.
Confirm the current version of each reference before issue.
8. Revision history
9. Approvals
Filled specimen
Extract for an example change control proposing a new elastomeric stopper supplier for a lyophilized biologic vial, prompted by a supply continuity concern with the incumbent vendor. Company and product are illustrative.
Impact evaluation: the original positive controls and RSF acceptance range were established against the incumbent stopper’s compression set behavior; a different elastomer formulation relaxes under crimp pressure at a different rate, so the existing RSF acceptance range cannot be assumed to still predict integrity for the new stopper. The MALL itself, sterility-driven, does not change, since the critical attribute and its derivation are independent of which stopper supplier is used.
Conclusion: existing CCIT validation package does not cover the new stopper without further work. Required action: run a new positive control set (laser-drilled holes bracketing the existing MALL) against the new stopper lot to confirm leak-test sensitivity is unchanged, and re-establish the RSF acceptance range against the new stopper’s compression behavior, tied back to that new leak-test evidence. Owner: Analytical / Packaging SME, target date set to precede first commercial use of the new stopper lot. The change cannot proceed to commercial batches until both the positive control confirmation and the revised RSF range are approved; QA holds the change control open pending that data.
Common inspection findings this risk assessment prevents
- A stopper or supplier change implemented through change control with no linked CCIT impact review.
- An in-line seal quality acceptance range left unchanged after a closure change, so it no longer predicts what it claims to predict.
- A device-assembly change that quietly removes CCIT test access, discovered only after the fact.
- A conclusion of “no impact” reached with no documented comparison against what the original validation’s positive controls actually represented.
How to adapt this risk assessment
- Link this assessment to the actual change control record in the header, not as a standalone document.
- Classify the change honestly against every row in section 4; more than one applicable row is common.
- Where the seal quality acceptance range is affected, do not close this assessment until that range is re-tied to new leak-test evidence, not just carried forward unchanged.
- Confirm every reference in section 7 against the current published version before issue.