Home / Topics

Stability testing ยท Protocol planning

Designing a small-molecule stability testing protocol

By Bhavya Madhavan

A practical educational checklist for defining stability study scope, sampling, testing schedules, trend review, and documentation.

Start with the study question

A useful protocol explains what decision the study will support and which records will support that decision. Before drafting a testing table, write down whether you are studying a drug substance or finished product, the development stage, intended markets, and proposed storage claim.

Use the guideline within its scope

ICH Q1A(R2) addresses registration stability studies for new drug substances and products. A drug substance may have a retest period; a drug product has a shelf life. Clinical studies, variations, and other application types need their applicable requirements checked separately.

For general-case long-term studies supporting a shelf life of at least 12 months, Q1A(R2) typically describes testing every three months in year one, every six months in year two, and annually thereafter. Thus 0, 3, 6, 9, 12, 18, and 24 months is an illustrative sequence, not a universal schedule. Refrigerated, frozen, and special packaging cases need separate consideration. Stress testing explores degradation and analytical suitability; it does not replace formal stability studies.

A drafting checklist

The following questions are an editorial planning aid, not a regulatory minimum:

Check the protocol against the eventual report

Try drafting a blank results table before approving the protocol. If you cannot tell where sample identity, actual pull date, method version, result, and deviation reference will go, the workflow needs clarification. This simple writing exercise can expose missing handoffs before samples enter a chamber.

Primary reference

ICH Q1A(R2): Stability Testing of New Drug Substances and Products, particularly scope, testing frequency, and storage conditions. Verify applicable regional requirements and revision status before operational use.

Continue reading