CCIT Result Investigation and Artifact Decision Plan

Document type	Plan
Topic area	Drug Product
Level	Advanced
Updated	October 2026

This is a ready-to-use plan for agreeing, before a real CCIT failure happens, the sequence used to decide whether a borderline or failing result is a true leak or a test artifact. Complete it during method validation or CCIT protocol drafting so the investigation logic exists before anyone is deciding under schedule pressure with a real result and a batch sitting in the warehouse. Replace every <<FILL: ...>> placeholder with your own specifics and route it through your normal document control, review, and approval. A worked filled specimen follows.

Document control header

Field	Entry
Document title	CCIT Result Investigation and Artifact Decision Plan for `<<FILL: method / product / container system>>`
Document number	`<<FILL: e.g. PLN-CCIT-003>>`
Version	`<<FILL>>`
Effective date	`<<FILL>>`
Linked CCIT study protocol	`<<FILL: ref>>`
Linked system suitability log	`<<FILL: ref>>`
Document owner	`<<FILL: e.g. Analytical / Packaging SME>>`

1. Purpose

This plan states, with a pre-agreed sequence, how a borderline or failing CCIT result is investigated before it is classified as a true leak or as a test artifact, and what happens to the result, and to units tested around it, at each step of that sequence.

2. Scope

Dimension	Decision
CCIT method(s) in scope	`<<FILL>>`
Container closure system(s)	`<<FILL>>`
Does the validated method pre-authorize a retest under confirmed-correct conditions?	`<<FILL: Yes/No; if Yes, cite the validated method section>>`
Out of scope	`<<FILL: e.g. the full deviation or OOS investigation procedure itself once a true result is confirmed, covered under the site's own procedure>>`

3. Responsibilities

Role	Responsibility
CCIT operator	Stops and reports a borderline or failing result immediately, without pre-judging whether it is an artifact
Analytical / packaging SME	Works the artifact-check sequence below and documents each step’s outcome
Quality Assurance	Approves the final classification and disposition; owns the conservative default for genuinely ambiguous cases

4. Artifact-check sequence

Work these checks in order for every borderline or failing result. Do not skip ahead to a retest before the earlier checks are documented.

Step	Check	Evidence required	Outcome if confirmed
1	System suitability bracketing this result	Reference to the bracketing log entry immediately before and after the suspect result	If the bracket itself failed, the instrument, not the unit, is the probable cause; investigate per the system suitability log’s escalation rule before proceeding
2	Fixture seating and alignment	Documented check against the qualified fixture geometry (cryobag restraint, PFS dual-seal scan fixture, or equivalent)	If misseated, re-seat correctly and retest only if the validated method pre-authorizes it
3	Thermal equilibration	Confirmation the unit reached the qualified test temperature before testing, with a time/temperature record	If not equilibrated, equilibrate and retest only if the validated method pre-authorizes it
4	Residual surface moisture or condensation	Visual or documented check for condensation, particularly on a unit moved from refrigerated or frozen storage	If present, dry per a documented procedure and retest only if the validated method pre-authorizes it
5	Pre-authorized retest, if all of steps 1 to 4 are resolved and the validated method permits it	Retest result on the same unit under confirmed-correct conditions	A reproduced result after this point is a true result, not an artifact

5. Decision rule

Situation	Classification	Disposition
An artifact source in steps 1 to 4 is confirmed with documented evidence, and the retest (where authorized) passes	Artifact, not a true leak	Original result voided per the documented artifact; unit released per the retest result
No artifact source is confirmed, or the result reproduces after a pre-authorized retest	True result	Handled under the site’s deviation or OOS investigation procedure; not dispositioned here
Genuinely ambiguous after working the full sequence	True result (conservative default)	Handled under the site’s deviation or OOS investigation procedure until the investigation resolves it

The sequence in section 4 is not an opportunity to propose a plausible-sounding explanation and stop; every step claimed as the cause has to carry documented evidence, not an assertion.

6. Escalation and documentation

Step	Requirement
Initial report	CCIT operator reports any borderline or failing result the same session, before proceeding to further testing
Sequence execution and sign-off	Analytical / packaging SME documents the outcome of each step in section 4, dated
Final classification	Quality Assurance approves the classification and disposition, citing the specific step(s) that resolved it
Record	Classification, evidence, and disposition recorded in `<<FILL: investigation log / eQMS reference>>`, cross-referenced to the batch or stability record affected

7. Conclusion

Field	Entry
Artifact-check sequence finalized and linked to the CCIT method	`<<FILL: Yes/No>>`
Approved by (QA, name, date)	`<<FILL>>`

8. References

USP General Chapter <1207>, Package Integrity Evaluation, General Considerations. 21 CFR 211.192, review and investigation of an unexplained discrepancy. See the paired article, building a container closure integrity program under USP <1207>, for the reasoning behind this sequence and the specific CCIT artifact sources it addresses. The paired CCIT system suitability verification log for the bracketing evidence step 1 relies on.

9. Revision history

Version	Date	Author	Summary of change
`<<FILL: 1.0>>`	`<<FILL>>`	`<<FILL>>`	Initial issue.

10. Approvals

Role	Name	Signature	Date
Author (Analytical / Packaging)	`<<FILL>>`
Reviewer (Fill-Finish Operations)	`<<FILL>>`
Approver (QA)	`<<FILL>>`

Filled specimen

Extract for a vacuum decay CCIT method on a lyophilized biologic vial, validated method permitting one pre-authorized retest per unit under confirmed-correct conditions.

A stability-pull unit read a pressure rise just past the acceptance threshold. Working the sequence: step 1, the system suitability bracket on either side of this unit both passed, ruling out an instrument-wide cause; step 2, fixture seating was not applicable (rigid vial, no restraint fixture); step 3, the unit had been removed from 2 to 8 degrees C storage and tested 4 minutes after removal, short of the method’s 15-minute equilibration requirement; step 4, no visible condensation was noted but was not separately documented at the time, a gap flagged for the method’s retest record going forward. The unit was re-equilibrated for the full 15 minutes and retested: the repeat result passed well inside the acceptance range. Classification: artifact, incomplete thermal equilibration, confirmed by documented equilibration time and a passing retest; original result voided per this plan, unit released on the retest result. QA approval cited step 3 as the specific resolving evidence.

Common inspection findings this plan prevents

A borderline result dispositioned as passing on a proposed artifact, residual moisture or a cold unit, that was never actually confirmed with documented evidence.
A retest performed with no pre-authorization in the validated method, amounting to an undocumented quiet retest.
An investigation sequence invented in the moment rather than worked against a pre-agreed order, producing inconsistent classifications for similar results over time.
A genuinely ambiguous result resolved in the direction that avoids an investigation rather than the conservative default.

How to adapt this plan

Confirm in section 2 whether your validated method actually pre-authorizes a retest; if it does not, strike step 5 and route every borderline or failing result directly to deviation or OOS investigation.
Set the artifact-check sequence in section 4 to match this specific method’s real failure modes; a method with no fixture, for example, can remove step 2 rather than carry an inapplicable row.
Train CCIT operators on the sequence before a real failure happens, not as a procedure read for the first time during one.
Route every classification through Quality Assurance approval; never let an artifact classification stand on the operator’s or SME’s documentation alone.