Copy the table below. After each mock, add a row for every question where you lost marks, tag the cause and write the fix. Count the causes each week.
The template
| Mock | Section | Topic or question | Cause | Fix | Fixed? |
|---|---|---|---|---|---|
Cause key
| Cause | Meaning |
|---|---|
| Concept gap | You did not know how to begin |
| Careless slip | You knew how, then made an error |
| Time sink | You solved it, but took too long |
| Bad guess | You guessed and lost marks to negative marking |
Weekly summary row
| Week | Concept gap | Careless slip | Time sink | Bad guess | First target |
|---|---|---|---|---|---|
| 1 | |||||
| 2 |
Example
| Mock | Section | Topic | Cause | Fix | Fixed? |
|---|---|---|---|---|---|
| 3 | QA | Percentages | Concept gap | Redo the chapter | No |
| 3 | DILR | Set 2 | Time sink | Cap at a fixed time | No |
| 4 | VARC | RC passage 3 | Bad guess | Practise elimination | No |
For the method behind it, read how to analyse a CAT mock test.
Where this doesn’t apply
The four-cause key is our method. It is not an industry standard. If a different tagging works for you, use it. We have not measured the score effect of keeping a log.
This template is our own. No third-party figure is used.