Use compact exhibits, short calculations, assumptions, and caveats to support Day 3 conclusions.
Exhibits and calculations should support the Day 3 conclusion, not become the response. A short case may include tables, emails, trial balances, budgets, transaction details, tax information, control notes, or performance data. The task is to find the exhibit item that changes the decision and use it efficiently.
A calculation is useful when it clarifies recognition, measurement, profitability, cash flow, tax impact, variance, valuation, or recommendation. It is not useful when it reproduces data without interpretation. The reader needs to know what the number means and how it changes the advice.
| Exhibit or calculation issue | What to do | What to avoid |
|---|---|---|
| Compact exhibit | Identify the line, trend, exception, or constraint that changes the answer. | Rewriting the entire exhibit in prose. |
| Short calculation | Show setup, result, and interpretation. | Building a full model when one decision metric is enough. |
| Missing input | State the assumption and the effect of uncertainty. | Inventing data or abandoning the conclusion. |
| Conflicting data | Explain which source is more relevant or reliable for the issue. | Averaging facts without judgment. |
| Recommendation support | Tie the result to the client objective. | Ending with a number and no advice. |
Before entering an exhibit, know what you are looking for. If the issue is pricing, search for variable cost, capacity, contribution, and strategic constraints. If the issue is a financial reporting treatment, search for contract terms, dates, amounts, rights, obligations, and estimates. If the issue is assurance, search for evidence quality, control exceptions, reconciliations, and missing support.
An exhibit often contains both direct evidence and context. Direct evidence changes the answer. Context may explain why the issue matters. Use direct evidence in the analysis. Use context only if it affects the recommendation or communication.
When an exhibit contains several numbers, do not assume every number should be calculated. Choose the number that answers the request. A small, well-labeled calculation is usually more effective than a large, unexplained table.
flowchart LR
A["Client request"] --> B["Needed decision"]
B --> C["Relevant exhibit line"]
C --> D["Input or exception"]
D --> E["Result or implication"]
E --> F["Recommendation"]
The map keeps exhibit work from becoming data transcription. Every exhibit fact used in the response should either become an input, identify an exception, support a caveat, or change the recommendation.
| Exhibit item | Use it when it… | Do not use it when it… |
|---|---|---|
| Date | Changes recognition, cutoff, deadline, payment timing, or filing posture. | Only describes background chronology. |
| Amount | Supports a calculation, materiality judgment, variance, tax effect, or cash impact. | Does not change the conclusion. |
| Contract term | Creates a right, obligation, condition, restriction, or risk. | Repeats a term that is not disputed. |
| Management assertion | Needs corroboration, skepticism, or caveat. | Is unsupported and irrelevant to the required. |
| Control note | Explains reliability, error risk, access, authorization, or monitoring. | Has no effect on evidence or recommendation. |
Day 3 calculations should be transparent. Show enough of the setup that the reader can follow the result. Label the inputs. Avoid excessive formatting. Interpret the conclusion immediately after the calculation.
For example, if the case asks whether a special order should be accepted, the calculation may focus on incremental revenue, variable cost, contribution margin, capacity constraints, and relevant qualitative factors. A full income statement may not be necessary. If the case asks whether an asset is impaired, the calculation may focus on carrying amount, recoverable or comparable amount, and the resulting implication.
The calculation should end with professional advice. “The option has a positive contribution of $X, but it uses scarce capacity and may conflict with regular customers” is better than a number alone. The interpretation turns arithmetic into judgment.
Use calculations only when they answer the client request.
| Calculation type | Minimal useful output | Interpretation to add |
|---|---|---|
| Relevant cost | Incremental revenue less incremental cost. | Whether the alternative improves contribution after constraints. |
| Variance or trend | Difference, percentage, or direction. | Whether the change signals performance, control, or forecast risk. |
| Financial reporting amount | Adjustment, carrying amount, estimate, or disclosure effect. | Whether the statement treatment or user communication changes. |
| Tax effect | Taxable amount, remittance issue, balance, or timing effect. | What the taxpayer should file, support, correct, or confirm. |
| Financing or cash flow | Cash shortfall, source, repayment, or covenant effect. | Whether the option is feasible and what risk remains. |
Missing data should be handled explicitly. State what is missing, what assumption is being used, and how the answer could change. If the missing information is critical, recommend obtaining it before final action. If the missing information is not critical, proceed and note the limitation.
Avoid creating false precision. If the case provides estimates, use language that reflects estimation. If the case provides partial data, do not make the answer look more certain than the evidence supports. A clear caveat is stronger than an unsupported exact conclusion.
Missing data should not become a default escape. Day 3 cases often provide enough information to make a practical recommendation. Use the available information, then identify the follow-up that would improve certainty.
A calculation should answer the question the client asked. A profitable project may still be rejected if it exceeds risk appetite, violates financing constraints, harms customer relationships, or conflicts with strategic direction. A tax saving may not be worthwhile if implementation risk is too high. A financial reporting adjustment may matter because of covenants, owner distributions, or stakeholder communication.
After each calculation, write one sentence that begins with the effect: “This means…” or “Therefore…” That sentence should connect the number to the recommendation. Without interpretation, the calculation is incomplete.
| Pitfall | Better approach |
|---|---|
| Copying exhibit data into the answer. | Extract only the facts that change the conclusion. |
| Calculating before identifying the issue. | Determine the decision first, then calculate what supports it. |
| Ending with a number. | Interpret the result and recommend an action. |
| Hiding assumptions. | Label assumptions and explain sensitivity where relevant. |
| Overbuilding a spreadsheet-style answer. | Use concise calculations that fit short-case scope. |
Use an exhibit-input-result-meaning pattern. Identify the exhibit fact or input, perform the necessary calculation, state the result, and explain what the result means for the client. This pattern keeps numerical work tied to professional advice.
The best Day 3 calculations are not the longest. They are the calculations that make the recommendation easier to trust.