ACCA SBL study materials
ACCA SBL study resources

ACCA SBL common mistakes

ACCA SBL · Understand the traps and how to avoid them.

Mistake 1

Writing a generic essay on the topic in the scenario prompt without applying it to the named organisation, its industry, and the people or numbers given in the case material.

Candidates memorise models and definitions during revision and then 'dump' them under time pressure, treating the case as a trigger for recalled theory rather than as the source of evidence the answer must use.

What to do instead

Before writing, extract the case facts into a short grid (organisation, sector, key stakeholders, the specific decision or problem, and the figures provided). Draft each paragraph so it opens with a case-specific claim and cites at least one named fact from the scenario, then use the model only to structure the argument.

Mistake 2

Producing bullet-point lists of model headings (PESTEL, Porter's Five Forces, SWOT) with one-word entries and no explanation of relevance or consequence for the organisation.

Lists feel fast and productive under exam time pressure, and candidates confuse coverage of a framework with analysis; they have practised recalling headings rather than using them to reach a judgement.

What to do instead

For every model point, write three linked sentences: what the case shows, why it matters for this organisation's objective, and what it implies the board or management should do. Delete any heading that cannot be tied to a case fact and a consequence.

Mistake 3

Ignoring the professional skills marks by answering only the technical content and never demonstrating scepticism, evaluation, or commercial acumen in the required format.

Candidates focus revision on technical syllabus areas and treat the skills marks as automatic, so they never practise the behaviours (challenging assumptions, weighing evidence, reaching a recommendation) that the marking scheme rewards.

What to do instead

Build a checklist of the assessed skills and deliberately place at least one challenge to a stated assumption, one balanced consideration of alternatives, and one clear recommendation with reasoning in every answer. Practise under timed conditions and self-mark against the skills descriptors.

Mistake 4

Presenting figures from the case without computing the relevant ratios, trends, or variances, or computing them but failing to interpret what the numbers mean for the decision.

Candidates either avoid numbers through anxiety or produce a page of calculations with no commentary, having practised computation in isolation from interpretation.

What to do instead

For each numerical exhibit, calculate only the two or three measures that bear on the question, then write an explicit 'so what' sentence linking the figure to the decision, including the limitation of the data. State the formula and the result briefly and spend the words on interpretation.

Mistake 5

Describing risks or controls in general terms without identifying the specific risk event, its likelihood and impact for this organisation, and a proportionate response with an owner.

Risk frameworks are often learned as lists of categories, so candidates name a category rather than articulating a concrete event and its consequence, and they omit ownership because the case does not state it.

What to do instead

Use a consistent structure for each risk: event, cause, consequence, likelihood and impact judgement, response (avoid, reduce, transfer, accept), and a named owner or monitoring mechanism. Tie each risk to a fact in the case and quantify the exposure where figures allow.

Mistake 6

Proposing technology or innovation solutions as generic recommendations ('invest in AI', 'improve cybersecurity') without assessing feasibility, cost, data readiness, or the ethical and governance implications for the organisation.

Candidates treat emerging technology as a buzzword topic and lack confidence in the operational detail, so they stay at the level of a headline recommendation rather than evaluating implementation.

What to do instead

For each proposed solution, state the business problem it solves, the data and capability required, an indicative cost and benefit, the key implementation risk, and the governance or ethical safeguards needed. Compare it against at least one alternative and justify the choice.

Mistake 7

Failing to answer the specific verb and format in the requirement, for example writing a report when a briefing note was asked for, or evaluating when the question asked for a recommendation to the board.

Candidates skim the requirement to save time and default to a familiar answer style, missing that format, audience, and instruction words carry marks.

What to do instead

Underline the instruction verb, the deliverable format, and the audience in the requirement before planning. Use the correct headings, tone, and structure for that format, and check at the end that every part of the requirement has been explicitly addressed.

Mistake 8

Presenting only one side of an argument or a single recommendation with no consideration of alternatives, assumptions, or sensitivity to changed conditions.

Candidates want to appear decisive and fear that balance looks indecisive, so they omit the evaluation that professional-level answers require.

What to do instead

Structure evaluative answers as options, criteria, and a justified recommendation. State the key assumptions behind the recommendation and describe what would change the conclusion if those assumptions failed.

Mistake 9

Running out of time because the candidate writes a long answer to the first requirement and leaves later requirements, often the highest-mark ones, barely attempted.

Poor time allocation in the planning stage and the temptation to perfect the first answer, combined with underestimating how long analysis takes under exam conditions.

What to do instead

Allocate time to each requirement in proportion to its marks before starting, and keep to it with a visible clock. Write the plan for all requirements first, then answer in mark order, leaving a fixed buffer for review.

Mistake 10

Treating ethical issues as abstract principles and failing to identify the specific stakeholder harmed, the applicable professional code principle, and the practical course of action for the individual or board.

Candidates learn ethics as definitions and do not practise applying a code to a concrete dilemma with named parties and pressures.

What to do instead

For each ethical issue, name the stakeholders affected, identify the relevant principle (integrity, objectivity, confidentiality, professional competence, or professional behaviour), explain the consequence of each option, and recommend a specific action with escalation steps.