Study guide

17.3 Common Cause vs Special Cause Variation

ASQ Certified Quality Auditor CQA

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 Current Exam Facts 0.2 Eligibility, Fees & Recertification 0.3 Case Studies & Study Strategy

2 Chapter 1: Types of Quality Audits

1.1 Product, Process, System, Hybrid & Remote Audits 1.2 First-, Second- & Third-Party Context 1.3 CAPA Verification, Risk-Based, Surveillance & For-Cause 1.4 Common Elements with Sustainability, EHS & Financial Audits

3 Chapter 2: Purpose, Scope & Audit Criteria

2.1 Elements of Purpose and Scope 2.2 Benefits of Audits (Effectiveness, Risk, Cyber) 2.3 Criteria: Standards, Contracts, Specs & QMS

4 Chapter 3: Roles, Ethics & Audit Credibility

3.1 Roles: Lead Auditor, Team, Client, Auditee, Observer 3.2 ASQ Code of Ethics, Due Care & Confidentiality 3.3 Legal Consequences of Improper Auditor Actions 3.4 Independence, Objectivity & Qualifications

5 Chapter 4: Audit Planning Fundamentals

4.1 Elements of the Audit Planning Process 4.2 Auditor Selection Criteria 4.3 Pre-Audit Documentation & Gap Assessments 4.4 Logistics: Safety, Escorts, Access & PPE

6 Chapter 5: Auditing Tools, Strategies & the Audit Plan

5.1 Sampling Plans, Checklists & Working Papers 5.2 Forward/Backward Tracing, Discovery & Observation 5.3 Creating and Distributing the Audit Plan

7 Chapter 6: Audit Performance Management

6.1 On-Site Management for the Auditor 6.2 On-Site Management for the Auditee 6.3 Opening Meeting

8 Chapter 7: Evidence Collection & Closing Meetings

7.1 Audit Data Collection and Analysis 7.2 Characteristics of Objective Evidence 7.3 Organizing Evidence by Risk and Significance 7.4 Exit and Closing Meetings

9 Chapter 8: Audit Reporting

8.1 Report Development and Content 8.2 Effective Reports: Summary, Findings & OFIs 8.3 Approvals, Distribution & Audit File Retention

10 Chapter 9: CAPA Follow-Up & Audit Closure

9.1 CAPA Process Elements & Root Cause 9.2 Reviewing and Negotiating CAPA Plans 9.3 Verifying CAPA Effectiveness 9.4 Ineffective CAPA Escalation & Audit Closure

11 Chapter 10: Auditor Characteristics, Resources & Conflict

10.1 Auditor and Lead Auditor Characteristics 10.2 On-Site Audit Resource Management 10.3 Conflict Resolution Techniques

12 Chapter 11: Communication, Interviewing & Team Dynamics

11.1 Communication and Presentation Techniques 11.2 Interviewing Techniques 11.3 Team Building, Facilitation & Development Stages

13 Chapter 12: Audit Program Management Core

12.1 Senior Management Support for the Audit Function 12.2 Staffing and Resource Management 12.3 Auditor Training and Development 12.4 Audit Program Evaluation Metrics

14 Chapter 13: Internal & External Audit Programs

13.1 Internal Audit Program Management 13.2 External / Supplier Audit Program Management 13.3 Standardizing Best Practices from Audit Results

15 Chapter 14: Risk, Management Review & Electronic Systems

14.1 Organizational Risk Management & Continuity 14.2 Management Review Input from the Audit Program 14.3 Electronic Records, Data Integrity & Cybersecurity

16 Chapter 15: Business & Financial Impact of Auditing

15.1 Auditing as a Management Tool 15.2 Interrelationships of Business Processes 15.3 Cost of Quality Principles

17 Chapter 16: Quality Tools & Process Improvement

16.1 Seven Basic Tools, Root Cause & PDCA 16.2 Six Sigma DMAIC for Auditors 16.3 Lean Principles and Tools

18 Chapter 17: Statistics & Process Variation

17.1 Mean, Median & Mode 17.2 Dispersion & Qualitative vs Quantitative Analysis 17.3 Common Cause vs Special Cause Variation 17.4 Process Capability Metrics & Outliers

19 Chapter 18: Sampling, Change Control, V&V & Risk Tools

18.1 Acceptance Sampling & Sampling Types (incl. MSA) 18.2 Consumer Risk, Producer Risk & Confidence 18.3 Change Control, Configuration Management, V&V 18.4 FMEA, HACCP, CTQ & SWOT

17.3 Common Cause vs Special Cause Variation

Key Takeaways Explain This Topic AI

Common cause variation is the stable, inherent variation of a process under its current design; improving it requires system change, not one-off blame.

Special cause variation is assignable, intermittent, or unexpected; it should be investigated, contained, and removed so the process returns to (or establishes) a stable state.

Control charts and pattern rules help distinguish the two; points beyond limits or non-random patterns often signal special causes.

Audit CAPA that treats common-cause problems as special causes produces endless firefighting; treating special causes as “that’s just the process” leaves hazards unaddressed.

Auditors evaluate whether management reacts correctly: special-cause reaction for assignable events, and fundamental process improvement for common-cause performance gaps.

Last updated: August 2026

17.3 Common Cause vs Special Cause Variation

Quick Answer: Common cause variation is the natural, stable variation built into the current process system. Special cause variation is unusual, assignable, and often intermittent. Auditors (BoK V.D.1 Apply ) judge which type is present and whether the organization responds with system improvement (common) or investigation/CAPA for assignable causes (special). Practice at /practice/cqa .

Why this distinction is an audit skill

