Part 01 · The Question→Part 02 · The Record→Part 03 · The File
← All Case Files
Inspection Case File · CF09 · Stability and Analytical

Stability OOT Disposition: The 483 Most Teams Don't See Coming.

A documented deviation. A signed CAPA. A closed investigation. And a single question, asked on day two of inspection, that the file does not answer.

What you'll see in this case file
  • The exact 483 observation language
  • The five required authorization fields
  • A complete reference DDR record
  • The blank template for your facility
See What Defensible Looks Like → Free to read. No payment to continue.
Citation · 21 CFR 211.166 ICH · Q1A Used by Quality leaders preparing for FDA inspections
The Scene

Day three of the inspection.

. The investigator pulls Stability OOT-2024-0019. Pantoprazole Sodium DR Tablets 40 mg, ongoing stability protocol. The 18-month assay result was within specification but had trended downward by 1.8% from baseline.

The investigation evaluated the trend. The conclusion: the result is within specification, the trend reflects expected analytical variability and is not a true degradation pattern. No impact to shelf life. Stability monitoring continues as scheduled.

The investigator turns to the conclusion.

Investigator
"Within specification — no impact to shelf life."
She reads the conclusion twice. Then she sets the file down and looks up.
Investigator
"Who authorized the no-impact conclusion? On what evidence specifically did the team conclude this was analytical variability rather than a degradation trend? Was the data trended against historical lot baselines? And on what basis was the projected shelf-life extrapolation deemed valid?"
She listens to the verbal answer. Then she asks for the documented reasoning.
Pause

Most QA teams answer this question verbally. The file does not contain the documented reasoning. That is the gap.

Skip ahead to the record format →
Why this matters now

Stability OOT investigations citing analytical variability without documented projection analysis are routinely flagged in inspection. The pattern: trend observed, variability explanation given, no documented projection analysis to demonstrate shelf-life support.

What the file contained

The OOT investigation was complete. The trend was acknowledged. The conclusion was reached and the protocol continued.

The Stability Manager reviewed the data. The analytical method was confirmed in control. Historical assay variability was referenced. Three months later, the 21-month timepoint was within specification. The OOT was closed.

What the file contained was the conclusion.

What the file did not contain was the decision.

A trend was observed. An explanation was provided. A no-impact conclusion was reached. But the rationale for treating the trend as analytical variability rather than a true degradation pattern, the documented analysis of trend rate against shelf-life projection, and the named individual who authorized the conclusion are not in the file.

The conclusion belongs in the file. The decision belongs in the record.

What the investigator is evaluating
21 CFR 211.166 requires that stability data support the labeled shelf life. The standard is not whether individual results are within specification. The standard is whether the no-impact conclusion was reached on a documented analytical basis.

Under ICH Q1E expectations, downward trends within specification can predict future OOS results before the labeled expiration date. The rigor required for a no-impact conclusion increases when a trend is present.

The OOT investigation must demonstrate — in writing, contemporaneous with the conclusion — that analytical variability was characterized from independent data, that the trend rate was projected against shelf-life specification, and that the named authorizing individual reviewed the projection before concluding no impact.

A within-specification result is data. A within-specification result is not, on its own, a documented stability disposition.

Investigator
"I am not asking whether the result was within specification. I am asking whether the no-impact conclusion was authorized — and on what evidentiary basis."
The Stability Manager cannot produce the record.
The Gap

The result may have been within specification. The file does not show the work behind the no-impact conclusion.

The OOT file documents the trend. It does not document who decided there was no impact, on what evidence, against what alternatives, and under what authority.

Ready to see the record format?
See the five fields the investigator expects to find →
The 483
"Failure to document the rationale used to justify the conclusion that the out-of-trend stability result did not indicate a product quality issue or warrant a change in expiry date, including the specific evidence reviewed and the basis on which alternative explanations were excluded. The stability disposition record establishes that the OOT was investigated but does not reconstruct the decision logic that produced the conclusion."
21 CFR 211.166 — applied regulatory framework.
Continued · Part 02 of 03

That 483 was avoidable.

See the record that prevents it.

The five fields the investigator expects to find. The alternative-causes evaluation that distinguishes a decision from a signature. A complete reference example from the Vancomycin scenario.

Show Me the Record →
✓ Free to read · No payment required to continue

Used by Quality and Validation leaders preparing for FDA and EMA inspections. Built around 21 CFR 211.192 and ICH Q9.