A sponsor moves an approved oral tablet into a new modified-release version, or takes an established active substance from an oral form into an injectable. The regulatory-CMC instinct is to open a fresh Q1A stability program and start the clock from zero — full long-term data, every box checked, as if the substance had never been studied before. ICH Q1C says that is more than the guideline actually requires. For a genuine new dosage form of an already-approved drug substance, Q1C lets the submission bridge on a reduced stability database — if the justification earns it.

What Q1C actually covers

Q1C's scope is narrower than teams often assume. It applies when a sponsor develops a different pharmaceutical product type that contains the same active substance as a product the authority has already approved. The guideline's own examples are concrete: oral to parenteral, an immediate-release tablet reworked into a modified-release tablet, a capsule or tablet reformulated as an oral solution or suspension. What it does not cover is a formulation change that stays inside the same dosage form — a new excipient in the same tablet, a coating change, a strength addition. Those changes run on other guidance; Q1C's reduced-database allowance is reserved for the dosage-form jump itself.

1996
The year ICH Q1C reached Step 4 — a stable, long-finalized annex to the Q1A framework.
~6 + 6 mo
The reduced accelerated and long-term dataset Q1C commonly allows at submission, in justified cases.
1 substance
Q1C bridges the new dosage form to data on an active substance already approved in another form — not a brand-new molecule.

Why the reduction isn't automatic

A reduced database is a conclusion a sponsor earns, not a default Q1C hands out. The justification has to draw on what the active substance's approved-form stability program already demonstrated — its degradation pathways, its sensitivity to temperature, humidity, and light, how predictable its behavior has been across batches. A substance with a clean, well-characterized stability history in its approved form supports a thinner bridging package for the new dosage form. A substance with marginal or inconsistent stability data does not get the same latitude just because Q1C exists. This is where CMC regulatory strategy work earns its keep: the bridging argument is substance-specific, and a generic citation to Q1C without that evidence behind it reads to a reviewer as an attempt to skip work, not an argument for skipping it.

Q1C doesn't lower the bar for what you have to know about the molecule. It lowers the bar for how much of that knowledge has to be freshly generated in the new dosage form before you can file. Why the bridging justification is the real deliverable

The protocol design doesn't change

Teams sometimes read Q1C as license to simplify the stability protocol itself — fewer time points, looser storage conditions, a shorter testing battery. That is a different guideline doing a different job. Q1C's own text says protocols should generally follow the Q1A approach: the same storage-condition matrix, the same expectation of stability-indicating methods, the same long-term commitment running to full shelf-life after approval. What Q1C narrows is how much of that long-term data has to already exist at the time of submission, not how the study is designed or how long the sponsor's obligation to collect data actually runs. A reduced database at filing is a timing concession, and the post-approval commitment to keep the long-term study running is where that concession gets paid back. Programs developing a new drug delivery system or shifting into oral solid dosage forms benefit most from treating Q1C this way — as a filing-timeline tool layered onto a Q1A-designed program, not a shortcut around designing one.

  • Confirm the dosage-form change is real. Route, delivery system, or dosage form — not a same-form reformulation — or Q1C's allowance doesn't apply.
  • Lean on the approved form's data, explicitly. The bridging justification should name the degradation pathways and stability behavior it is drawing from, not just assert that the substance is 'well understood.'
  • Keep the protocol Q1A-shaped. Storage conditions, testing intervals, and stability-indicating methods follow Q1A; only the submission-time database shrinks.
  • File the continuing commitment. The long-term study keeps running post-approval to full shelf-life — the reduced database is a sequencing choice, not a smaller total dataset.
A Q1C scoping sequence to run before the protocol is written
  1. Classify the change correctly. New dosage form under Q1C, or a same-form reformulation under different guidance — get this right first.
  2. Pull the approved-form stability record. Degradation pathways, sensitivity profile, batch-to-batch consistency — the raw material for the bridging argument.
  3. Draft the reduced-database justification before the protocol. Decide what the submission can responsibly lean on before designing the study around it.
  4. Plan the post-approval commitment alongside the filing strategy. The long-term obligation doesn't disappear; sequence it from the start.

None of this is exotic CMC work — it is a bounded scoping exercise: classify the change, inventory what the approved form already proved, build a justification that is specific to the molecule rather than generic to the guideline, and keep the protocol itself inside Q1A's design. Programs that treat Q1C as a blanket shortcut end up with a reviewer's question they can't answer substantively. Programs that treat it as a bridging argument — built on real data about a real molecule — are the ones that actually get the reduced timeline Q1C was written to allow.

Frequently asked questions

What counts as a 'new dosage form' under ICH Q1C?

Q1C defines it as a different pharmaceutical product type containing the same active substance as an already-approved product — a change in route of administration, a new delivery system or functionality, or a different dosage form on the same route. Examples the guideline gives include oral to parenteral, immediate-release tablet to modified-release tablet, and capsule or tablet to an oral solution or suspension. A reformulation that stays within the same dosage form is not what Q1C addresses.

How much stability data can a new dosage form submission rely on?

Q1C allows a reduced database at submission in justified cases — commonly framed as around six months of accelerated data and six months of long-term data from studies still in progress, rather than the full long-term dataset Q1A would otherwise expect. The reduction has to be justified against the drug substance's known stability behavior; it is not an automatic allowance.

Does Q1C replace the Q1A stability program?

No. Q1C is an annex to the parent Q1A framework, not a substitute for it. The new dosage form's protocol still follows Q1A's design principles — storage conditions, testing intervals, stability-indicating methods — Q1C only narrows how much data has to exist before submission, leveraging what is already known about the active substance from its approved form.

Sources & further reading

  1. ICH. Q1C — Stability Testing for New Dosage Forms, Step 4 guideline (6 November 1996). ich.org
  2. EMA. ICH Q1C — Stability Testing: Requirements for New Dosage Forms — Scientific Guideline. ema.europa.eu

This article is provided for general informational purposes and reflects the regulatory landscape as of November 2026. It is not legal or regulatory advice. Confirm current ICH Q1C expectations and regional implementation with FDA, EMA, or qualified CMC regulatory counsel before acting.