Most dMAT candidates practise plenty of questions but learn from only a fraction of them. You finish a set, note that you scored well enough, and move on — and the same kind of mistake quietly reappears a week later. An error log fixes that leak. It is nothing more than a running record of the questions you get wrong, written down in a way that turns each mistake into a specific thing to work on. Kept honestly, it becomes the most useful study document you own, because it is built entirely from your own weak points rather than someone else's guess at them.
Independent preparation notice: dMAT Prep is not affiliated with or endorsed by APS India, g.a.s.t., dMAT, DAAD or any German university. This article explains publicly available information and offers independent study guidance. Rules and dates can change, so always verify important decisions with the official sources.
Why a running log beats scattered notes
The problem with reviewing questions in the moment is that the lesson evaporates. You understand why you missed a figure-sequence item, feel a small flash of "ah, of course", and by the next session it is gone. A log makes the lesson permanent and, more importantly, collective: when ten mistakes sit on the same page, patterns appear that no single review could show you. You might notice that half your errors come from misreading the question rather than from the reasoning itself, or that you rush the first few items of every timed set. Those are not things you can see one question at a time.
A log also changes what "revision" means. Instead of re-reading material you already half-know, you spend your limited time on the exact operations that trip you up. That is the same principle behind reviewing a mock test properly — the difference is that an error log carries the insight across every practice session, not just one, so nothing you learn has to be relearned.
What to record for each mistake
Keep the entries short. If logging a mistake takes three minutes, you will stop doing it. A single line per question is enough, and a plain spreadsheet or notebook works better than anything elaborate. For each wrong answer, capture four things:
The question type. Note which part of the exam it belongs to — a core-module pattern item, a mathematical equation, a text from the general academic module. This is what lets you count patterns later.
What actually went wrong. Be specific and honest. "Careless" is useless; "misread the sign in the equation" or "picked the answer before checking the last option" tells you what to change. Most mistakes fall into a handful of causes, and naming yours is half the fix.
The correct approach. In one sentence, write the step you missed or the method that would have worked. You are not copying the full solution — you are recording the single move that would have flipped the result.
Whether it was a knowledge gap or a process slip. Knowledge gaps mean you did not know how to do something; process slips mean you knew but rushed, misread, or mismanaged your time. The two need completely different fixes, and separating them stops you from "studying harder" when the real problem was pace. Our guide to common preparation mistakes covers several of these process traps in more detail.
How to use the log so it changes your results
A log you never reopen is just a diary of frustration. Give it a job. Once a week, read back through your recent entries and sort them into two piles. The first is recurring types — the same question format showing up again and again. Those earn a dedicated practice block: pull ten similar items and drill them until the method feels automatic. The second pile is one-off slips that share a cause, such as answering before eliminating options. Those are fixed not by more content but by a small rule you carry into your next session, the same way you would rehearse a plan for questions you can't solve quickly.
Then close the loop. When you sit your next timed set, watch specifically for the errors your log predicted, and mark in the log whether you caught them. An entry that stops recurring can be retired; one that keeps returning has earned a larger place in your study week. Over a few weeks the document shrinks in the areas you have mastered and concentrates on the few that genuinely need attention — which is exactly what a good revision plan should do.
Keep it sustainable
The only error log that helps is the one you keep. Log every practice session while the questions are fresh, resist the urge to make it pretty, and review it on a fixed day so it becomes a habit rather than a chore. A free timed mock is a good place to generate honest entries, because mistakes made under real time pressure are the ones most worth recording. And if you are still mapping out what the exam involves, our overview of what the dMAT is sets the wider context.
You cannot stop making mistakes in preparation — that is what preparation is for. What you can do is refuse to waste them. Write each one down, look for the pattern, and let your own errors quietly build the study plan you actually need.
