Root Cause Analysis in Cannabis and GMP: 11 Mistakes to Avoid

If you run a GMP or GPP facility, problems are part of the job. Deviations, complaints, and out-of-specification results will happen. What separates a strong quality system from a weak one is not the absence of problems. It is what you do next. Too many teams spend their energy fixing the visible symptom and never reach the real cause, so the same problem returns, often at a worse moment.

Root cause analysis (RCA) is the discipline of finding the true reason a problem occurred so you can stop it from happening again. Done well, RCA protects your product, your licence, and your customers. Done poorly, it wastes time, drains resources, and leaves you exposed at your next Health Canada inspection. This guide explains how RCA works in cannabis and pharmaceutical quality systems, the tools that make it effective, and the eleven mistakes that quietly undermine investigations.

Executive Summary

Root cause analysis is a structured method for identifying the underlying cause of a problem rather than its surface symptom. In regulated cannabis and pharmaceutical facilities, every deviation, complaint, and out-of-specification result should trigger an investigation, and the quality assurance person (QAP) must investigate every complaint about product quality. A sound RCA feeds directly into corrective and preventive action (CAPA), which is how you prove to a regulator that a problem has been resolved for good.

The most common reason investigations fail is human, not technical. Rushing, bias, premature closure, and groupthink all push teams toward a convenient answer instead of the correct one. The eleven mistakes below show where RCA goes wrong, and the practical fixes that keep your investigations defensible. Strong RCA and CAPA are also your best defence against product recalls and repeat inspection findings.

What Is Root Cause Analysis?

What it is. Root cause analysis is a systematic process for finding the fundamental cause of a problem, the factor that, if corrected, prevents the problem from recurring. A problem usually has several layers. The visible issue is a symptom. Behind it sit one or more higher-level causes, and behind those sits the root cause. RCA works backward through that chain until it reaches the cause you can act on.

Why it matters. In a regulated facility, every incident or deviation must lead to corrective and preventive action. Regulators may request CAPAs during routine inspections or after exceptional events such as recalls. You cannot build an effective CAPA without first understanding the true cause, so RCA is the foundation of the entire investigation and CAPA cycle.

What you should do. Treat RCA as a defined, documented procedure, not an informal chat after an incident. Use the right tool for the problem, involve the right people, follow the evidence, and record your reasoning so the conclusion holds up under regulatory scrutiny.

Why RCA Matters for Cannabis and GMP Compliance

What it is. RCA is the engine of your CAPA program, and CAPA is one of the first things an inspector examines. Under Part 5 Good Production Practices of the Cannabis Regulations, licence holders must investigate complaints and deviations and take action to prevent recurrence. The QAP carries personal responsibility for the quality of the product and for investigating every quality complaint.

Following the 2025 cannabis regulatory amendments, Health Canada streamlined some requirements. Submission of a formal CAPA plan is now focused on major or critical inspection observations rather than every minor finding, but the expectation that you investigate and prevent recurrence has not changed. Weak root cause analysis is still one of the fastest ways to turn a minor observation into a repeat finding, and repeat findings escalate inspection ratings.

Common Root Cause Analysis Tools

No single tool fits every problem. Choosing the wrong technique is itself a common cause of failed investigations. The table below summarizes widely used RCA tools and when each works best.

RCA tool	Best used for	Strength
5 Whys	Simple, single-cause problems	Fast and easy to apply, asks why repeatedly until the cause is reached
Fishbone (Ishikawa) diagram	Brainstorming many possible causes	Groups causes by category such as people, process, equipment, materials, environment, and measurement
Failure Mode and Effects Analysis (FMEA)	Proactive risk assessment	Ranks failure modes by severity, occurrence, and detection so you act on the highest risks first
Pareto analysis	Prioritizing among many causes	Highlights the vital few causes that drive most of the problem
Fault tree analysis	Complex failures with multiple contributing factors	Top-down logic that maps how events combine to cause a failure
8D and CAPA	Team-based, regulated investigations	Structured, documented problem solving that links cause to corrective and preventive action

For most cannabis quality events, a Fishbone diagram to brainstorm causes followed by 5 Whys to drill into the most likely branch is a practical, defensible starting point. Reserve FMEA and fault tree analysis for higher-risk or more complex problems.

11 Common Mistakes That Cause Root Cause Analysis to Fail

