How to use SQE mock exams properly

Most candidates treat SQE mock exams as a box to tick: book it, sit it, look at the score, move on. That approach wastes most of the value a mock actually has.

A mock is a diagnostic tool, not a rehearsal for its own sake. Used properly, it tells you where your knowledge is weak, whether your pacing will survive the real thing, and what to study next. Used badly, it's just an expensive way to feel briefly good or bad about yourself. This post covers the difference: when to sit mocks, how often, and what to actually do with the results afterwards.

Start with the exam you're mocking

SQE1 is 360 multiple-choice questions split across two papers, FLK1 and FLK2, each with 180 questions sat over two sessions. Work out the time allowed per session and it comes out to roughly one minute forty seconds per question on average.

That number should shape every mock you sit. A mock that doesn't run to that pacing isn't testing the thing you'll actually face on exam day. Untimed question sets are useful for early knowledge-building, but they aren't a mock. Reserve that word for sessions run under realistic timed conditions, ideally in a format close to the real interface, so the exam feels familiar rather than new when you sit it for real.

If you're still mapping out fees and sittings around your mock schedule, the SQE cost breakdown and 2026-27 exam dates are worth having open alongside this one.

When to start mocking

Don't wait until you "feel ready." Readiness is exactly what a mock is meant to measure, so waiting for it before you start defeats the point. A reasonable structure for most study timelines looks like this:

1. Early phase (first third of your study period): short, low-stakes timed question sets on topics you've just covered. Not full mocks yet, just retrieval practice under a loose clock, aimed at building the habit of answering under time pressure.
2. Middle phase: full or half-length timed mocks roughly every couple of weeks. This is where mocks start doing real diagnostic work, because you now have enough syllabus coverage for the results to mean something.
3. Final phase (last four to six weeks): weekly or close to it, including at least a couple of full-length, two-session mocks that mirror exam day as closely as you can manage. The aim here is less about new knowledge and more about making the format itself boring through repetition.

A free SQE study planner can help slot mock sessions into your calendar around the rest of your revision, rather than leaving them to chance, which is usually when they get skipped.

Two mistakes show up constantly around this schedule. The first is sitting one mock a week before the exam and calling it preparation: a single data point tells you almost nothing you can act on with only days left. The second is over-mocking early, before you've covered enough material for the result to mean anything. A full 360-question mock in week two of a six-month plan mostly measures how much you haven't studied yet, which a shorter diagnostic quiz would tell you faster and cheaper.

Timing discipline during the mock itself

Running a mock under real conditions means enforcing the actual per-question pace, not an approximation of it.

• Set a visible timer and check it at natural breakpoints, for example every 30 or 45 questions, rather than only at the end.
• Don't pause the clock to look something up. If you wouldn't be able to do it in the real exam, don't do it in the mock.
• Practise the two-session structure at least once or twice before the real thing. Fatigue across a long sitting is part of what's being tested.
• If you're spending three or four minutes on a single question in practice, flag that as a pacing problem in your review rather than pushing through and forgetting it.

A mock run too gently, extra time, open notes, no real deadline, gives you a score that flatters you and a false sense of where you stand. That's worse than not mocking at all, because it delays finding the real problem.

The part most people skip: reviewing mistakes

The score at the end of a mock is the least useful number it produces. What matters is what you do with the wrong answers in the hour or so afterward.

For every question you got wrong, or got right by guessing, note down what it was testing, why you got it wrong (knowledge gap, misread question, ran out of time, careless slip), and what you'd do differently next time.

One wrong answer on a topic is noise. A cluster of three or four on the same topic, or a repeated pattern of "misread the question," is a signal. That's where your next study session should go, not back to the start of your notes.

A mock without a proper review is just an expensive way to find out a number. The number isn't the product. The list of specific, fixable gaps it produces is.

Keep this as a running error log across your whole study period rather than starting fresh after each mock. Over several months, the log becomes a more accurate map of your weak points than the syllabus itself, because it's built from your actual mistakes rather than a generic list of topics.

Reading your results honestly

Pass rates for SQE1 have varied noticeably between sittings, so don't anchor too hard to any single external benchmark when judging a mock score. What matters more is your own trend across successive mocks: is accuracy on previously weak topics improving, and is your pacing getting closer to the roughly one minute forty seconds per question the real exam demands.

A flat overall score can hide a lot. Two mocks with the same headline percentage can reflect very different situations, one a genuine plateau, the other a weak topic closing while a different one opens up. Track results by topic area, not just as a single number, so you can tell which one you're actually looking at.

For more on how the SRA's published pass rates work, see the pass rates explained post.

Frequently asked questions

How many SQE1 mock exams should I do before the real exam? There's no fixed number that suits everyone, since it depends on your study window and starting point. A reasonable pattern is light retrieval practice early on, a full or half-length timed mock roughly every two weeks through the middle of your preparation, and weekly mocks in the final month or so. What matters more than the total count is whether you review each one properly and track whether weak topics are actually closing.

Should SQE1 mocks be timed to match the real exam? Yes, at least for the mocks you're using to judge readiness. SQE1 gives roughly one minute forty seconds per question on average across its 360 questions, and a mock that doesn't hold you to something close to that pace won't tell you whether your real pacing will hold up. Untimed sets are still useful for early learning, just don't mistake them for a mock.

What should I do after a bad mock score? Review it properly before deciding how you feel about it. Break the wrong answers down by whether they were knowledge gaps, misread questions, or timing problems, and look for patterns rather than treating every wrong answer as equally important. A bad score with a handful of repeated, fixable patterns is good news this far out from the exam, because you now know exactly what to work on.

Is it bad to mock too often? Mocking too often too early, before you've covered enough of the syllabus, mostly measures how much you haven't studied yet. Spacing mocks out and building frequency as your exam date approaches gives more useful information than clustering lots of mocks early or right before the exam.

Do SQE1 mock scores predict the real exam result? They're an indicator, not a guarantee. A mock taken under realistic timed conditions, reviewed properly, and repeated across your study period gives a reasonably honest read on trend and weak spots. A single score in isolation, especially under loose conditions, tells you much less than a series tracked over time.

Mocks earn their place in a study plan by being treated as data collection, not performance. Time them properly, space them across your whole campaign rather than cramming them at the end, and spend at least as long reviewing the wrong answers as you spent sitting the paper. That combination is what actually moves a score, not the act of sitting another mock.