Study guide

12.1 Criteria for Evidence Quality

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

12.1 Criteria for Evidence Quality

Key Takeaways Explain This Topic AI

GIAS Standard 14.1 requires information that is relevant (bears on the objective and evaluation criteria, inside scope), sufficient (persuasive quantity so a prudent, informed, competent person could reach the same conclusion), and reliable (factual, current, trustworthy source)

CIA Part 2 B2a is an AND test: failing any one attribute means you do not conclude on that packet — volume does not repair irrelevance, and original documents do not repair a wrong question

Relevance fails when the evidence answers a nearby topic (matched invoices filed for a vendor-master dual-authorization objective) or uses the wrong period, population, or criterion

Sufficiency fails when nature, extent, or timing cannot support the intended conclusion — one observed Friday review does not prove a year of operating effectiveness

If relevant evidence cannot be obtained, identify a finding or scope limitation; do not launder the gap by calling leftover documents close enough

Last updated: August 2026

12.1 Criteria for Evidence Quality

Quick Answer: CIA Part 2 B2a tests whether you can apply suitable criteria to evidence: it must be relevant (it bears on the engagement objective and evaluation criteria), sufficient (enough persuasive quantity to support the conclusion), and reliable (quality you can trust given the source and how you obtained it). Global Internal Audit Standards (GIAS) Standard 14.1 requires all three before you analyze and evaluate. Failing any one attribute means you gather more, change procedures, or — if relevant evidence cannot be obtained — consider a finding. Volume does not repair irrelevance.

Chapter 11 identified sources of information: interviews, observations, walk-throughs, data analysis, policies, checklists, questionnaires, and self-assessments. This chapter is the quality filter you apply while you gather. Section B2 of the 2025 syllabus is proficient-level: evaluate relevance, sufficiency, and reliability of evidence gathered to support engagement objectives. You are in GIAS Principle 14 — Conduct Engagement Work — not still choosing design procedures (Chapter 9) and not yet aggregating findings into an engagement conclusion (Chapter 16).

The 2019 IPPF Performance Standard 2310 listed four attributes: sufficient, reliable, relevant, and useful . GIAS 2024 and the 2025 CIA Part 2 B2 bullets use three . If an item offers “useful to the organization” as a required fourth quality test for B2, treat it as a leftover, not the current exam criterion. Usefulness still matters as a professional outcome; it is not the B2a scoring key.

Why three attributes, not one score

Evidence quality is not a blended gut feel that the file looks thick. Each attribute answers a different question. The exam will give you a packet that is excellent on two attributes and broken on the third, then ask whether you may conclude.

Attribute Question it answers Failure mode Typical repair

Relevance Does this information bear on the objective and the evaluation criteria ? Right documents, wrong question Change what you collect; do not enlarge a wrong population

Sufficiency Is there enough persuasive quantity that a prudent, informed, competent person could reach the same conclusion ? Thin sample, one snapshot, inquiry only Expand extent, add procedures, cover the period

Reliability Is the information factual and current , from a source and method you can trust? Biased source, untested IPE, oral claim, weak system Obtain it yourself, corroborate, test IPE, go to an independent source

GIAS Standard 14.1 states the same three ideas in standard language:

Relevant — consistent with engagement objectives, within the scope of the engagement, and contributes to the development of engagement results.

Reliable — factual and current. Internal auditors use professional skepticism (GIAS Standard 4.3) to evaluate whether information is reliable. Section 12.2 unpacks the three official strengtheners: obtained directly or from an independent source, corroborated, and gathered from a system with effective governance, risk management, and control processes.

Sufficient — enables internal auditors to perform analyses and complete evaluations, and can enable a prudent, informed, and competent person to repeat the engagement work program and reach the same conclusions as the internal auditor.

Sufficiency therefore has two faces: enough for you to analyze, and enough for an outsider to reperform. Section 12.3 develops the outsider test as a documentation standard (GIAS 14.6). Here, treat it as the quantity and persuasiveness test.

If evidence is not relevant, reliable, or sufficient, Standard 14.1 requires you to determine whether to gather additional information . If relevant evidence cannot be obtained — records destroyed, a system with no audit trail, a scope block you cannot lift — identify that as a finding or a scope limitation . Scope limitations were Chapter 2. Here the skill is refusing to launder a gap by calling leftover documents close enough.

Relevance: it must bear on the objective and the criterion

Relevance is a relationship test, not a popularity test. Information is relevant when it helps you compare condition to evaluation criteria for the stated objective (GIAS 13.4 and 14.2). A perfect bank confirmation is irrelevant to an objective about physical inventory existence at a warehouse you never counted. A complete, well-controlled HR timesheet extract is irrelevant to whether three-way match blocked unmatched invoices before payment.

Ask three questions of every item you file:

Objective — Does this information answer the engagement objective, or a nearby interesting topic?

