Day 1 lessons for high-level calculations, qualitative implications, option ranking, uncertainty, integration, recommendation flow, implementation, and incomplete facts.
Integrated recommendation development turns analysis into board-level advice. Candidates should combine limited calculations, qualitative implications, uncertainty, technical breadth, sequencing, and risk mitigation without drifting into Day 2 depth.
Day 1 is connected to the Capstone 1 case context, so recommendations should not read like isolated technical memos. A strong answer explains what has changed, how the change affects the entity’s strategic choices, which option is most supportable, and what conditions or monitoring should accompany the advice.
flowchart LR
A["Quantitative signal"] --> B["Qualitative implication"]
B --> C["Trade-off"]
C --> D["Recommendation"]
D --> E["Implementation and monitoring"]
| Section | Decision habit | Response output |
|---|---|---|
| 3.1 Calculations | Use enough quantitative analysis to inform the strategic decision. | A calculation interpreted through constraints, risk, and option feasibility. |
| 3.2 Qualitative Implications | Select qualitative factors that change the recommendation. | Implications that explain why the fact matters, not generic pros and cons. |
| 3.3 Option Ranking | Compare alternatives against the same decision criteria. | A ranked recommendation with trade-offs and support. |
| 3.4 Scenario Risk | Test whether uncertainty changes the decision. | Advice qualified by assumptions, sensitivity, and downside risk. |
| 3.5 Technical Integration | Use technical facts at Day 1 breadth. | Board-level analysis that integrates accounting, finance, tax, governance, and operations without overbuilding. |
| 3.6 Recommendation Flow | Make the conclusion flow from the strongest evidence. | A clear line from issue, evidence, implication, recommendation, and condition. |
| 3.7 Implementation | Convert advice into an executable path. | Sequencing, mitigation, ownership, and monitoring points. |
| 3.8 Incomplete Facts | Preserve judgment when facts are missing or conflicting. | Conditional advice that identifies the missing fact and the next decision step. |
Read each section as a Day 1 response habit. Identify the board-level decision, separate baseline facts from current updates where relevant, integrate limited quantitative and qualitative evidence, and write a recommendation that fits the entity’s constraints.
Use the official exam context as the boundary: the Common Final Examination is a three-day exam, and Day 1 is linked to the Capstone 1 case. That makes strategic continuity, update recognition, and board-level communication more important than deep technical demonstration on this day. For public exam context, see the CPA Western School of Business page on the Common Final Examination.
| Trap | Better response |
|---|---|
| Repeating the case instead of updating it. | Explain what changed and why it matters now. |
| Treating Day 1 like Day 2 depth. | Keep the answer strategic, integrated, and board-focused. |
| Ending with vague advice. | State the recommendation, condition, implementation step, and monitoring point. |