How to Build an Error Log That You Will Actually Use
06 Oct 2026 · TestMint Team
The short answer: an error log is a short list of mistakes with the cause, the fix and a retest date. Keep each entry to three lines, tag it by topic and cause and review it weekly. A small log you use beats a detailed one you abandon.
What an error log is for
Most candidates make the same mistakes repeatedly because they do not keep track of them. An error log turns individual mistakes into patterns you can fix. After a month, it shows which topics and which causes cost you most, and it becomes the best source for short notes and last-week revision.
A minimal template
| Field | What to write |
|---|---|
| Date and source | Mock name, section, question number |
| Topic and cause | Topic; one cause label (concept, fact, misread, calculation, time, guess) |
| What went wrong | One line: what you did |
| The fix | One line: the rule, formula or habit |
| Retest | Date and a similar question or its source |
Three lines is enough. If an entry takes more than two minutes to write, you are writing too much.
Example entries
- Mock 7, QA, Q14. Time and work; concept. Added days instead of rates. Fix: add rates; total work = LCM. Retest: 3 problems on Thursday.
- Mock 7, Reasoning, Q22. Direction sense; misread. Took "north-west" as "north". Fix: draw a compass; read the final line twice. Retest: 5 direction questions on Friday.
- Mock 7, English, Q31. Subject-verb agreement; fact. Missed that "each of" takes a singular verb. Fix: rule card; five sentences on Wednesday.
- Mock 7, GA, Q45. Current affairs; fact. Did not know the recent appointment. Fix: add to the spaced schedule.
Use tags to find patterns
After 20 to 30 entries, count by topic and by cause. An illustration:
| Cause | Entries | Share |
|---|---|---|
| Concept | 12 | 40% |
| Fact or formula | 6 | 20% |
| Misreading | 6 | 20% |
| Calculation | 3 | 10% |
| Time and guess | 3 | 10% |
The log shows that concept gaps account for 40% of errors; the next study block should be topic repair, not speed. Without the log, the candidate might have spent weeks on speed drills.
A weekly routine (30 minutes)
- Read the week's new entries and the ones due for retest.
- Retest: solve a similar question for each due entry without notes.
- Mark each as fixed or not. Not fixed entries stay and get a new date.
- Count by cause and topic and write the top two targets for next week.
Paper or digital?
A notebook with one line per entry works, as does a spreadsheet or a notes app. A spreadsheet makes counting by tag easy. Choose the one that you will open without effort.
Keeping it small
- Log only errors worth fixing: not every slip.
- Merge duplicates: if you made the same error three times, make one entry with a tally.
- Archive fixed entries after two clean retests.
- Cap the active list at about 60 entries; if it grows beyond that, prioritise.
Turn the log into revision material
In the last two weeks, the log is your revision list: the entries you keep getting wrong are your real weak spots. Use it with short notes and the last-week plan. For the review method that feeds it, see how to review incorrect questions.
Common mistakes
- Writing long entries.
- Never opening the log.
- Logging without a fix or retest.
- Using too many cause labels.
- Starting a new log for each mock.
Start the log with your next practice test.
Frequently asked questions
Prepare with real mock tests
Attempt free and paid tests from coaching institutes, with instant results and rankings.
Try free mock tests Browse marketplace