Quality · Quality system

Deviations

A deviation is any departure from an approved instruction, specification or established standard — recorded, assessed for product impact, and investigated to a depth proportionate to its risk.

In one line

A deviation is any departure from an approved instruction, specification or established standard — recorded, assessed for product impact, and investigated to a depth proportionate to its risk.

Plain-English explanation, then the primary regulation it comes from.

Explanation

Understanding deviations

The scope question comes first, and sites get it wrong in both directions. Too narrow, and events that should be visible never enter the system, so trending is built on an incomplete picture. Too broad, and the system floods with trivia, investigation quality collapses, and the events that matter are buried. Clear criteria plus risk tiering is the only workable answer.

Every deviation needs an impact assessment on the batch, and on other batches that shared the same equipment, material, personnel or period. The second half is the one that gets skipped. A contamination event assessed only against the batch in front of you leaves the question an inspector will certainly ask — what else was affected — unanswered.

Investigation depth should track risk, but the standard for root cause does not move: 'human error' is a description, not a cause. Where a person made a mistake, the useful questions are why the process permitted it, whether the instruction was ambiguous, whether the layout invited it, and whether workload made it likely.

Investigation cycle time is one of the metrics inspectors read as a proxy for whether the quality system is under control. A queue of open investigations says the site cannot close what it opens, and each unclosed investigation raises the probability of a recurrence that will cost the same effort again.

What it requiresThe substance of the requirement, stated plainly.
Planned vs unplanned
A planned deviation is approved before the event and justified in advance; an unplanned one is discovered and assessed after.
Raised promptly
Ideally within one working day of detection, by operators as well as QA.
Impact beyond the batch
Assess other batches sharing equipment, materials, personnel or time window.
Root cause, confirmed
Established by evidence rather than assumed; 'human error' is where the analysis starts, not where it stops.
Trended
Recurrence is acted on before an inspector spots the pattern in your own records.
Where it goes wrongThe part a definition alone will not tell you.

Common failure modes

  • Criteria so broad the system floods, so investigation quality falls across every event including the serious ones.
  • Impact assessment limited to the batch in hand.
  • Investigations closed against a deadline rather than against a conclusion.
  • Trending performed but never reviewed, so the pattern exists in your data and only the inspector reads it.
Primary sourcesAlways verify against the primary source before acting; guidance is revised.

Where this is written down

One GMP problem. Multiple perspectives.

Deviations seen from four accountabilities

Deviation handling is the most-read part of a quality system, because it shows an inspector how the site behaves when something goes wrong.

Quality

Impact beyond the batch in front of you

Did we find the real cause, and what else is affected?

Every deviation needs an impact assessment covering other batches that shared equipment, materials, personnel or time window. That second half is the part most often skipped, and it is precisely the question an inspector will ask.

Set scope criteria and risk tiering deliberately. Too narrow and trending is built on an incomplete picture; too broad and investigation quality collapses across everything.

GMP for Quality
CEO

It is read as evidence of control

What does our deviation record say about us?

Investigation cycle time is one of the metrics inspectors use as a proxy for whether the quality system is under control. A queue of open investigations says the site cannot close what it opens — a conclusion drawn from your own records, not from an inspector's opinion.

Ask for ageing and recurrence, and for how often 'human error' appears as the concluded cause. Both are visible internally long before an inspection.

GMP for CEO
CFO

Loaded hours, multiplied by recurrence

What does each investigation actually cost?

An investigation consumes QA and technical hours at loaded rates, and a recurring event consumes them again. Where a batch is held pending the outcome, working capital sits idle for the duration at a financing cost that is rarely attributed to quality.

Model deviation volume, investigation hours and repeat rate together. The recurrence premium is usually the line that changes the conversation.

GMP for CFO
COO

Open deviations gate release

How is this affecting throughput?

Batches routinely wait on open deviations rather than on analysis, which makes investigation closure a throughput constraint as much as a compliance one. Recurring event types consume the same production and engineering capacity repeatedly.

Map where batches actually wait in the release path. Shortening the investigation route often releases more capacity than adding testing resource.

GMP for COO
Related

Read next

Looking for a definition rather than an explanation? The GMP glossary covers the abbreviations in one line each.

Applying this to your site

Knowing the requirement is not the same as closing the gap

If you want to know where your site actually stands against this, the readiness score covers seven quality-system domains in twenty questions, and takes about ten minutes.