20.2 Section-Specific Final Review Plans
Key Takeaways
- Final review should be section-specific because AUD, FAR, REG, BAR, ISC, and TCP differ in content weights, skill mixes, and simulation patterns.
- The AICPA Blueprints are the controlling final-review map: they list content areas, representative tasks, skill levels, item counts, and item-type score weights.
- AUD review should emphasize evidence sufficiency, risk response, reporting consequences, and independence; FAR/BAR should convert rules into schedules.
- REG and TCP review must convert tax rules into taxpayer-year-basis-character-limitation decisions, not isolated definitions.
- ISC review pairs high-volume MCQ practice with simulations on systems, security, privacy, SOC reporting, evidence, and control exceptions.
Final review is not one-size-fits-all
A useful CPA final review is built from the AICPA Blueprints, not from a list of topics that merely feel scary. Each Blueprint identifies content by area, group, and topic; shows score weighting; lists representative task statements; assigns a skill level (Remembering and Understanding, Application, Analysis, or Evaluation); and reports item counts and item-type weighting. That makes the Blueprint your control document for the last cycle.
Do not reread the entire course in the final two weeks. Convert your error log into a section-specific list of weak decisions, then run mixed sets that force a choice under test conditions: which rule applies, which exhibit matters, which cell needs a zero, and which issue can be left alone.
CPA section final-review map
| Section | Last-cycle emphasis | Simulation practice |
|---|---|---|
| AUD | Evidence sufficiency, risk assessment, planned responses, ethics, independence, attestation, reporting | Match assertions to procedures, evaluate exceptions, choose report modifications, interpret documentation |
| FAR | Financial reporting, select balance-sheet accounts, select transactions | Schedules for revenue, leases, equity, statements, consolidations, cash flows, adjustments |
| REG | Tax procedure, ethics, business law, property, individuals, entities | Taxpayer-year problems with forms, basis, limitations, character, filing consequences |
| BAR | Business analysis, technical accounting, reporting, state and local governments | Ratios, forecasts, budgets, revenue contracts, leases, consolidations, government reconciliations |
| ISC | Information systems, data management, security, confidentiality, privacy, SOC engagements | Map risks to controls, test evidence, evaluate incidents, handle SOC report effects |
| TCP | Individuals, personal planning, entity compliance, entity planning, property transactions | Basis schedules, distribution analyses, loss limits, disposition character, planning comparisons |
Core section plans
For AUD, spend final review on how facts change the conclusion. A weak candidate memorizes audit vocabulary; a strong one can explain why a procedure is responsive to an identified risk, why evidence is or is not sufficient and appropriate, and how an exception flows into the report (unmodified, qualified, adverse, or disclaimer). Review report language, but always apply it to facts.
For FAR, separate the recognition rule from schedule execution. You need enough technical memory to know the model — five-step revenue recognition, lease classification, bond amortization, deferred taxes — but the TBS risk is workpaper control: signs, dates, classification, and linked calculations. Drill bonds, leases, ASC 606 revenue, the statement of cash flows, equity, income taxes, contingencies, and consolidation eliminations.
For REG, keep final review taxpayer-centered. Label every question by taxpayer type, year, transaction, amount, character, and limitation. Business law and ethics belong in the plan, but should not crowd out individual and entity tax simulations, which carry the heavier analytical load.
Discipline section plans
For BAR, do not treat it as merely advanced FAR. Add genuine business analysis: budgets, variances, ratios, forecasts, cost behavior, valuation, and risk — plus the governmental accounting (fund accounting, modified accrual, government-wide reconciliations) that surprises FAR-strong candidates. Use TBS sets that require interpretation, not just arithmetic.
For ISC, the 60% MCQ weighting makes framework accuracy decisive — know SOC 1 vs. SOC 2, the trust services criteria (security, availability, processing integrity, confidentiality, privacy), and complementary user-entity controls. But the simulations still test control judgment: read a system description and turn it into control objectives, evidence requests, exceptions, and report implications.
For TCP, the final review must be basis-heavy. Many misses happen after the first computation, when the candidate stops before character, limitation, timing, or planning comparison. Work problems end to end — from contribution or acquisition through distribution or disposition — including partnership outside basis, S corporation stock and debt basis, and at-risk and passive loss limits.
Software pass
During final review, repeat the AICPA sample-test software session. The goal is not a score — it is unscored — but to make the driver boring: tabs, exhibits, spreadsheet, calculator, authoritative-literature search, and answer review should consume zero attention on test day.
Build the final cycle from the error log
The single most wasteful final-review habit is rereading chapters in order. Your error log already tells you where the points are leaking, so let it drive the schedule. Tag every missed practice item with three labels and review by tag, not by chapter:
| Error tag | What it means | Final-review fix |
|---|---|---|
| Content gap | You did not know the rule | Targeted reread of that narrow topic, then re-drill |
| Application slip | You knew the rule but applied it to the wrong facts | Mixed sets that vary taxpayer, period, or fact pattern |
| Execution error | Right approach, wrong sign, date, or empty cell | Timed TBS workpapers with a review-cell checklist |
| Pacing / software | Ran out of time or fumbled the tool | Full-length timed mocks in the AICPA software |
A practical final-two-weeks structure is: days 1-7 run mixed MCQ sets and tagged drills to convert content gaps into application practice; days 8-12 run timed TBS sets in the weakest content areas; days 13-14 take at least one full-length, software-based mock under exam conditions, then rest the day before. Resist adding new material in the last 72 hours — at that point reinforcement and recall beat first exposure, and confidence in the software driver matters more than one more obscure rule.
A candidate's FAR MCQ scores are high, but FAR simulations are weak because adjustments are entered with wrong signs and incomplete schedules. Which final-review move is best?
Which final-review plan best fits ISC?