Let's talk about free mocks

If you had to pick one hour of revision to protect above all others, it wouldn't be another hour of reading notes. It would be an hour spent answering questions under timed, exam-like conditions and then working out exactly why you got things wrong. That's not a slogan, it's what a large body of learning research points to, and it's worth being honest about why so many candidates still under-use it.

The testing effect, in plain terms

The core finding, associated with work by Roediger and Karpicke in the mid-2000s, is that retrieving information from memory strengthens your ability to recall it later far more than re-reading the same material does. In their studies, students who repeatedly restudied a passage did better on a test given right after the study session, but students who repeatedly tested themselves on the passage did substantially better on a test given days or weeks later. Restudying feels productive in the moment because recognition is easy; retrieval is harder and less comfortable, which is exactly why it builds a sturdier memory trace.

That's the honest, conservative version of the finding: it's not that re-reading is worthless, it's that retrieval practice tends to outperform it on the kind of delayed recall an exam actually demands. For SQE, where you sit FLK1 and FLK2 weeks or months after first covering a topic, delayed recall is the only kind that matters. A mock question forces retrieval. A highlighted paragraph doesn't.

Why the exam conditions part isn't optional

Answering questions is one thing. Answering them against a clock, in an unfamiliar interface, with the low hum of pressure that comes from a result at the end, is another. Skipping that part and only ever doing "relaxed" practice - untimed, browser open, no real stakes - means you're rehearsing a version of the exam that doesn't exist.

There's a reasonably intuitive logic here, sometimes called pressure inoculation: performing under mild, repeated exposure to exam-like stress makes the real thing feel more familiar rather than novel. You've felt the clock before. You've felt the slightly uncomfortable urgency of question 40 out of 90 before. None of that is a surprise on the day, because you manufactured a version of it deliberately, on your own terms, when a bad outcome cost you nothing.

This is also where timing specifically pays off. SQE1's single best predictor of a rushed final quarter isn't knowledge, it's pacing that was never practised. If the first time you find out your pace is off is in the real assessment, you've picked an expensive moment to learn it.

Debriefing a mock properly

A mock that ends with a percentage and nothing else is a wasted mock. The score tells you where you stand; it does nothing to tell you where to go next. The value is almost entirely in what you do in the twenty minutes after you finish.

Build an error log, not just a memory of "that felt hard." For every question you got wrong, or got right for the wrong reason, write down:

• What the question was actually testing, in one line.
• Why you got it wrong - a knowledge gap, a misread question, a timing scramble, or a careless error.
• What you'd do differently next time you see something like it.

Patterns matter more than individual questions. One wrong answer on a topic is noise. Four wrong answers on the same topic, or a cluster of "misread the question" errors, is a signal telling you exactly where to spend your next study session. Over a full campaign, this log becomes more useful than your notes, because it's built entirely from your actual failure points rather than a generic syllabus.

The point of a mock isn't the number at the end. It's the list of specific, fixable things it hands you afterwards.

How often, and when

There's no single right cadence, but a rough shape works for most people preparing over several months: light, low-stakes retrieval throughout (a handful of questions most weeks), building to a full timed mock roughly every couple of weeks as you move into the middle of your revision period, and then more frequent full mocks - weekly or close to it - in the final few weeks before your assessment window. The goal in that final stretch isn't just knowledge testing, it's making the exam experience itself boring through repetition, so the only new thing on the day is the specific questions.

Space mocks out rather than clustering them right before the exam. A single mock the week before tells you very little you can still act on. A mock every couple of weeks across your whole campaign gives you enough data points to actually see whether your error log is shrinking.

Cost should never be why you under-practise

Here's the part worth being blunt about. The best-evidenced study method available to you - frequent retrieval practice, under realistic conditions, followed by honest review - has historically been rationed by price. Full-length timed mocks with meaningful feedback aren't cheap to produce, so candidates on a budget have often practised less than they should, not because they didn't understand the value, but because each additional mock had a cost attached to it.

That's the specific barrier PasSQE's free mock engine is built to remove. It's timed, it uses an exam-style interface, and it gives AI feedback on written answers, so you're not just finding out you got a question wrong, you're getting a steer on why. If part of your preparation involves interview-style assessment, the partner interview practice works on the same logic: realistic conditions, low stakes, no reason to ration your reps. None of this is about being flashier than a paid mock. It's about making sure that budget is never the reason someone sits fewer mocks than they need.

The takeaway

Retrieval beats re-reading, especially for the kind of delayed recall an exam demands. Realistic conditions - timed, unfamiliar interface, real stakes - make that retrieval practice transferable to the actual day. And the debrief, built into an error log rather than left as a score, is where a mock turns into progress. Do this every couple of weeks through your campaign, more often near the end, and don't let cost be the reason you do it less than the evidence says you should.