W. Edwards Deming and Walter Shewhart framed process improvement around a simple truth: how you react to variation determines whether quality improves or chaos grows. If managers treat every defect as a special event, they rewrite procedures daily, punish people for system noise, and never redesign the process. If they ignore true special causes, equipment failures, wrong materials, and unauthorized changes fester.

Quality auditors evaluate whether the QMS reaction matches the variation type . That evaluation shows up in findings about CAPA effectiveness, management review, SPC use, and process control.

  • Definitions
  • Common cause variation
  • Present always when the process runs as currently designed

Produced by many small, ordinary factors (materials lot-to-lot noise, ambient conditions within normal range, method tolerance, typical operator differences under standard work)

Forms a stable, predictable distribution over time (in control)

Reduced only by changing the system (equipment capability, method redesign, better materials, poka-yoke, automation, etc.)

Calling common-cause output “operator error” without evidence of deviation from standard work is a classic management mistake—and an audit observation when it drives ineffective CAPA.

  • Special cause variation
  • Arises from specific, identifiable circumstances not part of the stable system
  • Often intermittent , sudden, or linked to a change event

Examples: broken tool, wrong batch of raw material, unapproved process change, power surge, new untrained temporary worker working outside procedure, software release bug

Requires detection, containment, root-cause removal , and verification that the assignable cause will not recur

Special causes can make the process unstable (out of statistical control). Stability must often be restored before capability metrics are trusted (next section).

Comparison table

  • Dimension Common cause Special cause
  • Nature Inherent to current system Assignable / exceptional
  • Predictability Stable pattern over time Unpredictable until cause is known

Typical signal In-control chart; random scatter within limits Point(s) beyond limits; runs, trends, cycles, mixtures

  • Management reaction Improve the system / process redesign Investigate, contain, eliminate cause
  • CAPA focus Systemic controls, design, standards Event-specific root cause + recurrence prevention

Wrong reaction Firefight each point; blame individuals for system noise Ignore spike as “normal variation”; no investigation

Detecting special causes (practical signals)

Control charts are the classic tool, but auditors also use domain knowledge:

Statistical pattern signals (examples used in many SPC systems):

  • Point beyond control limits
  • Run of points on one side of the centerline
  • Trend of steadily increasing or decreasing points
  • Cyclic patterns suggesting shift/tooling/setup rhythm
  • Sudden shift in level after a change point

Process/knowledge signals:

  • Documented change (material, method, machine, measurement, environment, people)
  • Maintenance event, scrap of a specific cavity, single supplier lot
  • Correlation with a known incident log entry

Auditors should not invent Shewhart rules not used by the organization—but they should verify that the organization has a rational method to separate noise from signals and acts accordingly.

Worked mini-scenario — classification

Scenario A: Fill weight X-bar chart in control for 30 subgroups; Cpk is 0.85 because the process is centered but somewhat wide vs. specs. Defects occur at a steady low rate.

→ Variation dominating the defect rate is largely common cause . Fix: reduce variation or center better via system improvement (tooling, method, specs review)—not 30 separate CAPAs for each defective unit.

Scenario B: Same process in control for months; then three consecutive points above UCL after a new resin lot arrives; bulk density is out of COA.

→ Special cause (material). Fix: quarantine resin, contain product, correct supplier/receiving controls, verify return to stability.

Scenario C: Night shift mean is always higher than day shift for months, both “in control” when charted separately , but the combined chart looks unstable.

→ Likely two systems (stratification issue). Treat as systemic difference between shifts—training, setup, or equipment—not one-off “special” points every night.

CAPA implications (audit lens)

Situation Effective response Ineffective response

Special cause event Containment, root cause of the assignable factor, preventive controls for recurrence “Retrain everyone” with no link to the actual cause

Common cause poor capability Process improvement project, redesign, resource for variation reduction Writing a CAPA for every scrap unit as if each were unique

Unstable process Restore control first; then reassess capability Publishing Cpk on out-of-control data as if it were a stable capability

Mixed streams Stratify and improve each system One plant-wide average hiding both problems

Auditor questions that reveal maturity:

How do you know this signal is special vs. common?

What data (chart, log, change record) support that classification?

Does the CAPA match the classification?

After action, did the process stabilize and did the metric improve for the right reason?

Tampering and over-adjustment

A related concept (Deming): tampering —adjusting a stable process in reaction to common-cause noise— increases variation. Example: operators tweak a knobs every time a single unit is slightly high or low without evidence of special cause. Auditors who see constant micro-adjustments, “tribal” compensations, or undocumented tweaks should connect that behavior to increased dispersion and weak process control—often a system finding, not a single bad actor.

  • Audit evidence sources
  • Control charts and reaction plans
  • Nonconformance and CAPA databases (repeat causes vs. unique events)
  • Change control and maintenance logs aligned to signal dates
  • Management review actions (system projects vs. only firefighting KPIs)

Interviews: Do supervisors distinguish “this is our normal noise” from “this is different”?

  • Exam anchors (Apply)
  • Differentiate common vs. special with scenario data—not slogans
  • Map reaction type to CAPA vs. system improvement
  • Reject capability claims on unstable processes when the scenario shows special causes unaddressed
  • Recognize stratification and mixed streams as system issues
  • Avoid automatic blame of people for common-cause outcomes
  • Link to the rest of Domain V

Common/special thinking feeds process capability (valid only on stable processes) and outlier handling (is an extreme point a special cause or a heavy tail of common cause?). It also connects to CAPA chapters: root cause quality depends on correct variation diagnosis. Continue with capability metrics next, and drill questions at /practice/cqa .