Deviation

A deviation is the formal record opened the moment any aspect of a regulated manufacturing or quality operation departs from the approved procedure, specification, master record or in-process control limit. Anything that is documented in advance as 'should happen this way' and then doesn't is a deviation. The MMR says weigh 12.5 ± 0.2 kg of active and the operator weighs 12.74 kg — deviation. The SOP says inspect every 30 minutes and the operator misses an inspection — deviation. The cleaning record says final rinse must be water for injection and reverse osmosis water was used — deviation.

The opposite of a deviation is conformance. Most batches run conformant most of the time. When they don't, the deviation record is the formal mechanism for capturing what happened, deciding what to do about it, and proving to a regulator later that the decision was risk-based and the product is still safe and effective. A site that records zero deviations is a site that is not looking — every FDA investigator knows that and pulls the deviation log first.

Three pieces of US cGMP carry the deviation obligation. 21 CFR 211.100(b) requires that 'written production and process control procedures shall be followed in the execution of the various production and process control functions and shall be documented at the time of performance. Any deviation from the written procedures shall be recorded and justified.' Note the two words: recorded and justified. Recording alone is not enough.

21 CFR 211.192 — the production record review rule — requires that 'any unexplained discrepancy (including a percentage of theoretical yield exceeding the maximum or minimum percentages established in master production and control records) or the failure of a batch or any of its components to meet any of its specifications shall be thoroughly investigated, whether or not the batch has already been distributed. The investigation shall extend to other batches of the same drug product and other drug products that may have been associated with the specific failure or discrepancy.' The 'shall extend to other batches' clause is what turns a single deviation into an investigation that can find multiple recall events.

21 CFR 211.180(e) requires that records of investigations be retained. EU GMP Chapter 1 §1.4(xiv) requires deviation handling as part of the pharmaceutical quality system; ICH Q10 §3.2.2 expands it; EU GMP Chapter 8 covers complaints and product recall which interlocks with deviation handling. ISO 13485 §8.3 (Control of nonconforming product) and §8.5 (Improvement, including CAPA) carry the equivalent obligation for medical devices, with 21 CFR 820.90 and 820.100 as the FDA equivalents.

Most QMS frameworks distinguish planned and unplanned deviations. The distinction matters because the approval path is different and the regulatory risk is different.

Planned (also called temporary or approved-in-advance) deviation

A planned deviation is an approved-in-advance departure from a procedure, typically for a specific period or a specific batch range, to handle an exception that would otherwise stop production but does not affect product quality. Examples: temporarily using a back-up balance while the primary is out for re-calibration; running a specific batch on a different filling line because the primary line has a planned shutdown; using a new lot of an excipient before the formal qualification is complete (with bridging studies). Planned deviations require pre-approval by Quality before they are executed and have a defined expiry — they cannot become 'the way we do it now'.

Unplanned (also called actual or incident) deviation

An unplanned deviation is a departure that happened — an operator missed a step, a temperature excursion occurred, a yield was outside limits, a sample bottle broke during transport. These are recorded after the fact, investigated, classified, dispositioned and closed. Most deviation records are of this kind.

Every mature deviation programme classifies deviations at the time of opening, because the depth of investigation, the approval level and the timeline all scale with classification. The three-tier Minor / Major / Critical scheme is the dominant convention.

Triage at the moment of opening is the highest-leverage decision in the programme. Misclassifying a critical as a major (because no-one wants the visibility) is the failure pattern that turns into a Warning Letter. Most mature programmes have an explicit triage SOP and require independent verification of any deviation classified as minor.

For anything above Minor, the investigation has three components: root cause, extension assessment and impact assessment.

Root cause

Why did this happen? Not 'because the operator made an error' — that is a symptom. Use 5-Why, fishbone (Ishikawa), fault-tree or Apollo as appropriate to the complexity. Stop when the next 'why' takes you outside the system you can fix. 'Because gravity exists' is a real stop point; 'because the operator was tired' is not — go further.

