Structure Day 2 depth responses with issue ranking and completeness under time pressure.
Depth on CFE Day 2 is not the same as writing a long answer. Depth means the response gives enough analysis for the declared role, uses relevant case evidence, explains implications, and reaches a supported recommendation. A long paragraph that repeats facts without judgment is still shallow.
The Day 2 case is built around a declared role. That role controls which issues deserve the most depth and which issues should be handled more briefly. The first response-quality task is therefore to rank issues before writing.
This lesson focuses on building a complete Day 2 role-depth response. It applies across assurance, performance management, finance, taxation, and other role cases.
| Response element | What it must do |
|---|---|
| Issue identification | State the problem, decision, risk, or required advice. |
| Role relevance | Explain why the issue matters in the declared role. |
| Case evidence | Use facts from exhibits, role instructions, quantitative data, and constraints. |
| Analysis | Apply the relevant rule, framework, calculation, procedure, or decision criterion. |
| Implication | Explain the effect on the client, entity, users, stakeholders, or professional duty. |
| Recommendation | State the action, conclusion, adjustment, procedure, or follow-up. |
Not every issue in the case deserves the same treatment. A role-critical issue should usually receive more analysis, more evidence, and a clearer recommendation. A common issue or background issue may still matter, but it should not consume the response if it does not drive the declared role.
Rank issues using these signals:
| Signal | Depth implication |
|---|---|
| Explicit role request | Requires direct attention and supported analysis. |
| Material financial effect | Needs calculation, interpretation, and conclusion. |
| Professional or ethical risk | Needs clear judgment and action. |
| Strategic or stakeholder consequence | Needs recommendation logic, not just technical treatment. |
| Minor correction or background fact | Address briefly if relevant, then move on. |
The strongest candidates do not simply answer issues in the order they appear. They use the role to decide what carries weight.
A complete response does not need every possible detail. It needs enough support to show that the conclusion follows from the facts.
For a financial reporting issue, completeness may mean identifying the applicable treatment, applying case facts, explaining the statement effect, and recommending correction or disclosure. For an assurance issue, it may mean identifying risk, linking it to assertions, proposing procedures, and explaining reporting or communication implications. For a finance issue, it may mean calculating cash impact, testing feasibility, and recommending action with conditions.
Use this structure:
| Move | Example function |
|---|---|
| Issue | “The proposed treatment may overstate revenue.” |
| Fact | “Goods have not yet been delivered and the customer can cancel.” |
| Analysis | “Control has not transferred, so revenue recognition is not supported.” |
| Implication | “Profit and receivables would be overstated, which may affect users and covenants.” |
| Recommendation | “Defer revenue until delivery and disclose the covenant risk if material.” |
False depth often appears as long background, copied facts, broad theory, or repeated pros and cons. It may look substantial, but it does not move the decision forward.
Common false-depth patterns include:
| Weak pattern | Stronger pattern |
|---|---|
| Copying exhibit facts in full. | Select the facts that affect the conclusion. |
| Explaining a rule generally. | Apply the rule to the case evidence. |
| Writing several alternatives without choosing. | Compare alternatives against role-specific criteria and recommend. |
| Adding caveats to avoid deciding. | State a supported conclusion and qualify only the material uncertainty. |
| Treating all issues equally. | Give more depth to role-significant issues. |
Day 2 is a five-hour exam day, but the case can still pressure time because role-depth analysis is demanding. Completeness requires planning. Before drafting, identify the major issues, allocate rough depth, and decide which exhibits support each issue.
Use a quick completeness checklist before leaving a major issue:
If one of these pieces is missing, the response may be incomplete even if it is long.
| Pitfall | Correction |
|---|---|
| Writing breadth-level treatment for a declared-role issue. | Add role-specific facts, analysis, implication, and recommendation. |
| Overanalyzing a minor common issue. | Keep it concise unless it changes the role recommendation. |
| Treating calculations as the whole answer. | Interpret the result and connect it to the decision. |
| Omitting the recommendation. | State what should be recorded, done, tested, disclosed, approved, or monitored. |
| Confusing length with depth. | Depth is evidence plus judgment, not more words. |