40.4 Discipline Final Mock and Review Log

Final discipline mock and review log

The final mock is a diagnostic tool, not a ceremony. A good discipline mock tells you whether you can manage the section's item mix, move through five testlets (two MCQ, three simulation), use exhibits efficiently, and recover from unfamiliar facts. Remember the CPA Exam scores on a 0 to 99 scale, and 75 passes; the score is a weighted blend of scaled MCQ and simulation scores. The review log then converts the score report into a short list of fixable behaviors.

Build the mock around your discipline

All three discipline sections are four hours, but they do not feel the same. The differences below should shape your mock and your pacing.

Because ISC weights MCQs at 60 percent, protect time for its 82 MCQs; in BAR and TCP, the 50/50 split means a strong simulation testlet can rescue a weak MCQ run, and vice versa.

The four-pass review method

Do not review a mock top to bottom. Use four passes:

1. Score pass: mark each miss and each guessed-correct answer.
2. Source pass: identify the sentence, exhibit, table, or rule that controlled the answer.
3. Error-type pass: classify the miss as knowledge, process, exhibit, timing, or confidence.
4. Retest pass: create a small drill testing the same skill without copying the original question.

Guessed-correct answers belong in the log because they are hidden risk. If you guessed that a SOC 1 report was correct but cannot explain user entities' internal control over financial reporting, the answer is not stable. If you guessed that a shareholder had S corporation debt basis without analyzing direct debt, that answer is not stable either.

Discipline-specific error codes

Use short codes so the log stays readable.

• BAR: RATIO, VAR, FORECAST, TECH, GOV, INTERP. A GOV miss means you failed to switch into state and local government accounting or missed a reconciliation adjustment. An INTERP miss means the math was right but the conclusion did not answer the business issue.
• ISC: ACCESS, CHANGE, BACKUP, INCIDENT, DATA, PRIVACY, SOC, CUEC, EVIDENCE. An EVIDENCE miss means you accepted inquiry, policy language, or incomplete logs when the question needed operating evidence.
• TCP: BASIS, DEBT, LOSS, DIST, PROP, RECAP, ENTITY, TRUST, PLAN. A PLAN miss means you did not compare alternatives against the taxpayer's stated objective.

Final review week schedule

Six or seven days out, take the discipline mock under timed conditions. The next day, review it with the four-pass method. Do not take another full mock immediately if the log shows obvious repair work. Spend two days on short drills tied to your top three error codes, then take a mixed timed set with MCQs and at least two simulations. The final two days should be light but specific: rewrite formulas, control-evidence patterns, basis-ordering rules, and government reconciliation adjustments from memory.

Simulation review drill

For every missed simulation tab, write three lines: what the tab asked, which exhibit controlled the answer, and what rule converted the exhibit into the answer. This matters most for BAR government reconciliations, ISC SOC report excerpts, and TCP basis schedules. Simulations are rarely missed because candidates cannot read; they are missed because candidates fail to decide which exhibit matters most.

The final go or repair decision

After the review, do not ask whether the raw score feels good. Ask whether the misses are concentrated and fixable. Ten misses all tied to S corporation basis is a cleaner repair path than ten misses scattered across every TCP area. Repeated ISC evidence misses mean you should drill control-operation proof, not memorize more cybersecurity terms. Repeated BAR interpretation misses mean you should practice writing conclusions under a timer. The log should tell you exactly what to repair next.

Pacing, the calculator, and exhibit discipline

Four hours sounds generous until the simulation testlets arrive. Use these benchmarks so the mock trains real pacing:

• MCQ pace. Budget roughly 1.25 minutes per multiple-choice question. That puts BAR's 50 MCQs near 60 minutes, TCP's 68 near 85 minutes, and ISC's 82 near 100 minutes; what remains funds the simulations. Flag-and-return rather than stalling on one item.
• Simulation pace. With three TBS testlets and one to two hours left after MCQs, target 12 to 18 minutes per simulation. Open every exhibit tab first and note which one carries the controlling number before you type anything.
• Authoritative literature and tools. Some simulations include a research tab or provided spreadsheet; practice using the on-screen calculator and the copy-from-exhibit workflow so the interface never costs you minutes on exam day.
• The 15-minute optional break. A standardized 15-minute break is offered partway through and does not count against testing time. Plan whether you will take it; deciding in the moment wastes focus.

Turning the log into a one-page playbook

The night before, compress the entire review log into a single page. List your top three error codes per content area, the one-sentence rule that fixes each, and the exhibit cue that signals the trap.

For BAR that might be "GOV: city named, switch to modified accrual, reconcile capital assets and long-term debt." For ISC it might be "EVIDENCE: backup scheduled but no restoration test equals insufficient evidence." For TCP it might be "DEBT: guarantee alone gives no S corporation debt basis without economic outlay." Reading this one page is far more valuable than rereading whole chapters, because it loads the exact triggers that have cost you points into working memory right before the exam. A focused playbook beats a broad reread every time, and it keeps the final hours calm rather than frantic.