Study guide

18.3 Selecting Appropriate Stakeholders for Engagement Communication

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

18.3 Selecting Appropriate Stakeholders for Engagement Communication

Key Takeaways Explain This Topic AI

C2c tests who should hear in-flight engagement communication: process owner, senior management, CAE, legal/compliance, and the board — chosen by role, need-to-know, and confidentiality, not by who is easy to copy.

The process owner is the default audience for objectives, scope, timing, status, and fact confirmation; suspected fraud or an implicated owner moves the first audience to the supervisor/CAE and legal per protocol.

A scope limitation must reach the engagement supervisor and CAE; the board hears it when the limitation impairs independence or the engagement, not because every draft observation is a board paper.

Copying the whole company — or even the whole activity — on a draft finding is the classic C2c trap: it violates need-to-know, can taint investigations, and confuses draft fact-checking with final issuance.

The CAE, not the staff auditor, decides dissemination of final results and most board-level communications; Part 2 still requires the staff auditor to pick the right in-flight audience so the CAE is not the last to know.

Last updated: August 2026

Who hears the message is as testable as what you say

C2c asks you to determine appropriate stakeholders for engagement communication . Method (Section 18.1) and escalation (Section 18.2) fail if the right words go to the wrong inbox. GIAS Standard 13.1 centers ongoing communication with management of the activity under review . The CAE is responsible for disseminating final engagement communications to appropriate parties — board, senior management, and those who will own action plans (Standard 15.1). Part 2 still requires you, during the job, to know who must hear a kickoff, a status slip, a scope limitation, a draft observation, or a suspected illegal act.

Use three screens on every message:

Role. What decision or confirmation do you need from this person? Need-to-know. Does this person need the information to do their job or to discharge a governance duty, or are they being copied for politics and CYA? Confidentiality. Could this content harm an investigation, a person, or the organization if it travels? When the three screens conflict, confidentiality and need-to-know win over convenience.

The stakeholder map

Process owner (management of the activity under review). Default audience for initial communication of objectives, scope, and timing; for status; for most fact confirmation; and for the closing meeting. They can correct errors, explain compensating controls, and start fixing issues while you are still in the field. They are not the first audience when they appear implicated in fraud or an illegal act, and they are not a substitute for telling your supervisor about an impairment.

Senior management. In-flight communication goes here when the issue exceeds the process owner’s span of control, when the owner is the problem, or when residual risk or a limitation will matter at an enterprise level. You still go through the engagement supervisor and CAE rather than cold-emailing the COO with a draft finding. Senior management is also who the CAE will often brief when access is refused at the activity level.

CAE. Must hear scope limitations, access refusals, suspected fraud or illegal acts, residual risk that may be unacceptable, independence impairments, and any disagreement that the supervisor cannot unstick. The CAE is not a weekly status distribution list for routine open items, but the CAE must never be the last person to learn of a red flag. Staff auditors brief the CAE through supervision unless the supervisor is implicated.

Legal and compliance. Enter when the content is a suspected illegal act, a likely regulatory notification, attorney-client or investigation privilege, sanctions, privacy law, or a need to preserve evidence. They are not a dumping ground for every control exception. Copying legal on a routine duplicate-payment draft does not make the communication more “complete.” Omitting legal when you have a bribery red flag does not make the communication more “constructive.”

Board (usually the audit committee). The board is not an in-flight fact-checking audience. Draft observations do not go to the board so the team can “be transparent.” The board must hear what the CAE determines it must hear: significant impairments to independence or to the engagement (including a serious scope limitation), suspected fraud involving senior management, and residual risk the CAE believes may be unacceptable. Those board communications are largely Part 3 / Domain III and Standard 11.5 territory in their finished form. On Part 2, the testable move is: get the issue to the CAE with the right confidentiality , and do not bypass the CAE with a staff briefing to directors.

Stakeholder Typical in-flight content Usually should hear a scope limitation? Draft finding?

Process owner Kickoff, status, fact confirmation, closing meeting Yes — they live the limitation and may be able to remove it Yes, if they are not implicated and distribution is tight

Senior management Issues beyond the owner’s control; refused access at the activity; enterprise-level residual risk Yes, once the CAE (or supervisor per methodology) takes it up Only if they own the process or must act; not as a FYI blast

