How to revise for mocks in two weeks

Mocks have a way of sneaking up on you. One week they're a distant thing on the calendar, the next they're two weeks away and you haven't started. If you're trying to work out how to revise for mocks without pulling a string of late nights, the good news is that two weeks is genuinely enough time to do this well, as long as you spend it on the right things. This is a calm, realistic plan for doing exactly that.

First, get the pressure in proportion

Mocks matter, but not in the way exam nerves make them feel. They're a rehearsal. Their real value is showing you what you actually know and how the exam feels, while there's still plenty of time to fix the gaps before the real thing. A rough mock is useful information, not a verdict.

So the goal for the next two weeks isn't to cram everything into your head for one morning. It's to revise in a way that both helps the mock and leaves you genuinely further ahead for the summer. That means using the two habits that actually build lasting memory, rather than the ones that just feel busy.

The two habits that do the work

Before the plan, the method, because how you revise matters more than how many hours you put in.

Test yourself instead of re-reading. Reading and highlighting your notes feels productive, but it mostly builds familiarity, you recognise the material, which isn't the same as being able to produce it in the exam. Closing the book and trying to recall the answer (active recall) is what actually strengthens the memory, and it shows you exactly what you don't know yet.

Space it out. Don't revise a topic once and tick it off forever. Come back to it a few days later, then again near the exam. Memory fades on a curve, and each well-timed review catches it just before it slips and resets it stronger. Across two weeks, revisiting a topic three times beats hammering it once.

Everything below is just these two habits arranged into a schedule.

Week one: cover the ground, find the gaps

The first week is for working out what you know and don't, and starting to fix it.

Days 1 to 2: map it and prioritise. List every topic that could come up, per subject. Mark each one honestly: confident, shaky, or no idea. Resist the urge to start with your favourite topic. The shaky and no-idea ones are where your two weeks will pay off most. The stuff you already know can wait.

Days 3 to 5: first pass by testing. Work through your weak topics, but revise them actively. Read a topic once to refresh it, then close everything and write down or say everything you can remember. Check what you missed. Turn the gaps into flashcards or a short list of questions, one idea each. You're not trying to master everything yet, you're building the material you'll test yourself on repeatedly.

Days 6 to 7: first past paper. Do at least one past paper or section under something close to exam conditions. Don't save papers for the end. Early on, a past paper is the most honest test of where you stand, and it tells you which topics to push in week two. Mark it properly against the mark scheme so you can see where marks are actually lost.

Week two: retrieve, apply, and rehearse the exam

The second week shifts from covering material to proving you can produce it under pressure.

Days 8 to 11: retrieval and weak spots. Now test yourself on the flashcards and questions you built in week one, and revisit the topics you got wrong in your first past paper. Space it: a topic you revised on day 4 is due another pass around now. Keep the sessions active, question, recall, check, rather than re-reading. Anything you get comfortably can drift to the back of the pile; anything you keep failing comes back sooner.

Days 12 to 13: past papers in the real format. Do full papers to time. This trains three things at once: recall, applying what you know to unfamiliar questions, and exam stamina. The gap between "I know this topic" and "I can answer this question about it under time pressure" is where a lot of marks quietly go, and past papers are the only thing that closes it.

Day 14: light review, then stop. The day before, do a gentle pass over your flashcards and the key facts you find slippery. Don't cram. A calm evening and a proper night's sleep will do more for your recall than another three hours of panic. Sleep is when your brain consolidates what you've revised, so it's part of the work, not time off from it.

A few things that make a real difference

• One idea per flashcard. A card asking for five things at once is really five cards in a trench coat, and it's much harder to recall. Keep them tight.
• Follow your mistakes. The topics you keep getting wrong deserve more of your time than the ones you get right. It feels nicer to review what you know, but it's the wrong place to spend the hours.
• Short, frequent sessions beat marathons. Four half-hour sessions across the week land better than one long cram, because the spacing is doing part of the work.
• Don't confuse a full schedule with a good one. Six hours of re-reading is worse than two hours of testing yourself.

Where doing it by hand gets messy

The plan above is simple in theory and fiddly in practice. The hardest part is the spacing: keeping track of which topic is due for another pass, and when, across every subject, while everything else in your life carries on. Two weeks in, a lot of students lose the thread of what they've revised and when, and default to re-reading whatever's in front of them.

A calmer way to run it

That tracking is what Recka is built to handle. It runs a modern spaced-repetition model (FSRS) that works out the day you're about to forget each card and puts it in front of you then, so you don't have to plan the schedule yourself. You do the testing; it decides what's due today and what can wait.

For a mock sprint specifically, you can set your exam date and it tightens the schedule around it, pushing your weaker, higher-value topics to the front so your limited time lands where it counts. It's free while it's in beta and runs fully offline on Windows and Mac, with a simulator on the site if you'd like to see it work before installing.

Two weeks is enough. Spend it testing yourself, not re-reading, space it out, and treat the mock as the rehearsal it is. You'll walk in calmer, and you'll be further ahead for the summer either way.