Maintaining accurate and compliant documentation of the re-test period is crucial for pharmaceutical quality systems. APIs and intermediates, unlike finished products, are assigned a re-test date rather than a fixed expiry. This flexibility requires well-documented processes for assignment, tracking, retesting, and updating of re-test dates.
This checklist-style article serves as a reference for pharmaceutical QA professionals to implement and audit robust systems for re-test documentation. It aligns with ICH Q7, GMP requirements, and other global regulatory expectations.
✅ 1. Re-Test Assignment Documentation
- ☐ Stability study data available for 3 batches (minimum)
- ☐ Signed QA-reviewed protocol for storage and test intervals
- ☐ Summary report for data trend analysis and justification
- ☐ Assigned re-test date documented in Quality Overall Summary (QOS)
- ☐ Change control raised for new re-test period implementation
✅ 2. CoA and Batch Record Updates
- ☐ “Re-test Before” clearly mentioned on Certificate of Analysis (CoA)
- ☐ Date format used: DD-MMM-YYYY (e.g., 30-JUN-2026)
- ☐ Internal batch records reflect assigned re-test period
- ☐ Re-test assignment rationale attached with each batch record
- ☐ Document version control maintained in the QMS system
✅ 3. Warehouse Labeling and Storage
- ☐ Container labels include bold “Re-test Before” field
- ☐ Storage conditions indicated on label: 25°C/60% RH or as per protocol
- ☐ Label checked during QA line clearance of storage
✅ 4. Re-Test Scheduling System
- ☐ QA master log of all API and intermediate re-test dates
- ☐ Calendar reminders set for re-test due dates
- ☐ Responsibility assigned for sample withdrawal and testing
- ☐ Periodic QA review to identify materials approaching re-test window
- ☐ Re-test results logged with timestamp and analyst signature
✅ 5. Requalification and Result Documentation
- ☐ Retesting results meet the current specifications in the DMF or QMS
- ☐ Analyst sign-off with review by QC lead
- ☐ QA approval documented before re-approval for further processing
- ☐ New CoA generated (if required) with updated re-test period
- ☐ Batch disposition note added to ERP system post-approval
For CoA formatting best practices, refer to pharma SOP templates.
✅ 6. Regulatory Filing and CTD Updates
- ☐ Re-test periods declared in Module 3.2.S.7 of CTD format
- ☐ Summary of stability data included in Module 3.2.R
- ☐ In-country variation filings updated post re-test period extension
- ☐ Re-test assignment linked to internal justification note
- ☐ Submission status tracked in regulatory tracking tool
✅ 7. SOP Coverage and QA Training
- ☐ Re-test period assignment covered under stability protocol SOP
- ☐ Retesting flow covered under warehouse material handling SOP
- ☐ Labeling requirements defined in packaging SOPs
- ☐ Annual QA training includes re-test documentation guidelines
- ☐ Mock audits simulate re-test data traceability checks
Refer to GMP QA training modules to stay updated on inspection readiness for re-test documentation.
✅ 8. Change Control and Deviation Handling
- ☐ Any re-test date extension supported by controlled change
- ☐ Deviation documented for missed or delayed re-test
- ☐ Risk assessment performed for late retesting events
- ☐ CAPA raised for procedural lapses and QA-reviewed
- ☐ Deviations summarized in annual product quality review (APQR)
✅ 9. Audit Trail and Inspection Readiness
- ☐ Electronic audit trail for digital re-test logs maintained
- ☐ Paper-based logbooks verified and controlled
- ☐ All changes to re-test period traceable to source data
- ☐ Re-test compliance included in internal audits
- ☐ Inspection readiness folder created for re-test documentation
✅ 10. Cross-Linking with Other Departments
- ☐ Regulatory Affairs notified of re-test updates for filings
- ☐ Production department advised of material re-approval
- ☐ QC team aligned on re-test sampling and analysis
- ☐ Warehouse trained to handle re-test-labeled materials
- ☐ Quality Council reviews re-test issues quarterly
📄 Sample Template: API Re-Test Logbook Entry
| Batch No. | Manufacture Date | Re-Test Before | Re-Test Done | Status |
|---|---|---|---|---|
| API2023009 | 10-Feb-2023 | 10-Feb-2025 | 05-Feb-2025 | Compliant |
💡 Best Practices
- Establish a centralized QA master sheet for all re-test batches
- Use unique re-test date codes for digital traceability
- Conduct annual review of re-test process effectiveness
- Integrate re-test logs into APQR and product lifecycle management
- Document rationale for any re-test date deviation or extension
QA teams can refer to clinical protocol compliance logs for analogous documentation controls in R&D settings.
Conclusion
Documenting re-test periods is not just a regulatory formality—it ensures that pharmaceutical materials remain suitable for use over time. A structured QA checklist enhances traceability, reduces risk of non-compliance, and prepares your team for regulatory inspections. By following this 10-point documentation framework, pharma companies can establish a gold-standard quality assurance system for re-test management.