RCA is a crucial step in problem solving, but errors in how it is run can make the whole investigation unproductive. These eleven mistakes appear again and again in real cannabis and GMP investigations.

1. Inadequate Planning

Lack of preparation is one of the most common reasons investigations fail. Rushing into analysis without first defining the problem leads to a shallow result and an incomplete understanding of what went wrong. The fix: take time to scope the problem clearly, gather the facts, and define what a good outcome looks like before you start analyzing.

2. Using the Wrong RCA Tools

Not every tool suits every problem. Picking the wrong technique leads to long, frustrating investigations and weak conclusions. The fix: make sure the people running the RCA understand the available tools, and select the method that matches the complexity of the problem.

3. Making Hasty Decisions

It is human nature to want a quick answer. Jumping to conclusions about what caused an issue often produces a solution that does not address the real cause. The fix: gather all the facts before deciding, and resist the pressure to close early. A little extra time up front saves far more time later.

4. Allowing Bias to Drive the Investigation

Two biases are especially damaging. Confirmation bias leads the team to seek evidence that supports a preferred hypothesis and ignore evidence that contradicts it. Selective perception leads people to focus on some facts while dismissing others. The fix: stay aware of these biases, weigh all the evidence, and view the problem from several angles before concluding.

5. Closing the Investigation Too Soon

Premature closure means reaching a conclusion before exploring all possible causes. The result can be an incorrect fix or a missed opportunity to find additional contributing causes. The fix: investigate every plausible cause systematically before declaring the problem solved.

6. No Action Plan After the Analysis

It is easy to identify a cause and then move on without acting on it, which does nothing to prevent recurrence. The fix: turn every confirmed root cause into a clear, documented CAPA with owners and due dates, then verify the action actually worked.

7. Not Learning From Past Investigations

Failing to learn from previous failures means making the same mistakes over and over. The fix: after each RCA, review what went well and what could improve, and feed those lessons into your procedures and training.

8. Letting Emotion Replace Evidence

Emotions can cloud judgement and push a team toward irrational decisions based on faulty logic, which leads to ineffective solutions or new problems. The fix: keep the analysis grounded in evidence and sound reasoning, not blame or assumption.

9. Forcing One Approach Onto Every Situation

RCA needs careful planning, and treating every problem the same way creates blind spots. Viewing a situation as a simple either or choice can hide real causes and solutions. The fix: stay flexible, consider the full range of possibilities, and adapt your method to the problem in front of you.

10. Groupthink

Groupthink occurs when a team makes decisions based on pressure to conform rather than sound reasoning, which can lead to poor decisions. The fix: make sure everyone can contribute, invite dissenting views, and remove pressure to agree with the loudest or most senior voice.

11. Dogma

Dogma is a fixed belief that refuses to change even when new evidence appears. Holding onto a conclusion despite contrary facts derails an investigation. The fix: stay open-minded, listen to every idea, and let the evidence, not prior conviction, decide the outcome.

Root Cause Analysis in Practice: A Worked Example

Consider a common scenario we see in cannabis facilities. A licensed producer receives several complaints that dried flower products are slightly over the labelled moisture target. The quick answer is operator error during packaging, and the easy fix is to retrain the operator. That is a symptom-level response, and the complaints return within weeks.

A proper RCA tells a different story. The team starts with a Fishbone diagram and brainstorms causes across people, equipment, process, materials, environment, and measurement. They then apply 5 Whys to the most likely branch. Why is moisture high? Because product is packaged before it reaches the target. Why? Because the in-process moisture check passes it. Why? Because the moisture analyzer reads low. Why? Because it was last calibrated outside its due date. Why? Because the calibration schedule was not linked to the equipment used on that line.

The root cause is a gap in the calibration management system, not the operator. The corrective action recalibrates and revalidates the analyzer, while the preventive action rebuilds the calibration schedule and adds an alert so no instrument is used past its calibration date. The team then verifies effectiveness by trending moisture results over the next several batches. This is the difference between a fix that lasts and one that simply resets the clock until the next complaint.

A Defensible RCA and CAPA Process

Use these steps as a backbone for every investigation, and keep records at each stage:

