Sitonce
Country: US
Show exams for United States Hong Kong
Sign in

A 10-Week CIA Part 2 Study Plan

Updated 8 min read
Key takeaway

This 10-week plan follows the current CIA Part 2 weights: 50% Engagement Planning, 40% Information Gathering, Analysis, and Evaluation, and 10% Engagement Supervision and Communication.

  • It combines focused study, original scenarios, error review, and timed mixed practice.
  • Adjust the pace to your diagnostic results and exam authorization.
On this page13 sections
  1. Before week one: diagnose and schedule
  2. Week 1: map the engagement
  3. Week 2: objectives, scope, and criteria
  4. Week 3: preliminary survey and risk assessment
  5. Week 4: procedures and work program
  6. Week 5: evidence quality
  7. Week 6: data, sampling, and analysis
  8. Week 7: evaluate and report
  9. Week 8: connect the domains
  10. Week 9: timed practice and repair
  11. Week 10: consolidation and exam readiness
  12. How to adapt this plan
  13. Weekly review and recovery

Before week one: diagnose and schedule

Start with a short diagnostic set across all three current domains. Do not use it as a pass prediction. Record correct, incorrect, guessed, and slow answers. Tag errors by objective/scope, risk assessment, procedures, evidence, sampling, documentation, supervision, or communication. This gives the plan a starting point.

Choose weekly hours you can protect. Four or five focused sessions are often more realistic than a promise of daily study. Each week should include learning, application, retrieval, and timed questions. If you are new to audit, plan additional foundation time; if you have experience, spend more time on the changed blueprint and unfamiliar processes.

Before registering or finalizing a date, compare the 180-day exam authorization with your three-year program expiration. The earlier date controls the time available. Put the appointment, rescheduling cutoff, result timeline, and retake wait on your calendar.

Week 1: map the engagement

Study the current three-domain blueprint and the engagement lifecycle. Create a one-page map from request to communication: objective, scope, criteria, preliminary understanding, risk assessment, procedures, evidence, analysis, conclusion, review, and report.

Choose one familiar process, such as employee access or supplier onboarding. Write three possible objectives and narrow them to one answerable question. Define the period, system, locations, and transactions in scope. List relevant criteria and note what remains uncertain.

Practice explaining assurance versus advisory work and how management ownership remains with management. Complete a short question set and write a rationale for each answer rather than just marking a letter.

Week 2: objectives, scope, and criteria

Practice converting broad requests into a precise objective. “Review payroll” is not enough. “Determine whether pay-rate changes were authorized and accurately entered for the selected period” is answerable. Identify the organizational objective and the risk that makes the engagement useful.

Build scope boundaries that match the objective. Consider process steps, data sources, time period, business units, and excluded items. Select criteria such as policy, law, contract, control design, or approved operating standard. If criteria conflict or are unclear, resolve the issue before concluding noncompliance.

Work cases with scope changes, prior findings, or another assurance provider. Explain whether the work can be relied upon and what gap remains.

Week 3: preliminary survey and risk assessment

Practice walkthroughs, interviews, observation, prior report review, and data analysis as ways to understand a process. Note what each source helps discover. A walkthrough traces a transaction; it does not prove a control operated all year. An interview can identify exceptions but may need corroboration.

Create a risk-and-control matrix. Link each objective to a risk, control, owner, evidence, and planned test. Prioritize by likelihood, impact, change, complexity, known incidents, and control dependence. Distinguish inherent risk from residual exposure after controls.

Solve questions about competing risks. Explain why a low-value but high-frequency error could matter, or why a rare event with severe impact deserves attention.

Week 4: procedures and work program

For each high-priority risk, design a procedure that addresses the objective. State the population, period, selection method, evidence, attributes, and expected result. Separate control design tests from operating-effectiveness tests.

Plan resources: staff competence, specialist skills, budget, time, data access, and technology. If the team lacks cyber or valuation expertise, identify a qualified resource or adjust the plan before accepting work the team cannot perform.

Complete a planning-focused timed set. Use the error log to identify unclear distinctions and revise your notes. Do not move on with a work program you cannot explain.

Week 5: evidence quality

Study relevance, reliability, and sufficiency. For each source, state the assertion it supports and its limitation. Compare inquiry with inspection, observation, external confirmation, system logs, and reperformance. Consider who created evidence, who can change it, and whether it covers the needed period.

Practice contradictory evidence cases. If management says all changes were approved but the log shows late approvals, test the chronology and inspect records. Document both evidence streams and how the contradiction was resolved.

Write a short workpaper for a fictional test. Include objective, procedure, evidence, result, exceptions, limitations, and conclusion. Ask whether a qualified reviewer could reperform or understand your reasoning.

