A mock exam that goes badly can be more useful than one that goes smoothly.
That sounds backwards, especially a few weeks before the December ACCA SBR sitting.
Most candidates want reassurance by this stage. They want a mock result that proves the revision is working. They want to finish the paper feeling reasonably confident and see a mark comfortably above 50.
The problem is that a comfortable mock can sometimes hide the exact weaknesses that will hurt you on exam day.
You pause the timer for a difficult calculation. You check a technical point because you are nearly certain but want reassurance. You spend an extra ten minutes finishing a requirement because abandoning it feels wasteful. You choose a paper containing topics you revised recently.
The final script looks respectable.
The conditions were not.
A genuinely useful December mock should expose weaknesses rather than protect confidence. Candidates working with an ACCA SBR tutor should use at least one mock as a diagnostic exercise designed to show what happens when the safety nets disappear.
If that mock goes badly, good.
You have found the problems while there is still time to fix them.
The purpose of a mock is not to make you feel ready
A mock exam should answer a simple question.
What would happen if you had to sit SBR today?
That means the conditions need to resemble the real examination closely enough to produce useful evidence.
The purpose is not to demonstrate how much you know when everything goes well.
It is to expose what happens when you are tired, uncertain, rushed and confronted with something you did not expect.
Those conditions matter.
You may understand impairment perfectly during revision but struggle to identify the issue when it is buried inside a long scenario.
You may know IFRS 9 but lose too much time trying to make one calculation perfect.
You may understand ethical principles yet write vague answers because the requirement appears late in the paper and you are rushing.
The mock needs to reveal those behaviours.
A reassuring score achieved under comfortable conditions may tell you less than a disappointing score achieved under strict ones.
Do not choose a friendly paper
Candidates naturally prefer questions containing topics they know.
That makes sense during early revision.
It makes less sense during a diagnostic mock.
If you deliberately select a paper because you recently revised the main topics, you are testing memory more than exam performance.
A proper mock should contain uncertainty.
You should not know in advance whether the paper will suit you.
That discomfort is useful.
The real exam does not ask which topics you would prefer.
You need to be able to identify unfamiliar issues, retrieve enough relevant knowledge and build a professional answer even when the question does not resemble the example you hoped would appear.
Choose a mock you have not already analysed in detail.
Do not read the answers first.
Do not search the topics before beginning.
Start with the paper.
Remove the pause button
Stopping the timer is one of the easiest ways to make a mock meaningless.
Candidates tell themselves they are only pausing for a minute.
They want to check a rule.
They need to refill a drink.
They want to finish the sentence before moving on.
Those minutes accumulate.
More importantly, pausing removes one of the biggest pressures of the real exam.
Time does not stop while you think.
You need to make decisions while the clock is moving.
That includes deciding when you know enough to write, when to abandon a difficult detail and when to move to the next requirement.
A mock that does not test those decisions is not testing one of the most important SBR skills.
Run the clock continuously.
If you lose five minutes thinking, those five minutes are gone.
That may feel harsh.
It is also useful.
Do not rescue yourself with notes
The same principle applies to technical support.
If you reach a point where you cannot remember the exact accounting treatment, do not immediately check your notes.
Write what you can.
Explain the principle you remember.
Use the scenario facts.
Make the best professional judgement available and move on.
After the mock, check the technical point.
This distinction matters because it shows whether you have a knowledge gap or an exam execution problem.
If you genuinely did not know the treatment, you need technical revision.
If you knew enough but panicked because you could not remember one detail, you need to practise working with imperfect recall.
SBR does not require a perfect memory of every paragraph in every standard.
It requires enough technical knowledge to produce relevant professional advice.
Let yourself get stuck
A diagnostic mock should allow problems to happen.
If a requirement confuses you, do not immediately abandon the exercise.
Observe what you do.
Do you reread the same paragraph repeatedly?
Do you start writing generic theory because you are not sure what the issue is?
Do you spend fifteen minutes chasing a five-mark point?
Do you freeze because you cannot identify the standard?
These behaviours are valuable evidence.
They show you what needs training.
The temptation after a difficult section is to say the mock was unfair or unusually hard.
That may occasionally be true.
More often, the difficulty is precisely why the exercise matters.
The real exam will contain something that feels uncomfortable.
Your preparation should include practising what you do next.
The mock should test completion above perfection
One of the biggest December risks is spending too long on answers you know well.
You see a familiar issue and begin writing.
The points come easily, so you continue.
Then you add another technical detail.
Then another.
The answer feels strong.
Twenty minutes later, you have spent far too long on a requirement that probably stopped earning significant extra marks several paragraphs ago.
The cost appears later.
The final part of the paper is rushed.
A whole requirement may be left incomplete.
That is why a strict mock should test whether you can stop writing.
When the time allocated to a section ends, move on.
Even when you know more.
Even when the conclusion could be better.
Even when another calculation step would make the answer feel complete.
The exam rewards marks across the paper, not satisfaction with one section.
A bad score needs to be diagnosed properly
Suppose you finish the mock and receive 42 per cent.
That number is disappointing.
It is not the diagnosis.
The useful question is why the mark was 42.
Did you leave 20 marks unanswered?
Did you attempt everything but produce generic answers?
Did technical gaps affect several major areas?
Did calculations consume too much time?
Did you repeatedly fail to conclude?
Did you answer the accounting topic but ignore the requirement verb?
Those problems require different solutions.
A candidate who scored 42 because they left the final 20 marks almost blank may be much closer to passing than someone who attempted everything but lacked the necessary technical knowledge.
The headline mark does not tell you what to revise next.
The script does.
Separate technical failure from exam failure
This is one of the most important things to do after the mock.
Go through every weak section and label the problem.
A simple diagnosis might include:
- Knowledge gap – you genuinely did not know the relevant accounting principle.
- Application gap – you knew the rule but failed to use the scenario facts.
- Requirement error – you answered the topic but not what was asked.
- Timing problem – you spent too long elsewhere and rushed the section.
- Conclusion gap – you discussed the issue but never stated the treatment or recommendation.
- Professional skills weakness – the answer lacked clarity, scepticism, analysis or practical advice.
You do not need twenty categories.
You need enough to identify patterns.
If most lost marks were technical, your final weeks need targeted knowledge repair.
If most were execution problems, more reading may be the wrong response.
Look for the marks that were never attempted
Blank space is one of the easiest weaknesses to diagnose.
If 15 marks were untouched, those marks were unavailable regardless of how strong the rest of the script was.
Candidates often respond by saying they simply need to write faster.
That may not be the real issue.
You may be writing too much.
You may be spending too long planning.
You may be trying to remember technical details that are worth only one mark.
You may be polishing early answers instead of moving on.
Find where the time disappeared.
Then recreate that problem in shorter timed sessions until the behaviour changes.
If you always overspend on the first large requirement, practise stopping.
Not reading about stopping.
Actually stopping.
Identify the paragraphs that earned almost nothing
A long paragraph can feel productive.
It may contain very few marks.
Look for sections where you explained an accounting standard accurately but barely referred to the scenario.
These are often theory dumps.
They are particularly dangerous because they make candidates feel knowledgeable.
The writing sounds technical.
The problem is that the examiner already knows the standard.
The marks come from using it.
Take one weak paragraph and underline every scenario fact.
If there is nothing to underline, that is a warning.
Rewrite the paragraph using the relevant fact, explain why it matters and reach a conclusion.
You will often find that the improved version is shorter.
Check whether your conclusions disappeared under pressure
Candidates frequently conclude well at the beginning of a mock and badly near the end.
That is useful evidence about what happens when fatigue and time pressure increase.
Read the final sentence of every requirement.
Does it tell the reader what the accounting treatment should be?
Does it advise management what to do?
Does it state whether the proposal is appropriate?
If the answer simply stops after the discussion, you have left work unfinished.
A conclusion does not need another paragraph.
One clear sentence is often enough.
Train yourself to include it before moving on.
The professional skills marks should also be tested
A strict mock should not focus only on technical marks.
Ask whether the script sounds professional.
Are headings useful?
Can somebody identify your main conclusion quickly?
Did you challenge management where necessary?
Did you explain the commercial or financial consequence?
Were recommendations specific?
Did you communicate to the recipient named in the requirement?
These are not decorative extras.
They influence how effective the whole answer becomes.
The December mock should reveal whether professional skills survive when you are under pressure.
If they disappear completely in the second half of the paper, that becomes part of your final revision plan.
Do not respond to a bad mock by restarting the syllabus
This is one of the worst reactions.
A candidate scores poorly, panics and returns to page one of the course notes.
Two weeks later, they have reread a large amount of material and done very little timed writing.
The technical knowledge feels more familiar.
The exam behaviours remain unchanged.
Use the mock to create a narrow repair plan.
If three technical areas genuinely caused problems, revise those three.
If the main issue was application, practise applied paragraphs.
If timing failed, use timed sets.
If requirements were misread, practise planning before writing.
The solution should match the diagnosis.
Your next practice should be shorter
You do not necessarily need another full mock immediately.
If the first mock exposed several problems, train them separately.
Suppose the biggest weakness was timing.
Complete a 40-minute set and move on exactly when each allocated section ends.
Suppose application was weak.
Take three requirements and force every substantial paragraph to use a scenario fact.
Suppose conclusions were missing.
Complete short questions where your only rule is that every section ends with a clear decision.
These sessions allow you to change behaviour without the noise of a full exam.
Then test the improvement later with another longer paper.
Confidence should come after the diagnosis
Candidates sometimes avoid strict mocks because they worry a bad result will damage confidence.
That can happen.
False confidence is worse.
You do not want to discover on exam day that your timing only worked because you paused during practice.
You do not want to discover that you recognised answers only because you had already read the model solution.
You do not want to discover that your technical recall collapses without notes.
A difficult mock gives you honest information.
Confidence can then be rebuilt from evidence.
You complete a timed set properly.
Your application improves.
You finish the paper.
A previously weak topic becomes manageable.
That is stronger confidence because it is based on changed performance.
The second mock should test whether you learned anything
The real value of the first mock appears in the next one.
Do not simply sit another paper and hope the mark rises.
Choose two or three behaviours to test.
Perhaps they are:
Finish every requirement.
Use the scenario in every substantial point.
Move on when the allocated time ends.
Then sit another strict mock.
Compare the scripts.
Did the behaviour change?
The mark may improve immediately.
It may not.
What matters first is whether the weaknesses you identified are becoming less visible.
A mock becomes useful when it changes the way you perform.
Why this matters particularly before December
By the final weeks before an exam, candidates often feel pressure to keep adding knowledge.
There is always another standard to revisit.
Another technical article to read.
Another video to watch.
At some point, the bigger question becomes whether you can use what you already know.
That is what the deliberately difficult mock tests.
It forces technical knowledge, application, judgement, communication and time control into one exercise.
It also gives you enough time to make focused corrections before exam day.
Candidates using a structured ACCA SBR course should treat marked mocks and feedback as diagnostic tools rather than simply milestones to complete.
The mark matters.
The reason behind the mark matters more.
What to do next
Choose one mock you have not already studied.
Sit it under strict conditions.
No notes.
No paused timer.
No checking answers halfway through.
No additional time because one requirement feels unfinished.
Let the paper expose the weaknesses.
Then review the script properly.
Identify the technical gaps, the marks you never attempted and the behaviours that wasted time.
Choose the two biggest problems and train them.
A mock that goes badly several weeks before the exam is not a disaster.
A mock that hides your weaknesses is more dangerous.
The purpose of December preparation is not to prove that you are already ready.
It is to find whatever still prevents you from being ready and fix it before the real paper begins.
