Definition · Plain-language
Root cause analysis (RCA)
Root cause analysis (RCA) is a structured problem-solving approach used to identify the underlying cause of a problem or deviation, rather than merely treating its symptoms.
The step most authors miss
Doing CRediT right? Don’t stop at the statement.
A CRediT statement credits you inside one paper. The recognition CRediT was built for happens when those roles are tied to you, persistently. Sign in with your ORCID — free — and claim your CRediT contributions on casrai.org, the home of the standard. They become a verified, portable part of your identity, not a line that disappears into one PDF.
Free: claim your contributions, then export a journal-ready CRediT statement, schema.org structured data, JATS XML, CSV or BibTeX — and preview your public profile. A membership publishes that profile publicly and verifies the journals you serve.
Symptom versus root cause
The central idea of RCA is the distinction between a symptom and a root cause. A symptom is the visible problem — a failed test, a mislabelled batch, a missed deadline. The root cause is the underlying reason the symptom occurred, which may be several steps removed. Treating only the symptom (for example, retesting and releasing) leaves the underlying cause in place, so the problem returns. RCA forces an investigation to keep asking why until it reaches a cause that, if corrected, prevents recurrence.
Common RCA techniques
Several structured methods support RCA. The 5 Whys asks “why?” repeatedly, peeling back layers of cause until a fundamental factor is reached. The Fishbone or Ishikawa diagram organises possible causes into categories — often people, process, equipment, materials, environment and measurement — to ensure breadth. Fault-tree analysis works top-down from a defined failure, mapping the logical combinations of events that could produce it. The right technique depends on the problem’s complexity; complex events often warrant more than one.
RCA as the foundation of CAPA
RCA does not stand alone — it is the investigative engine of the CAPA system. Identifying the true root cause is what allows a corrective action to remove the existing cause and a preventive action to stop the same cause arising elsewhere. If RCA is rushed or superficial — for example, blaming “human error” without asking why the error was possible — the resulting CAPA will be weak and the problem is likely to recur. Regulators frequently scrutinise the depth and logic of root-cause investigations.
Key facts
At a glance
- Definition: structured methods to find the underlying cause of a problem or deviation
- Core distinction: symptom (visible problem) versus root cause (underlying reason)
- Common techniques: 5 Whys, Fishbone/Ishikawa diagram, fault-tree analysis
- Relationship to CAPA: RCA is the investigation that drives effective CAPA
- Common pitfall: stopping at “human error” without asking why it was possible
- Goal: enable actions that prevent recurrence, not just fix symptoms
Common misconceptions
What people often get wrong
Often heard: A deviation usually has one single root cause.
Actually: Many problems have multiple contributing causes interacting together. Techniques such as the Fishbone diagram exist precisely to explore several causal categories; forcing a single cause can miss the true drivers of recurrence.
Often heard: “Human error” is a valid root cause to close an investigation on.
Actually: Human error is usually a symptom, not a root cause. Robust RCA asks why the error was possible — unclear SOPs, poor training, badly designed equipment — and addresses those system factors instead of blaming the individual.
Often heard: RCA and CAPA are the same thing.
Actually: RCA is the investigative step that identifies why a problem occurred; CAPA is the system of actions taken in response. RCA feeds CAPA — without sound root-cause analysis, corrective and preventive actions tend to address symptoms.
Going deeper
