A major or critical deviation
The instinct under pressure is to reach a cause quickly so the batch can move. That instinct is the source of most weak investigations.
The question that decides the investigation is not what happened, but what else shares the same cause.
Roughly the first working day
- Contain and quarantineSecure affected material and stop the process step where continuing would compound the issue.
- Record contemporaneouslyCapture what is known now, by whom and when, before recollection consolidates around a preferred explanation.
- Notify QA and, where release is in prospect, the QPEarly notification costs little. Discovering later that the QP was not informed is itself a significant finding.
- Assess impact beyond the batchOther batches sharing equipment, materials, personnel or time window, and any material already released.
- Classify by risk, not by convenienceClassification drives investigation depth. Under-classifying to reduce effort is visible in the record afterwards.
What must not be lost while people react
- Batch records and in-process data in their original form.
- Equipment logs, alarms and environmental data for the period.
- Personnel present, and their accounts recorded promptly.
- For anything electronic, the source records rather than printouts.
What shapes the investigation
- 01What is the evidence for the suspected cause, as distinct from the argument for it?
- 02Why did the process permit this — instruction, layout, workload, or a control relying on vigilance?
- 03Should the system have detected this earlier, and why did it not?
- 04Which other batches could share the cause, and what is their status?
- 05Has anything similar occurred before?
Things to consider, not conclusions to adopt
- Where a batch affected by an unresolved deviation is considered for certification, Annex 16 sets out expectations and the reasoning should be documented.
- Where released product may be affected, consider whether complaint, quality defect or recall processes are engaged — the assessment is specific to your product and market.
- Investigation cycle time and closure quality are commonly examined; both are visible in your own records.
What sites commonly get wrong
- Concluding 'human error' and stopping, which is a description rather than a cause.
- Limiting impact assessment to the batch in hand.
- Closing against a deadline rather than against a conclusion.
- Releasing on a passing retest without resolving why the original result occurred.
Ten steps, in this order
- 01
Contain
Stop the situation getting worse. Quarantine affected material, halt the process step if continuing would compound the problem, and secure the area or system involved.
- 02
Assess
Establish what is known versus assumed. What happened, when, to what, and who observed it. Resist the pull to conclude a cause in the first hour.
- 03
Escalate
Notify according to your own procedure. Getting the right people informed early costs little; discovering later that QA or the QP was not told is itself a finding.
- 04
Investigate
Establish the cause with evidence rather than plausibility. Depth should be proportionate to risk, but the standard for a confirmed cause does not move.
- 05
Document
Record contemporaneously as you go. Reconstructing a record afterwards converts a quality problem into a data integrity problem, which is a different order of seriousness.
- 06
Determine impact
Assess product impact beyond the batch in front of you — other batches sharing equipment, materials, personnel or time window, and material already released.
- 07
Correct
Fix the immediate instance, and separately address the cause. Conflating correction with corrective action is the most common weakness in a response.
- 08
Prevent recurrence
Address why the process permitted the event. Where the design invites the error, training a person not to make it is a delay rather than a correction.
- 09
Verify effectiveness
Check against a criterion defined before implementation. This is the step most often skipped, and the one that decides whether the event returns as a repeat finding.
- 10
Close and monitor
Close with evidence attached, and keep the indicator under review long enough to know the fix held rather than merely completed.
This is quality guidance, not legal advice
This is practical quality guidance, not legal or regulatory advice. Whether a specific event triggers a particular regulatory obligation depends on the product, the market, the marketing authorisation and the facts. Assess against your own procedures, and take qualified advice where the situation may involve notification, recall or a deliberate act.
A date you did not choose
If there is a response deadline or an investigation that has to hold up under scrutiny, a short call is the fastest route to a view on what to do first.