How to Revise for Mock Exams Without Inflating Your Score

Revise for mock exams lightly and honestly. Keep your normal spaced review running, go back over what you have already covered, and resist the urge to binge-revise a topic because you suspect it will come up. Then sit the paper exactly as if it were real. The revision that matters happens after the mock, not before it.

That is close to the opposite of the advice that works for every other exam, and the reason is a difference in what the exam is for. A mock is a full-length paper your school administers under exam conditions, usually weeks or months before the real GCSE or A-Level series, and nothing you score on it will ever appear on a certificate. It exists to produce information. Revision aimed squarely at the mock does not raise the grade you eventually get. It just makes the information worse.

What is a mock exam actually for?

A mock answers one question: what can you do right now, unaided, under pressure, across everything you have been taught so far. That is a genuinely hard thing to find out about yourself, and almost nothing else in a school year is set up to measure it. Homework is done with the book open. A class test covers one unit. A past paper attempted at the kitchen table gets interrupted, and the mark scheme is one tab away the whole time.

So the mock produces three things at once, and only the first is the one students look at. There is the score, which is the crudest of the three. There is the breakdown of where the marks were lost, which is worth far more, because it points at specific topics rather than at a number. And there is a set of readings you cannot obtain any other way: how your timing held up over a full paper, whether your hand and your concentration lasted to the end, and what happens to you when a question you did not expect appears in the second section.

Hold on to the word instrument here, because it is the whole argument of this post. A mock is a diagnostic instrument, not a rehearsal to be won. An instrument that gives you a reading you like is worthless if the reading is wrong.

Why revising hard for a mock defeats the point

Because you are measuring yourself, and you have complete control over the conditions of the measurement. Spend the week before the mock cramming three topics you think are likely to come up, and you will very probably score better. What you will not have is any idea which parts of the course you actually hold. Those three topics now look solid because you met them on Sunday, and the rest of the paper looks weak by comparison, so the priority list you walk out with is a record of what you revised last week rather than a record of what you know.

There is a clean demonstration of the gap between a near-term score and durable knowledge. In Test-Enhanced Learning, published in Psychological Science in 2006, Henry Roediger and Jeffrey Karpicke had students either restudy a prose passage or take a single recall test on it, then measured retention at different delays. Five minutes afterwards the restudy group came out ahead, 81 percent against 75. One week later the ordering had flipped hard: the tested group held 56 percent and the restudy group 42.

Read that as a finding about measurement rather than about flashcards. The arrangement that produced the best score minutes after studying was not the arrangement that produced the best score a week out, and at the short delay it pointed confidently in the wrong direction. A mock sits in exactly that position. It is a score taken days after a burst of revision, being used to predict a paper you will sit months later. Fill those days with cramming and you are carefully optimising the one number nobody needs.

The decay is the part that catches people out. Material pushed in during a single intensive week fades quickly once the pushing stops, which our guide to the forgetting curve covers in detail. The cruelty of a crammed mock is that those exact topics never make it onto the fix list, because they scored well, so the fade goes unnoticed until the paper that counts.

How much should you revise before a mock?

Enough that you are not walking in cold, and not so much that the result stops being yours. The workable line is between review and acquisition. Going over material you have already learned, at roughly the rate you were already going over it, keeps the measurement honest, because that review is part of your normal week and would have happened anyway. Learning a topic for the first time in the four days before a mock is a different act, and it is the one that bends the reading.

In practice that looks like carrying on with whatever loop your subjects are already running. If you are working through GCSEs, the retrieval-and-spacing habit described in our guide to revising for GCSEs across Year 11 continues untouched through mock season. If you are on a linear two-year course, the same holds in our guide to revising for A-Levels across Year 12 and Year 13, where mocks are one checkpoint in a long spacing schedule rather than an event the schedule bends around.

Three things are worth doing in the days before, and none of them are content pushes. Find out the format: how many papers, how long each one runs, how the marks are split, and what is allowed in the room. Sort out the practical layer, which is sleep, the right equipment and a calculator that works, because a mock lost to a dead calculator teaches you nothing except that batteries exist. And decide in advance that you are not going to open your notes in the corridor, since ten minutes of frantic reading changes your score slightly and your knowledge not at all.

One reframe makes the whole thing easier to accept. You are not choosing between a good mock and a bad mock. You are choosing between a mock that tells you the truth in January and a mock that tells you a comfortable story in January and the truth in June, when there is nothing left to do about it.

During the mock, treat it exactly like the real thing

This is the part where none of the above applies, and it is worth saying plainly, because a post arguing against cramming for a mock can very easily be read as an argument for not trying. Sit the paper at full effort, to time, with no notes and no phone, and behave as though the grade counts. Everything the mock is worth depends on the conditions being real.

The reason is that a large part of what a mock measures is not content at all. It is the skill of operating an exam paper: reading the question properly on the first pass, deciding how many minutes a section deserves and then obeying that decision, leaving a question you cannot start and coming back rather than sitting in front of it for twelve minutes, writing legibly and at speed for two hours, and recovering from the moment a question you do not recognise arrives. Those are trainable, and they only get trained under conditions that actually apply the pressure.

