Client case · Deviations
On this pharmaceutical site, close to 30% of deviations were attributed to a documentation or training cause. The internal reading was the one you hear everywhere: a problem of rigour in the teams. It was a problem of document design. The rate came down to 3%.
30% → 3%
Share of deviations whose retained cause was documentation or training, before and after the programme. Total deviation volume fell without a single control being added.
The interesting fact is not the drop, it is what the drop reveals: when a third of your deviations point at your own documents, your documents are the least controlled process on the site. No awareness campaign fixes that, because the cause is not in the execution.
The belief that costs you
"Those deviations are irreducible. It's the human factor."
That is the conclusion mechanically produced by an investigation that stops at the workstation. The three causes actually identified on this site were all documentary: procedures that contradicted each other, obsolete versions still circulating at the workstation, and training validated on texts that had since changed. None of them was about operator behaviour. All of them were measurable from a document management export.
What was done
A full export of the document management system, analysed: documents in force, overdue for review, never consulted, duplicates, contradictions detected by content comparison. Two days of work, and a map that points out the areas to address by itself. No rewriting started before this step.
Merging redundant documents, separating the stable principle from the variable parameter, removing with justification what no longer served any requirement. Every withdrawal went through change control with its rationale — a non-negotiable condition for the operation to be defensible.
The point that produced most of the gain. As long as the procedure lives in the document system and training lives in another tool, the two drift apart. Connecting them means a change propagates at once to the material and to the qualification — and the "trained on an obsolete version" deviation disappears structurally.
Our conviction
This site had responded to every deviation by adding a clarification, a reminder, a verification. Ten years of that policy produced a document set nobody could keep coherent — and it was that incoherence which generated a third of the following deviations. The loop opened the day the standard answer to a deviation stopped being "add something" and became "understand why the document did not hold".
What it changed
Workload
Fewer deviations opened means mechanically fewer investigations, fewer CAPAs and less review. The quality team got time back for the deviations that deserved it.
Onboarding
With the volume to absorb for qualification shrinking, the time before a new joiner became autonomous followed. It is the most visible benefit for production.
Reporting
An unexpected effect: operators reported more weak signals, once it became clear that the conclusion would not automatically land back on them.
So the figure to remember is not 3%. It is the share of your deviations that points today at your own documents — data you already hold, and that almost nobody calculates.
Frequently asked
You already hold the data. Two days is enough to read it, and to know whether the seam exists on your site.
