The latest SBL examiner's report is out. I've read all of it, so you don't have to — and if you sat the DKK paper and it didn't go the way you wanted, this page is where it actually went wrong. Not vague advice: the specific mistakes the report keeps naming, worst first, with the fix for each, plus a free checklist you can run over your last mock tonight. None of this is about working harder. The report is clear that time wasn't the problem. It's about a handful of habits — and habits you can change before the next sitting.
The report found no real sign that people ran short of time. That's the uncomfortable, useful part: the marks you lost, you lost on how you used the time, not how much of it you had. Everything below is one of those habits. Not one is a knowledge gap. All of them are fixable.
In the weeks before an exam, the pre-seen gets picked apart online, and every forum has its theory about what matters. So you walk in primed, and when you spot a chance to use what everyone was talking about, you take it — it feels like being ready. The report is blunt that it isn't: candidates dropped pre-learned issues into answers where they didn't fit, and got nothing back for them, because the tasks are built from what's in front of you on the day. The fix isn't more knowledge. It's the discipline to leave your best-prepared point unused when the question didn't ask for it.
The single most-failed part of the paper was a topic that sits near the very end of the syllabus. By the time most people reach it in revision they're tired, the exam's close, and they quietly decide it probably won't come up — so they never really learn it. The exam doesn't know what order you revised in, and it tests the last page as hard as the first. If there's a corner of the syllabus you've been hoping to avoid, that's the one to open tonight.
The report is unusually blunt here, and it's basic, which is exactly why it's dangerous. Nobody revises profit versus margin — it feels beneath you at this level, so you assume it's automatic. Then under pressure you read a falling margin as rising costs, when costs had actually fallen, and you write a whole confident paragraph on top of that wrong reading. It never feels like an error, because the writing flows — but the analysis was finished before it started. Margin is profit divided by revenue; a falling margin does not, on its own, tell you costs rose. Check the thing you're most sure you know before you walk in.
The report's biggest recurring complaint: people answered a different question from the one on the page. It doesn't feel like going off-track, because you're writing about the right topic — you're just answering a slightly different question about it than the one that was set. The verb is small, you read it in a second, and that second is where the paper is won or lost.
<aside> 🔴
Weak — answers a different question: "Is giving the managers more autonomy and a bonus a good idea?"
</aside>
<aside> ✅
Strong — answers the object of the verb: "Which style brings the change in — participative, so managers help shape it and own it, or directive, with clear targets set from the top?"
</aside>
<aside> 💡
Remember: the marks live in the object of the verb — here, the styles, not whether the change is wise. Name the object to yourself before you write a word.
</aside>