unavoidable constraints).

Unplanned deviation: an unexpected departure that occurs during execution (errors, breakdowns, unexpected conditions).

Important: Planned deviation is not a shortcut to bypass validation or change control. If the change is permanent or impacts validated state, it belongs in change control.

Deviation Handling: Practical Step-by-Step Workflow

1. Detection and immediate action: stop/contain, place batch on hold if needed, protect product.
2. Document the deviation: what happened, where, when, who, equipment ID, batch/lot, and immediate actions.
3. Initial impact assessment: assess patient risk, product quality impact, and data integrity impact.
4. Classification: minor/major/critical (site-specific definitions) based on severity and risk.
5. Investigation: determine root cause using evidence (records, logs, interviews, trend data).
6. Batch disposition decision: release, rework, reprocess, reject—based on science and documented rationale.
7. CAPA plan: corrective + preventive actions to prevent recurrence.
8. Effectiveness check: confirm deviation recurrence reduced and controls are working.

Mini Example: Unplanned Deviation During Granulation

Scenario: granulation mixing time exceeded the validated range due to equipment stoppage and restart. A solid deviation evaluation would include:

• Exact duration outside range and conditions during stoppage
• Batch record review, alarms, and equipment logs
• Risk assessment on CQAs (content uniformity, dissolution, moisture, impurities)
• Additional in-process or finished product testing justification (if needed)
• Root cause (e.g., maintenance issue, operator response gap) and CAPA (PM changes, training, alarm response SOP)

Impact Assessment: What You Must Evaluate

Impact assessment is where many deviation systems fail. A defensible assessment typically considers:

• Product quality: could CQAs be affected? any trend changes?
• Patient safety: any direct patient risk? (sterility, potency, impurities)
• Data integrity: are records accurate, attributable, complete?
• Regulatory commitments: any filing commitments or validated state impacts?
• Detectability: would existing tests/controls detect the impact?

Deviation vs Change Control (Critical Distinction)

• Deviation: an event that happened (departure from procedure/expected condition).
• Change control: a controlled decision to modify a system/process/document permanently (or systematically).

If a deviation reveals a needed process change, you usually open change control as part of CAPA. Auditors expect that linkage.

Common Confusions (Avoid These Audit Traps)

• Late reporting: deviations discovered days later look like poor control or data manipulation risk.
• “Operator error” as root cause: weak and often unacceptable unless supported by evidence and deeper causal analysis.
• No batch impact logic: “no impact” without science and evidence is a red flag.
• Repeat deviations with no CAPA: indicates ineffective quality system controls.
• Closing without effectiveness: completion of actions is not proof the issue is prevented.

Audit-Ready Talking Points

• Show deviation SOP, classification logic, and timelines
• Demonstrate one strong example with clear impact assessment and batch disposition rationale
• Explain how deviations trend into CAPA and management review
• Show linkage to change control for systemic fixes
• Provide evidence of effectiveness checks and reduced recurrence

Quick Deviation Checklist (Practical)

• Immediate containment and batch status control implemented
• Deviation documented with complete facts and timestamps
• Risk-based impact assessment completed
• Investigation uses evidence, not assumptions
• Batch disposition is scientifically justified and approved
• CAPA actions address root cause and prevent recurrence
• Effectiveness checks confirm sustained control

FAQs

What is a deviation in pharma?

A deviation is any departure from approved procedures, specifications, or expected conditions during GMP work that may impact quality, safety, data integrity, or compliance.

What is the difference between planned and unplanned deviation?

A planned deviation is pre-approved and documented before execution; an unplanned deviation is unexpected and occurs during execution.

Does every deviation require investigation?

Most deviations require at least an assessment. The depth of investigation should be risk-based; major/critical deviations generally require full investigation and CAPA.

Can a batch be released after a deviation?

Yes, if impact assessment and supporting evidence show product quality is acceptable and the disposition decision is justified and approved by QA as required.

What do inspectors commonly check in deviation records?

Timeliness, completeness, root cause quality, product impact rationale, CAPA effectiveness, and whether similar deviations are recurring without improvement.