Use problem solving, decision making, and alternative evaluation under short-case constraints.
Problem solving on CFE Day 3 starts before any calculation. The candidate has to identify the real decision, separate relevant facts from background information, evaluate alternatives, and recommend an action that fits the case constraints. A technically correct calculation can still be a weak response if it solves the wrong problem.
Day 3 cases often include multiple issues across different competency areas. The problem-solving skill is deciding what each issue is asking for and what kind of response would be useful to the reader.
This lesson focuses on defining the problem, choosing an analysis path, evaluating alternatives, and connecting the conclusion to action. It applies whether the issue is financial reporting, tax, assurance, finance, management accounting, strategy, governance, or ethics.
| Problem-solving step | Purpose |
|---|---|
| Define the decision | Identify what the reader needs to decide or understand. |
| Select relevant facts | Use facts that change recognition, measurement, risk, cash flow, compliance, or advice. |
| Choose the analysis method | Calculation, criteria comparison, risk assessment, procedure recommendation, or governance response. |
| Evaluate alternatives | Compare realistic options against the case objective and constraints. |
| Recommend action | State what should happen and why. |
A case fact may be a symptom, not the problem. Declining cash may be caused by poor collections, falling margins, inventory buildup, debt service, or tax arrears. A control error may be caused by missing approval limits, weak segregation, inadequate training, or management override. A client complaint may indicate communication failure, quality risk, or unrealistic expectations.
Before writing, convert the request into a problem statement:
| Weak framing | Better framing |
|---|---|
| “Discuss cash flow.” | “Determine whether the company can fund the expansion without breaching liquidity constraints.” |
| “Review controls.” | “Identify why unauthorized purchases occurred and recommend a control that prevents recurrence.” |
| “Analyze the offer.” | “Compare the sale offer with the owner’s objectives, tax effects, and stakeholder risks.” |
| “Comment on reporting.” | “Decide whether the accounting treatment is supportable and what correction or disclosure is needed.” |
The better framing helps the answer stay focused.
Relevance depends on the decision. A fact is relevant when it changes the conclusion, supports the analysis, limits an option, or creates risk. Background facts may help context, but they should not consume writing time if they do not affect the answer.
Important constraints include:
| Constraint | Example effect |
|---|---|
| Time | Filing deadlines, contract expiry, urgent financing, or limited case time. |
| Cash | Liquidity shortfall, debt service, working capital, or implementation funding. |
| Authority | Board approval, lender consent, owner agreement, policy limits, or professional role. |
| Evidence | Missing support, unreliable estimate, incomplete documentation, or untested assumption. |
| Risk | Compliance exposure, reputational harm, operational failure, or stakeholder conflict. |
| Capacity | Staffing, systems, expertise, training, or management attention. |
If a constraint rules out an option, say so. If a constraint makes an option conditional, state the condition.
Alternative evaluation should not be a generic pros-and-cons list. Compare alternatives against the criteria that matter in the case. The criteria may include profit, cash, risk, compliance, stakeholder effect, feasibility, mission fit, or professional obligation.
Use a concise table when it improves scanning:
| Alternative | Support | Concern | Conclusion |
|---|---|---|---|
| Option A | Best financial result or strongest technical support. | May breach a constraint or create risk. | Use only if the condition is met. |
| Option B | Lower risk or easier implementation. | Lower return or slower impact. | Prefer if feasibility matters most. |
| Option C | Preserves flexibility. | Does not fully solve the issue. | Use as interim action or reject if insufficient. |
The conclusion column matters. Without it, the table becomes notes rather than advice.
Day 3 responses often require both numbers and judgment. If the calculation supports one alternative but qualitative facts point the other way, explain the trade-off. For example, a project may have a positive contribution but require cash the entity does not have. A tax strategy may save cash but create unsupported compliance risk. A financing offer may solve liquidity but dilute control or impose strict covenants.
The answer should explain which factor carries more weight under the facts. Do not write “consider both quantitative and qualitative factors” without saying which one affects the recommendation.
Use this framework for problem-solving issues:
This framework is intentionally short. It helps avoid the two common extremes: jumping to a conclusion without analysis or writing a long answer that never decides.
| Pitfall | Correction |
|---|---|
| Solving a symptom instead of the problem. | Identify the decision the reader needs to make. |
| Listing facts without analysis. | Explain how each selected fact changes the conclusion. |
| Using a calculation because numbers are available. | Choose the method that answers the request. |
| Giving equal weight to every alternative. | Compare options against the most important case criteria. |
| Ending with “management should consider.” | State the recommended action and condition. |