Most candidates sit their first full mock far too late, and the reasoning always sounds responsible. There is no point attempting a whole paper before you have covered the material, so you work through the syllabus first and keep the mock for when you are ready. The effect is that the single most informative thing you can do arrives after most of your decisions have already been made — after you have chosen what to study, how to schedule it, and how long to allow. A first mock is not an exam you pass or fail. It is a measurement, and a measurement is worth far more at the start of preparation than at the end of it.
Sit it before you feel ready
The discomfort of an early mock is the point of it. Sitting a paper you are unprepared for tells you things the syllabus cannot: how long a question actually takes you rather than how long you assume it takes, whether your concentration survives a full sitting, which sections hold up under a clock and which quietly collapse. None of that is visible while you are working through topics at your own pace, and all of it shapes how you should be spending the weeks ahead.
Waiting until you feel ready also hands the decision to a feeling. Readiness is not something you can sense from the inside with any accuracy — candidates routinely over-rate areas they enjoy and under-rate ones they avoid — and the mock exists precisely to replace that impression with evidence. The cost of being wrong early is a mildly demoralising afternoon. The cost of being wrong late is weeks spent on the wrong thing.
Make the first paper as close to the real format as you can manage: full length across both modules if you have time for it, on a screen rather than on print, in one sitting with no pauses, and without rough paper if the real exam does not allow it. The setup matters more than usual here, because a baseline sat under comfortable conditions measures your comfortable conditions. If you have nothing to sit yet, a free practice test is enough to start with, and the case for matching real exam conditions applies from the first paper onward.
The first number is a starting point, not a prediction
Expect the score to be low, and expect that to feel worse than you anticipated. A cold first paper measures your unfamiliarity with the format at least as much as your reasoning: you are meeting the question types, the interface and the time pressure simultaneously, and most of what goes wrong the first time is attributable to that rather than to ability. Improvement from a first sitting is usually the fastest improvement you will see, because the easiest gains — knowing what the formats want, not losing a minute to each instruction screen — come from simply having done it once.
Two habits are worth resisting. The first is treating the result as a forecast. Because the dMAT reports a scaled score and a percentile rank rather than a raw mark, a modest number of questions can look like a dramatic position, and a single paper is in any case a point estimate of something that naturally varies between sittings. The second is letting the baseline set your target. A goal drawn from your worst-informed paper will either be so low that it stops guiding you or so high that you stop believing it; score goals are better set once you have two or three papers and can see a band rather than a dot.
Record the shape of the paper, not just the total
The total is the least useful thing your first mock produces. What you want is a description of how it went, written the same evening while you still remember, and four things are worth capturing.
Start with where the time went, subtest by subtest — specifically how far you got before the clock ran out, since questions never reached are a pacing problem and nothing else. Then separate the wrong answers you understood the moment you saw the solution from those you could not have solved with another ten minutes; the first group is carelessness or pressure, the second is method. Note where your attention dropped, which on a long paper is usually a specific point rather than a gradual fade. Finally, list the formats that were simply unfamiliar — the Core module mixes question types that reward practice heavily, and something like Latin squares can cost you far more on first contact than it ever will again. Check anything that surprised you against the syllabus and the official sources rather than against your memory of the paper.
That set of notes is the start of a habit. The same questions applied to every subsequent paper are what a proper mock review consists of, and keeping them in one error log is what turns isolated observations into a pattern you can act on.
Turn the baseline into the next few weeks
A baseline earns its place by changing your plan. Pick two or three priorities from it and no more: method gaps go into study time, pacing problems go into short timed sets rather than more full papers, and stamina goes into gradually longer sittings. If the notes point at one weak area, that is where the next fortnight belongs — but keep enough contact with your stronger sections that they do not drift while you are busy elsewhere.
Then leave it alone for a while. The baseline has done its job, and sitting papers back to back before you have changed anything just produces more measurements of the same candidate. A sensible gap between mocks gives your corrections time to take effect, and the interval should be set by how long you have until the test rather than by how anxious the first result made you.
The number from your first paper will not matter in a month. The decisions you make because of it will.
