Taktly
All articles
Quality|5 min read

Why 'operator error' is not a root cause (and exactly how to push one level deeper)

The single most-cited CAPA finding in FDA Warning Letters is the same sentence, written different ways: 'the investigation concluded with operator error as the root cause without identifying the system condition that allowed the error to occur.' If your last CAPA ended on a person, you wrote the document the auditor is paid to reject.

Why FDA doesn't accept it

An operator-error root cause has no system change attached. The same operator on the same SOP under the same supervision will produce the same outcome the next time the setup repeats. The CAPA, by design, cannot prevent recurrence. Under 21 CFR 820.100(a)(3), CAPAs must 'identify the action(s) needed to correct and prevent recurrence of nonconforming product and other quality problems.' Operator-error-as-cause produces an action ('retraining') that addresses neither the correction nor the prevention. FDA inspectors flag this every quarter — Aspen, Sun, Lupin, Cipla, Macleods have all been cited in the last 24 months.

The question to ask yourself

When your 5-Why chain wants to stop on a person, ask this question one more time:

Worked example

The hierarchy of controls — pair training with a system change

Training is the weakest control in the hierarchy. It's at the bottom. Above it: administrative controls (SOPs, work instructions), engineering controls (lockouts, alarms, mistake-proofing), substitution (different material / process), and elimination (remove the step entirely). If your CAPA's only action is 'retrain operators,' you've picked the weakest control on the chart. Pair every training response with a higher-tier change — otherwise the same deviation will be back in 90 days under a different operator.

How Taktly catches it

Taktly's audit runs a deterministic detector for operator-error and training-only patterns. It refuses to soften them — even if the LLM scoring layer wants to. Every match surfaces the paraphrased FDA Warning Letter example most closely related, so you can see exactly what the inspector will write if you ship the document unchanged.

Related guides