A question type in Quantitative Reasoning

UCAT Line Graphs: how to solve them

UCAT 2027·6 min read·Source: UCAT ANZ test format
Direct answerUCAT 2027

A line graph question gives you one or more lines tracking a value over time, against a labelled scale, and asks you to read a point, a change, or a trend. It’s a Quantitative Reasoning question type, answered as single-best-answer with an on-screen calculator. The skill it tests is reading each point’s height accurately off the scale for the right line, and knowing when the question wants a value (a height) versus a change (the slope between two points).

Reviewed by the MedPath UCAT team · June 2026
The basics

What is a line graph question?

You get a short framing sentence, then a line graph, then a set of questions that read from it. Each question is single-best-answer with five options, you have a basic on-screen calculator, and you’re working to roughly 43 seconds per question across the section.

Line graphs come in a few shapes: a single line tracking one value over time, several lines on one set of axes (like this one, two), a line with a second value axis on the right, or a line overlaid on a set of bars. The shape changes how many series you compare, but it never changes the discipline: read each point’s height against the scale, for the line the question names, and decide whether you want the height or the change between heights.

The arithmetic on a line graph almost never beats you. The numbers are usually clean and the calculator does the rest. What beats you is the read: a point lined up with the wrong gridline, the wrong line read where two cross, or a trend mistaken for a value (picking where the line is highest when the question asked where it climbed the most). Get fluent at reading each part of a line graph and most of the traps further down this page stop happening.

Tab through the parts of a line graph. Each one highlights where it lives, and what to check before you trust a number.

Anatomy of a line graph
FramingA regional clinic recorded how many patients booked an appointment through its new online portal each month from January to June, split between new patients and returning patients.
Online bookings050100150200JanFebMarAprMayJun
New patients
Returning patients
The framing line

One sentence above the graph tells you what it measures and how it is split. Read it first: here it sets the scope (six months, January to June), the unit (online bookings), and the two series the lines are split into (new and returning patients).

The parts to read, in order: the framing line (what it measures, and how the lines are split), the axes and scale (the unit and the gridlines on the value axis, the months on the time axis), the plotted lines (each one a patient type tracked month by month, whose direction is the trend), the points (each a real reading you take to the gridline, with the connecting line a guide rather than data), and the legend (which colour is which patient type, the only thing telling the two lines apart where they cross). The worked example below solves on the same graph.

Example

A worked example

Same graph, one sub-question. Every wrong option is a number you can reach from the graph by one specific slip, so read each new-patient point to its gridline, pin the colour, then take the rise across each gap, and the four lookalikes fall away.

Try it yourself
Quantitative Reasoning · Line Graphs
FramingA regional clinic recorded how many patients booked an appointment through its new online portal each month from January to June, split between new patients and returning patients.
Online bookings050100150200JanFebMarAprMayJun
New patients
Returning patients

Between which two consecutive months did new-patient bookings rise the most?

The traps

Common mistakes

The wrong answers on a line set are almost never bad arithmetic: they’re a number you can see, reached by one wrong move. And most of these slips aren’t specific to lines. The same wrong-base or wrong-line error bites on tables and bar charts too, because the trap lives in the operation, not the picture. So these guides are shared across Quantitative Reasoning; each links to a short worked example.

Reading a trend as a valueIn the example
The signature line-graph error. Picking the segment that reaches the highest point when the question asked where the line rose the most. The rise is the slope of a segment, not the height it ends at. This is the trap the worked example above is built around (option B: May to June ends at the peak but only climbs 25).
Reading the wrong lineIn the example
Following the wrong series, usually where two lines cross or run close together. Option D above is this trap, reading the returning line’s rise as if it were the new line’s.
Misreading the axis scale
A point read to the wrong gridline, usually jumping to the nearest major line and skipping the minor one between. A point sitting between 100 and 150 is on the 125 minor gridline, not the 150 above it.
Reading between the points
Treating the connecting line as data. Only the plotted points are real readings; the line between them is a guide to the trend, so do not quote a value for a month that was not measured unless the question asks you to estimate one.
Comparing against the wrong baseline
When a question asks for a percentage change over time, the base is the earlier value, not the later one or some other point on the line. Anchor the percentage to the starting figure before you divide.
Confusing percentage points with a percentage
A line rising from 40 to 50 is up 10 of whatever the unit is, and up 25%, but those are different statements about different things, and both will be on offer as options.
Adding percentages instead of compounding them
A value that rises 10% one month then 10% the next is up 21% overall, not 20%. Successive changes along a line multiply, they don’t add.
Slipping between a fraction and a percentage
“A quarter of the bookings” and “25%” are the same value, but a working in fractions that never converts at the end lands one step short, and an option will be waiting at that half-finished number.

Shared across all five QR types. Trap guides are being published; links open as each goes live.

How to approach it

A reliable method

1
Read the axes and the scale before any point.
Note what the value axis measures and its unit, what the horizontal axis tracks (usually time), where the major gridlines fall, and whether there are minor gridlines between them. Most line-graph traps are scale slips, and reading the scale up front removes them.
2
Match the colour to the line on the legend.
Confirm which line is which before you read, especially where two lines cross or run close, so you do not read the returning line when the question named new patients.
3
Decide whether the question wants a value or a change.
A value is one point’s height, read to its gridline. A change is the rise or fall between two points, the slope of a segment. For “biggest rise” or “steepest fall,” read the steepness of each segment, not where the line is highest.
4
Identify the operation and its base, then compute and round last.
Name the move (a difference, a percentage change over time, a share) and name what any percentage is taken of. Carry full precision through and round only the final answer.
How to practise

Practising line graphs

Line graphs reward one repeatable habit: read the scale, pin the line, then ask whether you want a height or a slope. The fastest progress comes from doing enough of them that a steep early climb stops hiding behind a line that drifts up to a tidy-looking peak.

MedPath drills line graphs trap by trap, with the working revealed step by step for each, and steers your practice toward the ones you keep getting wrong.

Practise adaptively

Practise line graphs adaptively.

MedPath drills line graphs trap by trap, with the working revealed step by step, and steers practice toward the trend-as-value and wrong-line slips you keep falling for.

Quantitative Reasoning · question type 3 of 5
FAQ

Common questions

Do I get a calculator?+

Yes. Quantitative Reasoning and Decision Making both give you a simple on-screen calculator; Verbal Reasoning and Situational Judgement do not. The calculator handles the arithmetic, so the work is reading the right point on the right line and choosing the right operation.

How are line graph questions scored?+

As part of Quantitative Reasoning’s 300–900 scaled score, which contributes to your total cognitive score (900–2700). Each question is single-best-answer, marked right or wrong, with no penalty for a wrong guess, so never leave one blank.

What if the question asks about a trend rather than a single value?+

Read the slope of the segment, not the height. A steep segment is a big change, a flat one is little change. “Rose the most” means the steepest single climb, not the point where the line is highest, and “fell the most” means the steepest drop. The line between two plotted points is a guide to the trend, so quote a value only for a month that was actually measured.

What’s the most common mistake?+

Confusing a trend with a value: picking where the line is highest when the question asked where it rose the most, or reading the wrong line where two cross. Reading the scale first, pinning the colour, and asking “do I want a height or a change?” before you calculate is worth drilling until it’s automatic.

Part of Quantitative Reasoning in The Complete UCAT Guide. Other Quantitative Reasoning types: Data Tables · Bar Charts · Pie Charts · Formulae & Figures.
Practise adaptively

Read the scale, pin the line, then ask: a height or a slope?

Practise line graphs on the full adaptive bank, trap by trap, scored, with a predicted band.

Join the waitlist See how it works