Revision notes

Mock Test Analysis: Foundation

The key points, rules to remember, tables and diagrams from all 9 lessons, on one page for quick revision. To keep a copy, use your browser's Print and choose "Save as PDF".

Lesson 1

What a mock test is for: a diagnosis, not a verdict

Two ways of reading the same score
Verdict thinkingDiagnosis thinking
My score is bad, I am not good enoughMy score is low; where exactly did the marks go?
I scored well, so I am readyI scored well; which marks were lucky guesses?
I need to take more mocksI need to learn more from each mock
My friend scored higher than meWhat did I do differently from my last mock?

A mock test is a diagnosis, not a verdict. The score tells you where you are; the analysis tells you what to do next.

  • The value of a mock is in what you find inside it, not in the score alone.
  • Read every result, good or bad, as a diagnosis: where did the marks come from and where did they go?
  • A mock cannot predict your exact exam result; it can show what to fix.
  • One mock analysed well is worth more than several mocks only scored.
Read the full lesson

Lesson 2

Taking a mock in exam-like conditions

Mock-day checklist
StageChecklist itemWhy it matters
BeforeUninterrupted slot, phone awayBreaks change your time data
BeforeGuess symbols decidedLets you find lucky marks later
DuringTime checkpoints writtenShows where the minutes went
DuringNo pausing or looking upKeeps the score honest
AfterTwo-minute feelings noteExplains panics and rushes

Sit the mock as if it were the exam: one sitting, no pauses, guesses marked and the clock written down.

  • A mock taken in pieces or with breaks gives misleading numbers.
  • Mark guesses during the paper; you cannot tell them apart from knowledge afterwards.
  • Time checkpoints are the raw material for finding where your minutes went.
  • Write a short note on how the paper felt before you see the answer key.
Read the full lesson

Lesson 3

The basic numbers: attempts, accuracy, net score and time per section

Basic mock numbers
NumberHow to find itWhat it tells you
AttemptsQuestions you answeredHow much of the paper you took on
CorrectAnswers that matched the keyWhat you earned
WrongAttempts minus correctWhat cost you marks
SkippedTotal questions minus attemptsWhat you left or did not reach
AccuracyCorrect ÷ attempts × 100How reliable your answers were
Net scoreMarks for correct minus marks deducted for wrongThe result after any negative marking
Arjun's time per section (total 22 + 14 + 12 + 12 = 60 minutes)
SectionMinutes usedTime per question
A2222 ÷ 25 = 0.88 min, about 53 seconds
B1414 ÷ 25 = 0.56 min, about 34 seconds
C1212 ÷ 25 = 0.48 min, about 29 seconds
D1212 ÷ 25 = 0.48 min, about 29 seconds

Accuracy = correct ÷ attempts. Net score = marks for correct − deductions for wrong. Always state the marking scheme you used.

  • Wrong = attempts − correct; skipped = total − attempts.
  • Accuracy is measured on attempts, not on the whole paper.
  • Net score combines attempts and accuracy, so compare students and mocks on net score, then look at both parts.
  • Time per section, from your checkpoints, shows where the clock went.
Read the full lesson

Lesson 4

Sorting every question into six categories

Six categories for every question
CategoryMeaningTypical fix
CorrectRight answer (note if it was a marked guess)None; but treat guessed ones as unknown
Wrong: conceptYou did not know the fact, rule or methodStudy the topic
Wrong: sillyYou knew the method but slipped in calculation or markingSlow down at checking points
Wrong: misreadYou answered a different question from the one askedRead the question stem fully
Skipped: could doYou left it but can solve it when you see it calmlyBetter question selection and time use
Skipped: couldn't doYou could not solve it even with timeStudy the topic, or accept leaving it
Check: 60 + 8 + 7 + 5 + 12 + 8 = 100
CategoryCount
Correct60 (6 guessed)
Wrong: concept8
Wrong: silly7
Wrong: misread5
Skipped: could do12
Skipped: couldn't do8

