CIMA SCS: The Five-Competency Balance Mistake That Fails Strong Scripts

It is entirely possible to produce a technically excellent CIMA Strategic Case Study script — sharp NPV workings, sound strategic analysis, a defensible recommendation — and still fail it. The reason has nothing to do with the quality of the technical work and everything to do with how SCS is actually marked. As our own guide to how CIMA case study exams are marked sets out, the exam is scored out of 150 with 80 needed to pass, but that overall threshold is not the only bar you have to clear: a minimum of one-third of the marks allocated to each individual competency area must also be achieved. A script that is outstanding on the numbers but thin on the other competencies can fail one of those individual floors and fail the case study overall, even with a comfortable-looking total.

The five competencies you are actually marked against

SCS marking is built around the CGMA competency framework, and every requirement in the exam is written to draw on more than one of these five areas at once, not to test them separately.

Worked example

Take a typical SCS-style requirement: the board has asked you to advise on whether to proceed with a major ERP system replacement, given the figures and background in the pre-seen and unseen material. A script that scores well on Technical and Business alone would calculate the payback and NPV of the investment, assess the strategic case for modernising the systems estate, and land on a recommendation. That is a solid start, but on its own it leaves three of the five competencies almost untouched.

A stronger answer to the same requirement, without needing extra time overall, folds in the other competencies directly rather than bolting on separate sections: it addresses how the recommendation would be communicated to the specific stakeholder the requirement names, whether that is a sceptical finance director or a board split on the decision (People); it sets out how the transition would actually be led, including how staff resistance or disruption during a system cutover would be managed (Leadership); and it flags the data migration, integration and digital governance risks inherent in an ERP replacement, rather than treating the project as a pure capital-investment decision (Digital). None of this requires abandoning the NPV working or the strategic analysis — it requires writing the same answer so that it visibly touches all five competencies rather than stopping once the technical and business points are made.

The exam trap

The trap is treating SCS like a technical exam paper where the goal is to maximise marks on the parts you are most confident about. Candidates who are strongest technically often over-invest time in calculations that plateau in value quickly — a correct NPV earns the Technical marks available for it and no more, however much further working is added — while running out of time or ideas for the People, Leadership and Digital dimensions of the very same requirement. Because those competencies each carry their own one-third minimum, a script can look strong overall and still fail on a specific competency that was effectively skipped. This is a different, more structural version of the mistake covered in why a numerically correct recommendation can still fail, which focuses on strategic fit and stakeholder acceptability within the recommendation itself; the competency-balance mistake is about whether the answer, taken as a whole across the paper, has actually engaged with all five marking dimensions rather than concentrating in one or two.

Building this into your exam approach

Before you start writing an answer to any SCS requirement, it is worth pausing to check which competencies the requirement is obviously inviting — most are written to touch at least three of the five — and deliberately planning to address each one within the same answer rather than assuming a strong technical response will carry the whole requirement. This is a planning habit worth rehearsing on full timed mock scripts before the real sitting, in the same way candidates are advised to plan time budgets and avoid generic, unanchored recommendations at the earlier case study levels; SCS simply raises the stakes because the competency-balance requirement is stricter and the material is more integrated across strategy, finance and implementation.

Exam technique checklist

• Remember the pass rule has two parts: 80 of 150 marks overall, and at least one-third of the marks allocated to each individual competency.
• Before answering a requirement, identify which of Technical, Business, People, Leadership and Digital it is inviting, and plan to touch each one within the same answer.
• Do not keep adding depth to a calculation once it is technically complete; that time is better spent addressing a competency your answer has not yet engaged with.
• Write directly to the stakeholder named in the requirement (People) and describe how a recommendation would actually be implemented and led (Leadership), not just what the recommendation is.
• Look for a genuine data, systems or digital governance angle in every requirement involving a change project or investment decision, rather than treating Digital as an afterthought.

Competency balance is a structural exam-technique issue that sits alongside, not instead of, strong technical work — both are needed, and neither compensates for a shortfall in the other under SCS's marking rules. For the full mechanics of how pre-seen and unseen material combine and how marks are awarded holistically across a script, see our guide to how CIMA case study exams are marked.