Part 01 · The Question→Part 02 · The Record→Part 03 · The File
← All Case Files
Inspection Case File · CF02 · Sterile Manufacturing

Deviation Root Cause Documentation: The 483 Most QA 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.192 ICH · Q9 Used by Quality leaders preparing for FDA inspections
The Scene

Day two of the inspection. The investigator pulls Deviation Report DR-2023-0441.

Vancomycin Hydrochloride for Injection 500 mg, Lot 2023-2206. Aseptic fill on Line 3.

The deviation is documented. The investigation is closed. The CAPA — operator retraining — is signed.

The investigator turns to the conclusion.

Investigator
"Operator technique variation."
She reads the conclusion twice. Then she sets the file down and looks up.
Investigator
"Who decided that was the cause? What evidence did they review before they reached that conclusion? And how did they rule out a systemic problem with the gowning procedure, the environmental monitoring, or the equipment on Line 3?"
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

FDA inspections occur on a 2-year cycle. Building a defensible authorization record retroactively — under inspection pressure — is not the same as having one in the file before the inspector arrives.

What the file contained

The deviation report was complete. The investigation was thorough. By every internal measure, the file was closed.

The CAPA was signed. The product impact assessment concluded that quality was not adversely affected.

What the file contained was the conclusion.

What the file did not contain was the decision.

A conclusion is a statement of result. A decision is a record of how that result was reached — what was weighed, what was rejected, who was responsible, and what authority they exercised.

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

What the investigator is evaluating
21 CFR 211.192 does not ask whether the team reached the right conclusion. It asks whether the conclusion was reached on a documented basis.

For sterile products, the standard is higher than for general manufacturing.

The investigation must demonstrate — in writing, contemporaneous with the decision — that systemic and environmental causes were formally evaluated and eliminated before an operator-specific root cause was concluded.

Verbal reasoning, no matter how sound, is not a record. A signature on a CAPA closure form is not a record of the reasoning that preceded it.

Investigator
"I am not asking whether the conclusion was correct. I am asking whether the conclusion was authorized — and on what evidentiary basis."
The QA Director cannot produce the record.
The Gap

The team may have reached the correct conclusion. The file does not show the work.

The deviation file documents what happened. It does not document who decided, 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 scientific and risk-based rationale used to justify the assigned root cause, including the specific evidence reviewed by the authorizing individual at the time of the determination, and the documented basis on which alternative systemic causes were eliminated."
21 CFR 211.192 — Investigation of discrepancies and failures to meet specifications.
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.