Most dMAT study plans answer the question of how long to prepare and never answer the question of how to divide it. The two modules sit side by side in every schedule, and the share each one gets is usually settled by accident — by which practice material came to hand first, or by which questions are more enjoyable to sit down with on a Tuesday evening. That is a real decision being made badly rather than no decision at all. A plan that never names a ratio has still chosen one, and it has chosen it on the basis of comfort. This article is about making the choice deliberately: what the scoring structure implies, why the two modules do not repay time at the same rate, and how to set a split you can defend with evidence rather than preference.
A total made of two parts changes the question
Start from how the result is reported. As our note on reading your two module scores sets out, the certificate reports the Core Module and the relevant subject module separately, and the official description of the scoring says the total is those two values added together. Confirm the current details on the syllabus page and the official sources it links, because this is the kind of thing worth reading first-hand.
If that structure holds, one consequence follows immediately: toward the total, a point is a point. There is no module where progress counts for more, which means the useful question is not "which module matters more?" — it is "where is my next hour of study worth more points?" Those are very different questions, and only the second one has an answer you can act on this week.
Two qualifications keep that from becoming too neat. Universities set their own admission criteria, so a programme may look at the shape of your result and not only the total; if your target universities publish anything about the modules, that information outranks any general rule. And a total built on one strong module and one weak one is more fragile on the day than an even one, because a single bad half has nothing to lean against.
The two modules do not repay time at the same rate
The reason a fixed split is the wrong tool is that the modules improve on different curves.
Core work often has a step change in it. Several task types reward a repeatable first move more than they reward general cleverness, and a candidate who has never been shown a systematic approach can gain a surprising amount in a short period simply by acquiring one. That is the premise of our Core Module strategy guide: there is a method floor, and crossing it is fast. Time spent there early tends to produce visible returns quickly, and then flatten into the slower work of accuracy and pace.
General Academic work behaves differently. Most of the difficulty is reading under time pressure — holding an unfamiliar argument in mind, finding what a table actually says, resisting an answer that sounds right. As our guide to preparing for the General Academic Module argues, this improves steadily rather than suddenly, and it responds to regular exposure rather than to a concentrated block. Reading speed in particular, covered in how to read faster on the dMAT, is built in many short sessions, not recovered in a weekend.
The practical implication is a shape rather than a number. A preparation that front-loads Core method while keeping General Academic reading ticking over two or three times a week usually beats both of the common alternatives: finishing one module before starting the other, or splitting every week exactly in half regardless of what the evidence says.
Set the split from evidence, then revisit it
A defensible split starts with a measurement rather than an impression. Sit a timed run and look at the two module results separately — the free dMAT practice test is enough for this, and reading your first baseline explains how to interpret a first attempt without over-reading it. Then ask three questions in order.
Which module is further from where you need it? Distance from target, not raw score, is what you are allocating against.
Within that module, is the gap technique or speed? The distinction matters because the fixes are unrelated, and a technique gap is usually the cheaper one to close. Balancing weak and strong Core subtests works through this for the three Core subtests specifically.
Does the gap have a known fix I can name? A weakness you can describe in a sentence is worth more study time than a vague one, because you can tell whether the time is working. If you cannot name it, your error log is the next place to go, not another hour of practice.
Treat the answer as a decision with an expiry date. Re-run those questions against fresh evidence every couple of weeks; a split that was right at the start of a three-month plan is unlikely to be right in week eight, because the point of the early weeks is to change the thing the split was based on.
Watch for comfort drift while you do. Core tasks give clean feedback — an answer is right or it is not — so they feel like progress. General Academic sessions feel slow and hard to grade, which is exactly why they are the first thing dropped from a busy week. If your log shows a split you never consciously chose, that is usually what happened.
Converge before the test
Whatever ratio you settle on, it should matter less as the date approaches. The exam runs both modules in one sitting, and the skills that decide the last stretch — pacing, recovering from a bad run of questions, arriving at the second half with something left — are not trained by drilling either module in isolation. Simulating real exam conditions is the work of the final phase, and it is deliberately unsplit.
So the split is a tool for the middle of a preparation, not a principle for all of it. Early on it should follow your weakest nameable gap; in the middle it should follow your evidence; at the end it should dissolve into full rehearsal. If you can say in one sentence why this week is weighted the way it is, the plan is doing its job.
