Usage Examples
- We only have six months of accelerated data, so we are asking for 24 months and committing to the rest.
- Significant change showed up at 40C/75% RH, so we now owe intermediate data.
- Run the stability protocol in the marketed blister, not the development bottle.
What is Stability Testing?
Stability testing is the formal study program that measures how a drug substance or product changes under defined temperature, humidity, and light conditions, generating the evidence that sets shelf life, storage conditions, and the expiration date on the label.
Stability testing exists because a drug's quality is not fixed at release. Assay drifts, degradation products accumulate, dissolution slows, water permeates the container. Without time-course evidence under controlled conditions, no one can defend an expiry date, and 21 CFR 211.137 makes that date a condition of the product meeting its standards at the time of use.
Stability testing covers formal studies on primary batches in the marketed container closure system: long term, intermediate, and accelerated storage, photostability under ICH Q1B, and in-use or reconstituted testing where the label allows it. Stability testing does not cover stress or forced-degradation work, which uses single batches at extreme conditions to map degradation pathways and prove the method is stability indicating.
Stability testing is run against a written testing program that fixes batches, timepoints, attributes, storage conditions, and acceptance criteria before the first sample goes on. Stability testing then produces the dataset a reviewer reads alongside the proposed shelf life and the label storage statement. Short-term excursions during shipping are justified from the accelerated and intermediate data, not from new studies.
Not to be confused with
- Stress testing (forced degradation)
- stress testing pushes a single batch past accelerated conditions to identify degradation pathways and validate the stability-indicating power of the method. Stability testing runs at least three primary batches at label-relevant conditions to set an expiry date.
- Accelerated testing
- accelerated testing at 40C/75% RH is one arm inside a stability program, not a substitute for it. Accelerated data alone supports only a tentative expiration date, and only while full shelf-life studies are actually being conducted.
- Release testing
- release testing is a single-timepoint verdict on whether a batch may ship. Stability testing is the time series that says how long that verdict holds and under what storage conditions.
- Photostability testing
- photostability is a separate light-exposure study run on at least one primary batch under the standard conditions in ICH Q1B. It is not one of the temperature and humidity storage arms with recurring timepoints.
The US obligations sit in Part 211; the data package expected at filing comes from ICH Q1A(R2).
What you must do
- 1Maintain a written testing program that assesses stability characteristics and determines appropriate storage conditions and expiration dates, with statistically based sample sizes and test intervals, specific test methods, and testing in the marketed container-closure system21 CFR 211.166
- 2Give every marketed drug product an expiration date determined by that stability testing, and relate the date to the storage conditions stated on the labeling21 CFR 211.137
- 3Test the attributes susceptible to change on storage using fully validated, stability-indicating analytical procedures, covering physical, chemical, biological, microbiological, preservative-content, and functionality tests as applicableICH Q1A(R2) SS2.2.5
- 4Place at least three primary batches on long-term storage, cover a minimum of 12 months at the time of submission, and continue until the proposed shelf life is coveredICH Q1A(R2) SS2.2.7
- 5Store to the general-case conditions (long term 25C/60% RH or 30C/65% RH, intermediate 30C/65% RH, accelerated 40C/75% RH) and add six months of intermediate data from a 12-month study if significant change appears at the accelerated conditionICH Q1A(R2) SS2.2.7.1
Common mistakes
Treating accelerated data as a shelf-life shortcut
accelerated results support only a tentative expiration date while real-time studies run, and that date has to be verified by actual shelf-life data. Planning a launch around six months at 40C/75% RH produces a deficiency letter and an approved shelf life shorter than the commercial plan assumed.
Running stability in the development container
Part 211 requires testing in the same container-closure system as marketed, and ICH expects the marketed configuration including secondary packaging and label. Change the vial, stopper, or blister after the study starts and the accumulated data no longer supports the product being registered.
Missing the intermediate-condition trigger
significant change at the accelerated condition obliges six months of intermediate data from a 12-month study. Teams find out at month six, have no samples on at 30C/65% RH, and cannot start the clock retroactively, so the filing slips by at least six months.
When This Matters
- We only have six months of accelerated data, so we are asking for 24 months and committing to the rest.
- Significant change showed up at 40C/75% RH, so we now owe intermediate data.
- Run the stability protocol in the marketed blister, not the development bottle.
Frequently Asked Questions
ICH Q1A(R2)'s general case sets three conditions: long term at 25C/60% RH or 30C/65% RH, intermediate at 30C/65% RH, and accelerated at 40C/75% RH, each with 2C and 5% RH tolerances. Products stored refrigerated, frozen, or in semi-permeable containers follow separate tables in the same section.
Related Use Cases
- Pharma Use Cases
Cut NDA and sNDA prep time by 60% with AI-assisted drafting and automated readiness checks
- Biotech Use Cases
Compress IND prep from 8-12 weeks to under 3 weeks with AI-assisted drafting and validation
- CMC Workflows
Track ICH quality guidelines automatically and get alerts when changes impact your products
- Quality/QA Workflows
Track GxP regulation changes and enforcement trends