Criterion — Does it speak to the standard you selected (policy, law, configuration, contract, COSO principle), or to a different standard?

Scope — Is it inside the activities, locations, systems, and period named in the scope?

Worked example — relevance fails. Objective: determine whether vendor bank-account changes in the ERP required dual authorization during the fiscal year. Criterion: the documented dual-control workflow. The auditor obtains 40 original, matched vendor invoices from a system with strong IT general controls. The invoices are reliable and plentiful. They do not bear on bank-account master-data changes . Filing them as the primary support for the objective is a relevance failure. Repair: obtain the vendor-master change log, workflow history, and who-approved extracts for the period — then apply sufficiency and reliability tests to those items.

Relevance also fails when the period is wrong (last year’s SOC report used as the sole support for this year’s access recertification), when the population is wrong (testing only domestic vendors when the objective includes the shared-service center’s offshore payees), or when the auditor tests a compensating control and then concludes on the original control without saying so.

Sufficiency: quantity and persuasiveness, not page count

Sufficiency is not “we printed a lot.” It is whether the persuasive weight of relevant, reliable evidence can support the conclusion you intend to draw . A high-risk, high-frequency manual control supported by two invoices from the last week of fieldwork is insufficient even if both invoices are authentic originals. A low-risk annual control may be sufficient with a deep test of that one occurrence.

Persuasiveness comes from nature × extent × timing , the same idea you used when planning operating-effectiveness procedures in Section 9.2:

Nature — inquiry is the least persuasive; observation is a snapshot; inspection and reperformance carry more weight. Inquiry alone is almost never sufficient to support an assurance conclusion.

Extent — how much of the population, how many procedures, how many independent sources.

Timing — evidence from throughout the period, including peak and cutoff, not a single comfortable month.

Sufficiency is conclusion-dependent . The evidence needed to say “we found no exceptions in a walk-through of design” is smaller than the evidence needed to say “the control operated effectively all year.” The evidence needed for a potential finding you will rate significant is larger than the evidence needed to drop a trivial observation. Do not over-file low-risk noise and under-file the issue that will drive the engagement conclusion.

Worked example — sufficiency fails. Objective: operating effectiveness of the Friday unmatched-invoice review. The auditor watches the supervisor perform the review once , on the Tuesday internal audit is in the building. The observation is relevant and, as far as it goes, reliable. It is not sufficient to conclude the control operated throughout the year. Repair: inspect signed reports across the period, test IPE completeness of the report, and reperform a sample of investigations. One observed performance is a snapshot, not a year.

Reliability: quality and source (preview of 12.2)

Reliability asks whether the information is factual and current and whether you obtained it in a way that professional skepticism would accept. A document can be relevant and numerous and still be unreliable: a photocopy the process owner printed the night before, an unsigned spreadsheet with no tie-out to the subledger, oral assurance from the person whose work you are evaluating, or an exception report nobody tested for completeness ( IPE — information produced by the entity).

Worked example — reliability fails. Objective: existence of inventory at a third-party warehouse. The warehouse manager emails a listing the manager prepared in Excel, with no receiving records, no independent count, and no auditor observation. The listing is relevant (it names the SKUs in scope) and voluminous (12,000 lines). It is not reliable as the sole support for existence. Repair: observe or independently count, obtain receiving and shipping records from a system you test, or confirm with an independent party — then corroborate.

All three, or you do not conclude

Treat the attributes as AND gates. Relevant plus sufficient but unreliable is advocacy, not assurance. Relevant plus reliable but insufficient is a hunch with nice exhibits. Sufficient plus reliable but irrelevant is a well-supported answer to the wrong question.

Packet Relevant? Sufficient? Reliable? May you conclude on the objective?

40 original matched invoices, strong ITGCs, objective is vendor bank-account dual authorization No n/a Yes No — wrong evidence

One observed Friday review, objective is year-long operating effectiveness Yes No Yes, for that day No — expand

Process-owner spreadsheet of “all exceptions closed,” weak controls, no corroboration Yes Maybe by volume No No — corroborate or replace

Auditor-obtained change log plus workflow IDs plus independent HR termination list, period coverage, IPE tested Yes Yes Yes Yes — proceed to analysis (14.2)

Exam traps

Equating volume with sufficiency, or original documents with relevance.

Concluding on inquiry alone.

Using last period’s evidence as if it were current (reliability and relevance both suffer).

Treating a 2019-style “useful” fourth attribute as the B2a key.

Filing evidence that supports a different criterion than the one you selected in planning (Chapter 3).

Skipping the Standard 14.1 duty to gather more — or to report that relevant evidence could not be obtained.

B2a is complete when you can look at a packet and name which attribute fails , why, and what you do next — not when you can recite three definitions.

Loading diagram... GIAS 14.1 three-attribute gate for engagement evidence

Illustrative persuasiveness by nature (1–4; still apply relevance and reliability — not IIA-published scores)