CFE Day 2 quick-reference checks for declared role, exhibit use, depth allocation, role-specific recommendations, common issues, and concise communication.
Use this cheat sheet after reading the CFE Day 2 guide pages. It compresses the response habits needed for long-case navigation, declared role discipline, common competency integration, and role-depth recommendations.
| Step | Question | Output |
|---|---|---|
| 1. Role | What role has the candidate declared or been assigned? | Role boundary. |
| 2. Evidence | Which common facts, role appendices, exhibits, and documents support the issue? | Evidence map. |
| 3. Depth | Which issues need full role-depth analysis and which need shorter breadth treatment? | Time allocation. |
| 4. Analysis | What calculation, procedure, tax treatment, valuation, KPI, control, or judgment applies? | Supported analysis. |
| 5. Advice | What should the client, board, partner, or management do next? | Recommendation. |
flowchart LR
A["Declared role"] --> B["Common case facts"]
B --> C["Role exhibits"]
C --> D["Issue ranking"]
D --> E["Depth response"]
E --> F["Recommendation support"]
Use the flow to protect role discipline. Common facts still matter, but the response should keep returning to the declared role, the relevant exhibits, and the depth required for that role.
| Topic | Trigger | Response move |
|---|---|---|
| Role Framing | Declared role, common facts, exhibit trail, quantitative setup, qualitative constraint, common issue, or communication audience appears. | Filter evidence through the role and rank required depth. |
| Assurance and Taxation | Assurance risk, evidence, controls, reporting, independence, taxpayer profile, owner-manager transaction, personal tax, CRA response, or appeal appears. | Apply Assurance or Tax role logic before writing technical detail. |
| Finance and Performance Management | Cash flow, financing, valuation, risk, transaction, strategy, cost, revenue, KPI, incentive, system, or control appears. | Convert analysis into decision support and implementation advice. |
| Integration Quality | Issue ranking, ethics, problem solving, integration, recommendation, missing facts, caveat, concise writing, or response weakness appears. | Improve completeness, synthesis, communication, and remediation. |
| Mistake | Correction |
|---|---|
| Writing generic analysis outside the declared role. | State the role boundary before analyzing. |
| Rereading exhibits instead of mapping them. | Link each exhibit to a specific issue and evidence need. |
| Overwriting one assessment opportunity. | Allocate time based on significance and role depth. |
| Making conclusions without support. | Tie every recommendation to case facts, calculation, procedure, source, or document. |
| Ignoring caveats. | State assumptions and follow-up without avoiding the recommendation. |
| Check | Why it matters |
|---|---|
| Role relevance | A role-depth issue needs more support than a common-area issue. |
| Exhibit density | More exhibits usually mean the issue needs evidence mapping, not a generic answer. |
| Decision consequence | High-impact recommendations need assumptions, alternatives, and implementation effects. |
| Technical uncertainty | Missing facts or uncertain standards require a caveat plus a practical next step. |
| Time pressure | A complete-enough answer beats an overbuilt first response that starves later issues. |
Use this table after the first case read and again before writing the main role-depth sections.
| Question | If yes | If no |
|---|---|---|
| Does the exhibit contain numbers, dates, controls, contracts, correspondence, or management assertions? | Extract the fact and state what it proves, limits, or requires. | Do not force the exhibit into the response just to mention it. |
| Does the issue belong to the declared role? | Give it full structure: issue, standard or method, evidence, analysis, conclusion, and advice. | Treat it as common competency, integration, or a shorter caveat unless the case signals otherwise. |
| Does the issue affect the user of the report or recommendation? | Add communication impact, reporting consequence, tax filing effect, financing decision, or implementation risk. | Keep the point concise and move to the next assessment opportunity. |
| Is there uncertainty or missing information? | Name the assumption and recommend a next step. | Avoid artificial caveats that weaken an otherwise clear conclusion. |
These sentence frames keep the response practical without becoming formulaic.
| Need | Sentence frame |
|---|---|
| Role boundary | “In my role as [role], the relevant issue is [issue] because [case fact].” |
| Exhibit use | “Exhibit [name] supports this because it shows [fact], which affects [analysis or recommendation].” |
| Calculation interpretation | “The result indicates [business meaning], not just [number], so management should consider [action].” |
| Assurance evidence | “A useful procedure would be [procedure] because it addresses [risk/assertion] using [source].” |
| Tax advice | “The tax consequence depends on [taxpayer/transaction/timing]; based on the case facts, [treatment] is more supportable.” |
| Caveat | “If [missing fact] differs, the recommendation may change; the next step is [specific follow-up].” |
| Role cue | Output to write |
|---|---|
| Assurance | Risk, procedure, evidence, conclusion, reporting or communication consequence. |
| Taxation | Taxpayer, transaction, calculation or filing effect, deadline, planning or CRA response. |
| Finance | Decision, method, assumptions, result, risk, recommendation, implementation. |
| Performance Management | Objective, measure or analysis, behaviour effect, control, recommendation, follow-up KPI. |
In the last review pass, reduce Day 2 notes to four checklists rather than rereading every topic.
| Checklist | Keep |
|---|---|
| Role map | Declared role, common issues, role-depth issues, and audience. |
| Evidence map | Exhibits, appendices, calculations, documents, and constraints tied to issues. |
| Depth map | Full-depth responses, moderate responses, quick common points, and caveats. |
| Recommendation map | Action, support, implementation, communication consequence, and follow-up. |
The goal is not to memorize a perfect answer pattern. The goal is to recognize when a role-depth issue needs enough support to be useful and when a shorter answer is sufficient.
Before leaving a Day 2 response, confirm that each major issue has role responsibility, case evidence, sufficient analysis, recommendation, implementation or communication consequence, and any necessary caveat.