On this page
How do you write the drug substance stability section in CTD S.7?
Assemble the actual study results by batch, process, package, condition and timepoint before writing the storage and retest-period or shelf-life proposal. Explain meaningful trends, analytical context and any extrapolation. Keep completed observations, future commitments and unresolved evidence separate so the conclusion does not overstate what has been demonstrated.
Before you begin
M4Q(R1) S.7 preparation; study design and conclusions need guidance appropriate to the substance, pathway and storage conditions.
What you will prepare: An auditable stability narrative with a clear data cutoff and a justified proposal linked to actual studies.
S.7.3: assemble the data before writing the conclusion
Build an inventory of protocols, batch identities, manufacturing versions, containers, conditions, timepoints and reports. Preserve the data cutoff. Present available results in a readable table, graph or narrative with units, criteria and qualifiers; account for missing or invalid timepoints through their controlled disposition. Link the analytical procedures and validation that support interpretation, including applicable stress or forced-degradation work.
Do not pool results from different packaging or process versions into an unlabeled average. If older methods were used, obtain the analytical assessment needed to compare them. An empty result cell means an unresolved or unavailable observation, not zero degradation.
S.7.1: explain what the evidence supports
Summarize the studies, meaningful trends and conclusions, then state the proposed storage condition and retest period or shelf life as appropriate for the substance. Distinguish observed duration from any proposed extrapolation and explain its scientific basis. The choice between a retest period and shelf life is not an editorial preference; obtain the substance-specific rationale.
Q1A(R2) is a relevant final guidance entrypoint for its stated scope, but this writing guide does not prescribe a universal batch count, condition or extrapolation rule. Biotech substances and other product contexts need their applicable guidance and assessment. If the product class or stability strategy is unknown, leave the proposal undetermined and assign the decision to the stability/regulatory owners.
S.7.2: make future work explicit and achievable
Present the applicable postapproval protocol and commitment separately from completed data. Identify the studies or batches, conditions, tests and schedule to which the actual commitment applies. Reconcile it with the remaining work and the organization's approved program. Do not copy a commitment from a different pathway or silently promise work that the team has not approved.
Fictional exercise: a draft claims a two-year retest period from a table with one year of data and no rationale. Record the observed duration accurately, obtain the scientific basis for the proposal, and check whether additional data or a revised proposal is needed. A planned future timepoint cannot be reported as an available result.
Separate observed evidence, proposed duration and future work
An editorial claim map makes the difference between a result and a proposal visible.
| Statement | Evidence needed beside it | Do not substitute |
|---|---|---|
| Results are available through a stated timepoint | Controlled results and data cutoff | A scheduled but untested timepoint |
| The proposed package is represented | Study container identity or supported relationship | An unqualified “same packaging” statement |
| A retest period or shelf life is proposed | Scientific evaluation and applicable guidance | The longest value found in a template |
| Further work is committed | Approved protocol, scope and schedule | A generic promise copied from another submission |
Start the writing sequence with S.7.3 data, then develop the S.7.1 conclusion and reconcile S.7.2 future work. The final dossier order need not mirror the order in which authors resolve the evidence.
Review exercise: one of two proposed substance packages has less follow-up. Keep the two evidence histories visible and ask the stability expert how they support the proposal. An average observation period does not explain either package. Likewise, missing observations must retain their actual status and disposition.
Use S.6 packaging and S.4 methods to verify the conditions under which the results are interpretable. Q1A(R2) has a defined product and application scope; this guide is a writing method, not a universal stability protocol.
Your preparation checklist
0/3 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
Is a drug substance retest period the same as a shelf life?
No. They describe different stability concepts and should not be chosen as interchangeable labels. Obtain the substance-specific stability strategy and scientific rationale, then use terminology consistent with the applicable guidance and actual proposal rather than the wording in a generic template.
Can planned timepoints be presented as available stability data?
No. State the data cutoff and the observations actually available. Describe scheduled future work separately in the applicable protocol or commitment. A planned observation does not become evidence supporting the current conclusion simply because its row exists in a study table.
Does Q1A(R2) prescribe the same package for every product?
No. Q1A(R2) has a stated scope for new drug substances and products, and other product or application contexts need their applicable guidance. Confirm the context before choosing study conditions or an extrapolation approach. This guide does not establish universal numerical requirements.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Guidance
ICH M4Q(R1): CTD Quality ↗Step 4, September 12, 2002; Module 3, printed pages 5–18. Organization/content guidance, not a universal list of required studies. Checked September 22, 2026. Guide-specific passages: 3.2.S.7.1–3.2.S.7.3, printed page 11.
Guidance
FDA Q1A(R2): Stability Testing ↗Final, November 2003. Scope is new drug substances/products; determine product-specific and pathway-specific guidance before designing a study. Checked September 22, 2026.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 3.2.S.7. A heading identifies placement, not mandatory applicability.