Set up calculations and assumptions so quantitative work supports role-depth advice.
Quantitative analysis in CFE Day 2 should be designed before it is calculated. The goal is not to fill the page with arithmetic. The goal is to use numbers to support the role-specific conclusion: valuation, financing, risk assessment, assurance planning, tax effect, performance analysis, or another assigned decision.
A calculation that is technically correct can still be weak if it uses irrelevant inputs, hides assumptions, ignores missing data, or fails to interpret the result. Strong quantitative setup begins with the issue and ends with an implication.
Day 2 often includes numerical exhibits, forecasts, transaction data, cost schedules, financing details, tax information, ratios, margins, or operational metrics. The candidate must determine which numbers are relevant to the declared role and how precise the conclusion can be.
The role controls the calculation. A finance role may need cash-flow, valuation, capital budgeting, financing, or sensitivity work. An assurance role may use numbers to assess materiality, risk, sample focus, or evidence implications. A performance-management role may use numbers to analyze cost behavior, pricing, variances, capacity, or incentives.
Before calculating, write the logic in words:
This short setup prevents irrelevant number work. It also makes the answer easier to follow if time pressure forces a simplified calculation.
| Setup question | Example |
|---|---|
| What is being decided? | Whether the investment creates enough value to justify financing risk. |
| What inputs matter? | Incremental cash flows, initial investment, working capital, tax effects, residual value, and discount rate. |
| What assumptions are sensitive? | Sales volume, margin, customer retention, cost escalation, and timing. |
| What limits the conclusion? | Forecast reliability, incomplete market data, or unconfirmed financing. |
| What should the result support? | Proceed, reject, delay, pilot, renegotiate, or seek more evidence. |
A numerical fact is relevant when it affects the calculation or interpretation. It is not relevant simply because it appears in an exhibit. For example, total revenue may be less useful than incremental contribution margin if the issue is whether to accept a new contract. Historical growth may be less useful than churn and capacity if the issue is whether a forecast is realistic.
Relevant-input selection should be explicit enough for the reader to see the logic. If you exclude a large number, explain why it is sunk, irrelevant, already included, non-incremental, unsupported, or outside the role issue. If you include an estimate, explain the assumption behind it.
Assumptions are unavoidable in many Day 2 calculations. The problem is not the existence of assumptions. The problem is failing to identify the assumptions that drive the conclusion.
Important assumptions often include:
If a conclusion is sensitive to an assumption, say so. A practical response might state: “The project appears profitable under management’s forecast, but the conclusion depends heavily on the 15 percent volume growth assumption. If growth is closer to the recent 5 percent trend, the recommendation would need to be reconsidered.”
Sometimes the case does not provide enough information for a precise calculation. A strong response still uses the available data. It may perform a partial calculation, identify the missing input, explain its effect, and recommend follow-up.
For example, if a valuation case gives earnings but no reliable maintainable earnings adjustment, the response can calculate a preliminary range while explaining that the range is limited by unadjusted earnings quality. If a financing case gives debt terms but not covenant definitions, the response can identify covenant risk and recommend confirming the lender’s calculation basis before final approval.
The reader should understand what the calculation can and cannot prove.
The final step is interpretation. A number alone is not a recommendation. A positive net present value, favorable margin, or lower cost may support a proposal, but qualitative constraints can still change the answer. A negative result may support rejection, but strategic necessity or risk mitigation may support a modified alternative.
Interpretation should connect the result to the role:
| Pitfall | Why it weakens the response | Better approach |
|---|---|---|
| Calculating before defining the issue. | The work may answer the wrong question. | Start with the decision the calculation must support. |
| Using every number in the exhibit. | Irrelevant inputs obscure the analysis. | Select incremental, role-relevant inputs. |
| Hiding assumptions. | The conclusion may appear more certain than it is. | State sensitive assumptions and limitations. |
| Stopping at the answer. | The reader does not know what to do with the result. | Interpret the result and connect it to the recommendation. |