Nonconformance, Root-Cause Analysis and CAPAIntroduction and ContextSupplier quality management is not limited to inspecting incoming material. Its central purpose is to ensure that purchased products, processes and services consistently satisfy specified requirements and support the organization’s operational, regulatory and customer obligations. When a supplier delivers a defective component, incomplete documentation, contaminated material or late product, the buying organization must respond systematically. A weak response merely removes the immediate defect; a mature response contains risk, determines why the failure occurred, prevents recurrence and verifies that the solution works. This chapter examines the connected disciplines of nonconformance control, containment, disposition, deviation management, structured problem solving, root-cause analysis, corrective and preventive action (CAPA), effectiveness verification and organizational learning. These activities are particularly important in regulated industries, complex supply networks and products in which a small supplier defect may create safety, reliability, legal or reputational consequences. A useful distinction is that correction addresses an observed problem, whereas corrective action addresses its cause. Rework may correct a defective batch; changing an inadequate process-control plan may be corrective action. Preventive action addresses potential causes of nonconformance before a failure occurs, although many modern management systems combine preventive thinking with risk-based planning and continual improvement. Learning ObjectivesBy the end of this chapter, the reader should be able to: - Distinguish nonconformance, defect, correction, corrective action, preventive action and deviation.
- Establish risk-based containment and disposition controls for defective supply.
- Apply the 8D method, 5 Whys, Ishikawa analysis and fault-tree analysis appropriately.
- Separate occurrence, escape and systemic causes.
- Design CAPA plans with measurable owners, deadlines and effectiveness criteria.
- Evaluate supplier responses critically rather than accepting superficial explanations.
- Govern concessions, deviations, records, escalation and communication ethically.
- Convert investigation findings into supplier-development and organizational learning.
1. Nonconformance in the Supplier RelationshipA requirement may originate from a drawing, purchase order, specification, contract, regulation, approved sample, process standard or customer expectation. A nonconformance is the failure to fulfil a specified requirement. A defect is a nonconformity that affects intended use or the ability to satisfy a requirement; organizations may define defect categories differently for critical, major and minor conditions. Nonconformances may be physical, functional, documentary, procedural or logistical. Examples include: - dimensional variation beyond drawing tolerance;
- incorrect material grade or traceability code;
- software or firmware version not approved;
- missing certificate of analysis;
- inadequate packaging causing transit damage;
- unauthorized process or material substitution;
- delivery of product after its permitted shelf life; and
- failure to follow a special process or inspection requirement.
The same observed condition can have different significance depending on use. A cosmetic mark on an internal bracket may be minor, while the same mark on a sealing surface may create a leak path. Consequently, classification should consider intended function, severity, probability, detectability, affected population and regulatory significance rather than appearance alone. Important distinctions| Term | Meaning | Typical response |
|---|
| Nonconformance | Failure to meet a requirement | Record, contain and evaluate | | Correction | Action to eliminate an identified nonconformance | Rework, repair, replacement or data correction | | Corrective action | Action to eliminate the cause of a nonconformance and prevent recurrence | Process, system or control change | | Preventive action | Action to eliminate the cause of a potential nonconformance | Risk reduction before failure | | Containment | Temporary action limiting use or spread of suspect material | Quarantine, screening, stop-ship | | Disposition | Formal decision about affected material | Use-as-is, rework, repair, return, scrap or concession | | Deviation | Authorized departure from an approved requirement or process | Time- or quantity-limited approval | | Escape | Failure of a control to detect or prevent a nonconformance before delivery or use | Detection-control investigation |
2. Immediate Control: Containment and TriageThe first duty is protection of the customer, user and downstream process. Investigation should not delay urgent containment. A typical initial response includes: - Identify the condition. Record part number, revision, lot, serial numbers, supplier, receipt date, quantity, requirement and evidence.
- Assess immediate risk. Determine whether the issue affects safety, regulatory compliance, critical function, cybersecurity, product availability or other customers.
- Control suspect material. Physically segregate stock, block inventory in the enterprise system, stop shipment or stop production when justified.
- Define the suspect population. Establish the last known good point and the first known bad point. Trace raw materials, work-in-process, finished goods and shipments.
- Protect downstream users. Notify relevant production, quality, engineering, service, logistics and customer representatives.
- Preserve evidence. Retain samples, photographs, test results, labels, process records, tooling and electronic data. Do not destroy evidence through uncontrolled sorting or rework.
- Begin a formal record. Assign an owner, due dates, risk classification and escalation route.
Containment may include 100% inspection, additional functional testing, supplier stop-ship, replacement stock, controlled rework or field notification. It is not a substitute for corrective action. A supplier that repeatedly screens defective parts may be reducing escape risk while leaving the generating process unchanged. Risk-based prioritizationA practical prioritization model combines severity, likelihood and detectability. A simple risk priority number is sometimes calculated as: RPN = S × O × D Here, S is severity, O is occurrence likelihood and D is detectability, each scored according to an organization-defined scale. The product has no universal unit and should not be interpreted as a probability. The method is useful for ranking within a consistent scoring system, but it can be misleading: a very severe failure may deserve immediate action even when its numerical score is lower than that of a frequent minor defect. Risk assessment must therefore include explicit escalation rules and professional judgment. A more direct expected-loss perspective is: E[L] = ∑ pi Ci where pi is the estimated probability of consequence scenario i, Ci is its consequence cost or impact, and the sum covers relevant scenarios. This approach requires credible estimates and should not reduce safety or legal decisions to monetary value alone. 3. Disposition and Deviation ManagementAfter containment, authorized personnel determine the status of affected material. Common dispositions are: - Use as-is: the material is accepted without modification because evidence shows that requirements and risk remain acceptable.
- Rework: processing returns material to full conformity using an approved method.
- Repair: a process makes the item usable, but the item may not fully meet the original requirement; repair therefore requires careful approval.
- Return to supplier: material is returned under controlled traceability.
- Scrap: material is destroyed or rendered unusable to prevent unintended use.
- Sort or screen: additional inspection separates conforming material from nonconforming material.
- Concession or deviation: an authorized party permits a specified departure for a defined quantity, period or application.
Disposition authority should be defined in advance. Engineering may need to assess functional implications; quality may control records and compliance; purchasing may manage commercial recovery; and the customer or regulator may require approval. No employee should silently convert a nonconformance into a deviation merely to protect delivery performance. A sound deviation record states the exact requirement, reason for departure, affected part and population, duration, risk evaluation, compensating controls, approval authorities, customer or regulatory authorization where required, and closure conditions. A deviation is not a permanent change to a specification. If the organization wants a permanent change, it must use formal change control. 4. Structured Problem Solving: The 8D MethodThe 8D method is a team-based framework for disciplined response. Organizations adapt terminology, but the logic commonly follows: | Discipline | Purpose | Typical evidence |
|---|
| D0: Prepare and emergency response | Confirm need, protect the customer and define urgency | Initial risk and containment | | D1: Establish the team | Bring together relevant technical and process expertise | Roles, authority and resources | | D2: Describe the problem | Define what, where, when, extent and significance | Is/is-not analysis, data and samples | | D3: Implement interim containment | Prevent further escape while investigating | Quarantine, screening, stop-ship | | D4: Identify root and escape causes | Explain occurrence and why controls failed | Verified causal analysis | | D5: Choose permanent corrective actions | Select actions that eliminate causes | Alternatives and risk evaluation | | D6: Implement and validate actions | Put actions into operation and confirm results | Trial data, revised controls | | D7: Prevent recurrence | Update systems, standards, training and similar processes | Horizontal deployment | | D8: Recognize the team and close | Confirm closure and capture learning | Approval and lessons learned |
D2 should be evidence-based. A vague statement such as “parts were out of specification” is insufficient. A stronger description specifies the characteristic, requirement, actual value, measurement method, affected lot, discovery point, time window and number of affected units. The “is/is not” technique compares where the problem occurs and does not occur, which can reveal a distinguishing condition. D4 should distinguish at least three causal layers: - Occurrence cause: why the defect was created, such as an incorrect tool offset or contaminated resin.
- Escape cause: why the defect was not detected before shipment, such as an unsuitable gauge or omitted inspection.
- Systemic cause: why the management system permitted both failures, such as weak change control, inadequate competency assurance or ineffective review of supplier process capability.
A response that identifies only operator error is often incomplete. It should ask why the error was possible, why the process did not prevent it, why the error was not detected and why previous data did not trigger action. 5. Root-Cause Analysis Methods5.1 5 WhysThe 5 Whys method repeatedly asks why a condition occurred until the team reaches a controllable cause. Five is not a mandatory number. The analysis stops when the team reaches a causal condition that is supported by evidence and can be controlled through a realistic action. Illustrative chain: - Problem: Incorrect connector was installed.
- Why 1: The assembler selected the wrong connector from the workstation.
- Why 2: Two visually similar connectors were stored together.
- Why 3: The point-of-use storage system lacked physical differentiation.
- Why 4: The work instruction specified part numbers but not visual segregation.
- Why 5: The process-design review did not assess misidentification risk.
The chain is valuable only if verified through observation, records, interviews and trials. A team should avoid blaming individuals when system conditions shaped the behavior. Multiple causal branches may exist; forcing a single linear chain can conceal important contributors. 5.2 Ishikawa or fishbone analysisAn Ishikawa diagram organizes possible causes into categories. Manufacturing teams often use the 6M categories: Manpower, Machine, Method, Material, Measurement and Mother Nature (environment). Service and administrative processes may use categories such as people, process, technology, information, policy and environment. The diagram is a hypothesis-generation tool, not proof of cause. Each proposed cause should be tested against data. Useful tests include comparing good and bad lots, reproducing the failure, checking calibration and maintenance records, examining material certificates, observing the process and analyzing time sequence. 5.3 Fault-tree analysisFault-tree analysis (FTA) begins with a defined top event and works deductively toward combinations of contributing events. “AND” and “OR” logic must be applied correctly. For example, an unsafe product release might require both a defect and an inspection escape; an OR gate may represent alternative paths by which release occurs. If basic events are statistically independent, the probability of an AND combination is: P(A ∩ B) = P(A) × P(B) For an OR combination of two independent events: P(A ∪ B) = P(A) + P(B) − P(A)P(B) These formulas require clearly defined events and independence assumptions. In real supplier systems, causes may be correlated—for example, poor training and inadequate work instructions may arise from the same management failure—so numerical FTA should not be performed mechanically. Qualitative FTA is often sufficient to expose barriers and escalation points. 5.4 Selecting the methodUse 5 Whys for a focused, relatively simple causal chain; Ishikawa analysis for broad exploration with a cross-functional team; and FTA when the top event has multiple pathways, safety significance or barrier logic. They can be combined: Ishikawa may generate hypotheses, 5 Whys may explore a branch, and FTA may model how occurrence and escape combine. 6. Corrective and Preventive Action DesignA credible CAPA plan links each verified cause to a specific action. The action should change the conditions that produced or allowed the failure. Examples include mistake-proofing, tooling redesign, automated parameter interlocks, validated software changes, revised sampling plans, supplier process redesign, improved material identification, competency assessment, layered process audits and stronger change approval. CAPA quality can be evaluated using the following questions: - Does the action address a verified cause rather than a symptom?
- Is it proportionate to severity and risk?
- Does it prevent recurrence at the source?
- Does it also address the escape mechanism?
- Is the action feasible, controlled and documented?
- Can its implementation and effectiveness be measured?
- Has the team checked for similar products, suppliers or processes?
Training alone is often a weak corrective action. It is appropriate when lack of knowledge is demonstrated, but it should be accompanied by process controls when human error is foreseeable. Similarly, increasing inspection may be necessary for temporary protection but does not normally eliminate the cause. A CAPA action should have an owner, due date, required resources, deliverable, approval method and risk review. Changes to drawings, software, process parameters, inspection methods or supplier locations require formal change control. Where validation is needed, the organization should define acceptance criteria before implementation. Effectiveness verificationImplementation asks, “Was the action completed?” Effectiveness asks, “Did the action reduce the relevant risk and prevent recurrence?” Suitable evidence may include: - zero recurrence across an agreed number of lots;
- stable process data over a defined time period;
- successful capability or performance results;
- audit evidence that the new control is used;
- reduction in escape or defect rate;
- successful challenge testing of an error-proofing device; and
- absence of similar failures in a defined family of products.
The metric must match the failure. If the problem is an escape caused by an ineffective test, measuring training completion does not demonstrate effectiveness. Verification should specify the population, observation period, acceptance threshold, data source and responsible reviewer. Closure is premature when the organization has only received a revised procedure without evidence of operation. 7. Quantitative Evaluation of Supplier QualitySupplier performance can be monitored with carefully defined measures. For a defect rate based on defective units: Defect rate = (Number of defective units ÷ Number of units received) × 100% If a unit can contain multiple defects, the organization should instead report defects per unit or defects per opportunity, with the denominator explicitly defined. A rate based on lots is not interchangeable with a rate based on units. For example, if 18 defective units are found among 6,000 received units: Defect rate = (18 ÷ 6000) × 100% = 0.30% A rate estimate is subject to sampling variation. If x defective units are observed in n inspected units, the estimated proportion is p̂ = x/n. For large samples and when the true proportion is not near zero or one, an approximate standard error is: SE(p̂) = √[p̂(1 − p̂) ÷ n] The approximation assumes independent observations and an appropriate sampling process. It should not be used to create false precision when inspection is biased, the population is clustered or the sample is extremely small. For rare defects, exact or improved binomial confidence methods may be preferable. Metrics should support decisions, not encourage concealment. A supplier may improve its incoming defect rate by shipping only after exhaustive sorting, while cost, lead time and process risk increase. Balanced measures may include escapes, repeat nonconformances, response time, closure quality, cost of poor quality, audit findings, process capability where appropriate, and the proportion of actions whose effectiveness is verified. 8. Governance, Ethics and Regulatory ConsiderationsNonconformance management is a governance process because records can affect product release, customer safety, regulatory submissions, warranty obligations and legal accountability. Important controls include: - documented authority for release and concession;
- secure, attributable and revision-controlled records;
- preservation of original data and audit trails;
- escalation of critical or potentially reportable events;
- truthful communication with customers and regulators;
- protection against retaliation for reporting defects;
- segregation of duties where commercial pressure could bias release decisions; and
- retention periods consistent with contractual and regulatory obligations.
A supplier should never be encouraged to alter inspection results, relabel material, backdate records or conceal a known deviation. Artificially improving supplier scorecards damages decision quality and may create safety and compliance exposure. Ethical quality leadership recognizes that delivery pressure is real but cannot override defined acceptance criteria without transparent, authorized risk assessment. 9. Technology, Data and Contemporary PracticeDigital quality systems can connect nonconformance records to purchase orders, lots, serial numbers, inspection results, supplier scorecards, engineering changes and CAPA workflows. Barcodes, serialization and genealogy tools improve suspect-population identification. Statistical process monitoring can provide early warning when process behavior changes before an out-of-specification result occurs. Artificial intelligence can assist with document classification, clustering of recurring failure descriptions, retrieval of similar historical cases and identification of patterns across suppliers. However, AI-generated causal suggestions are hypotheses, not verified root causes. Risks include biased historical data, false correlations, confidentiality breaches, opaque recommendations and automation of an inappropriate disposition. Human experts must retain decision authority for safety, regulatory and customer-impacting conclusions. Data provenance, access control, model validation and auditability are essential. Contemporary supplier quality programs increasingly emphasize resilience and upstream prevention. They combine risk-based supplier segmentation, process audits, digital traceability, collaborative development, design-for-manufacturability, climate and geopolitical risk assessment, cybersecurity controls and responsible sourcing. These concerns broaden the meaning of supplier quality beyond conformance of the delivered item. 10. Illustrative Case: Repeated Seal Leakage from a Purchased PumpBackgroundAn industrial equipment manufacturer received pumps from an approved supplier. During final assembly, three pumps in a lot of 240 failed a pressure-hold test because of seal leakage. The drawing required a specified seal material and installation orientation. The issue was classified as major because leakage could cause equipment shutdown and environmental release. Problem and containmentThe manufacturer stopped use of the lot, quarantined 240 pumps, traced two earlier lots and requested an immediate supplier stop-ship. A cross-functional team from quality, engineering, production, purchasing and the supplier was formed. Examination showed that seven of 720 pumps across three lots failed a repeated pressure test. Samples, photographs, seal labels, torque records and inspection data were retained. The supplier proposed 100% visual inspection of seal orientation. The customer accepted this only as interim containment because visual inspection could not reliably detect compression damage. A controlled functional test was added before release, and replacement stock was arranged. AnalysisAn Ishikawa session identified possible causes involving seal material, assembly fixture, operator method, torque, measurement and temperature. A comparison of good and failed units found that failures were associated with a recently replaced assembly fixture. Dimensional checks showed that the fixture allowed the seal to tilt under load. A 5 Whys analysis found: - The seal was damaged during insertion.
- The fixture applied uneven force.
- The replacement fixture had an incorrect guide dimension.
- The supplier’s incoming fixture verification checked presence and operation but not critical guide geometry.
- The change-control process did not require engineering approval and first-article validation for replacement fixtures.
The escape cause was also investigated. The supplier’s inspection sampled orientation but did not perform the pressure-hold test on a risk-based basis. The manufacturer’s incoming inspection relied on documentation and did not challenge the changed process. SolutionThe permanent actions were to redesign and validate the fixture, add a critical-dimension check to fixture acceptance, require engineering approval for fixture replacement, perform a capability study on the seal insertion process, and introduce pressure testing for the first three lots after implementation. The supplier revised the control plan, work instruction and change-notification procedure. The manufacturer updated supplier-change requirements and added the failure mode to its incoming risk review. Outcome and effectivenessThe supplier produced three consecutive lots totaling 1,800 pumps with no leakage failures. Audit observation confirmed the new fixture-verification record, and a challenge test demonstrated that a deliberately misaligned fixture could not be released without detection. The CAPA was closed only after evidence of both implementation and effectiveness. Learning pointsThe immediate defect was a damaged seal, but the systemic failure involved uncontrolled tooling change and inadequate validation. Visual sorting alone would have increased cost without eliminating the cause. The case also demonstrates that supplier quality is a shared system: the supplier owned the process failure, while the customer’s change-notification and incoming-risk controls influenced the probability of escape. 11. Challenges and LimitationsRoot-cause analysis is vulnerable to hindsight bias, confirmation bias, incomplete data and pressure to close cases quickly. Teams may select a convenient cause, confuse correlation with causation, or stop at “operator error.” Supplier investigations may also be constrained by proprietary processes, weak records or defensive commercial relationships. To improve rigor, teams should define the problem before proposing solutions, preserve evidence, include independent perspectives, test competing hypotheses, distinguish facts from assumptions and document rejected explanations. Where data are uncertain, uncertainty should be stated explicitly. A causal conclusion is stronger when changing the suspected cause changes the outcome, but controlled experimentation may not be possible for safety or production reasons. CAPA systems can also become bureaucratic. Excessive forms, arbitrary closure deadlines and large numbers of low-value actions create administrative compliance rather than improvement. Risk-based thresholds, intelligent escalation and periodic review of recurrence are more effective than treating every issue identically. Chapter SummarySupplier nonconformance control begins with accurate definition, risk-based containment and protection of customers and downstream processes. Disposition must be authorized, traceable and distinguished from permanent change. The 8D framework provides a disciplined sequence from team formation and problem definition through containment, causal analysis, corrective action, prevention of recurrence and closure. 5 Whys, Ishikawa analysis and fault-tree analysis serve different purposes and should be supported by evidence. Strong investigations distinguish occurrence, escape and systemic causes. CAPA must address verified causes, include accountable owners and deadlines, and be closed only after effectiveness is demonstrated. Metrics require clear denominators and appropriate assumptions. Ethical governance requires truthful records, controlled deviations, competent approval and resistance to commercial pressure that could compromise safety or compliance. Finally, lessons learned should be transferred across products, suppliers and processes so that each nonconformance strengthens the wider quality system. Key TermsNonconformance: Failure to meet a specified requirement. Defect: A nonconformity that affects intended use or requirement fulfilment. Containment: Temporary action that limits use or spread of suspect material. Correction: Action that removes an identified nonconformance. Corrective action: Action that removes the cause of a nonconformance and prevents recurrence. Preventive action: Action that removes the cause of a potential nonconformance. Disposition: Authorized decision concerning nonconforming material. Deviation: Approved, defined departure from an established requirement or process. Concession: Permission to accept a specified nonconforming condition. Escape: Failure of a control to detect or prevent a nonconformance before delivery or use. 8D: Structured, team-based problem-solving method. 5 Whys: Iterative questioning method for exploring causal chains. Ishikawa analysis: Cause-and-effect method that categorizes possible causes. Fault-tree analysis: Deductive analysis of how basic events combine to produce a top event. Occurrence cause: Cause that created the nonconformance. Systemic cause: Management or process condition that allowed failure or recurrence. CAPA: Corrective and preventive action system. Effectiveness verification: Evidence-based confirmation that an action achieved its intended result. Lessons learned: Validated knowledge transferred to prevent similar failures. Review QuestionsShort Answer Questions- What is the difference between correction and corrective action?
- Why is containment not a substitute for root-cause elimination?
- What information should a strong problem statement include?
- Distinguish occurrence cause, escape cause and systemic cause.
- What is the purpose of a deviation record?
Long Answer Questions- Explain the 8D method and discuss how each discipline contributes to supplier-quality improvement.
- Compare 5 Whys, Ishikawa analysis and fault-tree analysis, including the situations in which each is most useful.
- Discuss the principles of risk-based disposition for nonconforming purchased material.
- Explain how corrective-action effectiveness should be planned, measured and verified.
- Evaluate the ethical and governance risks of accepting supplier concessions under delivery pressure.
Analytical / Application Questions- A supplier reports that a dimensional defect was caused by an operator “not following the procedure.” Construct a deeper investigation using 5 Whys and identify evidence needed to validate the causes.
- A lot contains 24 defective units among 8,000 received units. Calculate the defect rate and explain why the result alone is insufficient for deciding whether the supplier is acceptable. Use the appropriate denominator and consider severity, detection and sampling limitations.
- A supplier introduces a replacement production fixture without notifying the customer, and failures appear three lots later. Design an 8D-based response covering containment, disposition, root-cause analysis, permanent corrective action, effectiveness verification and horizontal lessons learned.
Multiple Choice Questions with AnswersQuestion 1Which action primarily represents containment? A. Redesigning the supplier’s production fixture B. Quarantining all material from the suspect lot C. Revising the supplier’s change-control procedure D. Validating a new process capability study Correct Answer: B. Quarantining all material from the suspect lot Question 2Which statement best distinguishes corrective action from correction? A. Correction addresses the observed condition; corrective action addresses its cause B. Correction is always permanent; corrective action is always temporary C. Correction applies only to suppliers; corrective action applies only internally D. Correction requires customer approval; corrective action never does Correct Answer: A. Correction addresses the observed condition; corrective action addresses its cause Question 3In an 8D investigation, which discipline focuses on describing what, where, when and how extensively the problem occurred? A. D1 B. D2 C. D5 D. D8 Correct Answer: B. D2 Question 4What is the main limitation of the 5 Whys method? A. It cannot be used with process data B. It always requires exactly five questions C. A single linear chain may conceal multiple interacting causes D. It is applicable only to safety incidents Correct Answer: C. A single linear chain may conceal multiple interacting causes Question 5Which method is most explicitly designed to analyze combinations of events leading to a defined top event? A. Fault-tree analysis B. Check-sheet analysis C. Benchmarking D. Stratification Correct Answer: A. Fault-tree analysis Question 6A supplier finds 18 defective units among 6,000 received units. What is the defect rate? A. 0.03% B. 0.18% C. 0.30% D. 3.00% Correct Answer: C. 0.30% Question 7Which is the strongest evidence of CAPA effectiveness for an inspection escape? A. The revised procedure was distributed B. The responsible employee attended training C. The supplier stated that recurrence is unlikely D. Challenge testing showed that the revised control detects the failure mode Correct Answer: D. Challenge testing showed that the revised control detects the failure mode Question 8What is the principal purpose of a deviation approval? A. To permanently replace the original specification without change control B. To authorize a defined departure for a specified scope, duration or quantity C. To eliminate the need for risk assessment D. To conceal a nonconformance from the customer Correct Answer: B. To authorize a defined departure for a specified scope, duration or quantity Question 9Which statement about an RPN calculated as RPN = S × O × D is correct? A. It is a universal probability of failure B. It has a physical unit of defects per million C. It is a ranking aid based on organization-defined scoring scales D. It guarantees that the highest score is the most dangerous risk Correct Answer: C. It is a ranking aid based on organization-defined scoring scales Question 10Why should AI-generated root-cause suggestions not be accepted without expert verification? A. AI cannot process any quality records B. AI suggestions may reflect correlations, biased data or incomplete causal evidence C. AI is prohibited from all supplier-quality activities D. AI always produces numerical rather than qualitative results Correct Answer: B. AI suggestions may reflect correlations, biased data or incomplete causal evidence
|