Use problem solving, decision making, and alternative evaluation in role-depth responses.
Problem solving on CFE Day 2 means defining the decision before applying technical knowledge. The declared role gives the lens, but the case facts define the actual problem: a reporting treatment, assurance risk, financing decision, tax exposure, performance issue, governance weakness, or implementation constraint.
The strongest Day 2 response shows why the recommendation solves the problem in the role, not merely why a technical point is true.
This lesson focuses on defining decision problems, evaluating alternatives, balancing quantitative and qualitative evidence, and choosing a recommendation that fits the declared role.
| Problem-solving step | Role-depth purpose |
|---|---|
| Define the decision | State what the decision maker needs to resolve. |
| Identify constraints | Use role-specific facts, common facts, deadlines, cash, risk, and authority. |
| Select analysis path | Choose the calculation, framework, procedure, or criteria that answers the issue. |
| Evaluate alternatives | Compare realistic options against case objectives and constraints. |
| Recommend action | State the option, condition, implementation step, or follow-up. |
A case may contain symptoms that are not the real problem. Lower profit may be caused by pricing, volume, cost behaviour, controls, or strategy. A tax issue may be caused by poor documentation, missing filings, or unsupported structuring. An assurance issue may be caused by management bias, weak evidence, or reporting uncertainty.
Before writing, convert the issue into a decision statement:
| Weak framing | Better framing |
|---|---|
| “Discuss the expansion.” | “Determine whether the expansion is financially feasible and consistent with the finance role’s risk assessment.” |
| “Analyze the audit risk.” | “Identify the misstatement risk created by the revenue contract and recommend procedures.” |
| “Review tax planning.” | “Determine whether the proposed structure is supportable, documented, and cash-effective.” |
| “Comment on performance.” | “Decide whether the KPI set measures the behaviour management actually wants.” |
The better framing tells the response what evidence belongs.
Day 2 cases include role-specific evidence and common case facts. The declared role controls depth, but common facts can still change the conclusion. A finance role may need tax facts if after-tax cash affects financing. An assurance role may need strategy facts if they explain management bias or going-concern risk. A performance-management role may need governance facts if incentives create poor behaviour.
Use facts when they affect the decision, not merely because they are present.
| Fact type | Use when it affects |
|---|---|
| Quantitative exhibit | Calculation, materiality, cash flow, valuation, variance, or ratio. |
| Role instruction | Depth expectation and intended decision maker. |
| Common case fact | Strategy, risk, stakeholder effect, implementation, or governance. |
| Stakeholder detail | Feasibility, communication, conflict, or public-interest consequence. |
| Missing evidence | Assumption, caveat, or follow-up requirement. |
Day 2 problem solving often requires comparing alternatives. The response should not list pros and cons equally. It should identify the criteria that matter in the role and then choose.
| Alternative criterion | Example use |
|---|---|
| Technical support | Which treatment, procedure, tax position, or valuation input is supportable? |
| Quantitative effect | Which option has the stronger cash, profit, tax, or ratio result? |
| Risk | Which option creates compliance, assurance, financing, or stakeholder risk? |
| Feasibility | Which option can be implemented with available resources and authority? |
| Strategic fit | Which option supports the entity’s objective or mandate? |
| Professional duty | Which option respects integrity, objectivity, independence, and due care? |
End the comparison with a conclusion. If neither alternative is acceptable as proposed, recommend a modified option.
A Day 2 response often needs both numbers and judgment. A calculation may indicate the best financial result, but qualitative facts may change the recommendation. For example, a project with a positive return may exceed risk appetite, rely on unsupported forecasts, or breach debt covenants. A tax plan may save cash but create documentation and compliance risk.
State which factor controls. “Although the project has a positive NPV, the financing covenant would be breached unless the lender approves the new debt” is stronger than “There are qualitative factors to consider.”
Use this sequence:
| Pitfall | Correction |
|---|---|
| Starting with a calculation before defining the decision. | State what the calculation is meant to prove. |
| Solving a symptom. | Identify the underlying decision or cause. |
| Treating all alternatives equally. | Rank options against the role-specific criteria. |
| Ignoring common facts because they are outside the role exhibit. | Use common facts when they change the role conclusion. |
| Ending with a weak “consider” statement. | State the recommended action and the controlling reason. |