This is a ready-to-use SOP for the ongoing (annual) stability program that keeps a marketed product’s registered shelf life verified against real commercial production for the life of the product.
Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it.
Document control header
| Field | Entry |
|---|---|
| Document title | Ongoing (Annual) Stability Program |
| Document number | <<FILL: SOP-ID, e.g. SOP-QA-041>> |
| Version | <<FILL: version>> |
| Effective date | <<FILL: effective date>> |
| Supersedes | <<FILL: prior version or "New">> |
| Document owner | <<FILL: role, e.g. Stability Program Manager>> |
| Applies to | <<FILL: sites / products in scope>> |
1. Purpose
This procedure defines how <<FILL: COMPANY NAME>> maintains an ongoing stability program for marketed products, so the registered shelf life continues to be verified against batches actually manufactured under commercial conditions throughout the product’s commercial life, per 21 CFR 211.166 and, for EU-marketed product, EudraLex Volume 4, Part I, Chapter 6.
2. Scope
This procedure applies to all commercially marketed drug substances and drug products manufactured or released by <<FILL: COMPANY NAME>> at the sites listed in the header. It covers batch selection, placement, testing, trending against the registration model, and escalation of adverse trends. It does not cover the original registration stability program, which is governed by <<FILL: SOP-ID for the registration stability protocol>>, nor in-use, freeze-thaw, or photostability special studies, governed by <<FILL: SOP-ID(s)>>.
3. Responsibilities
| Role | Responsibility |
|---|---|
| Stability program manager / coordinator | Maintains the annual placement plan, tracks which products/strengths/sites have a batch placed each calendar year, initiates pulls and testing, and prepares the annual trend summary. |
| QC laboratory | Executes validated stability-indicating methods on schedule, records results contemporaneously. |
| Quality Assurance | Approves the annual placement plan, reviews trend summaries, oversees OOS/OOT investigations arising from ongoing data, and confirms the program is complete before each annual product review cycle. |
| Regulatory affairs | Confirms an adverse trend’s regulatory reporting implications (field alert, variation notification) and any resulting shelf life change. |
| Manufacturing | Ensures a representative batch is available for placement each year per product, strength, and container closure type. |
4. Definitions
- Ongoing (annual) stability program: the GMP-required continuation of stability testing on marketed product throughout its commercial life, distinct from the pre-approval registration study.
- Registration model: the regression line, confidence limits, and shelf life conclusion established in the original (or most recently updated) stability submission, against which ongoing results are trended, not just checked against the pass/fail specification.
- Adverse trend: a result or trajectory that, while still within specification, moves toward the limit faster than the registration model predicted, or a slope inconsistent with the registered batches.
- Out-of-trend (OOT) result: a result outside a pre-established statistical trending limit even though it may be within specification; see the stability OOT limit-setting worksheet.
5. Procedure
5.1 Build the annual placement plan
- At the start of each calendar year, identify every product, strength, and primary container closure type manufactured or intended for manufacture that year.
- Confirm at least one batch per product, per strength, per primary container closure type, per manufacturing site is scheduled for placement, unless no batch of that combination was manufactured that year.
- Where more than one site or manufacturer produces the same product, ensure each is represented over a defined cycle (state the cycle if not every site is placed every single year):
<<FILL: e.g. every site represented at least once in any rolling 24-month period>>. - Document any product/strength/site combination with no batch manufactured in the year, so the absence is a documented fact, not a silent gap.
5.2 Select and place the batch
- Select a batch representative of routine commercial production, not a batch already flagged for an unrelated quality issue, unless the investigation of that issue is itself a reason to place it.
- Pull initial (time zero) samples and place the batch into the qualified chamber(s) at the registered long-term condition (and accelerated, if the ongoing program design calls for it:
<<FILL: state whether accelerated is run on ongoing batches>>). - Record the placement in the stability tracking system with product, batch, strength, site, container closure, and the schedule.
5.3 Test on schedule
- Test at the time points and with the attributes defined in
<<FILL: reference to the standard ongoing time-point schedule, or the registered protocol if it differs>>. - Use the same validated, stability-indicating methods used in the registration study, or a validated equivalent with documented comparability.
- Record actual test dates; a result outside the defined pull window is a deviation per
<<FILL: SOP-ID for deviations>>.
5.4 Trend against the registration model
- Plot each ongoing result against the regression line and confidence limits established in the registration package, not only against the specification.
- Apply the pre-established OOT limit (see the OOT worksheet referenced in section 4) to flag results or slopes trending faster than the registered model.
- A result that is within specification but flagged OOT is assessed per
<<FILL: SOP-ID for out-of-trend investigations>>; it is a signal, not a result to file and forget. - A result outside specification is handled as an OOS per
<<FILL: SOP-ID for OOS investigations>>, in parallel with the trend assessment.
5.5 Escalate a confirmed adverse trend
- Where a trend is confirmed (not an isolated analytical excursion), assess whether the registered shelf life or storage statement remains supported.
- If the shelf life is no longer supported, open a CAPA and change control to evaluate a shelf life reduction, formulation change, packaging change, or other corrective action.
- Regulatory affairs assesses whether the finding requires a Field Alert Report (US) or notification to the relevant authority (EU/other), per
<<FILL: SOP-ID or regulatory procedure for field alerts/notifications>>. Do not wait for a confirmed OOS on marketed product before this assessment. - Document the disposition and communicate it into the next annual product review / PQR cycle.
5.6 Annual summary and program completeness check
- Before each annual product review cycle, confirm every product/strength/site combination due for placement that year was placed, tested, and trended.
- Document any gap (missed placement, missed time point not covered by a deviation) as a program-completeness finding, not silently rolled forward.
- QA reviews and approves the annual ongoing-stability summary.
6. Acceptance criteria
- At least one batch per product, strength, primary container closure type, and represented manufacturing site is placed each year a batch was manufactured, or the absence is documented.
- Every ongoing result is trended against the registration model, not only checked against specification.
- Every OOT-flagged result or slope is investigated per the OOT/OOS procedures referenced above.
- A confirmed adverse trend triggers a documented shelf life re-assessment and a regulatory reporting-obligation assessment, both before the next annual product review closes.
- The annual program completeness check is performed and approved by QA before each annual product review cycle.
7. Records generated
- Annual placement plan.
- Stability tracking log (placement, schedule, actual test dates).
- Time-point results and trend plots against the registration model.
- OOT/OOS investigation records arising from ongoing data.
- Annual ongoing-stability program summary.
8. References
21 CFR 211.166, Stability testing. 21 CFR 211.180(e), Annual Product Review (ongoing stability as a trended input). EudraLex Volume 4, Part I, Chapter 6, Quality Control (ongoing stability program expectation, EU). ICH Q1A(R2), Stability Testing of New Drug Substances and Products. ICH Q1E, Evaluation of Stability Data. FDA guidance on Field Alert Reports (US reporting trigger for confirmed adverse findings on marketed product).
Confirm the current version and clause numbers of each reference before issue.
9. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
10. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author | <<FILL>> | ||
| Reviewer (QA) | <<FILL>> | ||
| Approver (Quality Head) | <<FILL>> |
Filled specimen
The following shows the section 5.6 annual completeness check completed for an illustrative product line, so you can see the level of detail an inspector expects. Company and numbers are illustrative.
| Product / strength | Site | Batch manufactured this year? | Placed on ongoing stability? | Batch ID | Trend status |
|---|---|---|---|---|---|
| Fictional Tab 50 mg | Site A | Yes | Yes | FT-50-2026-04 | Stable, within registration model |
| Fictional Tab 100 mg | Site A | Yes | Yes | FT-100-2026-07 | OOT flagged at 12 months, investigation OOT-2026-019 closed, assay decline attributed to a reference standard lot change, corrected, no shelf life impact |
| Fictional Tab 150 mg | Site A | No | N/A | N/A | Documented absence, no batch manufactured in 2026 |
| Fictional Tab 100 mg | Site B (second manufacturing site) | Yes | Yes | FT-100-SB-2026-02 | Stable, within registration model |
Annual summary conclusion (specimen): all product/strength/site combinations with a 2026 batch were placed and tested on schedule. One OOT signal was raised, investigated, and closed with no impact to the registered shelf life. The 150 mg strength absence is documented, not a gap in program execution. The program is complete for annual product review purposes.
Common inspection findings this SOP prevents
- No batch placed for a product/strength/site combination in a given year, with no documentation of why.
- Ongoing results checked only against specification, missing a trend that is passing today but drifting faster than the registration data predicted.
- An OOT signal filed with no investigation because the result was within specification.
- A confirmed adverse trend never assessed for a Field Alert Report or equivalent EU notification obligation.
- The ongoing program existing on paper (a procedure) with no evidence it was actually executed that year.
How to adapt this SOP
- Set your document number, owner, and effective date in the header.
- State your actual multi-site representation cycle in step 5.1.3 if not every site is placed every year.
- Point every cross-reference (deviations, OOT, OOS, field alerts, CAPA, annual product review) to your real procedure numbers.
- State whether your ongoing design includes an accelerated leg or long-term only, and reference your registered protocol.
- Confirm every regulation in section 8 against the current published version before issue.