Study guide

12.3 Evidence an Informed, Competent Person Could Rely On

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.3 Evidence an Informed, Competent Person Could Rely On

Key Takeaways Explain This Topic AI

CIA Part 2 B2c is describing evidence that would allow an informed and competent person to reach the same conclusions as the internal auditor — a reviewer who has the file, not the staff member who remembers the hallway

GIAS 14.1 builds that outsider into sufficiency; GIAS 14.6 requires documentation so an informed, prudent internal auditor or similarly competent person could repeat the work and derive the same engagement results

Reperformable evidence shows objective, criterion, population and IPE source, procedures, items and exceptions with disposition, and a conclusion linked to those results — plus a tick-mark legend

The trap is “I was there so I know”: undocumented observation, unlabeled ticks, oral exception clearance, and significance calls that live only in the auditor’s head

Supervisor sign-off reviews the evidence; it is not a substitute for evidence — Chapter 17 uses this standard; Chapter 16 organizes the file; final-report form is not the B2c task

Last updated: August 2026

12.3 Evidence an Informed, Competent Person Could Rely On

Quick Answer: CIA Part 2 B2c asks you to describe evidence that would allow an informed and competent person to reach the same conclusions as the internal auditor. That person is a reviewer, another auditor, an external assessor, or a similarly skilled outsider — not the staff member who “was there.” GIAS Standard 14.1 builds this outsider into sufficiency ; Standard 14.6 requires documentation such that an informed, prudent internal auditor or similarly informed and competent person could repeat the work and derive the same engagement results . The trap is “I was there so I know” : undocumented observation, unlabeled tick marks, and conclusions that cannot be re-performed from the file.

If 12.1 is the three-attribute filter and 12.2 is how you rank reliability, 12.3 is the reperformance test . It is the reason workpapers exist. Chapter 16 will organize complete workpapers and retention; Chapter 17 will put a supervisor in the reviewer chair. This section is the B2c skill those later chapters assume: what must the evidence itself look like so someone who did not do the work can still agree with you — or show where you went wrong.

Who is the informed, competent person?

The standard is not “a random employee on the elevator” and not “only the CAE who already knows this process.” Think of a prudent, informed, competent reviewer who:

  • understands internal auditing and the type of engagement,
  • has the file, the work program, and the supporting exhibits,
  • does not have your memory of the hallway conversation,

could repeat the procedures and see how the conclusion follows.

GIAS 14.6 uses almost the same person: an informed, prudent internal auditor, or a similarly informed and competent person. Quality assessors, external auditors who rely on your work, and engagement supervisors are the practical faces of that person. If the file only works when you are in the room to narrate it, the evidence is not yet B2c-quality — and it is not sufficient under 14.1.

The person is informed (given the objectives, criteria, scope, and methods) and competent (could execute the procedures). You do not have to educate a novice from zero inside every tick mark. You do have to make the logic reconstructable: what you tested, against what, on what population, with what result, leading to what conclusion.

Confidentiality does not empty the file. You may restrict who sees workpapers. The authorized reviewer still needs a reperformable packet. “This is sensitive, so I kept it in my head” fails B2c.

What the file must show (the reperformance checklist)

Describe evidence at a level another auditor could reperform the logic , not merely admire the conclusion sentence.

Element What the outsider needs to see Failure if missing

Objective and criterion What question you were answering and the standard you compared to Relevant-looking exhibits that do not lock to a claim

Population and source Where the items came from, how completeness was addressed, IPE tests if a report was used Hidden selection bias; untested extract

Procedure actually performed Nature, extent, timing, who did it, when “Tested AP” with no method

Items and results What was selected, exceptions, how exceptions were resolved A conclusion with no trail to the sample

Link to conclusion Why these results support this conclusion, including significance A leap from “no issues noted” to “controls are effective”

Legend and indexes Tick-mark meanings, cross-references, version of the report Decorative ticks another auditor cannot decode

That is evidence , not bureaucracy. A screenshot of a live configuration with the parameter name, environment (production), date captured, and who can change it is reperformable. A sticky note that says “match is on” is not. A bank confirmation in the file, with the request, the reply path, and the reconciliation to the GL, is reperformable. “Cash is fine — I called the controller” is not.

You do not need to reproduce the entire ERP. You need a reproducible path : parameters, record counts, hash or control totals, sample selection method, and exhibits that still exist. If the only copy of a report was on a live screen you did not capture, the competent person has nothing.

The “I was there so I know” trap

Observation and professional judgment are real procedures. They become non-evidence when they leave no trail an outsider can evaluate.