CAE Impairments, fraud/illegal acts, unacceptable residual risk, deadlocks Must hear it After supervision; not every low-risk wording draft

Legal / compliance Suspected illegal acts, privilege, regulatory exposure When the limitation is legal in nature or the issue is an illegal act Not for ordinary control drafts

Board What the CAE takes upward: independence/engagement impairments, senior-management fraud, possibly unacceptable residual risk When it impairs independence or the engagement , not as a courtesy copy No — drafts are not board papers

  • Entire company / all-staff list Almost nothing about a live engagement No No — this is the classic trap
  • Need-to-know and confidentiality

Need-to-know is narrower than “people who would find this interesting.” A draft observation that user-access reviews in finance are weak belongs to the finance process owner (and your supervisor). It does not belong on the all-staff list, the IT newsletter, or a shared drive open to the business unit’s 200 employees. Broadcasting a draft:

  • violates confidentiality and can defame if facts are still in motion,
  • can tip a person who should not be warned,
  • creates unofficial “final” copies that outrun the CAE’s issuance, and

confuses fact-checking with public reporting.

Trap the exam loves: copying the whole company — or the whole activity — on a draft finding “for transparency” or “so the closing meeting has no surprises.” Transparency is achieved by the right people hearing timely, accurate information, not by maximizing the CC line. Constructive communication (Standard 11.2) is helpful to the engagement client; it is not a press release.

Consulting engagements can have a tighter client-defined audience than assurance engagements, but need-to-know still applies. Significant governance, risk, or control issues identified on a consulting job that matter to the organization still have to reach the people GIAS requires — including senior management and the board when significance warrants — through the CAE’s methodology. That is not a license for the staff auditor to freelance a company-wide note.

External parties (regulators, external auditors, customers) are almost never the staff auditor’s in-flight audience. If a regulator must be notified, legal and the CAE own the channel. If external auditors need a scope limitation or a fraud indicator, the CAE coordinates. Do not “cc the partner” on a draft observation to be helpful.

Who must hear a scope limitation

A scope limitation is a restriction that keeps the engagement from achieving its objectives as planned: denied records, excluded locations, unavailable key people, or a management-imposed cut to related-party testing. Standard 13.1 requires timely communication of changes to management of the activity. That is necessary but not sufficient.

Minimum in-flight audience for a scope limitation: the process owner (unless implicated or the one imposing a bad-faith cut), the engagement supervisor , and the CAE . Senior management hears it when they imposed it or must remove it. The board hears it when the limitation impairs independence or the engagement — for example senior management forbids testing of related-party transactions that were in the approved plan, or access remains blocked after the CAE has escalated inside management. A clerk who pulls samples is not an adequate audience. A company-wide draft-finding email is the wrong audience.

Write the limitation down: what was requested, what was refused, which objectives are affected, and who was told. Oral-only notice of a material limitation fails the evidence filter in Section 18.1 and leaves the CAE unable to brief anyone accurately.

Worked scenarios

Ordinary draft. Weak quarterly user-access reviews in finance. Send a tight draft to the finance process owner and copy the engagement supervisor. Do not copy all finance staff, HR, or the board. Ask the owner to confirm dates, system names, and compensating detective controls. That is stakeholder selection plus accurate, timely communication.

Imposed limitation. Senior management says related-party transactions are “out of scope for this quarter.” Tell the owner what you can still cover, and take the limitation to the supervisor and CAE the same day. Do not honor the cut quietly and hope the final communication can stay silent. Do not email the company that “management blocked related-party testing.”

Illegal act with the owner in the picture. Expense-report patterns suggest the process owner approved personal charges as business. Stakeholders are the supervisor, CAE, and legal/compliance per protocol — not the owner, not the owner’s department, not the intern study group, and not the board by a staff side-channel. The CAE and legal decide if and when directors are informed.

If you remember only one C2c discriminator: draft findings travel to the people who own the facts or the investigation; they do not travel to everyone who might have an opinion.

Loading diagram... Need-to-know map for in-flight engagement communication

Teaching illustration: typical audience breadth versus confidentiality (higher = tighter distribution)