Every question gets a category. Silly, misread and skipped-could-do are marks you already own; collect them first.

  • Sort all questions, including correct ones, into six categories.
  • Decide in order: misread? then concept? otherwise silly.
  • Silly, misread and skipped-could-do questions are recoverable without new study.
  • Correct answers that were guesses point to topics you still need to learn.
Read the full lesson

Lesson 5

A one-page analysis sheet and three actions for next week

One-page mock analysis sheet
Section of the sheetWhat to write
Mock detailsMock number, date, length, marking scheme used
Basic numbersAttempts, correct, wrong, skipped, accuracy, net score
TimeMinutes per section from your checkpoints; any minutes lost to disturbance
CategoriesCounts of the six categories, with guessed-correct noted
Top topics lostThe two or three topics where most concept errors and couldn't-do skips fell
Feelings noteOne line from your after-mock note: panic, rushing, tiredness
Three actionsWhat you will do before the next mock, with time and a check

One page, three actions: one for knowledge, one for care, one for time. Each with a time slot and a check in the next mock.

  • Put every mock's numbers, categories and time on one page.
  • Pick three specific, timed, checkable actions, not a long wish list.
  • Cover the three sources of lost marks: knowledge, care and time.
  • Make the actions fit the hours you actually have.
Read the full lesson

Lesson 6

The error log: writing down what went wrong and what to do about it

An error log with six columns
ColumnWhat you writeExample
QuestionNumber, topic and a few wordsQ14, percentages
My answer and the right oneBoth, brieflyI chose 24; right answer 30
Why it went wrongNot knew, misread or careless, and one line of detailMisread: 'of the total', not 'of the part'
Correct methodThe steps in your own wordsFind the total first, then take the percentage
FixOne action for next timeUnderline what the percentage is OF
Redo onA date about a week laterRedo next Sunday

A mistake is useful only when you write down why it happened and what you will do differently, and test it again later.

  • An error log has six columns: question, answer, reason, method, fix and redo date.
  • Each entry needs its own reason and its own fix.
  • Fill in the log within a day; redo the questions after about a week.
  • Keep entries short.
Read the full lesson

Lesson 7

Reviewing your correct answers: lucky guesses and slow solves

Sorting correct answers
KindWhat it looks likeWhat to do
SecureYou were sure, and the time was normalKeep going; no action needed
LuckyYou guessed or were unsure, and happened to be rightTreat as wrong for review: learn the topic
SlowRight, but it took over twice the normal timeFind a faster method; practise

A right answer you cannot explain is borrowed, not owned. Tag the unsure and the slow, and review them like mistakes.

  • Correct answers can be secure, lucky or slow.
  • Tag unsure answers during the mock and slow ones afterwards.
  • Secure rate = secure right answers / attempted.
  • Turn lucky answers into knowledge, and slow ones into faster methods.
Read the full lesson

Lesson 8

Tracking progress across mocks with a simple table

Aisha's table (invented scheme: +1, -0.25)
MockAttemptsCorrectAccuracyNet score
Mock 1483470.8%30.50
Mock 2524076.9%37.00
Mock 3504182.0%38.75
Mock 4554378.2%40.00
Combinations of columns
What you seeA possible reading
Net up, accuracy up, attempts steadyReal improvement in knowledge or care
Net up, attempts up, accuracy down a littleTrading some accuracy for more attempts; check that the trade pays
Net flat, accuracy up, attempts downPlaying safer; you may be leaving marks unattempted
Net down, accuracy downLook at the error log for the reason

Same columns, every mock. Read attempts, accuracy and net score together, and write one sentence and one action under the table.

  • Record the same columns for every mock.
  • Accuracy = correct / attempts; net = marks for right minus deductions.
  • Read the columns together, not one at a time.
  • Write one sentence and one action under the table.
Read the full lesson

Lesson 9

Scheduling mocks, protecting review time and handling a disappointing result

A mock costs a sitting and a review. After a low score, rest, check the swing, sort the questions and choose three actions.

  • Count a mock as sitting plus review when planning your week.
  • One mock a week is often enough if study hours are limited.
  • Rest before reviewing a disappointing result, then review within a day.
  • Turn the result into three actions.
Read the full lesson

Privacy · Terms · Refunds · Delivery