Most ACCA SBR candidates do not lose marks because they know nothing.
They lose marks because the knowledge they have does not appear clearly enough in their answer.
A requirement is misread. A paragraph explains the standard but never applies it. A conclusion is implied rather than stated. Too much time is spent on one issue while easier marks are left untouched elsewhere.
These problems are frustrating because they can survive weeks of revision. You may keep learning more technical content while repeating the same answer-writing habits in every timed practice.
An SBR answer audit helps you find those habits before exam day.
It is a structured review of your script that looks beyond whether the accounting treatment is technically correct. It checks whether your answer is relevant, applied, complete, professionally presented and written at a pace you can sustain across the whole exam.
Candidates developing their technique with an ACCA SBR tutor should use this type of audit regularly. The aim is not to make every answer perfect. It is to identify where marks are being lost unnecessarily and correct the pattern before it becomes fixed.
Why technical knowledge is only part of the result
SBR is not a memory test.
You need technical knowledge, but the exam does not reward everything you know about a topic. It rewards the points that answer the specific requirement.
A candidate may understand impairment thoroughly but still score poorly because the answer becomes a general explanation of IAS 36. Another candidate may know less detail but earn more marks by identifying the relevant indicators, applying the scenario facts and reaching a sensible conclusion.
The difference is not intelligence. It is answer control.
This is why candidates often leave an exam believing they wrote a lot but still receive a disappointing result. Volume does not guarantee marks. Technical accuracy does not guarantee relevance. A well-written explanation does not guarantee that the requirement has been answered.
An answer audit separates these issues.
It asks whether your knowledge has been converted into marks.
What an SBR answer audit actually checks
An answer audit is not the same as comparing your script with a model answer.
Model answers can be useful, but they often contain more detail than a candidate could realistically produce under timed conditions. Reading one may also encourage you to focus on points you missed rather than understanding why you missed them.
The audit instead examines your process.
It checks six areas:
- Requirement control
- Relevance
- Scenario application
- Technical accuracy
- Professional communication
- Time and completion
These areas overlap, but each reveals a different type of lost mark.
You may be technically strong but weak on application. You may write clearly but answer the wrong verb. You may produce good paragraphs but leave too much of the paper unfinished.
The purpose of the audit is to identify which failure is costing you the most.
Start with the requirement before reading your answer
The first step is to return to the requirement.
Do not begin by reading what you wrote. Read the requirement as if you were seeing it for the first time.
Identify the verb. Look for words such as explain, discuss, evaluate, advise or recommend. Then identify who the answer is for and what decision or issue needs to be addressed.
Now summarise the task in one sentence.
For example:
“Advise the directors on the correct accounting treatment and explain the effect on the financial statements.”
That sentence gives you a simple test for every paragraph in your script.
Does the paragraph advise the directors?
Does it explain the accounting treatment?
Does it show the financial statement effect?
If not, the paragraph may contain useful knowledge but still fail to answer the requirement.
This is often the first place an answer audit uncovers lost marks.
Audit the opening of each section
The first lines of an answer matter because they show whether you understood the task.
Weak openings often repeat the scenario or begin with a broad definition.
For example:
“Revenue is governed by IFRS 15 Revenue from Contracts with Customers.”
That statement may be correct, but it does not yet address the issue.
A stronger opening identifies the decision:
“The key issue is whether control of the goods passed to the customer before the reporting date.”
The second version is better because it immediately focuses on the accounting question.
During your audit, underline the first sentence of each section. Ask whether it identifies the issue or merely introduces the topic.
If it only introduces the topic, rewrite it as a decision or problem.
This small change can make the rest of the answer more focused.
Check whether every paragraph earns marks
Candidates often include paragraphs because they are technically correct, not because they are useful.
A paragraph earns marks when it does at least one of the following:
- identifies a relevant issue
- states a necessary accounting principle
- applies that principle to a scenario fact
- explains an effect on the financial statements
- evaluates an alternative
- gives a conclusion or recommendation
If a paragraph does none of these things, it is probably filler.
Filler is dangerous in SBR because it consumes time and creates the impression of progress while reducing the number of marks you can attempt elsewhere.
Read each paragraph and write a short label beside it.
Issue. Rule. Application. Impact. Conclusion.
If you cannot label the paragraph, ask whether it belongs in the answer.
A good SBR script does not need to be long. It needs to be productive.
Find the theory dumps
A theory dump occurs when a candidate writes everything remembered about a standard without selecting the parts relevant to the scenario.
It often begins well. The candidate recognises the topic and starts writing confidently. The problem is that the answer becomes a technical note rather than a response to the requirement.
For example, a question about whether an arrangement is a joint operation or joint venture does not require a full summary of IFRS 11. It requires the classification test, application to the contractual rights and obligations, and the resulting accounting treatment.
During the audit, highlight any block of three or more sentences that contains no scenario fact.
That does not automatically mean the passage is wrong. Some technical explanation is necessary. However, long stretches without application usually indicate that the answer has drifted into theory.
Try reducing the rule to one or two sentences, then use the saved space to apply the facts.
This produces a stronger answer and protects time.
Test the quality of your scenario application
Mentioning the company name is not application.
Repeating a fact is not analysis either.
Good application explains why the fact matters.
Suppose the scenario says that a customer can cancel a contract without penalty before delivery.
A weak application would be:
“The customer can cancel the contract before delivery.”
That simply repeats the fact.
A stronger application would be:
“Because the customer can cancel without penalty before delivery, the contract may not create enforceable rights and obligations at that stage. Revenue should therefore not be recognised merely because production has started.”
The second version connects the fact to the accounting consequence.
When auditing your script, circle each scenario fact you used. Then check the sentence that follows it.
Does the answer explain why the fact changes the treatment, estimate or disclosure?
If not, add the missing connection.
This is one of the fastest ways to turn a descriptive answer into an analytical one.
Look for conclusions that never arrived
Many SBR answers contain good discussion but no clear conclusion.
The candidate explains both sides, mentions several facts and then moves to the next section without stating the treatment.
Markers should not have to infer your decision.
A conclusion does not need to be long. It may be one sentence.
“The arrangement should therefore be classified as a joint venture and accounted for using the equity method.”
“The provision should not be recognised because there is no present obligation at the reporting date.”
“Management should revise the impairment model and disclose the key assumption and sensitivity.”
During the audit, go to the end of each requirement and highlight the conclusion.
If there is nothing to highlight, add one.
Clear conclusions help technical marks, professional marks and overall readability. They also force you to decide what the evidence means.
Audit how you handled the requirement verb
Requirement verbs are not decoration.
They tell you what kind of answer is expected.
To explain, you need to make the issue understandable.
To discuss, you usually need to consider relevant factors and reach a view.
To evaluate, you need to assess strengths, weaknesses, consequences or competing evidence.
To advise, you need to recommend an action or treatment.
To criticise, you need to identify weaknesses and explain why they matter.
A common answer-writing problem is using the same approach regardless of the verb. Candidates explain when they should evaluate, or describe when they should advise.
During the audit, write the requirement verb at the top of your script.
Then look for evidence that you performed that task.
If the requirement asked you to advise, underline your recommendations.
If it asked you to evaluate, identify where you weighed evidence or considered an alternative.
If you cannot find that evidence, the answer may be technically relevant but incomplete.
Check the financial statement impact
SBR answers often stop at identifying the accounting treatment.
A stronger answer explains what that treatment changes.
Depending on the issue, you may need to mention the effect on profit or loss, other comprehensive income, assets, liabilities, equity, disclosures or future periods.
You do not need to describe every possible effect. Focus on the consequences that matter in the scenario.
For example:
“Recognising the provision will increase liabilities and reduce profit for the year.”
“The effective portion of the cash flow hedge will initially be recognised in other comprehensive income.”
“The correction will reduce revenue and receivables at the reporting date.”
This is particularly important when the requirement asks about the impact of a treatment or asks you to advise management.
During your audit, identify each accounting conclusion and ask:
What changes in the financial statements?
If the answer is missing, add one clear sentence.
Review your use of professional judgement
SBR does not always provide a single obvious answer.
Some issues depend on evidence, estimates and judgement. Candidates can lose marks by avoiding a conclusion because they are worried about being wrong.
Professional judgement does not mean pretending to be certain when the facts are unclear. It means identifying the relevant factors, assessing the available evidence and reaching a reasonable view.
A good judgement paragraph might say:
“Although the legal form is a separate vehicle, the contractual terms give the parties direct rights to the assets and obligations for the liabilities. The arrangement is therefore likely to be a joint operation.”
The word “likely” acknowledges judgement, but the paragraph still reaches a conclusion.
During your audit, look for phrases such as “it depends”, “management should consider” or “there may be an issue”.
These phrases are not always wrong. The problem occurs when they replace analysis.
Ask what it depends on. State which facts support the stronger conclusion. Then give your view.
Check whether your recommendations are usable
A recommendation should tell management what to do.
Weak recommendations sound like this:
“Management should ensure that the correct accounting treatment is applied.”
That says very little. It repeats the responsibility without explaining the action.
A better recommendation is specific:
“Management should revise the forecast using supportable revenue assumptions, perform a sensitivity analysis and disclose the assumptions that create the greatest risk of material adjustment.”
This tells management what needs to change.
Recommendations are especially important in ethics, governance, current issues and narrative reporting requirements.
During the audit, put a box around each recommendation.
Then ask whether a finance director or audit committee could act on it.
If the answer is no, make it more specific.
Audit your professional marks
Professional marks should not be treated as something separate from the technical answer.
They are earned through the way you organise, analyse and communicate your response.
A script is more likely to earn professional marks when it uses clear headings, stays relevant, communicates in an appropriate tone and reaches practical conclusions.
The following checklist can be used for the whole answer:
- Headings reflect the requirement rather than broad syllabus topics
- Paragraphs are short and contain one main point
- Scenario facts are linked to accounting consequences
- Technical language is used accurately but explained clearly
- Recommendations are practical and directed to the intended recipient
- Conclusions are visible and unambiguous
- The answer avoids repetition, long introductions and unnecessary definitions
- The tone is professional and suitable for a board, finance director or audit committee
Do not wait until the final mock to think about these marks.
Professional communication is a habit. It develops through repeated practice and review.
Find where time was lost
An answer may be strong in isolation but still be part of a poor exam performance.
If you spent 35 minutes on a requirement that should have taken 20, the additional quality may not compensate for the marks left unanswered elsewhere.
Your audit should therefore include timing.
Write down how long you spent on each requirement. Compare this with the marks available.
Then look at the longest answer.
Did the additional time produce additional marks, or did it produce repetition?
Common signs of overspending include:
- long definitions at the start
- several paragraphs making the same point
- explaining standards beyond what the facts require
- rewriting a conclusion in different words
- remaining on a difficult issue instead of moving on
The goal is not to write faster for its own sake. It is to use time where it produces marks.
A complete paper containing concise, relevant answers is often stronger than an incomplete paper containing several polished sections.
Identify untouched marks
Blank sections are visible lost marks.
Partially answered sections can be just as damaging.
A candidate may begin a requirement, make one point and then abandon it when the time pressure increases. The script technically contains an answer, but many of the available marks remain untouched.
During the audit, estimate how many separate scoring opportunities each requirement offered.
Did the scenario contain three issues but you discussed only one?
Did the requirement ask for the accounting treatment and ethical implications, but you answered only the accounting part?
Did you identify a problem without explaining the effect or recommendation?
This is not about predicting the exact marking scheme. It is about checking whether you responded to the full task.
Write a short note beside every missing component. These become targets for your next timed practice.
Separate knowledge gaps from exam technique gaps
This distinction is essential.
A knowledge gap means you did not know the relevant principle.
An exam technique gap means you knew it but failed to use it effectively.
The correction is different.
If you did not know the recognition criteria, revise the technical area and then answer a short question on it.
If you knew the criteria but wrote an irrelevant definition, the solution is application practice.
If you knew the treatment but ran out of time before writing it, the solution is pacing and completion.
Candidates often respond to every weak answer by revising more content. This can leave the real problem unchanged.
Your audit should label each error as either knowledge or execution.
Over several scripts, a pattern will emerge.
That pattern should shape your revision plan.
Use the audit to choose your next practice task
An audit has little value if it ends with a list of faults.
You need to convert the findings into one or two actions.
Do not attempt to fix everything in the next answer. Choose the issue that is costing the most marks.
If your answers are generic, make scenario application the focus of the next practice.
If you miss conclusions, add a conclusion to every section.
If time control is the main problem, sit a shorter timed set and move on strictly when the allocated time ends.
If your recommendations are vague, practise writing advice to an audit committee.
One focused change is easier to measure than a general instruction to “improve exam technique”.
Rewrite only the part that matters
You do not need to rewrite the whole answer after every audit.
That can take too long and may turn review into another form of passive study.
Choose the weakest paragraph and rewrite it.
Keep the same technical issue, but improve the structure.
Begin with the issue. State the necessary rule. Apply the specific facts. Explain the impact. Finish with a conclusion or recommendation.
Then compare the original and revised versions.
Ask what changed.
The revised paragraph should usually be shorter, clearer and more applied.
This exercise helps you recognise strong writing more quickly during the exam.
Repeat the audit across several scripts
One answer may be affected by the topic, your mood or the difficulty of the question.
Three or four scripts reveal habits.
You may notice that you consistently:
- overwrite rules
- avoid clear conclusions
- miss the second part of requirements
- use scenario facts without explaining their significance
- spend too long on the opening question
- make vague recommendations
- leave ethics until the end and rush it
These patterns are more important than the mark from any single practice attempt.
Once you know your pattern, your revision becomes more targeted.
Instead of trying to become better at everything, you can remove the few habits that repeatedly cost marks.
When external feedback becomes useful
Self-auditing is valuable, but candidates cannot always see their own patterns.
You know what you intended to say, which can make an unclear paragraph look more complete than it really is.
External feedback helps when it identifies why the answer did not earn marks and what should change in the next attempt.
Useful feedback is specific.
It may show that a paragraph contains correct theory but no application, that a recommendation is too vague or that a conclusion contradicts the earlier analysis.
Candidates using a structured ACCA SBR course should make the most of marked practice by comparing the feedback with their own answer audit.
The aim is not simply to receive a mark.
It is to understand the repeated behaviour behind that mark.
Run a final audit before exam week
In the final stage of revision, use one complete timed script as your evidence.
Do not judge it by how confident you felt while writing. Audit what is actually on the page.
Check whether you:
answered every part of the requirement, used the scenario throughout, controlled the amount of technical detail, explained financial statement effects, reached conclusions, made practical recommendations and completed the paper within the available time.
Then identify the final two habits you want to protect on exam day.
These should be simple and memorable.
For example:
“Read the requirement before the scenario.”
“One applied point and one conclusion before moving on.”
“Stop when the allocated time ends.”
Your final exam strategy should not contain fifteen instructions. Under pressure, you need a few rules you can follow automatically.
The marks are often already within reach
Candidates sometimes assume that improving their result requires learning significantly more content.
Sometimes it does.
However, many candidates already know enough to earn more marks. The problem is that those marks are hidden behind weak application, unclear conclusions, incomplete requirements and poor time control.
An SBR answer audit brings those losses into view.
It shows you where your script stopped answering the question and started displaying knowledge. It reveals where you described a fact but failed to analyse it. It identifies conclusions that were never written and time that did not produce enough marks.
Once those problems are visible, they can be corrected.
What to do next
Choose one recent timed answer.
Read the requirement first, then audit the script for relevance, application, conclusions, professional communication and time control.
Identify the single habit that cost the most marks.
Rewrite one paragraph and make that habit the focus of your next timed attempt.
Do this consistently before exam day and your scripts will become shorter, clearer and more productive.
The aim is not to write more.
It is to make more of what you write count.
