Review CPA Canada Common Final Examination Day 1 reminders for strategic issue spotting, case context, alternatives, stakeholder constraints, implementation, and conclusion quality.
Use this CPA Canada Common Final Examination (CFE) Day 1 cheat sheet as a case-triage checklist before sample questions. Day 1 preparation should build the habit of turning case facts into strategic issues, alternatives, risks, and supported recommendations. This page is companion practice support and does not reproduce or mirror official CFE cases.
| Item | CFE Day 1 cue |
|---|---|
| Provider | CPA Canada |
| Assessment | Common Final Examination Day 1 |
| Current Finance Prep status | sample questions available |
| Main practice behavior | strategic issue spotting, alternative evaluation, stakeholder reasoning, implementation feasibility, and supported conclusions |
| Candidate risk | writing generic business advice instead of a case-specific recommendation tied to objectives and constraints |
Use this map before answering a Day 1-style prompt. The key is to move from facts to decision logic, not from facts to a generic recommendation.
flowchart LR
Facts["Case facts"] --> Issues["Strategic issues"]
Issues --> Options["Alternatives"]
Options --> Criteria["Objectives and constraints"]
Criteria --> Risks["Risks and stakeholders"]
Risks --> Plan["Recommendation and implementation"]
| Distinction | How to think in a question | Common trap |
|---|---|---|
| Strategic issue vs background fact | A strategic issue changes the organization’s direction, risk, resources, or stakeholder position. | Treating every fact as equally important. |
| Objective vs constraint | Objectives define what the organization wants; constraints limit what it can do. | Recommending an option that violates cash, covenant, capacity, or stakeholder limits. |
| Alternative vs implementation step | Alternatives are choices; implementation steps make the selected choice workable. | Recommending an option without explaining how to execute it. |
| Financial analysis vs decision support | Numbers should support the strategic choice, not become the entire answer. | Calculating everything in the case because the data is available. |
| Stakeholder issue vs public-relations note | Stakeholder facts can affect feasibility, risk, reputation, funding, or governance. | Adding stakeholder language only as a generic afterthought. |
| Risk vs reason to reject | A risk may require mitigation, sequencing, or conditions, not automatic rejection. | Rejecting every option with uncertainty. |
| Recommendation vs summary | A recommendation chooses a path and explains why it fits the case. | Restating pros and cons without deciding. |
| Case-specific conclusion vs memorized template | A good conclusion uses the case’s objectives, constraints, and evidence. | Writing a generic “grow carefully” conclusion. |
Look for these signals before choosing a recommendation:
| Criterion | What to ask | Weak answer pattern |
|---|---|---|
| Strategic fit | Does the option support the stated objective? | Picking the highest-growth option despite a stability objective. |
| Financial capacity | Can the organization fund and absorb the downside? | Ignoring cash flow, covenants, or working-capital strain. |
| Execution ability | Does management have the people, systems, and time to implement? | Assuming a complex launch is easy because the spreadsheet works. |
| Risk profile | What new risks replace the old risks? | Saying diversification eliminates all risk. |
| Stakeholder impact | Who is affected and can they block or weaken the plan? | Treating stakeholder commitments as soft background facts. |
| Governance | Are approvals, conflicts, or board oversight needed? | Proceeding with a related-party option because management likes it. |
| Timing | Does sequencing matter? | Recommending immediate action when financing or controls must come first. |
| Trap | Better candidate habit |
|---|---|
| Starting with detailed calculations before identifying strategic issues. | First identify the decision the board or management must make. |
| Recommending growth because it sounds strategic. | Test growth against cash, capacity, risk appetite, and objectives. |
| Ignoring implementation feasibility. | Explain staffing, systems, financing, timing, and control conditions. |
| Treating stakeholder issues as optional. | Ask whether stakeholder facts affect feasibility, reputation, or obligations. |
| Presenting alternatives without choosing. | Make a supported recommendation and explain why rejected options are weaker. |
| Overstating certainty. | State assumptions, risks, and conditions for success. |
| Using generic business advice. | Anchor each point to a case fact. |
| Missing governance and conflict facts. | Add safeguards, independent review, or approval steps when needed. |
A strong Day 1 recommendation usually includes:
Avoid wording such as “this will solve all problems” or “management should proceed because growth is positive.” Day 1 conclusions need confidence, but they also need limits.
Use the main CFE Day 1 page as a compact case-reasoning preview. After each missed question, identify whether you missed the issue, used the wrong criterion, ignored a constraint, or wrote a conclusion that was too generic. If the error was not technical, more memorization will not fix it; practise case triage and recommendation wording.
If you are repeatedly choosing the same type of attractive but unsupported option, slow down and write the objective, constraint, and risk in one line before selecting an answer.