Sandra Okonkwo signed the certificate of analysis. The investigator wanted to know what was reviewed, how the deviation was weighed, what risk judgment was made, and who accepted responsibility. The file didn't say.
"Who reviewed this batch before release, how was Deviation DR-2023-0088 evaluated in the context of the release decision, what risk judgment supported release, and who accepted responsibility for authorizing distribution of this lot?"
A QA signature on a certificate of analysis does not, by itself, preserve the full decision basis for batch release.
Lot 2023-0847, Lisinopril Tablets 10 mg. 250,000 units. Manufacturing completed 11 July 2023. One in-process deviation — DR-2023-0088, a blend-time exceedance — evaluated and closed two days before release. All testing within specification. Certificate of analysis signed 18 July 2023, 09:17 EST.
The investigator reviewed the batch record package and asked what was reviewed, how the deviation was evaluated for the release decision, what risk judgment supported release, and who authorized distribution. The firm produced the batch record and certificate of analysis. Neither answered the questions being asked.
A QA signature on a certificate of analysis does not, by itself, preserve the full decision basis for batch release.
The batch record showed what happened during manufacture. It did not show why the release decision made sense when it was made — the Reconstruction Tax is what it costs to answer that question after the fact instead of at the time.
The complete release decision record — evidence, reasoning, risk judgment, and authorization. Use it as the standard for your next release decision.
Instant download, PDF · Inspection Case File 02 · Batch Release Decision Record
Every batch released this year carries the same exposure, until the release record preserves more than a signature.
21 CFR 211.22(a) requires the quality control unit to approve or reject every drug product. A certificate-of-analysis signature confirms someone reviewed the document for completeness. It does not identify who made the release decision, what evidence they weighed, or how they evaluated any deviation against that decision. In this case, that was the distinction the investigator's questions turned on.
The 483 observation in this case followed a familiar pattern: the batch record was complete, the testing was in specification, the deviation was closed — and none of it documented who authorized the batch, on what evidence, or why the deviation didn't preclude release. The gap wasn't the deviation. The gap was the decision record behind it.
Preserving a batch release decision record for inspection means capturing it at the moment the release decision is made: the evidence reviewed, how any quality event was evaluated in context of that release, the risk judgment applied, who owns the decision, and when they made it. Reconstructing this after the fact — during an inspection, or months later during litigation discovery — is materially harder than preserving it once, at the point of release.
The lot, the product, the batch size, and every deviation associated with the run — named, not summarized.
A plain statement that release is authorized, and that the identified quality event was evaluated in the context of this release decision — not left to be inferred from a signature.
The batch record, in-process and finished-product testing, environmental monitoring, equipment qualification status, and the deviation's investigation and closure — enumerated, not implied by a signature.
How the deviation was evaluated specifically for its impact on batch quality and release suitability — root cause, corrective action, and why it didn't preclude release.
Quality-event risk, patient-safety risk, overall lot-quality risk, and distribution considerations — assessed individually and against the lot as a whole.
A named decision owner with confirmed release authority, and an authorization timestamp distinct from the certificate-of-analysis signing date.
The batch record explains what occurred during manufacturing. The certificate of analysis reports the results. The deviation record documents the quality event. None of them explains why the decision owner concluded the lot was suitable for release — that's the record that was missing.
When the FDA inspector asks who authorized this and why, ComplianceWorxs is the record behind the decision that answers.
The signature confirms someone reviewed the document for completeness. The decision record documents who made the release decision, what evidence they reviewed, how any deviation was evaluated in that context, and the risk judgment supporting release. Investigators treat these as two different acts with two different regulatory standings.
In this case: a 483 observation, a CAPA for the release-decision documentation process, and a retrospective evaluation of every lot released under the same procedure — 94 lots across 18 months. The observation moved from a documentation deficiency to a quality-system governance finding, and the firm incurred the Reconstruction Tax of rebuilding the decision basis after the fact.
Closing the deviation satisfies the deviation record. It does not, on its own, document that the deviation was evaluated specifically in the context of the release decision being made. Those are two separate evaluations, and investigators ask for both.
As far back as the batches currently in distribution or under review. In this case, the retrospective evaluation covered 18 months of releases — every lot signed under the same procedure was in scope once the procedure itself was found insufficient.
The scenario is a solid-dose release. The decision-record gap — a signature standing in for the evidence, reasoning, risk judgment, and authorization behind it — applies to any batch release decision across product types.
The full inspection scenario: the 483 trigger, the investigator's question, the evidence-present-versus-missing breakdown, the Reconstruction Tax the firm incurred, a worked release decision record showing what should have existed, and how to assess whether your own release decisions carry the same gap.
This is one release. Every batch you ship asks the same question.
If this lot were pulled for inspection tomorrow, the certificate of analysis would answer one question. It wouldn't answer the evidence reviewed, the risk judgment made, or who accepted responsibility.
Get the record — $149Instant download, PDF