Define the problem. Describe what happened, where, when, and how it was detected, with objective data.
Contain the immediate risk. Take interim action to protect product and patients or consumers while you investigate.
Gather evidence. Collect records, samples, interviews, and data before the trail goes cold.
Select the right RCA tool. Match the method to the problem complexity, such as 5 Whys, Fishbone, or fault tree analysis.
Identify the root cause. Work through the cause-and-effect chain until you reach a cause you can act on.
Define corrective and preventive actions. Correct the specific issue and prevent recurrence across similar processes.
Assign owners and timelines. Make each action accountable and time bound.
Verify effectiveness. Confirm the action worked and the problem has not returned before closing the CAPA.
Document and share lessons. Record the investigation and feed improvements into SOPs and training.

Red Flags Inspectors Notice

Beyond the eleven analytical mistakes, these process-level red flags often appear in cannabis and GMP inspections:

Investigations closed without a verified root cause, relying on phrases like human error with no deeper analysis.
CAPAs with no effectiveness check, so there is no evidence the action actually worked.
Repeat deviations that show a previous corrective action failed to address the true cause.
No link between complaints, deviations, and trends, so systemic problems are never seen.
Overdue or open CAPAs with no escalation, suggesting the system is not actively managed.

Frequently Asked Questions

What is the difference between root cause analysis and CAPA?

Root cause analysis identifies why a problem happened. CAPA is what you do about it: corrective action fixes the specific problem, and preventive action stops it recurring elsewhere. RCA comes first and feeds the CAPA. A CAPA built without a sound RCA usually treats the symptom and the problem returns.

Is root cause analysis required in cannabis facilities?

Yes, in effect. Under Part 5 Good Production Practices of the Cannabis Regulations, licence holders must investigate complaints and deviations and take action to prevent recurrence, and the QAP must investigate every quality complaint. While the regulations do not mandate a specific RCA tool, a documented, evidence-based investigation is expected and is examined during inspections.

Which root cause analysis tool should I use?

Match the tool to the problem. The 5 Whys works well for simple, single-cause issues. A Fishbone diagram helps brainstorm many possible causes. FMEA is best for proactive risk ranking, and fault tree analysis suits complex failures with multiple contributing factors. Many cannabis teams combine a Fishbone diagram with 5 Whys.

How do I know if I found the real root cause?

A good test is whether removing the identified cause would actually prevent the problem from recurring, and whether the cause-and-effect logic holds when you read it back from cause to effect. If your conclusion is a symptom or a person rather than a system or process gap, keep investigating.

How does weak RCA lead to recalls?

Many recalls are repeat events. A first signal, such as a deviation or complaint, is investigated weakly, the true cause is missed, and the problem returns at larger scale until product reaches consumers. Strong RCA and CAPA catch the cause early, which is why they are central to recall prevention. See our guide to avoiding cannabis product recalls.

Who should lead a root cause analysis?

RCA should be led by someone trained in investigation methods, with input from the people closest to the process and oversight from the QAP. A cross-functional team reduces bias and groupthink, and the QAP ensures the investigation and resulting CAPA meet regulatory expectations.

How MFLRC Can Help

MF License and Regulatory Consultants (MFLRC) helps Canadian cannabis and pharmaceutical operators turn investigations into lasting fixes. With more than 20 years of quality and regulatory experience, we strengthen the RCA and CAPA systems that inspectors examine most closely.

We support clients with quality assurance and quality control services, SOP development, gap assessments, and QAP services, and we design RCA and CAPA programs that hold up under scrutiny. Our audit services include internal audits, mock recalls, and inspection readiness reviews, while our regulatory affairs team supports complaint handling, recall reporting, and ongoing compliance.

We also train teams to run defensible investigations, helping you avoid the eleven mistakes above. Read more in our guides to internal audits and cannabis compliance essentials.

Need help building a root cause analysis and CAPA program that stands up to inspection? Contact MFLRC for expert guidance tailored to your business.

Book a Consultation

Conclusion

Root cause analysis is essential to any regulated facility because it lets you find the factors behind a problem and take corrective and preventive action that lasts. The eleven mistakes covered here are common, but each is avoidable with planning, the right tools, honest evidence, and an open mind. Get RCA right and you do more than close an investigation. You prevent the next deviation, the next complaint, and potentially the next recall.

If you want help building investigations that inspectors trust and that genuinely prevent recurrence, MFLRC is ready to support your team.