The root cause is written. The signatures are on the form. An inspector will ask something else: who authorized closing it, on what evidence, how product quality impact was weighed, and why the other explanations were set aside.
Answers use this article’s own words and show the section they come from. This is not advice on your own record.
Your question is saved without your name or contact details so we can see what readers want to know. Please leave out names and record details.
A deviation record documents the investigation. It can leave out the decision to stop investigating.
The gap sits after the root cause.
A deviation is opened, investigated, and closed. The form has a description, a root cause, a CAPA reference, and approval signatures. By every internal check, it is complete.
Then the question changes. An investigator does not ask whether the form is filled in. The investigator asks why this root cause, why this batch scope, and who decided that was enough.
If the answer lives in someone's memory, in a meeting nobody minuted, or in an email thread nobody can find, the record has a hole exactly where the decision was made.
What the regulations put on the record.
21 CFR 211.100(b) requires that any deviation from written production and process control procedures be recorded and justified. The word is justified, not merely logged.
21 CFR 211.192 requires that an unexplained discrepancy or a failure to meet specifications be thoroughly investigated, that the investigation extend to other batches and other drug products that may have been associated, and that a written record include the conclusions and followup.
21 CFR 211.22(a) places responsibility and authority with the quality control unit to approve or reject drug products and to review production records so that errors are fully investigated.
Four questions an inspector can ask of a closure.
None of these is exotic. Each one lands on a part of the decision the standard form does not ask for.
What the form usually shows
- “Root cause: operator error.”
- “No impact to product quality.”
- “Approved by QA.”
What the question needs
- The evidence that pointed to that cause and not another
- How impact was weighed, and across which batches
- The explanations that were considered and set aside, with the reason
- The named authority who decided it was enough to close
Use the Four Lenses on the closure.
The Four Lenses keep the parts of the decision separate, so a gap in one does not hide behind completeness in another.
Evidence
What was actually observed? Batch record entries, equipment and environmental data, sample results, interviews, timelines. Identify what supports the root cause and what was missing or not collected.
Judgment
How was it interpreted? Which root causes were considered, why this one was accepted, and why the others were not. Show the reasoning, not only the result.
Risk
What was the product-quality impact, and how far did it extend? Record the batch scope assessed, the other batches or products considered, what uncertainty remained, and what follow-up it created.
An illustrative closure, and where it breaks.
Consider a fictional fill-line deviation: a hold-time limit was exceeded on an intermediate. The investigation attributes it to a shift handover gap. The impact section says no effect on product quality. The deviation closes in nine working days.
This is an illustration, not a real case. Now apply the questions.
| Lens | What the closure says | What the inspector asks |
|---|---|---|
| Evidence | Handover gap identified from the shift log. | What else did the data show? Was equipment or material status checked against the same window? |
| Judgment | Root cause: handover communication. | What other causes were considered? Why was a material or process explanation ruled out? |
| Risk | “No impact to product quality.” | Based on what? Which batches shared the intermediate, and was that scope assessed? |
| Authorization | Closed by QA on the signature date. | Who decided the evidence was sufficient, and what did they have in front of them? |
Every statement in the left-hand column may be true. The record still cannot answer the right-hand column without someone reconstructing it.
The mechanism: capture, pressure-test, preserve.
The reasoning that matters is formed while the decision is being made. Weeks later it can only be remembered, and memory edits.
- Capture it as the decision happens. Record the evidence relied on, the root causes considered, the scope assessed, and the judgment, at the point of closure. Not in a summary written for the audit.
- Pressure-test it before authorization. Put the four inspector questions to the closure while the people who made the decision are still available. Where an answer is thin, the investigation is not finished.
- Preserve it with the decision. Keep the reasoning attached to the closure and the authorizing role, so the record that exists on the day of inspection is the record that existed on the day of the decision.
This sequence adds a short step at closure. It removes the long one later, when the deviation is being re-opened in front of an inspector.
Where this fits in deviation management.
Deviation management usually concentrates on speed: open on time, close on time, keep the aging report green. Those are real measures. They do not measure whether the closing decision can be explained.
A quick closure with a thin rationale and a slower closure with a documented one look the same on the aging report. They look very different across a table from an investigator.
The executive conclusion
The investigation ends when the root cause is written. The decision ends when someone can show who authorized the closure, on what evidence, with what judgment about product impact, and with what set aside. Ask for that record before it is asked of you.
To apply the same test to another completed GMP decision, see The Record Should Explain the Decision. For a related disposition record, see A Passing Retest Does Not Erase an OOS Result.
Source context: Regulatory requirements: 21 CFR 211.100, 21 CFR 211.192, and 21 CFR 211.22. The fictional hold-time deviation and the Four Lenses are CW editorial examples, not regulatory mandates. ComplianceWorxs does not provide regulatory or legal advice and does not judge whether any record is adequate.
