deviation

Core meaning

In regulated industrial and manufacturing environments, **deviation** commonly refers to a documented and controlled departure from an approved requirement, procedure, or specification.

It is typically used when an operation, batch, material, piece of equipment, or data point does not follow what has been formally defined in:

– standard operating procedures (SOPs)
– validated or approved process instructions
– specifications, limits, or recipes
– regulatory or internal quality requirements

A deviation is not just the nonconformity itself; it also encompasses the formal record that describes the event, its impact, and how it is handled.

How deviations are used in operations and quality systems

In day-to-day manufacturing, deviations are usually managed through structured quality or compliance workflows. These may be implemented in a QMS, MES, ERP, or a combination of systems. Typical elements of a deviation record include:

– **Description of the departure**: what was supposed to happen versus what actually happened.
– **Classification**: such as critical, major, or minor, based on potential impact.
– **Impact assessment**: evaluation of possible effects on product quality, patient or user safety, compliance, or supply.
– **Root cause analysis**: investigation into why the deviation occurred (when required by procedure).
– **Disposition and decisions**: decisions about use, rework, quarantine, or rejection of affected material or batches.
– **Corrective and preventive actions (CAPA linkage)**: when appropriate, deviations may link to or trigger CAPA records.
– **Approvals and documentation**: dated sign-offs by authorized roles, including quality and operations.

Deviations are a key input to continuous improvement, risk management, and regulatory inspections, because they provide evidence of how the organization identifies and handles departures from its own defined controls.

Authorized versus unauthorized deviations

Many sites distinguish between:

– **Authorized deviations**: A planned or consciously accepted departure that is formally assessed and approved before or during execution (for example, using alternate equipment, temporarily relaxing a sampling frequency, or bypassing a system step under controlled conditions).
– **Unauthorized deviations**: An unplanned or unintended departure that is discovered after it occurs (for example, a missed step, incorrect parameter, or unexpected equipment behavior). These typically require investigation and may lead to corrective actions.

In both cases, the term “deviation” refers to the recorded event and its management within the quality system.

Boundaries and exclusions

In this site context, **deviation** usually refers to:

– departures from **documented, approved** procedures and requirements
– events managed under **formal quality, compliance, or change-control frameworks**

It usually does **not** refer to:

– informal day-to-day variation within defined tolerances (e.g., normal process variability within control limits)
– continuous numeric differences without quality or compliance significance (e.g., statistical deviation alone)

When the intent is purely statistical, terms like *standard deviation* or *variance* are typically used instead.

Common confusion and related terms

Deviations are often discussed alongside other quality and compliance terms:

– **Nonconformance / nonconformity**: Often used for product- or material-level failures to meet specifications. In some organizations, nonconformance records handle product disposition, while deviation records handle process or procedural departures. In others, the terms overlap or are used interchangeably.
– **Incident**: A broader term that may include safety, environmental, IT/OT, or security events. A deviation is usually specific to process or quality requirements.
– **Change control / change request**: A planned, prospective change to a procedure, specification, or system. Deviations generally document departures from the current approved state, not the process of defining a new approved state.
– **CAPA (corrective and preventive action)**: Actions taken to address root causes of deviations or nonconformances. A deviation may lead to a CAPA, but the two records serve different roles.

Usage and boundaries between these terms can vary by company and industry, so local procedures and quality system definitions are typically authoritative.

Application in MES and shop-floor systems (site context)

In manufacturing execution system (MES) and related OT/IT integrations, **deviation** typically refers to exceptions to the normal, validated electronic workflow, captured and processed under defined rules. Examples include:

– recording when an operator cannot follow the exact MES step and uses an alternate path approved by quality
– documenting temporary bypasses of MES checks (for example, due to equipment malfunction or connectivity issues) with full traceability to batch, operator, and equipment
– linking deviation records in MES or an integrated QMS to specific electronic batch records, work orders, or equipment logs

In this context, deviations are often routed through pre-defined electronic workflows that enforce:

– standardized deviation types and categories
– required impact assessments and justifications
– electronic approvals by responsible functions (e.g., production and quality)
– traceability across MES, QMS, and ERP where applicable

Where hybrid electronic–paper processes exist, deviations also capture when and how MES was legitimately bypassed, and how that bypass is reconciled and reviewed within the quality system.