CPA Canada CFE Day 3 Case Navigation and Breadth Issue Identification

Case navigation is the control layer for CFE Day 3. The CPAWSB Common Final Examination page describes the CFE as a three-day examination where candidates demonstrate depth and breadth of competency development. In Day 3 study, the practical challenge is breadth: recognize the required issue, choose the relevant competency lens, use the facts that change the answer, and move to a concise recommendation.

Day 3 cases are shorter than a Day 2 role case, but they are not simpler in judgment. A compact case may contain financial reporting, management accounting, assurance, tax, finance, strategy, governance, and professional communication cues in close proximity. The candidate must decide what is being asked, what evidence matters, and how much response is enough.

    flowchart LR
	    A["Client request"] --> B["Required issue"]
	    B --> C["Competency cue"]
	    C --> D["Relevant facts"]
	    D --> E["Scope decision"]
	    E --> F["Concise recommendation"]

How This Chapter Is Organized

The Day 3 Navigation Sequence

Start with the request. The client, partner, controller, board, owner, or other decision maker usually tells you what they need. The first job is to translate that request into an issue statement. A request for “advice on the new contract” might be revenue recognition, pricing, risk, tax, assurance, or governance depending on the facts. Do not choose the technical path until the request and facts point to it.

Next, identify the competency cue. The same business fact can signal different work. A decline in margin may require variance analysis in management accounting, impairment analysis in financial reporting, pricing advice in finance, or strategy discussion if the client’s competitive position has changed. The cue is the fact that tells you which professional lens to use.

Then filter facts. Day 3 answers should not reproduce the case narrative. Use facts that change recognition, measurement, tax treatment, assurance evidence, financing advice, strategic choice, risk, or communication. Background facts can provide context, but they should not consume the response.

Finally, choose the scope. Some issues need a short rule and conclusion. Some need a small calculation. Some need a recommendation with one caveat. A few may need a slightly fuller explanation because they drive the client’s decision. The skill is proportionality.

Common Chapter Traps

Study Method

Practice with a two-pass reading habit. On the first pass, identify the decision maker, the requested advice, and the likely competency area. On the second pass, mark only the facts that change the answer. Then write a response that follows issue, fact, analysis, recommendation, and caveat where needed.

For review, ask whether each paragraph earns its place. If a sentence does not identify an issue, use a fact, apply a rule or framework, interpret a calculation, or support a recommendation, it probably belongs outside a Day 3 response.

In this section

• Required Issue Recognition and Competency-Area Cue Selection
  Recognize required Day 3 issues and choose the competency cue before writing technical analysis.
• Short-Case Fact Filtering and Client-Request Interpretation
  Filter compact Day 3 cases to identify facts that directly affect the client request.
• Time-Pressure Prioritization and Short-Case Scope Control
  Prioritize Day 3 analysis under time pressure without overbuilding low-value issues.
• Exhibit Use, Concise Calculations, and Missing-Data Control
  Use compact exhibits, short calculations, assumptions, and caveats to support Day 3 conclusions.
• Breadth Versus Depth Calibration Across Short Issue Sets
  Balance breadth and sufficient analysis across multiple short Day 3 issues.
• Professional Communication Under Shorter-Case Constraints
  Write concise, professional Day 3 advice that fits the audience and case objective.