Which means the small compromises are the expensive ones. Sneaking a glance at a formula, letting yourself run five minutes over, quietly deciding partway through that this one does not count and easing off: each of those wipes out a specific reading you would otherwise have got. And if you ease off, the paper you get back is unusable, because you cannot tell which lost marks were gaps and which were the easing off.

After the mock: the part that is actually worth your time

The marked paper is a map, not a verdict, and unlike almost every other piece of feedback you get, it arrives while there is still time to act on it. That gap between the mock and the real exam is the whole reason mocks exist. Whether it gets used is decided in the week the papers come back.

The mechanics of pulling a wrong answer apart are the same for any test you get handed back, and we have covered them properly elsewhere: our guide to reviewing a test with an error log works through sorting every lost mark by cause rather than by topic, and redoing the misses cold before you read the mark scheme. Use that as the tool. What is worth adding here is why a mock is an unusually rich thing to run it on.

It samples the whole syllabus in one sitting. A practice test on one topic tells you about that topic, and you chose the topic, which means you were already thinking about it. A mock covers everything taught so far, in proportions the exam board decided, so it can surface a weakness in something you had quietly stopped thinking about in October. Those are the gaps that never come up in self-directed revision, because self-directed revision keeps returning to the material you remember having found hard.

It compares subjects on the same day. A mock series gives you several papers sat under identical conditions inside one fortnight, which is the only fair way to find out where your weakest subject actually is. Nearly everyone is wrong about this by feel, usually confusing the subject they enjoy least with the subject they are worst at.

It arrives with runway attached. A gap you find in January before summer exams is a manageable piece of work. The same gap discovered in the exam hall is a lost grade. This is also the point at which the corrupted-measurement problem becomes concrete: a topic that scored well because you crammed it the week before will not appear anywhere on your list, and you will spend the runway on something else entirely.

Turning the list into actual work takes one more step, which is scheduling it. Rank the weaknesses by marks lost rather than by how annoying they felt, then block the top of that list into real slots. Our guide to building a revision timetable covers the mechanics, and a mock is the best input a timetable ever gets, because for once the weighting comes from evidence rather than from a hunch.

The exam-technique data only a mock can give you

Content gaps get all the attention after a mock, and they are usually not where most of the lost marks are. Go through the paper a second time asking a different question: not what did I not know, but what did I do.

Four patterns are worth looking for specifically. Marks lost at the end of the paper, which is a pacing problem, and one created much earlier in the paper by the handful of questions you refused to abandon. Questions where you answered something adjacent to what was asked, which is a reading problem and is fixed by a mechanical habit rather than by more content. Questions left blank that you could have made a partial attempt at, which is usually a confidence problem, and expensive in any subject where method marks exist. And the moment you froze, if there was one, which is worth writing down while you still remember what set it off.

None of these show up in a practice test you sat at home over an hour and a half with a break in the middle, because the conditions that generate them were not present. They are the part of the mock that is genuinely irreplaceable, and they are also the fastest thing to fix, since a pacing rule or a question-parsing habit can be in place by the following week.

What if the mock went badly?

Then it worked. That is not a consolation line, it is the literal function of the exercise: a mock exists to find weaknesses at a point where finding them is still useful. A student who is alarmed in January and a student who is alarmed in June have very different problems, and only one of them has any options.

The failure mode to avoid is the emotional response replacing the analytical one. A bad mock produces a strong feeling and a vague resolution to work harder, and a vague resolution distributes effort evenly across everything, which is the least efficient possible use of the information you were just handed. The paper is specific. Your response should be too. Four topics, ranked, with dates against them beats a fortnight of grim general revision.

It also helps to know what the result does and does not decide. Mocks do not form part of your final grade, but they do feed predicted grades, set placement and, at GCSE, tier of entry in subjects that have one. That makes them consequential without being final, which is exactly the position in which an accurate result is worth more to you than a flattering one.

Redrilling the weak topics with GeniusPal

The mock hands you a list. What it does not hand you is any way to find out whether the fixing worked, and that is a real gap, because the next full paper under exam conditions may be months away, and rereading a topic until it feels familiar will tell you nothing at all.

So the loop after a mock is short. Take the material for one topic on your list, your class notes, a chapter of a revision guide, a set of lesson slides, and upload it. PDF, Word, PowerPoint, plain text, Markdown and CSV files all go in, up to 10 MB. What comes back is a quiz, a set of flashcards or a recall drill built only from that topic, which is the point: the mock already decided what deserves the attention, so there is no reason to redrill a whole subject. Then do the part that supplies the answer, which is running the set cold a week later with nothing in front of you. Produce it from memory and the gap is closed. Fail to, and it is still open, and you found that out in February rather than in the exam hall.

A new account gets two study-set generations for the lifetime of the account before anything is paid for, which is enough to take the two worst topics off a mock paper and see whether the loop suits you.

What no tool can do is the decision at the top of this post. Nobody else can choose to walk into a mock without a week of cramming behind you, and that choice, made before the paper rather than after it, is what decides whether the list you come out holding is worth working from at all.