A CFE Day 2 study plan that sequences role framing, Assurance, Taxation, Finance, Performance Management, integration, and response quality.
CFE Day 2 study should be organized around declared-role execution. The central question is not “what do I know about this topic?” The stronger question is “what is my role, what evidence belongs to that role, and what recommendation is sufficiently supported?”
Use this plan to move through the 32 CFE Day 2 section pages while building a repeatable role, evidence, depth, recommendation, and communication rhythm.
CFE Day 2 is a long-case discipline test. The study plan should train candidates to protect the declared role, use exhibits efficiently, write enough depth on role issues, and still handle common competency issues without losing time.
| Habit | What to practice | Why it matters on Day 2 |
|---|---|---|
| Keep the role visible. | State whether the issue belongs to Assurance, Taxation, Finance, Performance Management, or common competency work. | Generic answers lose the role-depth lens that Day 2 is built around. |
| Map evidence before writing. | Connect common facts, role appendices, exhibits, numbers, and constraints to each issue. | Long cases reward evidence use; rereading without mapping wastes time. |
| Allocate depth deliberately. | Decide which issues need full analysis and which need concise treatment. | Overwriting one issue can starve later assessment opportunities. |
| Support the recommendation. | Tie advice to case facts, calculations, procedures, tax effects, valuation assumptions, KPIs, or controls. | Unsupported conclusions are weak even when the technical direction is reasonable. |
Use each lesson page as a role-depth habit. The first pass should establish coverage; later passes should turn the section pages into timed issue maps and response drills.
| Block | Main pages | Case-writing objective |
|---|---|---|
| 1. Role framing | Declared Role, Relevant Facts, Depth Allocation, and Exhibits | Identify role responsibility, filter evidence, rank issues, and map exhibits to assessment opportunities. |
| 2. Analysis setup | Quant Setup, Judgment, Common Touchpoints, and Communication | Control assumptions, constraints, common issues, and audience before writing depth responses. |
| 3. Assurance role | Assurance Planning, Assurance Evidence, Controls, and Assurance Reporting | Convert assurance risks, evidence, controls, reporting, independence, and ethics into role-depth advice. |
| 4. Tax role | Taxpayer Profile, Owner-Manager Tax, Personal Tax, and CRA Responses | Classify taxpayer facts, calculate where needed, and advise on compliance, planning, CRA responses, and appeals. |
| 5. Finance role | Finance Analysis, Capital & Valuation, Risk & Transactions, and Finance Synthesis | Use cash, capital, valuation, risk, transaction, and implementation evidence to support finance recommendations. |
| 6. Performance Management role | Strategy Alignment, Reporting & Cost, Measures & Incentives, and Systems & Controls | Connect strategy, cost, revenue, measures, incentives, systems, controls, and behaviour to PM recommendations. |
| 7. Integration quality | Depth Structure, Ethics, Problem Solving, and Integration | Improve answer completeness, ethics, alternative evaluation, and synthesis across role and common issues. |
| 8. Final response quality | Recommendation Logic, Uncertainty, Concise Writing, and Remediation | Strengthen recommendations, caveats, concise writing, and remediation of recurring Day 2 weaknesses. |
flowchart LR
A["Confirm declared role"] --> B["Map exhibits"]
B --> C["Rank issues"]
C --> D["Choose depth"]
D --> E["Write supported analysis"]
E --> F["Recommend with caveats"]
Use this loop before every timed Day 2 practice response. If the answer begins with technical analysis before the role and evidence map are clear, the response is likely to drift into generic writing.
Because Day 2 is role-depth driven, study emphasis should follow Day 2 behaviour: role framing first, role-depth work next, and response quality throughout.
| Area | Study emphasis | Response standard |
|---|---|---|
| Role framing and case navigation | Declared role, relevant facts, depth allocation, exhibit trails, quantitative setup, qualitative constraints, common touchpoints, and communication. | Role boundary plus evidence map before writing. |
| Assurance and taxation role depth | Assurance planning, evidence, controls, reporting, taxpayer profile, owner-manager tax, personal tax, CRA responses, and appeals. | Advice tied to risk, evidence, reporting, taxpayer facts, deadlines, or CRA process. |
| Finance and Performance Management role depth | Finance analysis, capital, valuation, risk, transactions, strategy, cost, revenue, KPIs, incentives, systems, and controls. | Recommendation supported by calculation, assumptions, behaviour, implementation, and monitoring. |
| Integration and response quality | Depth structure, ethics, problem solving, synthesis, recommendation logic, uncertainty, concise writing, and remediation. | Complete-enough answers across issues, not a perfect answer to one issue. |
Use the eight blocks in sequence, but keep role framing and integration quality active every week. A useful pattern is to read one role-specific section, write an issue map, then rewrite the response to add missing evidence or caveats.
| Task | Output | Minimum standard | | — | — | | Read one section page. | One role responsibility, evidence source, and response-quality trigger. | The trigger must say whether the issue is role depth, common competency, or integration quality. | | Build a short response. | Role, issue, exhibit evidence, analysis, recommendation, communication point. | The answer must cite or use at least one case fact or exhibit implication. | | Debrief the response. | One missed exhibit, unsupported conclusion, weak caveat, or time-allocation problem. | The debrief should name whether the failure was role, evidence, depth, recommendation, or communication. | | Turn the lesson focus into a trigger. | A note that links role responsibility, exhibit evidence, required depth, and recommendation support. | The trigger should help identify a similar issue in a new long case. |
Use this drill before writing a long-case response.
| Step | Question | Strong output |
|---|---|---|
| Role | Which declared role or common competency area owns the issue? | Assurance, Taxation, Finance, Performance Management, common issue, or integrated issue. |
| Exhibit | Which fact, appendix, calculation, document, or narrative cue supports the issue? | Evidence source and what it proves or limits. |
| Depth | How much analysis does the issue deserve? | Full depth, moderate support, concise comment, or caveat-only treatment. |
| Method | What analysis is needed? | Procedure, tax calculation, finance method, KPI analysis, control assessment, or qualitative judgment. |
| Recommendation | What action follows? | Practical advice with implementation, communication, caveat, or follow-up. |
After each practice case, score the response by behaviour.
| Dimension | Debrief question |
|---|---|
| Role discipline | Did the response stay inside the declared role and identify common issues separately? |
| Evidence use | Did the answer map exhibits and facts to the issue instead of writing from memory? |
| Depth allocation | Did high-value issues receive enough support without overbuilding minor points? |
| Analysis quality | Did calculations, procedures, tax treatments, valuation assumptions, KPIs, or controls answer the actual required? |
| Recommendation support | Did the recommendation rest on evidence, reasoning, caveats, and implementation? |
| Communication | Was the response concise enough to preserve time for later issues? |
In the final week, prioritize full long-case behaviour and debrief rather than isolated topic rereading.
| Day | Focus | Work product |
|---|---|---|
| 1 | Role framing and evidence mapping | One long-case map that separates role issues, common issues, exhibits, assumptions, and required depth. |
| 2 | Assurance or Taxation depth | One role-specific response set with evidence, conclusion, communication, and caveats. |
| 3 | Finance or Performance Management depth | One role-specific response set with calculations, assumptions, behaviour, implementation, and follow-up measures. |
| 4 | Common competency integration | One mixed set where common issues interact with the declared role. |
| 5 | Recommendation and uncertainty | Rewrite weak prior responses to add support, caveats, and next steps. |
| 6 | Full timed practice | One long-case attempt with issue map, depth allocation, and post-case scorecard. |
| 7 | Light repair review | Review recurring role, evidence, depth, and communication failures without exhausting yourself. |
Prioritize sections where you lose the role lens, overwork one issue, ignore common competencies, calculate without interpretation, or recommend without implementation and follow-up.
The strongest final review output is a short list of repair rules. Examples include “state role ownership before analysis,” “map the exhibit before writing,” “rank issue depth before calculating,” “add caveats without avoiding the recommendation,” and “stop a response once it is sufficient enough to move on.”