Deviation

What a deviation is

A deviation is an unplanned departure from an approved procedure, specification, master batch record, SOP, or other controlled document. It captures any event where the actual outcome differs from the documented, approved process.

Deviations are distinct from planned deviations (pre-approved changes with risk assessment) and from nonconformances (product-focused quality issues). Most GMP regulations use "deviation" for process and "nonconformance" for product, though terminology varies.

Why deviations are so heavily inspected

Deviations are the primary early signal of process drift, training gaps, equipment issues, or supplier problems. Inspectors read deviation trends to assess whether an organization sees its problems and manages them proactively.

Repeat deviations without corresponding CAPAs, long-open investigations, and superficial root causes are among the most common sources of 483 observations and warning letters.

Where deviations appear in regulations

Deviation handling requirements appear in every major GMP framework:

• FDA 21 CFR Part 211 §211.192 — Investigation of any unexplained discrepancy
• EU GMP Chapter 1 §1.4(xiv) — Deviations investigated and documented
• EU GMP Chapter 8 — Complaints and product defects management
• ICH Q10 — Deviation management inside a pharmaceutical quality system
• ISO 13485 §8.3 — Control of nonconforming product
• PIC/S PE 009 — Aligned with EU GMP on deviation investigation

The deviation lifecycle

Typical stages of a deviation record:

• Detection & reporting — operator, QA, or automated monitoring flags the event
• Classification — minor, major, or critical based on impact and risk
• Immediate containment — stop shipment, quarantine batch, pause process
• Investigation — root cause analysis, impact assessment, batch disposition
• CAPA linkage — corrective and preventive actions defined if needed
• Closure — QA approval, training update, record archival

What good deviation controls look like

Strong deviation programs have:

• Low barrier to report — operators can flag without approval gates
• Defined classification criteria — major/critical escalate automatically
• Time limits on closure — 30/60/90-day tiers with overdue escalation
• Structured root cause templates preventing shallow analysis
• Impact assessment on other batches, equipment, documents
• Trending on recurring root causes feeding CAPA prioritization

How Complere manages deviations

The Complere Deviation workflow provides intake through closure with structured investigation and direct CAPA linkage.

• Single-click escalation from deviation to CAPA
• Configurable classification matrix by product line or site
• Structured root cause capture with controlled taxonomy
• Impact assessment fields linked to batch, equipment, documents
• SLA-driven overdue alerts to QA leadership
• Trending dashboards on root cause categories and recurrence
• Full audit trail with e-signatures per 21 CFR Part 11

Terms related to deviation

Deviation is tightly coupled with several other quality concepts:

• CAPA — the follow-on action when a deviation requires systemic fix
• Root Cause Analysis — the investigation inside the deviation record
• Out of Specification (OOS) — a specific deviation type in analytical testing
• Audit Trail — the record history of investigation steps
• Validation — deviations may signal process validation gaps