Why retesting stability samples needs strict control:

Stability testing must reflect real-time degradation trends and provide a reliable basis for shelf life. Retesting without proper authorization can obscure true data, delay investigations, or result in selective reporting. Only when scientifically justified and QA-approved should a retest be allowed. This practice upholds the transparency, consistency, and regulatory acceptance of the stability program.

Risks of uncontrolled or undocumented retesting:

Repeated testing in pursuit of “better” results undermines data credibility. Unjustified retesting can appear as data manipulation, leading to serious regulatory consequences. It also creates ambiguity in result reporting and may interfere with OOS/OOT investigations. Without documented QA oversight, auditors may interpret such actions as deliberate non-compliance or falsification.

Regulatory and Technical Context:

ICH and WHO requirements for test result integrity:

ICH Q1A(R2) and WHO TRS 1010 clearly state that stability data must be complete, scientifically sound, and traceable. WHO GMP Annex 4 and US FDA guidance on data integrity highlight that retesting is not permitted unless it’s part of a structured OOS investigation or approved deviation. All results—initial and repeat—must be documented, and reasons for repeat testing must be justified, preferably pre-approved by QA.

Expectations during audits and dossier review:

Inspectors will assess how test failures are handled and whether the lab follows a formal retesting policy. Repeated or inconsistent results without a traceable rationale may be flagged as data manipulation. CTD Module 3.2.P.8.3 must reflect actual results—retested or not—along with deviation summaries when applicable. Retesting policies are often reviewed as part of laboratory controls during GMP inspections.

Best Practices and Implementation:

Implement a strict QA-reviewed retesting SOP:

Develop and enforce a written SOP that outlines:

• When retesting is allowed (e.g., instrument malfunction, analyst error, sample spill)
• Who can approve a retest (QA or Quality Head)
• How to document all results (initial, repeat, and final)
• Requirement for investigation and deviation initiation

Include reference to related procedures such as OOS/OOT handling and change control to maintain consistency.

Train analysts and reviewers to flag unauthorized repeat testing:

Educate QC staff on the difference between genuine analytical failure and poor data acceptance practices. Reinforce that repeat testing must never be used as a means to avoid reporting unfavorable data. QA reviewers must be trained to identify and question repeat entries or inconsistent test logs, especially when results diverge significantly from prior time points.

Link retesting control to LIMS and documentation systems:

If using LIMS, configure the system to restrict retest entries unless a deviation or CAPA reference is provided. Maintain clear audit trails for every retest—including who requested it, why it was approved, and what actions followed. Store all chromatograms, raw data, and annotations for both initial and repeat tests.

By limiting retesting to QA-approved scenarios and documenting every instance thoroughly, pharmaceutical teams can uphold the integrity of their stability data, satisfy inspectors, and build long-term credibility in their regulatory filings.