Study guide
17.1 Supervision Throughout Planning and Fieldwork
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
17.1 Supervision Throughout Planning and Fieldwork
Key Takeaways Explain This Topic AI
CIA Part 2 2025 Section C is 10% of the exam; C1a tests supervision throughout the engagement, including planning, not a last-day workpaper stamp.
GIAS Standard 12.3 requires the CAE or engagement supervisor to provide guidance throughout the engagement, verify work programs are complete, and confirm workpapers support findings, conclusions, and recommendations.
Domain V (Principles 13–15) is where engagement work is performed and supervised; Principle 15's final-communication and action-plan monitoring details are primarily CIA Part 3 2025.
Standard 13.6 requires the CAE to review and approve the engagement work program and any subsequent changes; the approval test is whether the program achieves objectives efficiently.
The extent of supervision depends on internal audit function maturity, auditor proficiency and experience, and engagement complexity; evidence of supervision must be documented and retained.
Last updated: August 2026
CIA Part 2 2025 Section C, Engagement Supervision and Communication, is 10% of the exam. Objective C1 is to apply appropriate supervision throughout the engagement. C1a is the planning-and-fieldwork requirement: describe how supervision applies throughout engagements, including during engagement planning. The item writers like a picture you should reject on sight: staff finish planning alone, the supervisor is too busy until wrap-up, and a senior then initials a stack of workpapers the afternoon before the exit meeting. That is a closing stamp. It is not supervision.
Supervision is a live control on the design and execution of this engagement. It exists so that engagement objectives are achieved, work quality conforms to the Global Internal Audit Standards (GIAS) and the internal audit function's methodology, and the people doing the work develop competence. Those three outcomes cannot be inspected into existence after the activity under review has already heard a rating. If the objective is vague, the engagement risk assessment is copied from last year, the work program tests the wrong activities, or the staffing mix cannot perform the tests, late review only documents a failed design.
GIAS map: Standard 12.3 applied across Domain V
Keep the domain map accurate. The methodology for supervision sits in Domain IV (Managing the Internal Audit Function), Principle 12 Enhance Quality, Standard 12.3 Oversee and Improve Engagement Performance. The chief audit executive must establish and implement methodologies for engagement supervision, quality assurance, and the development of competencies. The CAE or an engagement supervisor must provide internal auditors with guidance throughout the engagement, verify that work programs are complete, and confirm that engagement workpapers adequately support findings, conclusions, and recommendations. Supervisory duties may be delegated to appropriate, qualified people; the CAE still retains ultimate responsibility, including when work is performed by staff or by other service providers. Evidence of supervision is documented and retained.
That is not a license to turn this chapter into CIA Part 3. Part 3 2025 is where candidates are tested on managing the internal audit activity, function-level quality programs as an operations system, board reporting, final engagement communication attributes, residual-risk acceptance, and action-plan monitoring. Part 2 tests how supervision is applied to the engagement you are running.
Domain V, Performing Internal Audit Services, is where that application happens. Domain V includes Principle 13 Plan Engagements Effectively, Principle 14 Conduct Engagement Work, and Principle 15 Communicate Engagement Results and Monitor Action Plans. Domain V does not name a separate supervision principle, but it includes supervision of engagement work: approving the work program and its changes, reviewing documentation, and keeping conclusions from outrunning evidence. Use Principle 15 on Part 2 only as it applies to supervising work — blocking unreviewed conclusions from being communicated. Do not treat Standard 15.1 final-communication elements or Standard 15.2 confirmation of action-plan implementation as Section C1 topics.
Planning: objectives, risk assessment, work program, staffing
GIAS commentary on Standard 12.3 is direct: during the planning phase, the engagement supervisor approves the engagement work program and may assume responsibility for other aspects of the engagement. Standard 13.6 Work Program requires that the program be based on planning information, including the engagement risk assessment, and that it identify evaluation criteria, tasks to achieve objectives, methodologies and tools, and the internal auditors assigned to each task. The CAE must review and approve the work program and any subsequent changes. The primary criterion for approval is whether the program achieves the engagement objectives efficiently.
A supervisor who never touches objectives (Standard 13.3), the engagement risk assessment (Standard 13.2), resources (Standard 13.5), or the program (Standard 13.6) until fieldwork is done has not supervised planning. Staff who plan alone and then ask for a signature are the de facto engagement leaders. The supervisor is a notary.
Staffing is planning supervision. Standard 13.5 requires identifying the types and quantity of resources necessary to achieve the objectives, considering nature and complexity, the time frame, and whether financial, human, and technological resources are appropriate and sufficient. Matching a first-year auditor to a high-judgment fraud-sensitive estimate with no in-flight coaching is a supervision failure, not a stretch assignment. Matching only financial testers to a cybersecurity scope the team cannot execute is a resource failure the supervisor must raise before the program is treated as executable. If the limitation cannot be fixed, the program and, if needed, the scope must change — with approval — rather than silently shrinking tests in the field.
Fieldwork: guidance, program completion, and documented presence
After approval, supervision means monitoring that the work program is completed and that changes are approved before they become unofficial scope. The supervisor should see early that a sample will not support the objective, that a walk-through contradicted the control narrative, or that a tester is about to rate a control effective from inquiry alone. GIAS states that the extent of supervision required depends on the maturity of the internal audit function, the proficiency and experience of internal auditors, and the complexity of engagements. Intensity scales; disappearance is not allowed. A new auditor on a first physical inventory needs tighter direction than an experienced senior repeating a well-understood test. A first review of an ERP cutover needs more supervisor time than a recurring low-complexity checklist. Remote fieldwork does not reduce the duty; it changes the tools — more frequent checkpoints, earlier workpaper review, and a clearer rule about who may speak for the team.
Document the supervision: program approval, staffing decisions, approved changes, and timely workpaper review. Claiming you were on the status call is not a quality record.
The closing-stamp trap
A payroll team copies last year's program, starts sampling on day one, and tells payroll management in week three that overtime controls look fine. On the last afternoon the supervisor initials every paper and signs the conclusion. The initials are neat and the file looks reviewed. C1a still fails. The supervisor never challenged the objective, never tested whether this year's risks belonged in the program, never approved the quiet drop of exception testing, and allowed an unreviewed conclusion to reach the activity under review. The required pattern is supervisor involvement in objectives, risk assessment, work program, and staffing before substantial testing, then continued guidance while tests run.
Engagement moment Supervised action Closing-stamp substitute
Objectives and scope Confirm objectives are specific, risk-aligned, and still valid after requests or limits Sign a memo staff already used to start testing
Engagement risk assessment Require this year's risks to drive tests; reject a copied matrix Skim the matrix after fieldwork
Work program (Standard 13.6) Approve because it can achieve objectives efficiently; approve later changes Initial the cover after samples are finished
Resources (Standard 13.5) Match skills, time, and tools; escalate real limits Assign whoever is free
Fieldwork (Principle 14) Guide testers and keep the program current Discover problems only in a last-day review
Communications (Principle 15 as applied to work) Block unreviewed conclusions from leaving the team Learn the client already heard the rating