Rough work is one of the few things in the exam room that is entirely under your control, and one of the few that almost nobody practises. Most candidates rehearse the reasoning — how to attack a sequence, how to set up an equation — but leave the writing itself to improvisation. Then, under time pressure, the page fills with half-finished fragments, a digit gets copied across wrong, and a question that was genuinely solved ends up answered incorrectly. Your working is not a scribble pad. It is an extension of your memory, and like any other technique it rewards a little deliberate practice.
What rough work is actually for
Rough work has exactly three jobs, and it is worth naming them, because most wasted writing does none of them.
The first is holding intermediate results so you do not have to. Working memory is small and it degrades under stress; the moment you are carrying three numbers and a rule at once, one of them will slip. Writing a value down costs you a second and buys back the attention you were spending on not forgetting it.
The second is making structure visible. Some problems are hard only because they are hard to hold in the head — a set of constraints, a grid of possibilities, a relationship between two quantities. Drawn on paper, the same problem often becomes ordinary.
The third is recording decisions you have already made, most obviously eliminations. If you have ruled out two options, that judgement is worth preserving; re-deriving it on a second pass is pure waste.
If a piece of writing does none of these three things, it is costing you time without returning any. Copying the question out, writing full sentences, or neatly re-doing an arithmetic step you have already trusted — all of that is ink spent on nothing.
Write less, but write the right things
The instinct under pressure is either to write everything or to write nothing. Both are expensive. Aim instead for a small, consistent set of habits.
Label what a number means. A column of bare figures is unreadable thirty seconds later. A number with a one- or two-character tag beside it — a variable name, a unit, an initial — stays useful for the rest of the question. This is the single cheapest defence against the sort of slip covered in our guide to avoiding careless mistakes.
Write down what you are solving for. On multi-step problems it is startlingly easy to compute a correct intermediate value and then submit it, because you have lost track of the actual question. One short note at the top of your working — the target quantity — prevents it.
Record eliminations, not deliberations. A stroke through a rejected option is enough. You do not need to write why. Our guide to process of elimination covers the reasoning; the note here is simply that the outcome belongs on the page and the argument does not.
Do not re-copy. Every transcription is a chance to introduce an error. Work from the question where you can, and copy only the values you will actually manipulate — a discipline that matters most on the calculation-heavy items discussed in solving dMAT mathematical equations under time.
Give the page a structure
Unstructured rough work fails in a specific way: you solve the question, then cannot find your own answer.
Work in one region per question and put the question number beside it. When you come back on a second pass — and you will, for the items you deferred — you want to resume, not restart. Working that wanders diagonally across the sheet, mixed in with two other questions, forces you to redo everything.
Match the shape of the working to the shape of the problem. Constraint puzzles want a grid, and our systematic approach to Latin squares is essentially a method for drawing one well. Questions built on data want a small two-column table rather than prose, which is also the habit that makes graphs and tables tractable. Sequences want the terms written in a row with the differences underneath.
And keep your digits legible to yourself. Under time pressure a hurried 1 and 7, or 4 and 9, or 0 and 6, start to look alike. A mark lost to your own handwriting is about the most avoidable loss on the paper.
Build the habit before test day
Rough work is a motor habit, not a piece of knowledge, so it only changes through repetition. Practise it under the conditions you will actually face rather than at a comfortable desk with unlimited paper — the setup described in simulating real exam conditions is the right one, and a full timed paper such as our free dMAT diagnostic is a good place to watch your own habits under load.
Then make your working part of your review. When you get a question wrong, look at what you wrote as well as what you answered: unlabelled numbers, a missing target quantity, working that ran out of room. These leave a visible trace, and the same trace tends to repeat.
One practical constraint is worth settling before any of this matters. Everything above assumes you have something to write on, and that assumption is not safe: g.a.s.t. does not publish, on its public pages, what may be brought to the desk or what the centre hands you. The rules for your own sitting are in the exam-rules document and your participant instructions, so find out there — early, while you can still change how you practise — rather than discovering it on the morning. Our test-day checklist covers what else to settle in advance.
If it turns out you are given nothing, none of this is wasted, but it stops being the main skill. The Core subtests are built to be answered without written working, so the safer default is to train your working memory to carry the intermediate results, and treat rough work as a bonus you may or may not have.
None of this is dramatic. Nobody has ever transformed a score through better handwriting. But rough work sits underneath every calculation you make on the paper, and a small, consistent method removes a category of loss that has nothing to do with how well you understand the material.
