When an investigator asks why a decision was reasonable, a missing connection turns a records request into a reconstruction exercise.
The question good documentation practices don’t answer.
Every quality leader knows the moment. An investigator, auditor or new executive picks up a closed record and asks one question the system was never designed to answer.
| What the system shows | What scrutiny asks |
|---|---|
| The CAPA was closed as effective | Who judged it effective, against which criteria and over what observation period? |
| The batch was released | Who authorized release with an open quality event, and why was that reasonable? |
| The deviation was closed | Who accepted the residual risk, and on what basis? |
The answers usually exist, but not in one place. They live in an impact assessment, an email thread, a review meeting, a verbal escalation and the memory of the person who signed. Each piece may be valid on its own. Together they form a trail that someone has to walk back through, under time pressure, often after the people involved have changed roles.
That is the Reconstruction Tax: the time and credibility an organization spends rebuilding reasoning that could have been preserved once, when the decision was made.
What FDA 483 observations show.
The regulations already set the expectation. 21 CFR 211.22(a) gives the quality control unit “the responsibility and authority to approve or reject” drug products, and 211.22(d) requires its procedures to be in writing and followed (eCFR, 21 CFR 211.22). 21 CFR 211.192 requires that any unexplained discrepancy be thoroughly investigated, that the investigation extend to other batches that may be associated with the failure, and that a written record of the investigation include “the conclusions and followup” (eCFR, 21 CFR 211.192).
Those are also the two regulations FDA cited most often on drug 483s in FY2025: 211.22(d) 243 times and 211.192 164 times, according to the agency’s Inspection Observations data. These are counts of citations, not of firms, and they cover system-generated 483s only. But the pattern is clear: inspectors spend much of their time on how quality decisions were made and documented, not only on whether results met specification.
A worked batch release decision record.
Here is one batch-release decision documented the way the question would be asked. The batch, people and dates are fictional, taken from the ComplianceWorxs Batch Release Authorization Case File.
The situation. Batch TAB-0626-118 was ready for release, but deviation DEV-0626-044 was open: an operator’s qualification had expired six days before he performed the blending step.
Evidence
The executed batch record, the deviation, product impact assessment PIA-0626-044, in-process and final QC results, and the operator’s training history. Blend time was 42 minutes, inside the validated range of 25 to 45 minutes. All results met specification. The record also states what was inferred rather than established, including that no pattern exists across prior batches, because that lookback was still open.
Judgment
The lapse was a procedural compliance failure and required formal evaluation. The decision did not rest on the lapse being insignificant. It rested on evidence that the lapse did not become a failure of the operation or the finished batch.
Risk
Two alternatives were considered and rejected: continuing the hold, because more time was not expected to resolve a product-quality question the evidence had already answered; and rejecting the batch, because that was disproportionate to the evidence. The open lookback was assigned to the QA Compliance Lead under CAPA-0626-009, due July 17, with a stated trigger: any adverse finding reopens the disposition.
Notice what this record does not do. It does not claim the decision was correct. It does not remove the uncertainty. It makes the basis visible, so a qualified reviewer who was not in the room can see what was known, how it was weighed, what was left open and who accepted it.
An inspection readiness test for one decision.
Pick one consequential decision closed in the last six months: a CAPA effectiveness check, a batch release with an open quality event, or a deviation closed with residual risk. If you are already answering an observation, start with the FDA 483 response planner. Then, using only the record, answer four questions:
- Evidence: What did the decision owner know at the time, and what was inferred rather than established?
- Judgment: Why was this outcome chosen over the alternatives?
- Risk: What was knowingly left open, who owns it and what would reopen it?
- Authorization: Who accepted the decision, under what authority, and when?
Where ComplianceWorxs fits.
ComplianceWorxs does not replace your QMS, your CAPA or deviation systems, or your response to FDA. Those systems preserve what happened. The Inspection Response Record preserves why one consequential decision was authorized: the evidence, judgment, risk and authorization in one reviewer-ready record. ComplianceWorxs does not make, approve or recommend regulated decisions. Your organization and its authorized people remain accountable.
Next step: Check one completed decision in about three minutes. No documents, email or sales call required. Or see a completed record first.
Sources: eCFR, 21 CFR 211.22, Responsibilities of quality control unit; eCFR, 21 CFR 211.192, Production record review; FDA, Inspection Observations (FY2025 spreadsheet, Drugs); FDA, Data Integrity and Compliance With Drug CGMP: Questions and Answers, December 2018.