Study guide

15.4 Root Causes, Effects, and Significance of Findings

CIA Part 2 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CIA Part 2 Exam Orientation

1.1 Current CIA Part 2 Exam Facts 1.2 Eligibility, Fees, and Pearson VUE Scheduling 1.3 Scoring, Results Timing, and the 2025 Syllabus Map

2 Chapter 2: Engagement Objectives and Scope

2.1 Topical Requirements in Objectives and Scope 2.2 Elements Used to Build Engagement Objectives 2.3 Scope Limitations, Stakeholder Requests, and Scope Changes

3 Chapter 3: Evaluation Criteria and Planning Context

3.1 Selecting and Testing Evaluation Criteria 3.2 Applying Topical Requirements When Planning 3.3 Strategy, Risk Management, and Performance of the Activity Under Review

4 Chapter 4: Technology, Continuity, and Finance in Planning

4.1 Cybersecurity, IT General Controls, Privacy, and Data Security 4.2 Business Continuity, Disaster Recovery, and Resilience 4.3 Finance and Accounting Concepts for the Activity Under Review

5 Chapter 5: Business Process and System Risks in Planning

5.1 Asset, Supply Chain, Inventory, Payables, Procurement, and Compliance Processes 5.2 Third-Party Process Risks 5.3 CRM, ERP, and GRC System Risks

6 Chapter 6: Engagement Approach and Project Management

6.1 Agile, Traditional, Integrated, and Remote Approaches 6.2 Project Management While Planning and Conducting Engagements

7 Chapter 7: Engagement Risk Assessment

7.1 Topical Requirements and Pervasive Financial, Operational, IT, Cyber, and Regulatory Risks 7.2 Emerging Risks and the Impact of Change 7.3 Methods to Evaluate and Prioritize Risks and Controls

8 Chapter 8: Structure, Environment, and Culture

8.1 Centralized vs Decentralized, Flat vs Traditional, In-Person vs Remote 8.2 Culture, Group Behavior, and Tone at the Top

9 Chapter 9: Control Design, Effectiveness, and Efficiency Procedures

9.1 Procedures to Evaluate Control Design 9.2 Procedures to Test Operating Effectiveness 9.3 Procedures to Test Control Efficiency

10 Chapter 10: Work Programs, Testing Methodologies, and Resources

10.1 Evaluating Adequacy of the Engagement Work Program 10.2 Testing Methodologies for Accounting, Finance, IT, Operations, and Cybersecurity 10.3 Financial, Human, and Technological Resources and Limitation Implications

11 Chapter 11: Information Sources and Preliminary Survey

11.1 Interviews, Observations, and Walk-Throughs 11.2 Data Analysis as an Information Source 11.3 Policies, Checklists, Risk-and-Control Questionnaires, and Self-Assessments

12 Chapter 12: Evidence Relevance, Sufficiency, and Reliability

12.1 Criteria for Evidence Quality 12.2 Independence, Corroboration, and the Control Environment 12.3 Evidence an Informed, Competent Person Could Rely On

13 Chapter 13: Technology Options for Findings and Conclusions

13.1 Artificial Intelligence, Machine Learning, and Robotic Process Automation 13.2 Continuous Monitoring, Dashboards, and Embedded Audit Modules

14 Chapter 14: Process Mapping and Data Analytics

14.1 Workflow Segments, Process Maps, Walk-Throughs, and RACI 14.2 Structured vs Unstructured Data and the Analytics Process 14.3 Diagnostic, Prescriptive, Predictive, Anomaly, and Text Analysis

15 Chapter 15: Analytical Review and Finding Evaluation

15.1 Ratios, Variances, Trends, and Benchmarking 15.2 Selecting Analytical Techniques for Engagement Objectives 15.3 Comparing Existing Conditions to Evaluation Criteria 15.4 Root Causes, Effects, and Significance of Findings

16 Chapter 16: Workpapers and Engagement Conclusions

16.1 Organizing Complete Workpapers with Sufficient Evidence 16.2 Linking Workpapers to Results; Retention, Regulation, and Policy 16.3 Aggregating Findings and Concluding on Governance, Risk, and Control

17 Chapter 17: Engagement Supervision

17.1 Supervision Throughout Planning and Fieldwork 17.2 Coordinating Assignments and Reviewing Workpapers and Conclusions 17.3 Evaluating Auditors' Performance

18 Chapter 18: Communication During the Engagement

18.1 Formal and Informal Communication Across Planning, Fieldwork, and Reporting 18.2 Situations That Require Escalation 18.3 Selecting Appropriate Stakeholders for Engagement Communication

19 Chapter 19: Final Review and Test Day

19.1 2025 vs 2019 Traps and Part 2 vs Part 3 Boundaries 19.2 Pacing, Test-Center Rules, and Official Results

15.4 Root Causes, Effects, and Significance of Findings

Key Takeaways Explain This Topic AI

B6b–c tests root-cause analysis, potential effects on objectives, and significance for this engagement's findings and conclusions—not Part 3 recommendation and action-plan protocol.

Five-why analysis separates contributing causes (the clerk skipped the match) from root causes (force-pay access was never recertified and has no second reviewer).

Effect is the consequence for engagement and activity objectives, including realized loss and reasonably possible exposure, not a vague statement that the issue looks bad.

Significance weighs materiality, risk appetite, pervasiveness, compensating controls, and trend; an isolated, compensated, trivial exception is not automatically reportable as a significant finding.

Treating every exception as equally reportable is the classic trap; two gaps with the same CCCE labels can support different conclusions for this engagement.

Last updated: August 2026

Root Cause Versus Contributing Cause