Week 6: data, sampling, and analysis

Practice validating extracts before analysis. Check source, date range, field definitions, duplicates, missing values, totals, and reconciliation to an independent record. A beautiful chart based on an incomplete extract is not reliable evidence.

Compare statistical and nonstatistical approaches, random selection, judgmental selection, and discovery testing. State the inference each selection can support. A high-risk targeted sample can find exceptions but should not be described as a population-wide rate without a suitable basis.

Use trend, variance, ratio, benchmarking, and workflow analysis in fictional cases. Describe what a pattern suggests, what alternative explanations exist, and what follow-up evidence is needed.

Week 7: evaluate and report

Study how to compare condition with criteria and describe risk, cause, effect, and action. A finding should be supported by the evidence. Do not claim a root cause when the work has not established one. Keep wording proportional to the sample and scope.

Practice management disagreement. Validate facts, distinguish factual correction from disagreement about severity, and retain the evidence-based conclusion. If management accepts significant risk, follow the established escalation path. Internal audit does not own the corrective control.

Review supervision tasks: assign work, monitor progress, review workpapers, resolve gaps, and ensure conclusions match evidence. Produce a concise report for a fictional audit and have another person trace each assertion to support.

Week 8: connect the domains

Work two end-to-end cases from planning through reporting. One should involve a process control failure; another should involve suspicious data or a scope limitation. For each, define the objective, risk, criteria, test, evidence, conclusion, and communication.

Take a mixed timed set. Mark questions that were correct but guessed, because these may reveal fragile knowledge. Revisit the two weakest error tags and solve fresh cases rather than rereading everything.

Make a one-page decision guide with distinctions you tend to confuse: design versus operation, inquiry versus corroboration, sample finding versus population inference, condition versus cause, recommendation versus management decision.

Week 9: timed practice and repair

Complete larger mixed practice under the available time. The live exam has 100 questions in 120 minutes, an average of 72 seconds each. A proportional checkpoint is about 30 minutes per 25 questions. Practice leaving a difficult item and returning when possible.

After each set, review rationales for wrong, uncertain, and guessed answers. For every close alternative, write what fact makes it premature, unsupported, or outside the auditor’s authority. Use that reasoning to improve the next timed set.

Do not repeatedly memorize one question bank. Use unseen scenarios, mixed topics, and changed facts to test transfer.

Week 10: consolidation and exam readiness

Review the three domain weights and key task sequence. Take one final timed set early in the week, then use the remaining days to repair a small number of high-value gaps. Do not add an entire new resource at the last minute.

Confirm appointment details, identification, location or permitted delivery requirements, change deadline, and authorization validity. Plan rest and travel. Keep a short note of key distinctions rather than trying to review every page on exam day.

Readiness is a pattern: consistent reasoning on unfamiliar cases, acceptable pacing, clear understanding of evidence limits, and coverage across all domains. If a major gap remains, use an allowed reschedule or program option rather than pretending the calendar itself proves readiness.

How to adapt this plan

If you work in audit daily, shorten introductory review but keep planning and current-syllabus practice. If you are new to internal audit, extend the first four weeks and learn terminology through applied examples. If you have little study time, spread the plan over more calendar weeks instead of eliminating evidence practice.

If a diagnostic shows one domain is markedly weaker, add focused sessions there while preserving mixed practice. If the same error repeats, change technique: draw a process map, compare evidence sources, or write a decision sequence. More reading is not always the best fix.

The ten weeks are a template, not an official IIA schedule. The appropriate pace depends on current knowledge and life constraints. Use objective progress and the exam’s real deadlines to tailor it.

Weekly review and recovery

Each Sunday, compare the planned work with what you actually completed. If a week was missed, move the unfinished learning objective forward and reduce optional rereading; do not compress several weeks of new material into one night. Keep a small buffer before the exam for an unexpected work deadline or family obligation.

A study partner can review your rationale without teaching you the answer. Ask them to challenge the objective, criteria, evidence source, or inference. If you cannot defend a choice in plain language, return to that skill before adding more timed questions.

A candidate studying part-time can extend each two-week planning phase into three calendar weeks while keeping the same sequence. A candidate with stronger diagnostic results can combine weeks 1 and 2, but should preserve the week 9 timed mixed practice. Adapt time, not coverage.

Recheck these adjustments after your diagnostic rather than following the calendar blindly. If the main weakness is writing conclusions, add case practice at the end of weeks 6 and 7. If the main weakness is timing, retain the learning sequence and add short timed sets during each week.

Keep the plan tied to demonstrated skills, not a fixed calendar label. Use a weekly checkpoint. Then adjust. as needed. Weekly. during review.