Extension assessment (211.192's 'shall extend')

What other batches, other products, other lines, other lots could have been affected by the same root cause? An out-of-spec assay in batch 2406-A from a wrong-spec excipient lot means every batch made with that lot is in scope. The extension list is documented; each in-scope batch gets its own disposition decision.

Impact assessment

What is the consequence to product quality, patient safety, regulatory commitments, supply continuity, and other in-flight batches? The impact assessment ends in a disposition decision: release as-is (with rationale), release after rework, release after reprocessing, quarantine pending further investigation, reject, recall (if already distributed).

Every deviation that affects material reaches a disposition decision. Use-as-is requires a scientifically defensible rationale that the deviation did not affect product quality — accepted only by Quality, with full documentation. Rework follows the original procedure with the deviation corrected (e.g. re-mix because of poor blend uniformity). Reprocess follows a different procedure approved for the rework — 211.115 requires this to be approved and the reprocessed batch to be tested against the same specs. Reject means the material does not enter commerce and is destroyed-and-witnessed. Recall applies when affected material has already been distributed; 21 CFR Part 806 governs the recall procedure.

Disposition decisions for critical deviations and for any 'use-as-is' regardless of class require the Quality Unit's sign-off independent of production.

These three records overlap and the terminology varies by company. The clean separation:

• Deviation — process / procedural departure. The procedure said X, what happened was Y. Captured on the BMR / DHR; closed at batch level.
• NCR (Non-Conformance Report) — material did not meet specification. An incoming lot, an in-process intermediate, or finished product is out-of-spec. Triggers disposition (use-as-is, rework, reject, return).
• CAPA — a systemic correction. The deviation or NCR investigation revealed a system-level problem (procedure unclear, training inadequate, equipment unreliable, supplier weak) that requires a documented action plan, an effectiveness check, and management visibility.

Workflow: A deviation might trigger an NCR (if material is affected) and an NCR might trigger a CAPA (if the cause is systemic). Not every deviation triggers an NCR; not every NCR triggers a CAPA. Forcing one-to-one mapping clogs the CAPA queue with low-impact items and dilutes management attention. A mature programme has roughly 10:1 deviations to NCRs and 5:1 NCRs to CAPAs.

1. Deviations opened days or weeks after the event — fails contemporaneity (ALCOA+) and 211.100(b) 'documented at the time of performance'.
2. Single-line root cause: 'operator error' — fails the five-why depth expectation.
3. Extension assessment missing — 211.192's 'shall extend' is the most-cited deviation observation.
4. Disposition rationale that recites the spec rather than explaining why this deviation did not affect this batch.
5. Repeat deviations not trended — the same equipment fails the same way every other month with three different supervisors signing it off.
6. Planned deviations renewed indefinitely — operating an MMR change as a perpetual deviation.
7. Deviation closed without CAPA when one was clearly warranted — closed-loop systemic correction missing.
8. Deviations exist on paper but the operator could not open one at the kiosk without a supervisor present — friction so high that minor deviations go unrecorded.
9. Audit-trail review at batch release does not flag deviations as a high-priority review item.

A deviation programme that does not collapse under volume has these properties:

• Low-friction opening — the operator can open a deviation at the kiosk in 30 seconds, attach a photo, classify Minor / Major / Critical with a guided picker, and continue work. Supervisor verification follows asynchronously.
• Automatic triggers — the system opens deviations on its own for known triggers (yield out of band, time-limit breach, in-process spec breach, tolerance band breach on a dispense weight). The operator confirms the auto-opened deviation rather than typing it from scratch.
• Triage SOP with peer review — classification is verified by a second person within hours, not weeks.
• Linked to the originating record — every deviation is linked to the WO, BMR step, equipment, operator, lot and material it occurred on. Reverse-search from a batch returns every deviation that affected it.
• Extension assessment as a structured step — not a free-text paragraph but a query against batches that shared the root-cause variables (same lot, same line, same shift, same SOP version).
• Trending visible — top-10 deviation categories, top-5 repeat offenders, deviation rate per batch per line per shift, all on a Quality dashboard refreshed daily.
• Aging discipline — open deviations age into red after the class-specific deadline; aged deviations escalate to Quality Council; chronic agers trigger a CAPA on the deviation process itself.
• Effectiveness check on critical deviations — 3-6-12 month look-back to confirm the corrective action held.

Section 211.192 ties deviation closure to batch release: 'A written record of the investigation shall be made and shall include the conclusions and follow-up.' The Quality Unit cannot release a batch with an open critical deviation. Major deviations must be investigated and dispositioned before release; the CAPA can extend past release if the immediate batch-impact decision is documented. Minor deviations may be closed inside the batch-record review with a brief justification.

In EU release, the Qualified Person (QP) under Directive 2001/83/EC Article 51 personally certifies each batch. A QP will not sign on a batch with an unresolved critical deviation; the QP's certification record is itself a regulated record reviewed by inspectors.

Operationally this means the BMR review and the deviation investigation must converge before release. A mature shop closes minor deviations during BMR review (same day as the run completes), majors within the next few days, and only escalates criticals to a longer investigation timeline — with the batch held pending closure.

V5's deviation module is wired into kiosk, BMR / DHR, QMS and management review so the programme cannot operate as a separate parallel system.

• Kiosk-side opening — one-tap deviation form with photo / sketch / voice-note attachment; auto-classification picker; the operator continues work after opening, supervisor confirmation follows.
• Auto-opening on tolerance breach — dispense, in-process check, yield, time-limit, cleaning verification, environmental excursion.
• Linked to the originating record — WO, BMR step, equipment ID, operator, lot, material, SOP version at execution time.
• Triage workflow — supervisor verifies classification within configurable SLA; mis-classification flagged on Quality dashboard.
• Investigation form — guided root-cause (5-why or fishbone), structured extension query, impact assessment, disposition decision with QA e-signature.
• CAPA escalation when criteria met — repeat count, criticality, root-cause category trigger an automatic CAPA proposal.
• Aging and escalation — colour-coded aging, management-review report, Quality Council queue.
• Effectiveness check on critical deviations — scheduled 3, 6, 12 months after closure with mandatory evidence and signature.
• BMR / DHR review at release flags every deviation on the batch with status; QA cannot release with any open critical.
• Audit trail on every deviation field per 21 CFR 11.10(e) and Annex 11 §9.