The disposition survived. Could you produce the reasoning that authorized it?

A disposition is the answer the organization recorded. Leadership needs to know whether the record can still explain the decision.

Consider a closed deviation that supported a batch disposition. The investigation, final conclusion, and Quality approval are available. An independent reviewer then asks which evidence ruled out a broader impact, why the selected action was proportionate, and who accepted the remaining uncertainty. Those answers may exist across linked records, but the approval alone cannot supply them.

For drug product manufacturing, 21 CFR 211.192 requires investigation of unexplained discrepancies and a written investigation record. The quality unit's review and approval authority is described in 21 CFR 211.22. The practical leadership question here is narrower: can the organization connect the available evidence to the judgment and authorization it actually made? The framework below is CW's way to test that connection, not a regulatory form or a claim that every deviation needs a separate document.

What exactly must the disposition explain?

Start with the question a reviewer would ask, rather than the document list: Why was this outcome reasonable on the evidence available at the time? The answer needs a traceable chain. A completed form may contain each piece somewhere; the test is whether another qualified person can follow them without relying on the original decision maker's memory.

These are review questions, not a universal checklist for every quality event. The depth of the answer should fit the decision's consequence and the organization's procedures. FDA's quality systems guidance describes management and quality-unit responsibilities in a functioning pharmaceutical quality system; CW's decision-trail test applies that concern to later reconstruction.

Use a worked disposition to locate the gap.

Suppose a batch record discrepancy was discovered during review. The deviation concluded that the affected batch could be dispositioned because a second check found no additional discrepancies. Quality approved closure. Months later, the batch record, deviation, second-check results, and signature are all retrievable. This is a fictional example; it does not establish that any actual release was justified.

The most useful finding is often specific: “The second check is present, but the record does not show how its scope addressed the possibility of a broader failure.” That gives Quality a concrete question to evaluate. “The file is incomplete” does not.

What should leadership do with the finding?

Classify the record before assigning a remedy. That keeps a retrievability problem from being treated as an unsound decision—and keeps a substantive risk from being buried under document cleanup.

1. Connected and retrievable. The contemporaneous sources support the conclusion and can be followed. Record where the evidence lives, who owns retrieval, and which controlled record remains authoritative. Sample another consequential decision later to see whether the method is repeatable.
2. Evidence present, reasoning dispersed. The original materials are available, but their connection to the approval takes work to explain. Assign a qualified reviewer to map the references, label inferences, and document any present-day reconstruction as such. Check whether the same gap recurs in a small set of similar decisions.
3. Basis missing or contradicted. Essential evidence cannot be located, an adverse signal was not resolved, or the documented conclusion exceeds what the record supports. Escalate through the quality system for an impact assessment and a decision by the proper authority. Preserve the gap and the subsequent decision separately.

There is no honest shortcut from “approved” to “defensible.” There is also no reason to reopen every closed deviation because one file took time to assemble. The scope of any wider review should follow the seriousness of the gap and evidence of a repeatable failure mode.

Make the next decision easier to inspect.

For future consequential dispositions, define a short decision summary at the point of authorization: the question being decided, evidence relied upon, material alternatives, risk accepted or controlled, conclusion, and approver. Link it to the controlled investigation and supporting records. This is a practical method for preserving reasoning, not a replacement for the deviation record or the site's procedures.

Two business effects matter. Risk mitigation: leadership can identify an unsupported conclusion before it is challenged later. Operational efficiency: Quality can answer a later question from a known evidence trail rather than convening the original participants to reconstruct it. Both are plausible benefits of a better decision record; this article does not claim measured savings or improved inspection outcomes.

Cross-functional alignment matters when Manufacturing, Laboratory, Regulatory, or Quality contributed materially to the disposition. Record whose evidence changed the decision and who retained final authority. Agreement in a meeting is not a substitute for a reviewable basis for approval.

The executive conclusion

Ask Quality to demonstrate one real disposition from the record as it stands today. If the reasoning is traceable, preserve access to it. If the trail breaks, classify whether the problem is retrieval, reasoning, or substantive risk; give that specific gap an owner and a decision path. The goal is an organization that can explain what it decided, what it knew, and why it was authorized—without inventing the answer later.

Source context: 21 CFR 211.192 · 21 CFR 211.22 · FDA Quality Systems Approach. The worked scenario and decision-trail categories are CW editorial examples, not regulatory mandates.