A result tells you what happened. A good debrief helps explain why. Spend twenty minutes recording what the exam exposed while the experience is still fresh.
Written by Michael Siaw Larbi · Wednesday, 11 November 2026
On this page
A week after an exam, memory starts editing the story.
The question that consumed twenty minutes becomes “a difficult question”. The moment you forgot a rule disappears. You remember feeling rushed but not where the time actually went.
Then results arrive weeks later and you are trying to diagnose the paper from a much blurrier memory.
Do a short debrief while the experience is fresh.
Twenty minutes is enough.
Leave mark predictions out of the debrief. You rarely have enough information to do that accurately.
The goal is to capture useful evidence about how you performed.
Minute 0 to 5: reconstruct the paper
Write the main questions or topics you remember.
Do not worry about exact wording.
Beside each, note:
- attempted fully;
- attempted partly;
- rushed;
- left blank;
- felt strong;
- felt uncertain.
That gives you a map.
The debrief grid
- Completion: Full / Partial / Blank
- Confidence: High / Medium / Low
- Time: Comfortable / Tight / Overrun
- Main issue: Knowledge / Recall / Technique / Calculation / Application / Careless error / Other
The tool should never estimate a score.
Minute 5 to 10: identify the first cause
For every weak area, ask what happened first.
Example:
“I ran out of time on Question 4.”
What happened before that?
Perhaps Question 2 ran over by 18 minutes.
Why?
Perhaps you kept rewriting the same discussion because you were unsure whether your first point was enough.
Now the lesson is more specific than “improve time management”.
Another example:
“I forgot the formula.”
Was the formula never learned properly? Was it learned but not retrieved for two weeks? Did you confuse it with a similar formula? Did panic block something you normally knew?
Different causes need different fixes.
Minute 10 to 15: separate four kinds of problem
Use four buckets.
Knowledge
You genuinely did not know the rule, concept or method.
Future fix: learn or relearn it.
Retrieval
You had learned it before but could not produce it when needed.
Future fix: spaced retrieval, mixed practice, faster recall.
Technique
You knew enough but used the exam badly: misread requirement, poor structure, weak application, bad time allocation.
Future fix: targeted technique practice.
Execution
Careless copying, sign error, wrong period, missing label, calculator slip, poor handwriting, skipped subpart.
Future fix: personal check routines and error drills.
A fifth category can be circumstance: illness, severe travel disruption or another genuine external problem. Record it without forcing it into an academic explanation.
Minute 15 to 20: write three lessons only
Do not leave with a page of twenty resolutions.
Choose three.
For example:
- I need to stop Question 1 when its time is up.
- I need weekly retrieval of older tax rules, not only current class topics.
- I need to practise writing conclusions that answer the advice requirement directly.
Those three can shape the next sitting.
A full example
Esi finishes a professional paper and writes this:
Question 1
Full. Felt strong. Ran five minutes over.
Question 2
Full. One calculation uncertain.
Question 3
Partial. Misread part (b) at first and restarted.
Question 4
Rushed. Only 20 minutes left for a 30-minute budget.
Her first reaction is: “My problem was Question 4.”
The debrief shows something else.
Question 4 was the victim.
The earlier time overrun and restart created the shortage.
Her lessons become:
- practise requirement decoding before writing;
- use a visible time budget on each question;
- when a point is uncertain, move instead of rewriting the whole section.
That is useful information even if she later passes comfortably.
Debrief a good paper too
Students usually analyse failure and forget success.
If a paper felt excellent, ask why.
Maybe:
- the topics had been retrieved repeatedly;
- your question practice was varied;
- you recognised the scenario quickly;
- your timing was disciplined;
- you used headings naturally;
- you slept well and arrived settled.
Keep successful behaviours.
You want to know what to repeat just as much as what to repair.
Do not turn the debrief into self-marking fiction
Unless you have an official solution and a reliable understanding of the marking approach, be cautious about adding up imagined marks.
Students often overestimate and underestimate different parts for reasons that have little to do with the real marking scheme.
Write what you observed.
You can later compare with official materials if they become available.
When the result arrives
Bring the debrief back.
If you passed, identify which habits helped and what still needs improvement for later levels.
If you failed, compare the outcome with your own notes.
Did the paper feel weak where the debrief said it was weak? Were there signs of a broader technique problem? Do you need feedback from a lecturer on a likely knowledge gap?
The debrief becomes evidence for your comeback plan.
The existing Blueprint guide on passing a resit can then help you diagnose the next move.
Keep a sitting archive
Create one folder for each exam diet.
Save:
- the debrief;
- your final mistake book;
- your last revision plan;
- key practice scores or observations;
- official result when available.
Over several sittings, patterns become visible.
Perhaps timing appears in every diet. Perhaps you repeatedly neglect one paper until the final weeks. Perhaps calculations are fine while application is consistently weak.
One exam can feel emotional. Several exams can reveal a system.
What if you cannot remember the questions exactly?
That is fine.
Write the experience you do remember:
- where you slowed down;
- which topic surprised you;
- where you felt confident;
- where you guessed;
- where the paper format caused difficulty;
- which technique habit helped.
The debrief is for learning, not historical reconstruction.
Four short questions
Should I do the debrief immediately after the exam?
If you still have papers ahead, protect those first. A few quick notes are enough during the diet. Complete the fuller review after your final paper while the details are still relatively fresh.
Should I compare answers with friends as part of the review?
Your own performance process comes first. Later discussion can help identify technical issues, but avoid treating group consensus as an official marking scheme.
What if I passed? Do I still need a debrief?
Yes. A pass can hide habits that will become expensive at a harder level. It also reveals what worked and deserves to be repeated.
What if the result later contradicts how I felt?
That is useful information. Your confidence calibration may need work. Compare the result, official feedback where available and the original debrief before deciding what to change.
Take twenty minutes while you still remember
Open a fresh page.
Map the questions.
Find the first cause behind the weak moments.
Choose three lessons.
Then file the paper away and get on with the next stage.
Series note: The Excellence Blueprint is MSL Business School's weekly guide to studying, remembering and performing better in professional examinations.
A second debrief example: the paper felt good
Debriefs are useful after strong performances too.
Suppose Kofi finishes a paper feeling confident.
His quick review shows:
- timing was controlled;
- one calculation format worked particularly well;
- he used scenario facts more consistently than in practice;
- he almost missed a small second verb in one requirement;
- his final 20 minutes felt rushed even though he completed the paper.
He records the final point.
Why?
Because a pass or prize can still contain a process weakness that becomes expensive in a harder sitting.
A useful debrief does not search only for failure.
It identifies what to repeat and what to refine.
Separate the event from the cause
Write what happened first.
Then ask why.
Example:
Event: I spent 35 minutes on a requirement planned for 25.
Possible cause: I could not remember the calculation setup.
Deeper cause: I had practised reading worked answers more often than rebuilding the method from a blank page.
Repair: three setup drills next cycle before full calculations.
Another:
Event: My discussion became generic.
Possible cause: I forgot to use scenario facts.
Deeper cause: I planned the topic before rereading the requirement.
Repair: underline two usable scenario facts during the answer plan.
The repair should attach to the cause.
Keep a “Repeat This” column
Your debrief form should have four columns:
| What happened | Likely cause | Repair | Repeat this |
|---|---|---|---|
| calculation setup slow | weak blank-page production | setup drills | workings were clearly labelled |
| one generic paragraph | missed scenario cue | fact-first planning | conclusion answered requirement |
| time tight at end | early question overrun | stricter checkpoints | attempted every major section |
Students often build systems entirely from mistakes.
Keep the good behaviours too.
Reopen the debrief when results arrive
Your immediate debrief captures memory of the experience.
The eventual result gives another piece of evidence.
When results arrive, compare them.
If you expected a paper to be weak and the result confirms it, your original diagnosis may still need refinement.
If you expected a strong result and performed below expectation, look at the gaps between feeling and evidence.
If formal feedback, examiner reports or marked scripts are available through the relevant body, use them where appropriate.
Do not rewrite history simply because the result surprised you.
Keep the original debrief date and add a second note.
Turn one debrief into the next study cycle
A debrief should eventually change the timetable.
Suppose the three biggest findings are:
- slow calculation setup;
- weak application in written answers;
- good memory of direct technical rules.
Your next cycle should contain more setup drills and scenario-based writing, while technical-rule recall moves into shorter maintenance sessions.
That is how an examination becomes data for the next one.
The 20-minute debrief sheet
Keep the form short enough that you will actually complete it.
Minutes 0 to 5: what happened
Write facts only.
- which parts ran over time;
- which topics felt inaccessible;
- which questions felt strong;
- whether every requirement was attempted;
- any practical issue that affected concentration.
Minutes 5 to 12: why
Choose the likely cause for each important event:
Knowledge
The rule or method was missing.
Technique
The knowledge existed, but the requirement, application or answer structure was mishandled.
Timing
The paper was not allocated or managed well.
Execution
Careless transfer, arithmetic, presentation or concentration errors appeared.
Minutes 12 to 18: convert to action
Write one repair for the two biggest issues.
Minutes 18 to 20: close the file
Save it with the paper and date. Move on.
The debrief is finished when it has produced usable evidence. It should not become a second sitting of the examination in your head.
Leave these things out of the debrief
A useful review is short enough to finish.
Leave out:
- guesses about the final mark;
- a reconstruction of every answer from memory;
- long arguments about what “should” have been examined;
- self-criticism with no repair attached;
- technical disputes that can wait until the sitting is over.
Capture what will help the next performance. Then close it.
The Excellence Blueprint by MSL Business School helps professional students study, practise and perform with greater purpose.
