Diagnose weak Day 3 responses and drill the response moves that fix them.
Remediation is the process of turning a weak Day 3 response into a repeatable improvement. It is not enough to read the solution and agree with it. Candidates need to identify why their answer was weak, isolate the response move that failed, and practise the corrected move until it becomes automatic.
The best remediation is specific. “Study tax more” is too broad if the real weakness was failing to explain the cash tax implication. “Write clearer” is too broad if the real weakness was missing the recommendation sentence. Diagnose the pattern before choosing the drill.
This lesson focuses on diagnosing weak responses, classifying error patterns, rewriting answers, and creating short drills that improve future case performance.
| Weakness category | What it looks like |
|---|---|
| Issue spotting | The response misses the required issue or answers a different question. |
| Technical knowledge | The rule, calculation, procedure, or standard is wrong or incomplete. |
| Fact use | The answer states a rule but does not apply the case facts. |
| Analysis depth | The response jumps from fact to conclusion without explaining the implication. |
| Recommendation | The answer never says what should be done. |
| Time management | One issue is overbuilt while other issues are missed. |
| Professional judgment | Ethics, audience, stakeholder, or feasibility issues are ignored. |
Start by marking the exact failure. A weak paragraph may have more than one problem, but one problem usually drove the lost value. Ask:
This diagnostic sequence prevents shallow debriefing. A candidate who only rereads technical notes may not fix a writing problem. A candidate who only practises speed may not fix a knowledge gap.
| Weak response pattern | What to drill |
|---|---|
| “I knew the topic but missed the issue.” | Read case requests and write one-sentence issue statements before solving. |
| “I listed facts but did not analyze.” | For each fact, add “therefore” and explain the implication. |
| “My calculation was fine but the answer was weak.” | Add interpretation and recommendation sentences after every calculation. |
| “I wrote a generic recommendation.” | Rewrite the recommendation using the case objective and constraint. |
| “I ran out of time.” | Practise issue ranking and stopping rules on short case sets. |
| “I missed ethics or stakeholders.” | Add a final scan for professional duty, audience, and affected users. |
A rewrite drill should be short and targeted. Do not rewrite the entire case unless the whole answer structure failed. Instead, rewrite the paragraph that caused the weakness and compare it with the expected response style.
Effective drills include:
| Drill | How to perform it |
|---|---|
| Issue-statement drill | Write only the issue sentence for five past case requests. |
| Fact-to-implication drill | Convert five case facts into “fact, therefore, implication” sentences. |
| Recommendation drill | Write one direct recommendation and one condition for each issue. |
| Calculation interpretation drill | After each calculation, write what the number means and what action follows. |
| Audience-fit drill | Rewrite the same conclusion for a board, owner-manager, and controller. |
| Time-box drill | Answer one issue in a fixed short time and stop when complete enough. |
These drills are narrow by design. They fix the response move that failed rather than creating more passive review.
A remediation log helps identify recurring patterns. Keep it brief enough to use after every case.
| Field | Example entry |
|---|---|
| Case issue | Cash shortfall and financing choice. |
| Weakness | Calculated shortfall but did not recommend a funding source. |
| Cause | Stopped after arithmetic; no implication sentence. |
| Fix | Add “therefore” sentence and funding recommendation. |
| Drill | Three calculation interpretation drills. |
| Next check | Look for recommendation after each calculation. |
The log should track behaviour, not self-criticism. The point is to identify the next correction.
If the weakness is technical knowledge, remediation should still be applied through cases. Read the rule, then immediately answer a small fact pattern that requires application. Technical review without application can feel productive while leaving the response problem unchanged.
Use this pattern:
The variation matters because exam performance depends on recognizing what changes the conclusion.
If the weakness is writing, focus on structure and clarity. Rewrite weak paragraphs using issue, analysis, implication, recommendation, and caveat. If the weakness is time, practise stopping rules and prioritize coverage. If the weakness is issue spotting, practise reading case requests without solving them and identifying the required response.
Do not treat every weakness as a content gap. Some candidates know enough but fail to show it because the answer is vague, unsupported, poorly ranked, or unfinished.
Use this remediation cycle after each practice case:
| Pitfall | Correction |
|---|---|
| Reading solutions passively. | Rewrite the weak response in your own words. |
| Treating every error as a knowledge gap. | Diagnose whether the problem was issue spotting, analysis, writing, or time. |
| Rewriting the whole case every time. | Target the failed response move. |
| Keeping vague study notes. | Track the cause, fix, drill, and next check. |
| Repeating the same error without a drill. | Convert each recurring weakness into a small practice routine. |