Prioritize Day 3 analysis under time pressure without overbuilding low-value issues.
Scope control is the ability to decide how much analysis an issue deserves before writing too much. Day 3 short cases create pressure because several issues may need attention in a limited response window. The safest answer is not the longest answer. The safest answer is the one that gives each required issue enough support and then moves on.
Overbuilding is a common failure pattern. A candidate recognizes a familiar topic, writes a long explanation, and leaves too little time for later issues. Underbuilding is the opposite problem: the response names the issue and conclusion but does not show enough case support. Scope control sits between those extremes.
| Scope signal | Likely response size | What to include |
|---|---|---|
| Direct treatment question with clear facts | Short to medium | Rule, key fact, conclusion, and any caveat. |
| Decision between alternatives | Medium | Criteria, brief comparison, recommendation, and implementation note. |
| Small calculation | Short to medium | Setup, result, interpretation, and caveat if data are incomplete. |
| Professional risk or governance issue | Medium | Issue, implication, audience, recommendation, and follow-up. |
| Minor background issue | Very short | Acknowledge only if it affects the required advice. |
Before drafting, ask what the issue needs: a rule, a calculation, a comparison, a risk comment, a documentation request, or a recommendation. If the issue needs a rule, write the rule briefly and apply it. If it needs a calculation, show the setup and interpret the result. If it needs a decision, compare the criteria that matter.
The answer should not grow because the topic is familiar. A familiar topic still receives only the analysis needed by the case. Conversely, an unfamiliar topic may deserve enough explanation if it is central to the client request and supported by case facts.
flowchart LR
A["Required issue"] --> B{"What does the client need?"}
B --> C["Treatment or rule"]
B --> D["Calculation"]
B --> E["Decision between options"]
B --> F["Risk or communication"]
C --> G["Rule, fact, conclusion"]
D --> H["Setup, result, meaning"]
E --> I["Criteria, comparison, recommendation"]
F --> J["Implication, audience, action"]
Use the flow before writing the first paragraph. It forces the answer to match the required response type instead of defaulting to a familiar structure.
Day 3 scope is easier to control when you decide response size deliberately.
| Response size | Use it when | Typical structure |
|---|---|---|
| One sentence | The issue is minor, obvious, or only a caveat to a larger recommendation. | Conclusion plus action or caveat. |
| Short paragraph | The issue needs one rule, one fact, and one conclusion. | Issue, fact, treatment, recommendation. |
| Calculation block plus sentence | The number changes the recommendation. | Setup, result, meaning, action. |
| Comparison table | Two or more options must be ranked quickly. | Criteria, option effects, recommendation. |
| Fuller issue block | The issue is directly requested and drives the client decision. | Issue, facts, analysis, risk, recommendation, follow-up. |
The table is not a rigid template. It is a safeguard against using the same amount of space for every issue.
Day 3 case sets often require broad coverage. The first issue should not consume the response. If a paragraph is becoming long, pause and ask whether the conclusion is already supportable. If it is, move to the next issue.
One useful habit is to draft compact issue blocks. Each block should contain the issue, one or two relevant facts, the analysis step, and the recommendation. This keeps the response modular. It also makes it easier to recover if time pressure increases.
False depth is extra writing that looks technical but does not improve the answer. Examples include listing every possible accounting criterion when only one criterion is disputed, explaining tax policy when the issue is documentation, or describing assurance procedures that do not address the risk in the case.
Depth should be case-specific. If the case turns on one contract term, analyze that term. If the issue turns on a cost constraint, use the constraint. If the issue turns on stakeholder risk, explain the stakeholder consequence. Do not add broad theory to make the answer look fuller.
Stopping is an exam skill. Stop writing an issue when the reader can understand the conclusion and the next action.
| If you have already… | Stop unless… |
|---|---|
| Stated the applicable rule and applied the decisive fact. | Another fact changes the conclusion. |
| Calculated the relevant decision metric and interpreted it. | Sensitivity or a missing input could reverse the advice. |
| Compared the realistic alternatives on the main criterion. | A secondary criterion materially changes ranking. |
| Named the control weakness and recommended a practical fix. | The audience or severity changes the communication. |
| Identified the tax treatment and filing action. | Another taxpayer, deadline, or remittance layer is affected. |
A short calculation can support a conclusion quickly, but a calculation can also become a time trap. Set up only the calculation needed for the decision. Label assumptions. Interpret the result in words. If the data are incomplete, show what can be calculated and state what missing input would change the answer.
For example, if the client needs to decide whether to accept a special order, contribution margin and capacity may matter more than a full income statement. If the client needs to evaluate a financing choice, relevant cash flows may matter more than accounting profit. Scope follows the decision.
| Pitfall | Better approach |
|---|---|
| Writing a full textbook explanation. | Apply only the rule or framework needed for the case. |
| Stopping at issue identification. | Add enough fact support to make the conclusion defensible. |
| Letting the first issue dominate. | Use compact issue blocks and move on once support is sufficient. |
| Performing unnecessary calculations. | Calculate only numbers that affect the decision. |
| Ignoring uncertainty. | Add a concise assumption or follow-up where missing facts matter. |
Use a scope-first pattern: decide the response type, write the issue, apply the facts, and stop when the recommendation is supported. This approach feels restrained, but restraint is part of Day 3 professionalism. A concise answer that answers all required issues is usually stronger than a long answer that exhausts one issue and neglects the rest.
Scope control improves with review. After practice, mark any sentence that did not change the answer. Those sentences reveal where future responses can be shorter without becoming weaker.