Core takeaways: (1) Plan each answer before writing: evidence, framework, format, recommendation. (2) Tie every governance and ethics point to specific case facts and consequences, not textbook recitals. (3) Pick the framework the requirement's verb needs; evaluate, don't describe. (4) Connect technology and change recommendations to strategy, risk and people together. (5) Drill one requirement at a time against a rubric, then rehearse full cases under timed conditions and use consistent rubric scores as your readiness gate.
Planning an SBL answer before writing a single sentence
Treat each requirement as a deliverable to be architected first: choose the exhibits you will cite, the framework that organises them, the requested format, and the recommendation you will land on.
SBL requirements are integrative by design. A single task can ask you to assess a proposed acquisition while simultaneously touching governance of the deal process, ethical threats around valuation advice, and the risk of a difficult integration. That breadth is where the concept gets hard: knowing a model is separate from assembling a coherent argument across syllabus areas. A plan converts that breadth into structure. Spend the opening portion of each task listing, in shorthand, the two to four exhibits that anchor each main point and the verb you must serve — evaluate, advise, assess — before composing anything.
The plan should also fix the format early. A board memorandum needs headings, a conclusion up front and a clear recommendation; an email needs audience-appropriate tone and brevity; briefing notes need short, headed points. Writing the skeleton — section headings mapped to exhibits — means later sentences have a destination. It also exposes gaps while you can still fix them: if two planned points draw on the same exhibit, or none of your points produce a recommendation, you have found the flaw in minutes rather than after committing it to prose.
Mining the exhibits: turning case documents into evidence
Read exhibits actively, tagging each with the syllabus area it feeds — governance signals, ethical red flags, performance data, culture cues — so evidence is retrievable the moment a requirement names its topic.
Exhibits are the raw material for application, and each type signals differently. Board minutes reveal decisions, dissents and who raised concerns — often the seed of a governance answer. Financial extracts supply trends you can use to test whether an option is acceptable. Internal emails expose culture and ethical tone; news cuttings bring stakeholder reaction; job descriptions and organisation charts expose reporting lines and control gaps. Reading with a pen, marking each document as you go, turns a pile of papers into an indexed evidence bank you can consult while drafting.
Active reading means questioning rather than absorbing. When an executive claims a project is on track, check whether the minutes or financial data corroborate it; unverified claims are exactly where professional scepticism earns its place. Note dates and sequences too: if a risk was flagged in a meeting months before an adverse event, that timeline is itself analysable evidence about the risk management process. The output of this pass is a short map — exhibit name, one-line relevance, syllabus area — which replaces the need to re-read documents under time pressure.
A tag-coding scheme keeps this pass fast and repeatable across practice cases. Mark each exhibit as you first read it, using the same six tags every time so retrieval becomes automatic rather than a fresh decision in every exam.
- G — governance and board behaviour
- E — ethics and professional threats
- R — risk, control and internal audit
- F — financial and performance evidence
- S — strategy, market and competitive position
- T — technology, data and digital change
Governance tasks: board oversight versus management action
Anchor governance answers in the case's specific appointments, committees and behaviour, then connect them to the agency problem — managers' interests diverging from owners' — and a concrete, case-specific remedy.
Agency theory is the organising idea: directors are agents delegated to run the company on shareholders' behalf, and governance mechanisms exist to monitor that delegation. Generic statements — that boards need independent oversight — organise an answer but stand for little on their own. Application means naming the case's specific deviation from sound oversight and tracing its consequence: if appointment power effectively sits with the chief executive, monitoring weakens because the agent influences who watches the agent. From that diagnosis, a remedy follows naturally — an independent nominations process, a committee membership review, or disclosure to shareholders.
Worked scenario: an exhibit shows a recently retired executive director being appointed to the board, and the chief executive chairing the committee that recommended it. The plausible mistake is to recite that non-executive directors provide independent challenge, full stop. The stronger answer observes that a former executive is unlikely to be independent in appearance or substance, that the appointment process concentrated power in the agent being monitored, and that investors may reasonably question the board's oversight quality. The recommendation — reconstitute the committee, review the appointment, disclose the rationale — is then case-specific, consequential and actionable, which is what turns a principle into marks.
Ethics dilemmas: resolving them, not labelling them
Name the threat, map the affected stakeholders, generate and evaluate options, then recommend a defensible course with escalation routes. Labelling behaviour 'unethical' without a resolution path stops the analysis short.
ACCA's fundamental principles — integrity, objectivity, professional competence and due care, confidentiality and professional behaviour — are the vocabulary, but the substance sits in the resolution. An ethical task usually expects you to identify the threat type (self-interest, self-review, familiarity, intimidation or advocacy), weigh consequences for stakeholders, and recommend what the protagonist should actually do, including where to escalate. A complete answer also distinguishes between what is commercially prudent, what breaches a principle, and what a professional accountant's ethical framework expects, because those three can diverge in a given case.
Worked scenario: a finance director pressures an accountant to recognise revenue early so a loan covenant is met, and the accountant emails you for advice. A weak response says only that this breaches integrity. The stronger one identifies self-interest and intimidation threats, notes the consequence that misstated accounts may later need correction with covenant and reputational fallout, sets out options — raise it with the finance director citing reporting standards, escalate to the audit committee, seek confidential advice — and recommends escalating if the pressure persists, with every step documented. That structure shows the decision, not just the diagnosis.
Model selection: matching frameworks to the requirement verb
Use the requirement's verb to select one or two organising frameworks, then evaluate — weigh significance, strengths and weaknesses — rather than describing every model you can recall from the syllabus.
Descriptive answers catalogue; evaluative answers judge. 'Describe the competitive environment' permits a structured survey; 'evaluate the competitive position' demands a conclusion about relative strength, supported by evidence. The verb is the instruction. Similarly, 'assess strategic options' invites suitability, acceptability and feasibility tests applied to each option, ending in a justified choice. Selecting the smallest framework that answers the question leaves time for judgement — the part that differentiates an answer — instead of spending it reciting definitions the case never asked for.
Two habits sharpen selection. First, match frameworks to tasks deliberately during practice: after each drill, ask which framework the verb called for and whether a different one would have served it better. Second, adapt the vocabulary to the case's sector and circumstances — a five-forces analysis of a subscription software business should discuss switching costs and network effects as the case presents them, not as generic textbook forces. A framework earns its place when it organises the case's facts into a judgement a board could actually use, and the table below makes that matching explicit.
| Requirement focus | Better-fit frameworks | What the answer must add |
|---|---|---|
| External environment | PESTEL and key drivers | Which trends matter to this strategy, and their implications |
| Industry and competitive position | Porter's five forces, SWOT | Force strengths and a conclusion on relative position |
| Evaluating strategic options | SAF: suitability, acceptability, feasibility | A justified choice plus reasons for rejecting alternatives |
| Risk management and control | Risk appetite, risk register logic, control classification | Whether risks are owned, controlled and reported, with gaps named |
| Leading organisational change | Force-field analysis, Lewin, change levers | This culture's specific barriers and a sequenced set of actions |
| Board and governance review | Agency theory, committee roles, independence | Specific deviations in the case and matched remedies |
Technology and data tasks: integrating digital themes, not isolating them
Treat a technology initiative as a strategic decision with risk, people and governance consequences. Evaluate whether it advances the organisation's objectives and what controls must accompany it.
A proposed data analytics platform, for example, is never just technology. It carries a strategic claim — faster, better-informed decisions that competitors cannot easily match; risk dimensions such as data quality, cyber exposure and data protection duties; people implications in skills and job redesign; and a governance question about who owns the data and reports on the programme to the board. An answer that touches those dimensions together, in the case's context, reflects how the syllabus positions digital topics: as business decisions to be evaluated, not IT specifications to be listed.
Evaluation means weighing, not enumerating benefits. Ask what evidence the case gives that the initiative will deliver: does the financial extract support the projected return, does management have the capability, is the organisation's risk appetite consistent with the exposure the technology introduces? Where the case shows weaknesses, recommend mitigations — a phased rollout, a named data governance owner, board-level reporting on cyber risks. Framing the recommendation as conditional, worth pursuing only if the named controls are in place first, demonstrates judgement and keeps the answer anchored in evidence rather than enthusiasm.
A preparation sequence with a self-check rubric
Move through three phases: refresh frameworks through case reading, drill single requirements against a rubric, then rehearse full cases under timed conditions, scoring every attempt against the same checklist.
Phase one pairs each syllabus area with a full case read for evidence rather than revision notes: refresh the framework the same week you practise spotting it in exhibits. Phase two is the one-requirement drill — take a single task, allow yourself ten minutes of planning, then produce only the plan plus one formatted section, and mark it against the rubric below. Phase three assembles full cases under timed conditions, with every deliverable written in full. One administrative note: for current exam sessions, entry rules and scheduling, rely on ACCA's official qualification pages rather than secondary summaries.
Score each attempt against the rubric and treat the totals as learning milestones, not pass predictions. A plan that cannot name its exhibits, or an answer that ends in a balanced summary instead of a recommendation, tells you exactly which phase needs more time. Rotate syllabus areas across drills — governance one day, ethics the next, technology and change after — so the integration habit forms across contexts. Keep a running list of case facts you failed to notice; reviewed before the next drill, that list is the most direct feedback loop this format allows. Meeting all five rubric checks consistently is your readiness gate.
- Evidence: each main point draws on at least two distinct exhibits
- Application: every point links framework, case fact and consequence
- Format: the deliverable matches what the requirement named, structured for its audience
- Recommendation: a clear, justified course of action appears, with rejected options acknowledged
- Scepticism: management claims are tested against other exhibits rather than accepted at face value
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.