How to revise for A-Level Maths mocks: the four-week plan

Last updated: July 2026

Four weeks is enough to change a mock grade — but only if the weeks run in the right order, which is almost exactly the reverse of what most students do. The instinct is to start with full past papers "to see where I am" and end with anxious note-reading. The working order is the opposite: audit first, repair second, mix third, and only then full papers under time, with the notes barely featuring at all. Here's the plan week by week, as I set it for my own students every mock season.

Week one: the audit and the hit list

Day one isn't revision; it's reconnaissance. Take the topic list the mock will cover and grade every line honestly: solid, shaky, or missing — where "solid" means "I can do exam questions on it, today, unaided", not "I remember liking it". The evidence for this audit already exists in the homework record: everything marked wrong this term is a vote for shaky. Out of this comes the hit list — typically five to eight topics — ranked by two things: how many marks the topic carries, and how repairable it is in a month. Algebra-adjacent weaknesses go top regardless, because they leak marks into every other topic on the paper. The rest of week one starts the repair: one hit-list topic per session, rebuilt with pen in hand — explanation, then a climbing question set, marked line by line as you go. What does not appear anywhere in week one: reading through notes, making beautiful summaries, or any activity where the pen isn't answering questions.

Week two: repair, then prove it

Week two continues down the hit list with one addition that separates revision that works from revision that feels nice: every repaired topic gets proved before it's crossed off. The proof is exam questions — real board questions on that topic, done cold, at something approaching real speed. The gap between "I can do the exercises" and "I can do the exam questions" is where mock grades actually live: exercises announce their topic and arrive in convenient sets; exam questions arrive disguised, mixed, and worded to test whether you can find the maths inside the sentence. A topic leaves the hit list when its exam questions come out, not before. By the end of week two the hit list should be at least half crossed off — and if some stubborn topic refuses to move after two honest attempts, flag it for help now, while a fortnight remains, rather than discovering it again in the exam hall.

Week three: mixed practice — the missing middle

This is the week most students skip entirely, jumping straight from topic work to full papers, and its absence is why their paper scores disappoint them. The skill a full paper actually tests first is recognition — deciding what each question even wants, with no topic label to help — and that skill needs training on mixed material: compiled mixed exercises, review sections, or half-papers assembled from past papers across many topics. Work in forty-five-minute timed blocks, mark immediately, and start the error log if it doesn't exist: every dropped mark, one line — topic, cause, fix. Within a few sessions the log develops its repeats, and those repeats are pure gold: they are the specific, personal leaks that week four will target. Keep one session this week for the applied content specifically — statistics and mechanics starve quietly during pure-heavy revision, and a third of the mock lives there.

Week four: full papers, real conditions, no heroics

Now the full papers — two or three across the week, under genuinely honest conditions: the real time limit, no phone, no notes, the formula book you'll actually have and nothing more. Mark each one against the scheme the same day, harvest the error log, and spend the between-days closing the two or three leaks the log names most often. Expect the first paper's score to sting slightly; that's normal and it climbs. Practise the two habits that convert knowledge into marks under pressure: triage — banking every accessible mark before wrestling the monsters — and showing working relentlessly, because method marks are the difference between a bad question and a catastrophe. The final forty-eight hours: one light session on the error log's greatest hits, checking the formula book's contents so nothing in it surprises you, and then genuinely stopping. The night before is for sleep. A tired brain loses more marks than one final practice paper has ever gained.

What the mock is actually for

A last reframe, because it changes how the whole month feels: the mock's real product isn't the grade — it's the highest-quality diagnostic data of the year, generated under the only conditions that tell the truth. Sat properly off the back of a real four-week preparation, the mock tells you precisely which gaps survived, how your timing holds across a full paper, and what your nerves do to accuracy — knowledge that makes the spring's final campaign dramatically more efficient. So sit it like it's real, then read it like it's data. The students who do both, in that order, are the ones whose summer grades routinely embarrass their mock ones.

If the audit in week one turns up more damage than a month can repair — or one topic simply won't move — that's the moment targeted help pays best, while there's still time to use it. Get in touch and I'll help sort what the four weeks should attack first, or take the stubborn topics off the list entirely.