Solving a past exam is only half the work — what you do afterward is where scores actually move. A complete walkthrough: classifying errors into four types, building a lean review notebook, and running your second and third passes.
Here's what most people do after finishing a past exam or mock test: grade it, look at the score, done. "I got 65. Fifteen points short of the passing line. I'll try harder next time." Close the exam booklet at that point, and most of the value of the hours you just spent solving it evaporates. To put it bluntly, a review that stops at the score tells you where you currently stand — and tells you nothing at all about what to do to move up.
Past exams really serve two purposes. The first is showing you the exam's patterns: which topics appear every year, which question formats eat your time, where the heavily weighted questions sit. This emerges naturally as you solve and grade. The second is exposing your own gaps — and this one never emerges unless you dig into each wrong answer and ask why you missed it. Two students can both score 60, but a 60 caused by missing knowledge and a 60 caused by botched time management call for completely different next steps.
Skipping the review is expensive in time, too. One year of a past exam takes the full test duration to solve — say 90 to 180 minutes. Move straight on to another year without reviewing, and you'll lose points to the same gaps in the same way, spending several more hours to do it. People whose scores stay flat no matter how many years they solve are almost always stuck in this loop. People who spend at least as long reviewing as they spent solving close a few gaps with every paper — so their scores move even on a smaller volume of practice.
One common misstep worth addressing here: the idea of "saving the past exams for the final stretch." The logic is to use them as a dress rehearsal once your ability is fully built — but that postpones discovering your gaps until the very end. Before it's a final check, a past exam is a diagnostic that sets the direction of your studying. It's fine to attempt the first pass before you're ready; solve one paper early in your preparation and use it as a map of what to study.
As a benchmark, budget 90 to 120 minutes of review for a 90-minute exam. That may sound like more than you can afford, but as the following sections explain, reviewing does not mean giving every question equal time. Classify your errors, focus on the ones that actually need work, and this time budget is more than enough.
The first step of a review isn't reading the answer explanations — it's classifying your errors. Go through each question you missed (plus any you got right without being sure why) and sort it into one of four types based on why you lost the points.
The first type is a knowledge gap: you simply didn't know it or had never seen it. Not knowing a word's meaning, not having memorized a formula, not knowing a legal provision — all of these qualify. The telltale sign is reading the explanation and immediately thinking, "I just didn't know that. If I memorize it, I can solve it."
The second type is an understanding gap: the material looked familiar, but you couldn't use it. You knew the formula but couldn't tell this was the situation to apply it, or you read the explanation and something still doesn't quite click. Telling this apart from a knowledge gap is simple: if the explanation instantly makes sense, it was a knowledge gap; if something still nags at you after reading it, it's an understanding gap.
The third type is a careless mistake: you knew it and lost the points anyway. A dropped minus sign, a misaligned answer-sheet row, reading "choose the incorrect statement" as "choose the correct statement" — these are the classics. The temptation is to groan "I actually could have solved that" and move on, but as we'll see below, careless mistakes aren't bad luck. They're a pattern you can fix.
The fourth type is running out of time: you could have solved it with more minutes on the clock, but never reached it — or panicked and stalled. Count not only the questions you left blank, but also points lost because you overspent on the first half and rushed through the second.
One more thing: always include the questions you got right without confidence. A four-option question you narrowed to two and then guessed correctly is a question you'll lose half the time on exam day. It may have a mark next to it, but in substance it's a wrong answer — flag it and classify it the same way. Whether you catch these or not makes a real difference in how complete your review is.
Why does this classification matter so much? Because the four types have four different causes, and therefore four completely different fixes. Re-solving a knowledge-gap question over and over won't help if you never memorize the missing fact. Studying the explanation of a careless-mistake question intently won't prevent the next slip. The standard advice — "read the explanation and re-solve everything you missed" — is inefficient precisely because it ignores these differences. In practice, all you need to do is mark each wrong answer with a single letter as you grade — K, U, C, or T. It takes a few seconds per question and perhaps ten minutes for a whole paper.
Once the classification is done, treat each type with its own fix. This is the part that translates directly into points.
The fix for a knowledge gap is adding it to a memorization list. The point is not to cram it on the spot, but to load it into a system that will show it to you repeatedly later. Humans reliably forget things they've seen only once, so turn the item into a flashcard-style entry that keeps resurfacing every time you review. Facts that appeared on a past exam are facts with a track record of being tested — treat them with higher priority than anything in an off-the-shelf vocabulary book.
The fix for an understanding gap is going back to your study materials. Don't settle for the answer explanation; reopen the relevant unit in your textbook and reread it from the foundations up. To judge whether you've actually understood it, use one test: can you explain it to someone else without looking at anything? There is a wide gulf between "I read the explanation and I think I get it" and being able to reconstruct the reasoning in your own words — and the first state will cost you the points again on exam day. This fix takes time, but one understanding-gap question usually has several other lost points from the same unit hiding behind it, so the time pays back more than any other type.
The fix for careless mistakes is recording your mistake patterns. "I'll be more careful next time" is not a countermeasure. Did you miscopy a sign? Skip over a condition in the problem statement? Fail to leave time for checking? Write your mistakes down and line them up, and you'll be surprised how often the same few patterns repeat. Once you've identified a pattern, decide on one concrete procedure that cancels it — for example, "on calculation questions, re-check only the signs at the end," or "always underline the word 'incorrect' in the question stem." If you can narrow your mistakes down to about three types, the list doubles as a pre-exam checklist worth reading one last time before the real thing.
The fix for running out of time is reworking your time allocation. Start by reconstructing where the minutes went, question block by question block (from the next paper onward, jot the elapsed time next to each section as you go — it makes this far more accurate). Then set a target time per section and a bail-out line — "if I pass this many minutes, I skip and come back" — and test it on the next paper. If you're slow because one particular topic is under-practiced, that's a volume problem rather than a pacing problem, so add drills for that topic to your plan. And if a brutally hard question swallowed your time, then concluding "the right move was to abandon that question and spend the minutes elsewhere" is itself a perfectly good fix.
Here's roughly how much time each fix deserves: a few minutes per question for careless mistakes and time-outs, about a minute per item for knowledge gaps if you're just adding them to a list, and 15 to 30 minutes per question for understanding gaps. Understanding gaps are by far the heaviest, so don't try to clear everything in a single review session — treat those questions as a separate assignment, along the lines of "these three by the end of the week," and the review as a whole won't stall.
Your classifications and fixes get recorded in a review notebook — an error list. The single most common failure here is carefully copying out full problem statements and explanations until producing a beautiful notebook becomes the goal in itself. Copying takes a long time, and your brain is barely working while you do it. If you're about to spend ten minutes transcribing one question, spend those ten minutes re-solving it instead — that builds real ability.
Write down only the minimum you'll need to re-solve the question later. Concretely: where the question lives (year and question number — this is what makes copying the problem text unnecessary), the error type, one line on why you missed it, and one or two lines on the correct line of thinking. That's all. One to three minutes per question is the right amount; if you feel the urge to write more, suspect you're overdoing it. A single line like "2023, Q18 / understanding gap / confused a shift of the demand curve with movement along it / the whole curve moves only when a non-price factor changes" carries everything you'll need on the second pass.
Items classified as knowledge gaps are better turned into flashcards than notebook entries. With a prompt on the front and the answer on the back, you can drill them in spare moments anywhere. Paper cards work, but a tool like a browser-based flashcard app automatically adjusts how often each card comes up based on whether you got it right — sparing you the waste of flipping through cards you've already mastered. Items harvested from past exams pile up quickly, so automating this bookkeeping pays off substantially.
Keep your careless-mistake patterns on a separate single sheet that you grow over time, apart from the per-question notes. The error list grows question by question, but mistake patterns converge to a handful of entries — "didn't re-check signs," "misread the question stem," and so on. That one sheet becomes pre-exam reading material of a kind nobody but you could ever produce.
Finally, a review notebook is the kind of tool that easily becomes "made it, done with it." Don't treat the moment you write it as the moment it's finished — it's a living document you add to with every re-solving pass. Build a standing slot into your study plan — ten minutes, once a week — for rereading it, and everything you wrote down will reliably get used.
With the review notebook in place, the next step is re-solving — and the first principle here is: don't re-solve everything. Redoing questions you answered confidently and correctly on the first pass yields almost nothing. The second pass covers only what's on the error list: the questions you missed, plus the ones you got right on shaky reasoning. This brings the second pass down to a third or half the time of the first, and the time you save goes toward another year's paper or drills in a weak area.
The second principle is spacing the passes out. Re-solve a question immediately after the first attempt and you'll get it right not because you understand it, but because you remember the answer — which verifies nothing. As a guide, schedule the second pass one week after the first, and the third another two weeks to a month after that. The longer the gap, the harder the recall — and that difficulty is exactly what strengthens the memory. The thinking behind "review right around the point of forgetting" is covered in depth in our article on spaced repetition and the forgetting curve.
The second pass sorts the questions further. Anything you now solve correctly can come off the error list (if deleting feels risky, just check it off and exclude it from future passes). Anything you miss a second time is a genuine pressure point for you — flag it and carry it to the third pass. And for any question you've now missed twice in a row, question your original classification. "I thought it was a careless mistake, but it was actually an understanding gap" happens more often than you'd expect.
To put numbers on it: if the first pass put 30 of 90 questions on your error list, the second pass re-solves only those 30. Get 20 of them right, and the third pass covers just the remaining 10, plus the few that newly wobbled on the second pass. The pool shrinking to roughly a third with each pass is a good sign the cycle is working.
Keep running this cycle and the pile of questions to re-solve shrinks with every pass, until you're left with the handful you miss no matter how many times you try. That handful is the final form of your weaknesses. In the last stretch before the exam, cycling through those few questions, your memorization list, and your mistake-pattern sheet will do more for your score than reaching for any new material.
Mock tests come with a source of information past exams don't have: the score report. Yet score reports tend to get the same "solve and move on" treatment — a glance at the percentile and the pass-likelihood grade, a moment of joy or despair, done. Percentiles and grades only tell you where you sit relative to other test-takers; they say nothing about what to study next. What deserves your attention is the breakdown underneath: your results by topic and by section.
One caveat specific to mock exams: timing. The score report arrives weeks later, but your error review should start the day of the test or the day after, when you self-grade. Your memory of how you reasoned through each question fades within days, and once you can no longer recall why you picked a given option, classifying the error becomes impossible. The realistic approach is two-stage: do the classification and fixes at self-grading time, then add the topic-breakdown reading once the report arrives.
Read the breakdown along two axes. The first is your own success rate per topic. Two students with identical totals can need opposite prescriptions: "90% on grammar but collapsed on the long reading" calls for concentrated investment in reading passages, while "an even 60% across every topic" calls for a general audit of fundamentals. The second axis is the overall success rate combined with your own answer. Most mock exams print the percentage of all test-takers who answered each question correctly. Your top review priority is any question with a high overall success rate — say, 70% or above — that you missed. Those are the questions that decide who passes. Conversely, a question fewer than one in ten test-takers solved can safely drop to the bottom of the pile.
Reading reports gets sharper when you line up several of them instead of one. Compared with the last mock, which topics improved and which stalled? If you've been logging study time by topic, you can also identify the topics that aren't improving despite the hours — a signal to change how you're studying, not just how much. For the concrete method of setting your logs against your results, see how to read your study graphs.
Finally, turn what you've read into the next plan. Don't stop at "I'm weak on long reading" — get all the way to "over the four weeks until the next mock: reading-passage practice three times a week, one error-list re-solving session a week," a plan with a duration and a frequency. That last step is what completes the review. The full procedure for building this kind of plan is laid out in how to build a study plan for a certification exam. Run this cycle after every mock, and the score report stops being a results notice and becomes the blueprint for your next month.
With MonoStudy, the knowledge gaps you find in past exams go straight into flashcards, reviewed on a schedule that follows the forgetting curve — while your study time builds up automatically, logged by subject.
Open the app free →