CIMA SCS: Why a Numerically Correct Recommendation Can Still Fail

Every marking cycle, CIMA examiners describe the same pattern in the Strategic Case Study (SCS): a candidate runs a technically flawless calculation, then writes a recommendation that has almost nothing to do with the organisation in the case. The number is right. The advice is wrong. And because SCS marks integration and judgement rather than arithmetic alone, that gap costs marks that a candidate genuinely believed they had already earned.

This matters more at SCS than anywhere else in the CIMA qualification, because CIMA's Strategic Case Study is deliberately built to test whether you can think like an integrated finance business partner across all three Strategic-level pillars at once: E3 Strategic Management, P3 Risk Management, and F3 Financial Strategy. The exam is set around a detailed pre-seen scenario, developed further with unseen material on the day, and candidates respond in a written, scenario-based format rather than picking multiple-choice answers. That format is precisely why calculation-only answers underperform: there is no box to tick for "correct number," only a mark scheme built around how well your advice fits the specific organisation you have spent weeks studying.

The mistake: solving the sum, not the case

The pattern usually looks like this. A requirement asks the candidate to evaluate a financing option, a proposed acquisition, an investment appraisal, or a strategic option using an F3-style technique — say, comparing the cost of debt versus equity finance, building an NPV, or valuing a target business. The candidate does the technical work competently, arrives at a defensible figure, and then writes a one-line conclusion: “the NPV is positive, therefore the project should proceed” or “the equity option is cheaper, therefore the company should raise equity.” Technically, none of that is false. But it is not an answer to the question SCS actually asked, because the case will almost never be testing whether you can compute a discounted cash flow — it is testing whether you can turn that output into commercially sound advice for the specific board, in the specific pre-seen context, under the specific constraints the scenario has built in.

The reason this keeps happening is that the calculation feels like the hard part, so candidates relax once it is done and treat the recommendation as a formality. In an integrated case study, it is the opposite: the calculation is the entry ticket, and the recommendation is where the marks for strategic judgement — E3's and P3's territory as much as F3's — actually sit.

What examiners are actually looking for

A recommendation that scores well in SCS typically does three things a purely numerical answer skips entirely.

1. It connects back to the organisation's stated strategic objectives

Every SCS pre-seen sets out what the organisation is trying to achieve — growth into a new market, protecting a core competitive advantage, diversifying revenue, improving margins, and so on. A recommendation should explicitly test the numerical outcome against those objectives. A positive NPV that pulls the business away from its stated strategy, or that requires capabilities it does not have, is not automatically a “yes” — and a good answer says so.

2. It considers acceptability to the people who actually decide

Boards, shareholders, lenders, employees, and regulators do not evaluate proposals purely on expected value. A financing recommendation that is numerically optimal but breaches a loan covenant, dilutes a founding family's control, or conflicts with the organisation's culture is unlikely to be accepted in practice — and unlikely to score well if the answer does not flag that tension.

3. It is realistic given what the organisation can actually deliver

Feasibility asks whether the organisation has the funding headroom, management capacity, systems, and time to execute the option, not just whether the maths supports it in theory.

These three lenses — suitability, acceptability, and feasibility (often shortened to SAF) — give you a fast, repeatable check for whether a recommendation is actually embedded in the case, rather than bolted onto a calculation. Suitability asks whether the option fits the strategic direction and addresses the underlying problem; acceptability asks whether stakeholders (financial, risk-related, and reputational) will tolerate it, including whether it sits within the organisation's stated risk appetite; feasibility asks whether it can realistically be implemented with the resources, skills, and time available.

A practical technique: the three-question filter

Before submitting any recommendation in SCS, run it through three quick questions, drawing directly on details from the pre-seen:

• Does this fit where the organisation says it wants to go? Quote or paraphrase a specific strategic objective from the pre-seen and check the recommendation against it, rather than asserting fit in general terms.
• Would the people who matter actually accept it? Name the relevant stakeholder group — the board, a majority shareholder, lenders, the works council — and identify the specific objection they would likely raise, referencing risk appetite where relevant.
• Can the organisation realistically deliver it? Point to a constraint already established in the case — funding capacity, management bandwidth, a live restructuring, a fragile IT system — that affects whether the option is deliverable on the proposed timescale.

If you cannot answer all three using case-specific detail, the recommendation is not finished, however solid the underlying number is. This is a different lens from evaluating risk appetite against a formal risk register, which is its own recurring P3 exam-technique issue — see our related piece on risk appetite versus the risk register for that narrower distinction. The pattern covered here is broader: it is about numbers-without-judgement across all three Strategic pillars, not risk management specifically.

Why this integration is the whole point of SCS

CIMA designed the Strategic Case Study to sit above the three separate Strategic-level subjects precisely because real finance leaders do not solve E3, P3, and F3 problems in isolation — a financing decision has strategic and risk consequences, and a strategic move has financial and risk consequences. Practising calculations in isolation, subject by subject, is necessary preparation but is not sufficient preparation, because it trains the technique without training the habit of stepping back and asking what the number means for this organisation, right now, given its stated direction and its constraints.

Building that habit early — ideally while working through practice questions, not for the first time in the exam hall — is what separates candidates who show technical competence from candidates who demonstrate the strategic judgement SCS is actually built to assess. For a broader walkthrough of how to structure your SCS preparation and exam-day approach, see our guide on how to pass CIMA SCS, and for how the case study format works across all three levels, our CIMA case study exams guide.

FAQ

Is a numerically correct answer worthless if the recommendation is weak?

No — technical marks are still available for a correct, well-presented calculation. But SCS mark schemes reward integration and judgement heavily, so a calculation with a thin or generic recommendation will consistently score below a similar calculation paired with a recommendation grounded in the pre-seen's strategic objectives, stakeholders, and constraints.

How long should the recommendation section be relative to the calculation?

There is no fixed ratio, but many well-scoring answers spend as much space justifying the recommendation against the case context as they spend on the calculation itself. If your recommendation is a single sentence tacked onto a page of workings, it is very likely under-developed.

Does this apply to every requirement in SCS, or only financing and investment questions?

It applies wherever a requirement asks for advice, evaluation, or a recommendation — which covers most of the paper, not just F3-flavoured numerical questions. The same suitability, acceptability, and feasibility check works equally well for a strategic option evaluation (E3) or a risk response decision (P3).