Section B6b asks you to identify root causes and potential effects of deviations. Section B6c asks you to appraise factors that establish the significance of findings. Together they implement Standard 14.3 (Evaluation of Findings): evaluate each potential finding to determine its significance, considering root cause and effects. This chapter stops at that evaluation. Agreeing recommendations, owners, due dates, residual-risk acceptance, and follow-up monitoring is CIA Part 3 work. Do not drag that protocol into a Part 2 significance question.

Root cause is the underlying process, system, design, or governance failure that, if fixed, would prevent recurrence of the condition. Contributing causes are real factors that made the gap easier, but removing only them would leave the engine intact. "The clerk was not trained" is almost always contributing. Why was the clerk on the desk without training? Why did the system allow an untrained user to force-pay? Why did exception access survive go-live without recertification? Why is there no second reviewer on force-pay? Those questions move you toward a root cause such as access governance failure or exception-path design with no compensating review .

Five-why is a practical method, not a ritual of exactly five questions. You keep asking why until you reach a cause the activity can actually address at the process or control-design level, and until further whys would jump outside the engagement scope (enterprise culture, board composition) without a factual bridge. Stop too soon and you will treat a symptom. Keep going into speculation and you will invent a cause the evidence does not support. Fishbone (people, process, technology, policy, environment) is a cousin: it prevents you from parking every gap in the "people" bone.

North Hub payment example. Why were invoices paid without receiving reports? The clerk used force-pay. Why could the clerk? The system allows force-pay without a receiver. Why is that enabled? Exception access was granted at WMS go-live. Why was it never removed? Access recertification was not in the IT general-control calendar for this application. Why did no one catch the payments? The exception report exists but is not assigned to an independent reviewer. Root cause: exception access and monitoring were never designed into BAU after go-live . Training the current clerk, by itself, would not close that cause.

Effects on Objectives

Effect is what the deviation does—or credibly could do—to the engagement objectives and to the activity's objectives. Write it in operational language, then quantify when evidence allows. Realized effects (duplicate payments already made, shrink already in the count, customers already shipped late) differ from potential effects (exposure if the gap continues, likelihood of a control failure in peak season). Standard 14.3 expects both impact and likelihood thinking even though you are not running a full enterprise risk workshop.

Tie effect back to the objective. If the engagement is about payment accuracy, the effect is incorrect disbursements, duplicate payments, and unmatched inventory. If the engagement is about dock-to-stock cycle time, the same missing receiver may matter more as a delay driver than as a dollar error. An effect that cannot be connected to an objective is a sign you are inflating significance or that the item belongs in a different engagement.

Do not confuse effect with significance. Effect is the consequence description. Significance is the appraisal of whether that consequence, in context, is important enough to shape this engagement's findings and conclusions.

Appraising Significance for This Engagement

B6c is a judgment, not a scorecard you memorize as a formula. The factors the exam expects you to weigh are consistent with Standard 14.3 and with how engagement conclusions are later aggregated (Chapter 16):

Factor Question Makes the finding more significant Makes it less significant

Materiality (quantitative and qualitative) Is the effect large enough, or sensitive enough (fraud, law, safety, integrity of reporting), to matter? Dollar error above engagement materiality; legal or safety exposure; management override Trivial dollars; no qualitative overlay

Risk appetite Does the residual risk sit outside what the organization is willing to accept for this activity? Clear breach of a board- or management-set appetite or policy limit Within appetite and still monitored

Pervasiveness Is the condition isolated or spread across the population, sites, periods, or transaction types? 40 percent of the sample; multiple sites; whole exception path One transaction, one clerk, one day

Compensating controls Does another control operate and reduce the residual effect? No second line of defense; compensating control missing or failing tests Independent daily exception review tested and operating

Trend Is this a one-off or a deteriorating pattern? Rate up from 12 percent to 40 percent over three quarters First occurrence after a known, contained incident

Trap: treating every exception as equally reportable. Two exceptions can both be true and both documented in CCCE form and still support different conclusions for this engagement. Exception A: one $180 missed early-payment discount; dual approval of the invoice operated; no trend. Exception B: 40 percent of invoices over $5,000 missing receivers, rate rising for three quarters, force-pay unmonitored. Exception B shapes the conclusion on payment controls. Exception A may be documented in the workpapers and still be insignificant to the engagement conclusion. Equal reportability is not professional skepticism. It is a refusal to evaluate.

Compensating controls deserve care. A control that exists on a flowchart but fails operating-effectiveness tests does not reduce significance. A well-designed system report reviewed daily by an independent monitor, with evidence the review actually happens and exceptions are cleared, can reduce residual effect and therefore significance—even if the primary three-way match is broken. You still have a condition (primary control failed). You may not have a significant finding for this engagement's conclusion if the compensating control is real. That distinction is exactly what B6c tests.

Qualitative materiality can override small dollars: a $200 override by a senior manager, a single safety interlock bypass, a privacy-rule breach, or a fabricated receiver. Risk appetite cuts the other way only when it is an actual organizational statement, not when operations say "we are comfortable" after you arrive.

What you are not being asked here is to negotiate an action plan, assign a due date, accept residual risk on behalf of management, or write the final engagement communication. Those are Part 3. On a Part 2 item, if an option says the auditor must obtain management's action plan before the finding can be evaluated, that option is the boundary trap. Significance is appraised from criteria, evidenced condition, root cause, effect, and the factors in the table—so the engagement team can conclude on the activity's governance, risk management, and control for this engagement.

Loading diagram... Five-why from contributing cause to root cause

Missing-receiver rate at North Hub (percent of invoices over $5,000)