Study guide
15.3 Comparing Existing Conditions to Evaluation Criteria
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.3 Comparing Existing Conditions to Evaluation Criteria
Key Takeaways Explain This Topic AI
GIAS Standard 14.2 requires auditors to compare evaluation criteria (the expected state) with existing conditions (the current state) to develop potential engagement findings.
Finding elements are criteria, condition, cause, and effect (CCCE); a gap without all four is incomplete analysis, even if the condition looks dramatic.
Criteria are selected and tested in planning (Chapter 3, Standard 13.4) and are not quietly swapped in fieldwork to avoid an unfavorable result.
Condition is what is, evidenced: relevant, reliable, and sufficient information—not rumor, not an untested dashboard tile, not a manager's vibe.
Cause and effect explain why the gap exists and what it does to objectives; they are developed here and appraised for significance in the next section.
Last updated: August 2026
Criteria Versus Condition Is the Heart of a Finding
Section B6a requires you to analyze existing conditions and compare them to evaluation criteria. Under Standard 14.2 , internal auditors analyze relevant, reliable, and sufficient information to develop potential engagement findings . The comparison is simple to say and easy to fail on the exam: criteria are the expected state (what should be); condition is the current state (what is). The gap between them is what you then explain with cause and effect . Those four elements— criteria, condition, cause, effect (CCCE) —are how IIA materials have long structured a finding. CIA Part 2 still tests the structure even though final communication of findings is primarily a Part 3 skill.
If you cannot name the criteria, you do not have a finding. You have an observation that something happened. If you cannot evidence the condition, you do not have a finding. You have a lead. If you skip cause, you will later mis-rank significance and, in Part 3, mis-aim any recommendation. If you skip effect, you cannot tell whether the gap matters to the engagement objectives.
Criteria Are Locked in Planning
Standard 13.4 (Evaluation Criteria) lives in planning, which this guide covered in Chapter 3. By the time you are in B6, the criteria should already be identified, relevant to the objectives, and—where practical—discussed with management of the activity. Typical sources: laws and regulations, contracts, board-approved policies, documented procedures, industry standards the organization adopted, engineered standards, service-level agreements, and performance measures the activity itself uses to run the process.
Fieldwork does not get a silent rewrite. If results look unfavorable, you do not swap in a softer expected state so the activity "passes." If the original criteria turn out to be genuinely inappropriate—wrong policy version, criterion that does not match the objective, a stretch target that was never an operational standard—you document a criteria change with rationale , including who was informed. That is a planning correction, not moving the goalposts. Management's current informal preference ("we usually try to three-way match when we can") is not automatic criteria unless planning accepted it as the expected state.
Weak criteria produce weak findings. "Best practice" with no source, an auditor's undocumented personal preference, last year's actual used as a permanent standard without considering change, or a peer's number that is not comparable—all fail the relevance test from Chapter 3 and will fail B6a when the stem asks what is missing from the finding.
Condition Must Be Evidenced
Condition is the factual current state of the activity, described at the level of precision the objective needs. "Receiving often skips three-way match" is not a condition. It is an allegation . A condition looks like: in a statistically or judgmentally justified sample of 40 invoices over $5,000 paid in Q2, 16 (40 percent) lacked a receiving report in the three-way-match file; the exception rate in Q4 last year on the same test was 12 percent. That sentence can be tied to workpapers, source documents, and a population definition.
Evidence quality is Chapter 12 (Standard 14.1), but B6a will still punish you for promoting rumor. Relevant evidence actually bears on the criteria. Reliable evidence is produced under conditions you can defend (independent source, effective control environment, original documents, corroboration). Sufficient evidence is enough for an informed, competent person to reach the same condition statement. A single dashboard screenshot, an anonymous comment, or one walk-through anecdote can start inquiry. It cannot be the condition on which you hang cause, effect, and significance.
Analytical review from 15.1–15.2 often points at a condition. The unexpected freight gap, the sales-versus-shipments shortfall, the overtime ratio that did not move with volume—those are differences. You still have to evidence what is happening in the process: misposted accounts, unbilled shipments, unapproved overtime, missing receivers. Do not paste the variance chart into the finding and call the chart the condition.
Cause and Effect Complete the Comparison
Once criteria and evidenced condition show a gap, Standard 14.2 expects you to determine potential causes and effects . You do not need the full significance appraisal yet (that is B6b–c in the next section), but you cannot stop at "variance noted."
Cause is why the condition exists. Surface causes ("the clerk skipped the match") are usually not enough; you are looking for the process, system, or governance failure that allowed the skip. Effect is the consequence for the activity's objectives: incorrect payments, inventory overstatement, missed discounts, regulatory exposure, extra freight, delayed customer orders. Effect should be described in operational and, where possible, quantified terms, including whether the effect is already realized or is a reasonably possible exposure.
Element Meaning North Hub three-way-match example Fail pattern
Criteria Expected state from planning Policy and system design require a receiver, PO, and invoice match before payment over $5,000 "I prefer three-way match" after seeing results
Condition Evidenced current state 16 of 40 sampled invoices over $5,000 paid with no receiver; rate up from 12 percent to 40 percent "Staff say receiving is sloppy"
Cause Why the gap exists Force-pay access never recertified after WMS go-live; exception path has no second reviewer Stop at "human error"
Effect Impact on objectives Duplicate and unmatched payments; inventory receipts lag; $X unmatched AP; stockouts from delayed receiving "Looks bad" with no link to objectives
A complete CCCE package is still a potential finding until you appraise significance (15.4). Isolated, compensated, or trivial gaps may not survive that appraisal. That does not mean you skip CCCE. It means you build the four elements so the significance decision is evidence-based.
On the exam, when a stem gives a dramatic anecdote and asks what to do, the answer is usually: identify the planning criteria, gather evidenced condition, then analyze cause and effect. When a stem shows the auditor changing the target because operations complained, the answer is: keep the planning criteria or document a justified change—do not sanitize the expected state. When a stem offers a finding with only a variance chart, name the missing element: usually an evidenced condition, a sourced criterion, or both.