Worked example — undocumented observation. The auditor visits the warehouse, watches receiving, and concludes dual custody of high-value items is effective. The workpaper says “Observed receiving — OK.” A reviewer cannot tell which dock, which shift, which SKUs, whether staff knew they were being watched, or how one visit supports a period-long conclusion. Repair: date, location, who was present, what was supposed to happen (criterion), what actually happened (condition), photographs or count sheets if used, limitations (snapshot), and why the observation does or does not support the objective. The observation can still be relevant and, for that hour, reliable. Without that description, it fails the competent-person test — which is a sufficiency and documentation failure, not a finding that observation is never evidence.

Worked example — undocumented judgment. Five exceptions in a sample of 25. The auditor writes “immaterial — no finding.” The reviewer cannot see the dollar effect, the root-cause hypothesis, whether items were in a high-risk class (vendor bank changes versus office supplies), or whether the five share a pattern. Repair: show the calculation or qualitative rationale a competent person could challenge. Significance evaluation is GIAS 14.3 and Chapter 15; B2c is the demand that the basis sit in the evidence, not in the auditor’s head.

Worked example — oral close-out. Management explains all exceptions in a meeting. The auditor is persuaded and files nothing but “cleared in discussion.” An informed person cannot evaluate the explanation, cannot see corroboration (12.2), and cannot reperform the clearance. Repair: document the explanation, obtain supporting records, and show why the evidence now supports — or still does not support — the original conclusion.

The same trap appears as unlabeled tick marks, as “tested 25 — OK” with no listing of items, and as a conclusion drafted before exhibits were attached ( file stuffing ). A reviewer who cannot tell whether you sampled from the full unmatched population or from a filtered “clean” list cannot reach your conclusion honestly.

Linking 14.1 sufficiency to 14.6 documentation

Candidates split these standards into “fieldwork versus paper.” The 2025 exam does not. If a competent person cannot reach the same conclusion from the file, the information was not sufficient under 14.1, even if you personally remember more. Standard 14.6 then requires the analyses, evaluations, and supporting information to be documented so that person could repeat the work and derive the same engagement results . Supervisors review documentation for accuracy, relevance, and completeness (14.6) — that review is Chapter 17; your job in B2c is to produce evidence that makes the review possible.

Supervisor sign-off is not a substitute for exhibits. Sign-off means someone reviewed the evidence. Empty papers with a reviewer’s initials still fail B2c. Likewise, a process-owner “agrees with the rating” in a closing meeting is communication during the engagement (Chapter 18), not evidence that an outsider could reperform.

Retention, legal hold, and linking workpapers to final communications are Chapter 16. Final report attributes, recommendation protocols, residual-risk acceptance, and follow-up monitoring are not the B2c task — and are primarily CIA Part 3 2025. Stay on: would another competent person, looking only at this evidence, reach the same conclusion?

Describing B2c-quality evidence (what good looks like)

Use the AP unmatched-invoice review as a complete packet an informed person could rely on:

Objective: operating effectiveness of the Friday unmatched-invoice review for the fiscal year.

Criterion: policy requiring weekly review of all unmatched invoices over $5,000, evidenced by sign-off and investigation notes.

Source: production ERP exception report; IPE tested by reconciling one week’s report to the unmatched table, including parked items; parameters screenshotted.

Procedures: inquiry (documented, not sole support); inspection of signed reports for 12 weeks spread across the year including close; reperformance of 15 investigations; user-ID comparison to the authority list.

Results: one unsigned week in March (system outage); 14 of 15 investigations supported; IPE complete for the weeks tested.

Conclusion: control operated with a documented exception in March; exception evaluated for significance with amounts and duration shown.

A reviewer can disagree with the significance call — that is healthy — but cannot say the conclusion is unavailable to evaluate . That is B2c.

Packet Can an informed, competent person reach the same conclusion?

  • Tick marks, no legend, no population, conclusion “effective” No
  • “Observed warehouse — OK” No
  • “Controller said cash is correct” No
  • Selection method, IPE tests, exhibits, exceptions with disposition, linked conclusion Yes

Perfect exhibits for last year’s engagement reused without noting this year’s period No — not current, and the person cannot see this year’s work

  • Raw ERP dump with a one-line conclusion and no procedure description No
  • Exam traps

Believing personal knowledge substitutes for evidence another person can evaluate.

Confusing confidentiality (you may restrict who sees the file) with emptiness (the authorized reviewer still needs a reperformable file).

Dumping raw extracts with no procedure description and calling it sufficiency.

Writing the conclusion first and attaching random documents.

Treating supervisor sign-off as a substitute for evidence.

Drifting into Part 3 final-report form and follow-up tracking.

B2c is complete when you can describe a packet that would let a competent outsider repeat the logic — and reject a packet that only makes sense if the original auditor is still in the building.

Loading diagram... Competent-person reperformance test (GIAS 14.1 and 14.6)

Illustrative reperformance ability from the file (0 = memory-only, 4 = full trail; teaching scale)