Error log: turn mistakes into marks
The difference between a 60% score and a 75% score is usually not knowledge — it is repeat errors. Candidates who track their mistakes improve faster because they focus practice on the specific error types that cost them the most marks. Use this with wrong-answer review and practice strategy.
- An error log is useful only if it records the cause, not just the topic.
- Most candidates have one dominant error type after three sessions.
- Slow correct answers belong in the log too because they steal time later.
- The fix should be a behaviour: underline, estimate, skip, or re-check.
Reviewing wrong answers immediately is the fastest way to stop repeat mistakes. Open analytics
What to focus on first
| Focus area | Why it matters | Best drill |
|---|---|---|
| Cause | Topic labels are too broad to change behaviour. | Write misread, method, arithmetic, timing or format. |
| Frequency | One-off errors matter less than repeated patterns. | Count error types every three sessions. |
| Fix | A vague note does not change the next attempt. | Write one concrete next action. |
| Slow correct | These questions look fine in score reports but damage pacing. | Log any correct answer that took too long. |
Common traps
- Writing only the right solution. You need why your answer went wrong.
- Logging too much. One clear line per miss beats a long diary.
- Ignoring timing errors. A correct method can still fail if it is too slow.
How to practise from here
After each timed set, spend ten minutes tagging every miss and every slow correct answer. Pick the most common tag and make the next practice session only about that tag.
The four mistake categories
- Concept gap: You did not know the method. Fix: learn the method and do 5 similar questions.
- Careless error: You knew the method but made a calculation slip. Fix: build a checking habit.
- Misread: You used the wrong number from the table/passage. Fix: underline the specific data before calculating.
- Timing: You ran out of time or rushed. Fix: practice pacing and learn when to skip.
How to log an error
After every practice session, open your log and write one line per wrong answer:
| Q# | Type | Category | What went wrong | Fix |
|---|---|---|---|---|
| 7 | Numerical | Misread | Read Q2 row instead of Q3 | Underline row before calculating |
| 12 | Numerical | Careless | Divided by new value instead of base | Always label base value first |
| 18 | Verbal | Concept | Confused inference with stated fact | Re-read Cannot Say rules |
Misreading is your dominant error type. You do not need more concept learning — you need to build the habit of underlining the specific data point before calculating. Spend your next session practising table-reading speed, not new topics.
Why this works
Without a log, you repeat the same errors because they feel like “bad luck”. With a log, patterns become visible within 2–3 sessions. Most candidates discover that 60–70% of their errors fall into just one or two categories.
How to turn the log into the next drill
The log should end with an action. If the largest category is misread data, drill data interpretation. If it is unsupported inference, drill Cannot Say. If it is pacing, use time management.
Keep the drill narrow enough that you can tell whether it worked. “Do more numerical” is too broad. “Do 12 chart questions and underline the denominator before calculating” is useful. After the drill, compare the same error category against the previous session. If it drops, keep the habit. If it stays flat, the fix is probably too vague and needs to be rewritten as a visible action.
Source notes
forge checks review advice against official provider preparation pages from SHL and Aon. The principle is stable: reviewed practice beats raw volume.
Review your errors on forge
Every wrong answer on forge shows the correct solution and tags the error to a sub-skill — so your error log builds itself.
View your analyticsFrequently asked questions
What should I put in an aptitude test error log?+
Record the question type, mistake category, what went wrong and the specific fix you will use next time.
Should I log correct answers?+
Log slow correct answers. They reveal pacing issues that can become wrong answers under harder timing.
How often should I review the log?+
Review it every three sessions. Count mistakes by category and choose the next targeted drill from the largest repeated pattern.
Stop reading. Start practising.
Try a few real questions — free.
You know the format now. Reading about the test won't move your score — timed reps will. Do a free diagnostic, earn credits just for signing up, and see exactly where you stand.