It was not thorough because it was long. It was thorough because it showed its work.
It did not tell me the event was isolated. It showed me the four other places the same failure could have surfaced, and what the writer checked to rule each one out. By the time I reached root cause, I already believed it, because I had watched them earn it.
Most investigations do the opposite. They state a conclusion and ask you to trust it.
Isolated event. Root cause, human error. No recurrence expected.
Those are not findings. They are assertions, and an assertion is the thing that falls apart the moment someone asks the second question.
Here is a better way to write an investigation that holds up. It does not necessarily require a longer record. It requires putting the work in a more useful order.
Before you write root cause, define the boundary.
Ask where else this failure could live: which other batches, lines, shifts, products, suppliers, or processes share the same mechanism. Then show what you checked and why each one is or is not affected.
That turns “we think it was isolated” into evidence showing where the problem starts and stops. More importantly, it gives the team a much better foundation for correcting the actual condition instead of waiting for the same issue to appear under a new event number.
Then take root cause one step further.
Do not stop at who made the error. Ask what made the error possible and why the system did not catch it.
Human error may be part of the cause. Too often, it is where the investigation stops instead of where the next question begins.
For drug CGMP manufacturers, FDA continues to put real weight on investigation scope, supported root cause, systemic issues, CAPA, and effectiveness. Its March 2026 draft guidance on 483 responses also tells establishments to consider why issues leading to an observation were not previously identified by the quality unit or corrected by management, and whether improvements to the quality system, personnel management, or quality culture are needed.
That is an important question.
Because a weak investigation does more than leave one event poorly explained. It can leave the organization without a clear understanding of where the problem exists, why it happened, and whether the controls intended to prevent it are actually working.
The encouraging part is that the answer is not a heavier investigation process. It is a clearer one.
MEDVACON LIFE SCIENCES, LLC works closely with quality teams to build investigations that show their work, so the record demonstrates how the cause was established, how the condition was addressed, and why the issue can be considered controlled, not simply that the event was closed.
The standard should not be an investigation that looks complete. It should be one where the evidence makes the conclusion difficult to argue with.