• Practice
  • About 14 min
  • 5 practice questions

Building an error log from each mock

Keep a one-line-per-question error log for every mock, find the root cause behind each entry, and tally the log by category and topic to see what keeps costing you marks.

If something looks wrong, please tell us.

The one-page analysis sheet from the foundation course gives you counts. An error log goes one level deeper: one line for each question that cost you marks, with the reason and the fix. Kept across several mocks, it shows the mistakes that keep coming back, which are the ones worth fixing first. (A separate mistake notebook for revising content is covered in the Note-Making course; the error log here is about the mock itself.)

What goes into the log

  • Every wrong answer.
  • Every skipped-could-do question.
  • Every correct answer that was a guess.
  • Not every skipped-couldn't-do question one by one: if a whole topic is unstudied, write one line for the topic instead.
Sample error log rows
MockQTopicCategoryWhat went wrongFixRe-test by
412Number seriesConceptDid not see the squares patternPractise 15 series with squares and cubesNext Sat
427PercentagesSillyWrote 15% of 240 as 32Write the multiplication line, do not do it in the headNext mock
441Reading comp.MisreadMissed 'according to the author'Underline the source the question asks aboutNext mock
466RatiosSkipped: could doLooked long; solved at home in 90 sRead the last line before judging lengthNext mock

Find the root cause, not the label

'Careless' or 'did not know' is a label, not a cause, and labels do not suggest a fix. Ask 'why?' once or twice more until you reach something you can change. 'I got it wrong' → 'I made a sign error' → 'I did two steps in my head when I felt rushed'. The last answer gives a fix: write each algebra step on the rough sheet, even when hurrying.

Worked example 1: Pooja tallies her log

Pooja, a B.A. student, logs 14 entries from mock 4: 11 wrong answers and 3 skipped-could-do. At 3 minutes an entry, logging takes about 14 × 3 = 42 minutes. She then tallies the log two ways.

Both columns add to 14
By categoryCountBy topicCount
Concept5Number series4
Silly4Percentages3
Misread2Reading comprehension3
Skipped: could do3Other topics (one each)4

Reading the tally: number series appears 4 times, and 3 of those entries are concept errors, so that is a study task. Percentages appears 3 times, all silly errors, so the fix there is the written multiplication line, not more theory. One mock is a small sample, so she marks both as 'watch' and checks whether they return in mock 5.

Worked example 2: Gaurav digs into silly errors

Gaurav has 5 silly errors in a mock. His first note says 'careless' five times. He asks why for each: 3 were sign errors in algebra done mentally, 1 was marking option C on the answer sheet when he had worked out B, and 1 was misplacing a decimal. Root causes: skipping written steps (3) and transfer error to the answer sheet (1); the decimal slip (1) is a one-off. Fixes: write one line per algebra step; after every 10 questions, check that the marked options match his rough work. Two fixes cover 4 of his 5 silly errors.

One line per lost mark: topic, category, real cause, fix. Then count. What repeats is what you fix first.

Key takeaways

  • Log every wrong answer, every skipped-could-do question and every lucky guess.
  • Ask 'why' until the cause suggests a concrete fix.
  • Tally the log by category and by topic after each mock.
  • Treat a pattern from one mock as something to watch; act firmly when it repeats.

Check your understanding

  1. 1. Which of these does NOT need its own line in the error log?

    1. Each question from a topic you have not studied at all
    2. A correct answer that was marked as a guess during the mock
    3. A wrong answer caused by misreading
    4. A question skipped that you could solve at home
    Show answer

    Answer: A. An unstudied topic is recorded once as a topic to study. Guesses, misreads and skipped-could-do questions each get a line because each has its own fix.

  2. 2. Which entry is a root cause rather than a label?

    1. I was careless
    2. I did not know it
    3. I did two algebra steps in my head while rushing
    4. It was a silly mistake
    Show answer

    Answer: C. A root cause points directly to a fix (write the steps down). The other three are labels that do not say what to change.

  3. 3. Pooja logs 14 entries at about 3 minutes each. Roughly how long does logging take?

    1. 17 minutes
    2. 28 minutes
    3. 56 minutes
    4. 42 minutes
    Show answer

    Answer: D. 14 × 3 = 42 minutes.

  4. 4. In a tally, 'Percentages' appears 3 times, all as silly errors. What is the most suitable fix?

    1. Re-reading the whole percentages chapter from the textbook again
    2. Skipping all percentage questions
    3. Taking an extra mock
    4. A checking habit such as writing out the multiplication line
    Show answer

    Answer: D. Silly errors mean the method is known; the fix is a careful-working habit, not more theory.

  5. 5. A pattern appears once in a single mock. What does the lesson advise?

    1. Ignore it completely
    2. Mark it to watch and act firmly if it repeats in the next mock
    3. Rebuild the whole study plan around it straight away from this week
    4. Stop taking mocks until it is fixed
    Show answer

    Answer: B. One mock is a small sample. Watching for repetition avoids over-reacting to a one-off while still catching real patterns.

Sign in to keep track of the lessons you finish.

Next lesson → Finding where the time went in a mock

Privacy · Terms · Refunds · Delivery