Past Paper & Mock Test Training: A 10-Step Method

How Many Past Papers You've Solved Matters Less Than How You Fixed Your Mistakes

Solving the same past papers repeatedly rarely raises your score on its own — this walks through a training order built around actually processing wrong answers.

The number of past papers you've worked through often gets treated as a measure of effort, but what actually moves your score is how you deal with wrong answers, not how many times you've practiced. If you get the same question wrong for the same reason three times in a row, repetition by itself isn't doing much. This list runs from sourcing official past papers all the way to timed practice, focused on actions that leave a visible result behind.

Each step is judged not by whether you 'did it' but by what you confirmed and what you'll change next. Skip whatever doesn't fit your exam, and if you already have a backlog of wrong answers logged, feel free to start directly at item 4.

Source official past papers first

Collect the questions, answers, and correction notices published by the exam administrator, organized by year and session. Treating unofficial reconstructed questions as if they were the real thing can leave you practicing on subtly different question types, so verifying the source is worth the habit.

Sort past papers by exam unit

Group questions by year, subject, question type, or difficulty tier — whatever fits your exam. Mixing questions from before and after a system change can mean you're studying question patterns that no longer apply.

Solve the first session while logging your process

Loosen the time limit and write down your reasoning and where you got stuck next to each question. The key here is not tricking yourself into thinking you got something right after already reading the explanation.

Sort wrong answers into four causes

Split each mistake into a concept gap, a memory failure, a misreading of the question, or a time or simple error. Lumping every wrong answer into 'just a mistake' makes it easy to miss the real cause that keeps recurring.

Attach a next action to each wrong answer

Depending on the cause, decide whether to re-study a concept, build a recall card, flag a condition, or adjust your solving order — and note the date. Copying the answer explanation alone doesn't count as fixing it.

Cover the answer and solve it again

After some time has passed since reviewing the explanation, solve the same question again from scratch. Getting it right because you remember the answer choice and getting it right by rebuilding the reasoning yourself are two different outcomes worth telling apart.

Measure time spent per question

Pick a representative session, log the start and end time for each question, and identify which types run long on average. It's also worth checking whether pushing for speed is quietly costing you accuracy.

Test a fixed solving order across sessions

Decide which sections to solve first, when to leave room for review, and when to mark answers, then test that order across multiple sessions. It's safer to judge after a few repeats than to lock in an order based on one result.

Run a mock session under real conditions

Apply the exact time limit and allowed tools confirmed in the latest official notice, and complete one session without stopping partway through. Logging where your focus broke down, not just your score, gives you something useful for the next round.

Compress everything into a final weak-point list

Pull out only the question types you keep missing and the sections that take too long, and turn them into a short list to review right before the exam. The point of this step is to keep that list short, not to keep adding new material to it.

Frequently asked questions

How many past papers is enough to work through?

There's no set number. Whether the same type of mistake keeps repeating matters more than the count of papers completed, so it's often more efficient to check whether your existing errors are shrinking before adding more new papers.

Does an error log have to be handwritten?

The format doesn't matter. Whether it's on paper or in a spreadsheet, what matters is that the cause of each mistake and your next action are recorded together and easy to find later.

How many weeks before the exam should full mock tests start?

This depends heavily on the exam and your own preparation, so there's no general rule to give. That said, you'll want enough time to test different pacing and question orders more than once, so starting somewhat earlier rather than at the very end leaves more room to adjust.

NEWSLETTER

Get new lists before anyone else

Once a week — only the new lists worth your time.

No spam · unsubscribe in one click

This page contains affiliate links. We may earn a commission from qualifying purchases.

Source official past papers first👍 Upvote

Sort past papers by exam unit👍 Upvote

Solve the first session while logging your process👍 Upvote

Sort wrong answers into four causes👍 Upvote

Attach a next action to each wrong answer👍 Upvote

Cover the answer and solve it again👍 Upvote

Measure time spent per question👍 Upvote

Test a fixed solving order across sessions👍 Upvote

Run a mock session under real conditions👍 Upvote

Compress everything into a final weak-point list👍 Upvote