21 CFR 211.192 makes an unexplained discrepancy an investigation record

Record review is a release control

The direct answer in 21 CFR 211.192 is that drug-product production and control records, including packaging and labeling records, are reviewed and approved by the quality control unit for compliance with established, approved written procedures before release or distribution. The review is not just a completeness check. It sits at the decision boundary between manufacturing evidence and release, alongside the quality control unit's authority under section 211.22.

A digital workflow should therefore preserve the batch and product identity, applicable master and controlled procedures, performed steps, results, exceptions, signatures, review scope, reviewer authority, unresolved items, and final disposition. A green dashboard or completed routing state does not by itself establish that the quality control unit evaluated the records required by the regulation. The system must make the underlying evidence and deviations accessible to the accountable reviewer.

A passing result does not explain a discrepancy

Section 211.192 requires a thorough investigation of any unexplained discrepancy, including a theoretical-yield result outside the established maximum or minimum, or the failure of a batch or any component to meet a specification. The requirement applies whether or not the batch has already been distributed. That makes the trigger the unexplained event or failure, not only the current inventory status or whether a later test produced an acceptable value.

The investigation record should distinguish the original observation, specification or approved procedure, data and sample provenance, immediate controls, hypotheses, tests performed, results, scientifically supported conclusion, and disposition. A retest can be evidence within an investigation; it is not an explanation by itself. Systems that replace the first result, detach it from chronology, or close the event when an acceptable value appears can obscure the very discrepancy the rule says must be investigated.

The scope can extend beyond the first batch

The regulation says the investigation must extend to other batches of the same drug product and to other drug products that may have been associated with the specific failure or discrepancy. That does not mean every investigation must include every product. It requires a reasoned scope determination based on the possible association. Equipment, material, method, analyst, environment, process, facility, time period, packaging line, or other shared conditions may inform that decision.

A useful investigation system supports that reasoning without silently deciding it. It should show which potentially related records were searched, the criteria and dates used, what was included or excluded, the evidence reviewed, and who approved the scope. Links to batch, laboratory, deviation, complaint, maintenance, change, supplier, and corrective-action records should retain their own provenance rather than being copied into an untraceable summary.

Closure requires conclusions and follow-up

Section 211.192 requires a written record of the investigation that includes conclusions and follow-up. A conclusion should answer the question the investigation actually tested and preserve uncertainty when evidence does not support a definitive cause. Follow-up may connect to correction, corrective and preventive action, change control, monitoring, additional review, field action, training, or another governed process as appropriate to the facts and applicable procedures.

The operational test is whether a reviewer can reconstruct the discrepancy, scope, evidence, reasoning, disposition, approvals, and promised follow-up from the retained record. This analysis does not prescribe an investigation method or decide batch disposition. Product, process, filing, jurisdiction, and circumstance remain material, and organizations must apply the complete regulation, their approved procedures, other applicable requirements, and qualified scientific and legal judgment.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.