The September ACCA exam session is close enough that revision strategy needs to change.
Strategic Business Reporting is scheduled for Thursday 10 September 2026. At this stage, the biggest mistake is not necessarily doing too little. It can be doing too much of the wrong thing.
Candidates often react to the final weeks by increasing everything.
More notes. More videos. More technical articles. More flashcards. More questions downloaded for later. More hours added to a revision plan that was already difficult to maintain.
The result is often anxiety rather than improvement.
You reach the final week surrounded by material, aware of dozens of areas you could revise and increasingly unsure whether you are ready.
This is the point where good candidates need to become selective.
The question is no longer:
“What else can I learn?”
It is:
“What will actually improve the script I produce on 10 September?”
For many candidates, the answer is not another set of notes. It is better application, stronger conclusions, tighter time control and the ability to keep moving when a question feels uncomfortable.
Candidates using support from an ACCA SBR tutor should now be shifting away from broad syllabus coverage and towards the specific weaknesses showing up in timed answers.
The final countdown is about converting what you already know into marks.
Stop trying to finish your notes
There is a dangerous idea in professional exam revision that your notes should somehow become complete.
They never will.
SBR is too broad. There will always be another technical article, another example or another accounting issue you could add.
Trying to finish everything creates a false finishing line.
You tell yourself that once the notes are complete, serious question practice can begin.
Then the exam arrives.
At this stage, your notes should become a reference tool rather than a project.
If you discover a genuine technical gap during question practice, fix it. Add one useful explanation if necessary.
Then move back to writing.
Do not spend three evenings redesigning a set of notes on a topic you broadly understand.
That activity feels controlled because there is no timer and no risk of producing a poor answer.
The exam will not ask to see your notes.
It will ask you to produce advice.
Stop revising topics simply because they feel comfortable
Comfortable revision is particularly dangerous in the final weeks.
Everyone has subjects they like.
Perhaps group accounting makes sense to you. Perhaps ethics feels straightforward. Perhaps you are comfortable with impairment or financial instruments.
Returning to familiar topics creates confidence, but it may not create marks.
Your final revision plan should be driven by evidence from your own scripts.
Which requirements are you avoiding?
Which topics cause you to hesitate?
Where do your answers become generic?
Which areas make you lose time?
Those are the areas that deserve attention.
The purpose is not to become equally brilliant at every topic.
It is to remove the weaknesses most likely to interrupt your performance.
If IFRS 11 still causes you to freeze, do a short classification question.
If current issues answers become vague, practise one applied current-issues requirement.
If financial instruments send you back into long theoretical explanations, write a short scenario-based answer and force yourself to conclude.
Work on the point where the marks are leaking.
Stop reading model answers before you attempt the question
Model answers are useful.
They are also one of the easiest ways to create false confidence.
You read a question, glance at the solution and think:
“Yes, that makes sense.”
Of course it does.
Someone else has already identified the issue, selected the relevant facts and organised the answer.
Recognition is not the same as retrieval.
On exam day, nobody gives you the structure first.
You need to create it.
For the remainder of your revision, attempt the requirement before looking at the answer.
Even if you only give yourself 20 minutes, write something.
Then compare.
Ask which points you missed and why.
Was it because you did not know the technical rule?
Or did you know it but fail to spot the scenario trigger?
That distinction matters.
A knowledge problem requires technical revision.
A recognition problem requires more question practice.
Stop measuring revision by hours
Ten hours of revision does not necessarily produce ten hours of useful preparation.
The final weeks are a good time to stop obsessing over study hours.
Measure output instead.
A useful week might contain:
- two short timed requirements
- one longer mixed question session
- one proper mock or substantial timed set
- a review of recurring mistakes
- targeted technical repair based on those mistakes
That is the only bullet list needed here.
A candidate completing those tasks may improve more than someone spending twice as many hours watching lectures.
The closer you get to the exam, the more your revision should resemble the activity you will actually perform.
You are preparing to read, think, decide and write.
Practise doing that.
Stop treating every technical weakness as an emergency
There will almost certainly be something you still do not understand perfectly.
That is normal.
SBR does not require perfect knowledge of every possible issue.
The danger is allowing one weak area to consume the final fortnight.
A candidate discovers that they struggle with one difficult technical topic and spends the next three days trying to master every detail.
Meanwhile, time control, professional skills and broader question practice disappear from the plan.
Ask a more useful question.
If this topic appears, can I still earn some marks?
You may not remember every rule, but can you identify the issue?
Can you state the principle?
Can you apply one relevant fact?
Can you reach a reasonable conclusion?
That is often enough to keep the exam moving.
A partial answer is better than ten minutes of panic followed by a blank screen.
Stop writing introductions that earn nothing
This is one of the easiest habits to remove before the exam.
Many candidates begin an answer by easing themselves into the subject.
They define the standard.
They explain the background.
They repeat information from the requirement.
They write several lines before reaching anything that could earn a mark.
You do not have time for that.
Start with the issue.
Instead of:
“IAS 36 deals with the impairment of assets and sets out the procedures that an entity applies to ensure assets are not carried above their recoverable amount.”
Try:
“The forecast used in the impairment review appears optimistic because management assumes revenue growth despite the decline in recent sales.”
The second sentence is already doing useful work.
It identifies the issue and applies the scenario.
That is the standard you want.
Stop trying to make the first question perfect
One of the most damaging SBR habits is over-investing in the beginning of the exam.
The first question feels important.
You are fresh.
You recognise some of the issues.
You want to begin well.
So you keep adding another paragraph.
And another.
Ten extra minutes disappear.
Those minutes have not vanished. You have borrowed them from a later requirement.
Eventually you arrive at the final part of the paper with a fraction of the time you intended.
Completion is one of the most practical skills you can train in the final countdown.
When the allocated time ends, finish the point and move.
Your answer may feel incomplete.
Move anyway.
You are not trying to produce one exceptional answer.
You are trying to earn marks across a 100-mark paper.
Stop avoiding full exam conditions
The official pre-September mock and debrief material is already available.
This is the right time to use it properly.
Not with your notes open.
Not while answering messages.
Not across two evenings.
Not with the timer paused while you make a cup of tea.
A mock is useful because it exposes what happens when the pressure stays on.
You may discover that your technical knowledge is fine for the first 90 minutes and then your concentration falls.
You may discover that your planning is too slow.
You may discover that you are spending too much time on Section A and leaving Section B rushed.
You may discover that you are avoiding difficult requirements instead of starting with one safe point.
That information is valuable.
A comfortable mock can reassure you.
An uncomfortable mock can improve you.
Stop sitting mocks without debriefing them
Doing a mock is only half the exercise.
The debrief is where the improvement happens.
Do not simply look at the score.
Look at the script.
Where did time disappear?
Where did you write accurate theory without applying it?
Where did you miss a conclusion?
Where did the requirement ask for advice but your answer only explained?
Where did you ignore a scenario fact that should have changed your judgement?
Choose the two biggest weaknesses.
Then use your next practice sessions to attack those weaknesses.
If you sit another mock without changing anything, you are testing the same candidate again.
The objective is to become a slightly different candidate before the next attempt.
Stop adding technical detail when application is missing
A technically detailed paragraph can still be weak.
This is one of the biggest lessons in SBR.
Suppose the question involves impairment.
You could write a technically accurate explanation of recoverable amount, value in use and fair value less costs of disposal.
If you never mention that sales have fallen, margins have reduced and management’s forecast assumes an immediate recovery, the answer has missed the strongest material in the scenario.
Application is what turns knowledge into marks.
A simple test helps.
Read a paragraph you have written and remove the company name.
Could that paragraph appear in almost any answer about the topic?
If yes, it may be too generic.
Add the fact that changes the conclusion.
Then explain why it matters.
Stop hiding from conclusions
A surprising number of candidates discuss an issue reasonably well and then stop.
They never tell the reader what should happen.
In SBR, that can weaken both technical and professional marks.
A conclusion does not need to be dramatic.
It may be one sentence.
“The arrangement should therefore be classified as a joint venture and accounted for using the equity method.”
“Management should revise the impairment forecast because the current revenue assumptions are not supported by recent performance.”
“The expenditure should be recognised as an expense because the development recognition criteria have not yet been demonstrated.”
Conclusions are efficient.
They tell the marker exactly where your reasoning has landed.
Make them automatic.
For the remainder of your revision, look at every completed requirement and ask:
“Where is my answer?”
If you cannot point to it, write one.
Stop treating professional marks as bonus marks
Professional skills are not decoration.
They are part of the exam.
Current SBR contains four professional skills marks, and the qualities they reward also improve the rest of your answer.
Clear headings help the marker understand your structure.
Scepticism helps you challenge questionable assumptions.
Analysis helps you connect facts with financial consequences.
A useful recommendation makes your answer sound like advice rather than revision notes.
You should not arrive at the final week planning to “look at professional marks”.
They should already be built into your writing.
When you practise, write as though your answer is genuinely going to a finance director, audit committee or board.
Would they know what the problem is?
Would they understand why it matters?
Would they know what you recommend?
If not, improve the paragraph.
Stop memorising complete current-issues essays
Current issues create anxiety because candidates do not know exactly what will appear.
That uncertainty can encourage memorisation.
You read a technical article and try to remember a ready-made answer.
The problem is that the exam may use the topic in a completely different context.
A better approach is to understand the reporting problem.
Why does the issue matter?
Who needs the information?
What is weak about the current reporting?
What judgement does management need to make?
How could the development affect the financial statements?
What should the board do?
If you understand those questions, you can adapt.
That is far safer than hoping the examiner asks for the essay you memorised.
Stop chasing predictions
The closer the exam gets, the more predictions appear.
Candidates discuss which standard has not been examined recently.
Forums speculate about likely topics.
People claim that a certain current issue is “due”.
This is not a strong revision strategy.
Nobody outside the exam process knows your paper.
Prediction can also create dangerous gaps. A candidate decides a topic is unlikely to appear and quietly stops revising it.
Use probability sensibly if you need to prioritise, but do not build the final fortnight around guesses.
Build it around skills that work regardless of the topic.
Read the requirement.
Find the issue.
Apply the facts.
Conclude.
Manage the time.
Those skills will appear in every paper.
Stop comparing your revision with somebody else’s
The final weeks can make comparison difficult to avoid.
Someone has completed six mocks.
Someone says they revise four hours every evening.
Someone has finished every question in the practice kit.
Someone else claims to have memorised every current issue.
None of this tells you whether they will pass.
It certainly does not tell you whether you will pass.
Your useful comparison is with your own scripts from several weeks ago.
Are you finishing more?
Are you applying more facts?
Are you writing less unnecessary theory?
Are your conclusions clearer?
Are you recovering more quickly when a question feels unfamiliar?
That is progress.
What you should still be doing
Stopping low-value revision does not mean doing less for the sake of it.
It means creating space for the things that matter.
In the final two weeks, most candidates should be spending a substantial proportion of their time writing and reviewing answers.
Technical revision still has a role.
Use it surgically.
If a question exposes a weak area, repair the gap.
If you repeatedly forget an important rule, refresh it.
If a current issue remains unclear, read enough to understand the reporting problem.
Then return to questions.
Your revision should move in a loop:
Attempt.
Review.
Repair.
Attempt again.
That is much more effective than trying to consume the whole syllabus one final time.
The final week needs to become calmer not busier
Panic revision has a strange logic.
The closer the exam gets, the more tired candidates make themselves.
They stay up later.
They increase the hours.
They attempt to learn topics they have barely touched for months.
Then they arrive at the exam mentally exhausted.
The final week should move in the opposite direction.
You want familiarity, not overload.
Short timed requirements.
Review of recurring errors.
Brief technical refreshers.
A final check of exam technique.
Normal sleep.
You are trying to protect the performance you have built.
There is little value in learning one extra technical detail at midnight if it reduces your concentration across a 100-mark paper the following day.
Your last few days should focus on control
By the final few days, you should know the handful of behaviours you want to protect.
Perhaps yours are:
Read the requirement before getting drawn into the scenario.
Use headings immediately.
Stop writing theory once you have enough to apply the rule.
Conclude every requirement.
Move when the time ends.
You do not need twenty exam-day rules.
You need a few habits that survive pressure.
Candidates following a structured ACCA SBR course should use the remaining sessions, marking and mock feedback to identify those final habits rather than trying to reopen the entire syllabus.
September is now about execution
The September sitting is close.
That should simplify your revision rather than complicate it.
You do not have to know everything.
You do not need perfect notes.
You do not need to complete every question ever written.
You need enough technical knowledge to recognise the issues and enough exam skill to turn that knowledge into marks.
Stop polishing the revision materials.
Stop avoiding timed work.
Stop spending five minutes earning a mark you probably already earned three minutes ago.
Stop leaving conclusions in your head.
Stop allowing one difficult requirement to damage the rest of the paper.
The final countdown is not about cramming more accounting into your memory.
It is about making sure that what you already know appears clearly, efficiently and professionally on the screen when it matters.
