Most candidates have a method for a passage and some method for a chart, and then nothing in particular for a diagram. A diagram does not have a paragraph you can reread or an axis you can trace from, so it gets glanced at and interpreted on instinct. That is a mistake worth fixing, because a diagram is not decoration around a question. It is a dense piece of text written in shapes, and every box, arrow and label in it is a claim the question can test. The syllabus lists reading a diagram alongside tables and graphs as part of the General Academic Module. This guide is about reading one deliberately rather than by feel.
Treat it as text written in shapes
A paragraph explaining a process might take a hundred words. A diagram makes the same claims in a dozen boxes and a few arrows, which is efficient for the writer and demanding for the reader, because nothing is repeated and nothing is explained twice. If you misread one arrow, there is no later sentence to correct you.
So begin the way you would begin a chart, with the frame rather than the content. Read the title or caption first, then any key or legend, then every label. Ask what kind of diagram you are looking at before you ask what it says. Most diagrams fall into a few broad families, each with its own grammar:
- Sequences and processes, where arrows mean "then" and the order of steps is the point.
- Cause-and-effect or flow diagrams, where arrows mean "leads to", "produces" or "moves into", and the direction carries the logic.
- Structures and hierarchies, where position and lines show what contains or belongs to what.
- Cycles, where the last step feeds back into the first and there is no real starting point.
The same arrow means different things in each family. Deciding which family you are in, before reading the detail, prevents the most common misreading: treating a sequence as a causal chain, or a feedback loop as a straight line.
Read the connections, not just the boxes
Under time pressure the eye goes to the boxes, because that is where the words are. But the boxes are usually the easy part. The question tends to live in the connections, which is where the diagram makes its actual claims.
For every arrow that matters to the question, check three things. First, its direction: which end is the source and which is the target. Second, its label, if it has one, because "inhibits" and "increases" look identical when the arrow is unlabelled in your memory. Third, whether a line is an arrow at all, since a plain connecting line often shows association or membership rather than flow. If the diagram uses different line styles, such as solid and dashed, check the key for what the difference means instead of guessing.
Then watch for what is absent. If there is no arrow between two boxes, the diagram is not claiming any direct relationship between them, even if your general knowledge says there should be one. This is the same trap described in our guide to passages outside your field: what you already know about a subject is a liability whenever it fills a gap the material deliberately left open. Answer from what is drawn.
Let the question choose the path
Once you have the frame, read the question and decide what it is asking you to do with the diagram before you go back into it. Diagram questions tend to ask a small number of things:
- Trace a path. What happens after a given step, or what must happen before it? Put your finger, or your cursor, on the starting box and follow the arrows one at a time.
- Find a consequence. If one element changed or were removed, what else would be affected? Follow every arrow leaving that element, then the arrows leaving those, and stop where the chain stops.
- Identify a role. Which element is an input, an output, or an intermediate step? Count the arrows going in and coming out.
- Check a statement against the diagram. Does an answer option describe something the diagram actually shows, or something that merely sounds plausible?
That last type is where careful readers gain the most. An option can be true in the real world and still be wrong, because the diagram does not support it. The discipline is the same one our guide to research summary passages applies to studies: separate what the material establishes from what it only suggests.
Use rough work to slow the diagram down
A complicated diagram is easier to work with once you have reduced it to the part the question needs. A quick sketch on your scratch paper of just the three or four relevant boxes and arrows takes seconds and removes the visual noise. If the question asks about a chain of effects, write it as a single line, A → B → C, and check each link against the original before choosing an answer. Our note on rough work covers how to keep that sketching brief and legible.
When a diagram comes with a passage or a table, decide which one is the primary source for the question. Often the diagram summarises the text, and the precise wording sits in the text. If they appear to disagree, reread both carefully before you assume either is wrong. The difference is usually a detail you skipped in one of them.
Practising without a stock of exam diagrams
There is no large supply of dMAT-style diagram questions, and you do not need one. Diagrams are everywhere in academic writing: textbook process figures, flowcharts in reports, organisational charts, cycles in science explainers. Take one from a field you know nothing about, cover the caption, and describe it aloud in plain sentences. Then write two questions about it, one that traces a path and one that tests a tempting but unsupported statement, and answer them a day later.
Alongside that, work through the official model tasks, which are the best guide to how the real material presents information. Our guide to preparing for the General Academic Module puts diagram practice in the context of the module's other skills, and our guide to graphs and tables covers the quantitative side. If you want to try mixed questions under time, the free practice test is a reasonable place to start.
A diagram rewards the reader who slows down for the frame and the arrows, then speeds up once the question has narrowed the search. Read it as text, follow only the path you were asked about, and let the drawing, not your expectations, decide the answer. For the exact scope of the module, check the official sources rather than any summary, including this one.
