Container Closure Integrity Testing (CCIT) Procedure for Stoppered Vials and Sealed Containers
This CCIT procedure guides the testing of stoppered vials and sealed containers to confirm closure integrity before release. Use it to catch leaks, protect sterility, and document pass/fail results with clear escalation paths.
Trusted by frontline teams 15 years of frontline software
Built for: Pharmaceutical Manufacturing · Biotech And Biologics · Medical Device Packaging · Contract Manufacturing
Overview
This standard operating procedure defines how to perform container closure integrity testing on stoppered vials and other sealed containers using an approved, validated method. It covers the full workflow from confirming the sample set and equipment readiness through running the CCIT cycle, reviewing results against acceptance criteria, documenting the outcome, and opening non-conformance when a unit fails.
Use this template when closure integrity is a release requirement, when you need evidence that the package can resist microbial or gas ingress, or when you want a controlled record for investigations, stability work, or post-change verification. It is especially useful in regulated environments where the sample identity, test method, and disposition must be traceable and reviewable.
Do not use this SOP as a substitute for method validation, product-specific acceptance criteria, or equipment qualification. If the test method is not approved, the sample set is not representative, or the container format differs materially from the validated configuration, stop and escalate before testing. The procedure also should not be used to justify release when results are borderline, the cycle deviates from the validated range, or the reviewer cannot confirm the record is complete.
Standards & compliance context
- The record structure supports ISO 9001:2015 documented information expectations by capturing method control, traceability, review, and retention details.
- The workflow aligns with GMP-style quality control practices by requiring approved methods, defined acceptance criteria, and documented disposition of failures.
- For sterile or high-risk packaging applications, the procedure supports contamination-control expectations by documenting evidence of closure integrity before release.
- If your site uses validated hazardous or pressurized test equipment, add permit-to-work, PPE, and escalation controls consistent with OSHA-style safety management practices.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns CCIT into a controlled sequence with clear ownership, verification, and escalation at each point.
-
Verify the approved test method and sample set
The QA Technician verifies the approved CCIT method version, container type, sample count, and acceptance criteria in the batch record or test plan before testing begins.
-
Inspect the test area and confirm equipment readiness
The QA Technician inspects the test area for cleanliness and confirms the CCIT system is in service, calibrated, and free of visible damage before use.
-
Identify and segregate the test samples
The QA Technician identifies each vial or sealed container, confirms traceability to the batch or study record, and segregates test samples from non-test material.
-
Prepare the containers for testing
The QA Technician prepares the containers exactly as defined by the validated method, including fixtures, orientation, and any required preconditioning steps.
-
Run the validated CCIT cycle
The QA Technician runs the approved CCIT cycle using the validated parameters and monitors the system for alarms, drift, or interruptions during the run.
-
Review results against acceptance criteria
The QA Technician reviews each sample result against the approved acceptance criteria defined by the validated method, including the site’s ISO 11607 / USP <1207> acceptance criteria by name where applicable.
-
Document the passing result
The QA Technician documents the passing result, records the method revision and sample disposition, and completes the test record for review.
-
Release the record
The QA Reviewer confirms the record is complete, reviews the documented passing result, and releases the CCIT record for filing or batch disposition.
-
Quarantine failed samples and initiate non-conformance
The QA Technician quarantines failed containers, completes the deviation or non-conformance form, and escalates the failure to QA for investigation and disposition.
How to use this template
- 1. The quality role verifies the approved CCIT method, the current acceptance criteria, and the correct sample set before any container is moved to the test area.
- 2. The operator inspects the test area, confirms equipment status, and records readiness checks for calibration, power, cleanliness, and any required environmental conditions.
- 3. The operator identifies each vial or sealed container, segregates test samples from non-test material, and confirms traceability to the batch or study record.
- 4. The operator prepares the containers for the validated CCIT cycle exactly as defined by the method, including any required fixtures, orientation, or preconditioning steps.
- 5. The operator runs the CCIT cycle, monitors for deviations or alarms, and stops the process if any parameter moves outside the validated tolerance.
- 6. The reviewer checks the results against acceptance criteria, documents passing units or opens non-conformance for failures, and releases the record only after all required signatures are complete.
Best practices
- Use only the approved method version and record the revision number on the test record.
- Verify sample identity against the batch record before the test starts so untested units are not mixed into the set.
- Photograph or otherwise capture the test setup when your site procedure requires visual evidence of container orientation or fixture placement.
- Treat any cycle alarm, parameter drift, or unexplained interruption as a deviation until a competent person reviews it.
- Keep acceptance criteria visible during result review so the operator does not rely on memory or informal thresholds.
- Quarantine failed or suspect units immediately and label them clearly to prevent accidental release or retest without authorization.
- Document the reason for any retest and require quality approval before repeating the cycle.
- Link the CCIT record to the batch, stability, or investigation file so the result is easy to trace during review or audit.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What containers does this CCIT procedure apply to?
This template is written for stoppered vials and other sealed containers that require verified closure integrity before release. It fits products where microbial ingress, gas ingress, or loss of container seal would create a quality or patient-risk issue. If your package format uses a different closure system, you can adapt the sample handling and acceptance criteria while keeping the same documented workflow.
How often should CCIT be performed?
Use this procedure whenever your validated testing plan requires routine lot release testing, stability checks, or investigation of a suspected packaging issue. Many teams also use it after process changes, equipment maintenance, or container-closure component changes. The right cadence should follow your validated method, product risk assessment, and quality system requirements.
Who should run the CCIT procedure?
A trained quality control analyst, laboratory technician, or other competent person should perform the test under an approved method. The reviewer or quality unit should verify that the sample set, cycle parameters, and results meet the acceptance criteria before release. If the method includes hazardous materials or pressurized systems, the assigned role should also be authorized for that equipment.
Does this template support GMP and ISO documentation expectations?
Yes. The record structure supports documented information practices aligned with ISO 9001-style control of records and GMP expectations for traceable, reviewable testing. It also helps preserve the evidence needed for deviation handling, batch disposition, and audit readiness. You can customize the approval fields, retention notes, and reviewer sign-off to match your site quality system.
What are the most common mistakes when using a CCIT SOP?
Common failures include using an unapproved sample set, skipping equipment readiness checks, or accepting results without comparing them to the validated criteria. Another frequent issue is poor sample segregation, which can mix tested and untested units or blur pass/fail status. This template is designed to force those checks into the workflow so the record is usable later.
Can this procedure be customized for different test methods?
Yes. You can adapt it for vacuum decay, pressure decay, dye ingress, helium leak, or other validated CCIT methods by replacing the cycle parameters and acceptance criteria sections. Keep the same structure for sample identification, verification, result review, and non-conformance handling so the procedure remains controlled and easy to audit.
How does this compare with ad-hoc leak checks?
Ad-hoc leak checks may find obvious defects, but they usually do not create a controlled record of method, sample identity, acceptance criteria, and disposition. This SOP turns the activity into a repeatable quality control step with clear verification and escalation points. That matters when the result is used for batch release, investigation, or trend review.
What should I integrate with this procedure?
This template works well with batch records, equipment logbooks, calibration records, deviation or non-conformance forms, and electronic quality management systems. If your site uses LIMS or MES, you can link sample IDs, test runs, and reviewer approval to the same record set. The goal is to keep the test result traceable from sample selection through final disposition.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
AI employee self-service assistants cut HR and IT support time with instant answers, automated routing, and better employee experience.
-
A vendor-agnostic checklist covering architecture, frontline access, AI, compliance, and payroll to evaluate any scheduling platform.
-
See how Power Tables and Live Boards give frontline operations structured, queryable data instead of scattered spreadsheets and chat threads.
Ready to use this template?
Get started with MangoApps and use Container Closure Integrity Testing (CCIT) Procedure for Stoppered Vials and Sealed Containers with your team — pricing built for small business.
