Acing QR (UCAT) from a 900 Scorer

The first time I sat a UCAT Quantitative Reasoning subtest, I got 480.

I genuinely looked at the maths in front of me and could not figure out what was going on. Question after question I looked at and felt nothing but absolute defeat. Disappointment in myself. Fear of the road ahead.

For months, I was barely scraping 600s. I'd do test after test, watch my scores stay flat, and eventually just make peace with QR being my fumble.

Yet on exam day, I scored a perfect 900.

I want to be really clear about what didn't happen. I didn't have some breakthrough about being secretly good at maths. I didn't suddenly get faster at mental arithmetic. The content stayed the same (it's all Year 8 to 9 level maths) and you almost certainly already know it. What changed was how I was practising, how I approached each question, and how I held my nerve during the test.

This blog is the playbook. If you're sitting in the 500s or 600s right now and your scores aren't moving, this is probably why.

Most improvement comes close to the end.

Stop spamming tests. Start reviewing them.

For the main 4 months I practiced for the UCAT, my QR scores wouldn’t increase. Whether I didn’t practice for days, or did bouts of test after test:

My score barely moved.

This is the single most common mistake UCAT students make. We treat practice tests like the practice itself, as if the act of doing them is what improves you. It isn't. The doing is just where you generate data. The improvement comes from what you do with that data afterwards.

If you're doing two practice tests a day and not reviewing either of them properly, you're not practising. You're just generating bad scores faster. You’re repeating a corrupted formula expecting new results.

Real reviewing means going through each question and asking yourself a series of harder questions than "did I get it right?":

• Did I get it right because I used the right method, or did I just guess and get lucky?
• Did I get it wrong because I didn't know the maths, or because of a strategy problem?
• Did I run out of time on it? If so, why?
• Did I miss a small note or detail in the stem? What was it, and how would I catch it next time?
• Did I follow the strategy I'd been practising, or did I revert to old habits?

The rule I'd give myself was: spend at least as long reviewing a test as you spent doing it. Sometimes longer. Reviewing is slower than testing, not faster. That's the whole point.

The other tool that turned reviewing into actual improvement was an error log. Every question I got wrong, I'd categorise, by topic (percentages, ratios, rates, etc.) and by type of mistake (misread the stem, calculation error, ran out of time, didn't know the method). Within a week, patterns showed up that I genuinely hadn't seen before. I was burning the most time on table questions. I was misreading stems specifically when there were multiple tables on screen. I was spending too long on the first few stems of questions and running out of time before even getting close to the end.

Once I could see the patterns, I could target them. I would then do a practise where my focus would simply be to read the stem carefully. Review. Note down improvements. Note down errors. Form a new focus. Focus on skipping questions that were taking too long. Review. Note down improvements. Repeat. That's what error logs do; they take the vague feeling of "I'm bad at QR" and replace it with specific, fixable problems.

The error log doesn't have to be fancy. A Google Doc with three columns is enough.

The skipping reflex (and why it took me weeks to learn)

Of all the things I changed in those last three weeks, the single biggest one was learning to skip properly.

QR isn't really a maths test. It's a time test wearing a maths costume. You've got a tiny window per question, and the test is specifically designed so that some questions will burn through your time if you let them. The students who score well aren't necessarily faster at maths, they're better at recognising, in the first 10 seconds, when a question isn't worth their time right now.

The problem is that skipping feels awful. You feel like you're giving up. You'll convince yourself you're 30 seconds away from the answer, and then 90 seconds later you're still stuck on it with a sinking feeling in your chest.

So I had to actively train the skipping reflex. The rule I gave myself: if I wasn't making concrete progress within 10–15 seconds, flag it and move on. Not "I'll come back if I have time." Move on immediately, without negotiation.

Two things happened when I started doing this consistently. First, I started actually finishing the section, which meant I was attempting easier questions later in the test that I'd previously been missing entirely. Second, when I came back to the flagged questions at the end, I'd often see them with completely fresh eyes. Sometimes a different question I'd done in between had even given me a clue about how to approach it.

That second part surprised me. Coming back to a question after a break genuinely changes how you see it. The trick is being willing to leave it in the first place.

How to approach every question: read → plan → execute

Once skipping was working, the next shift was changing how I approached the questions I did attempt.

For every single question, in this order:

1. Read: figure out exactly what the question is asking
2. Plan: work out the steps you'll need to take to answer it
3. Execute: do the maths

Most students collapse all three steps into one. They start reading the stem from top to bottom, start calculating things they see, and only realise halfway through what's actually being asked. By that point they've burnt time on data they didn't need.

The "plan" step is the easiest of the three. You read the question and go, "okay, I need to find X, which means I need Y and Z from the stem, and then I divide." Done. Now you execute.

The other thing this framework does is force you to look at the question first, before the stem. The data table might have eight columns; you might only need two of them. Reading the question first means you process only the data that matters.

The other thing to watch for at the read stage is what I call "trip-up notes" small details, usually at the bottom of the stem or in tiny text, that change how you're supposed to interpret the data. Things like "note that this figure refers only to full-time employees" or "all amounts are in thousands." Miss one of these and the whole question collapses, no matter how good your maths was. A quick skim for these before you start calculating saves more marks than people realise.

Eyeballing is a skill, not a shortcut

When you're executing, the other thing you want in your toolkit is eyeballing.

QR gives you four answer options. That's a lot of information, and most students treat it like a formality, they do the full calculation and then pick the matching option. The high scorers don't. They use the answer options to narrow down the work they need to do.

You glance at the question, estimate roughly what the answer should be (around 25, say), and look at the options. If three of them are 60, 10, and 145, you don't need to calculate the exact value, you already know it's the fourth one. You've just saved 45 seconds.

Eyeballing only works if you're genuinely good at mental maths, though. So train it. There are free apps and websites (Math Trainer is a popular one) where you can drill mental arithmetic for 10 minutes a day. Get fast at percentages, ratios, two-digit multiplication, and rounding. It compounds quickly.

Other eyeballing techniques worth practising: looking at the final digit of a calculation to eliminate wrong answers. Reading graph and table trends rather than specific values. Spotting when an answer can't possibly be in a certain range based on the data. This is efficiency.

QR triggers: the 80% to 100% upgrade

A "QR trigger" is a small mental check you run when you see a specific type of question. A checklist for the silly mistakes students consistently make on that question type. I built mine up over weeks of reviewing my error log, and it ended up looking something like this:

• Geometry questions → check the units (am I working in cm or m?)
• Money questions → check the currency (especially in multi-country questions)
• Shopping list questions → check for discounts, surcharges, or GST
• Percentage change questions → check I haven't swapped the initial and final values
• Speed, distance, time → check I'm using the right formula and right units
• Rounding questions → check whether the context requires rounding up, down, or normally

The reason these matter so much is that they're not "you didn't know the maths" mistakes. They're "you knew the maths but missed a detail" mistakes. Those are the ones that separate 80% accuracy from 100% accuracy. They're also the easiest to fix, because once you've spotted the pattern, it just takes a 2-second check. Build your own triggers list.

Notice how the stem provides background information and the table is in thousands per hectare; check units and set up for table questions.

Set up for the exam, not your bedroom

There's one more change that I think is the most underrated piece of UCAT advice I can give you: practise in the conditions you're actually going to be tested in.

The single biggest version of this is the calculator. The UCAT calculator is a number-pad calculator that you operate with a separate keyboard. If you're doing all your practice with your phone calculator or clicking buttons on your laptop trackpad, you're going to walk into the exam and lose 30–60 seconds per question fumbling with an unfamiliar layout. By the end of the test, that's minutes you can't get back.

If you don't already have a USB number-pad keyboard, buy one. It's the cheapest score boost you can give yourself.

The broader principle is bigger than calculators, though. Practise in conditions as close to exam day as you possibly can. Same chair, same screen, same time pressure, ideally same time of day. The thing that trips up genuinely capable students on exam day isn't the maths. It's the unfamiliar environment. The nerves. The small differences from how they'd been practising. The more of those variables you can eliminate beforehand, the less they can hurt you on the day.

Momentum is the invisible variable

The last piece:

QR is a test where, once you lose momentum, it is genuinely very hard to get it back. You hit a question that's too hard, you spend too long on it, you start panicking about the clock, you get the next one wrong because you're rushed, you panic harder, and suddenly the whole subtest has gone sideways.

The skipping reflex is your single best defence against this. But there are a few other things that protect momentum:

• Check your answers as you go, not at the end. Give each question 2 seconds of sanity-checking before moving on
• Don't get complacent if you're ahead of time. Students who realise they're ahead often unconsciously slow down and start making careless mistakes
• Build buffer time deliberately. Aim to finish a couple of minutes early. That buffer gives you space to come back to flagged questions without panicking
• Recognise when you're tilting. If you feel your heart rate spike or your reading slow down, take a 5-second breath. That tiny reset is worth way more than the time it costs

The difference between performing at your potential and underperforming on exam day is almost entirely down to the mindset you walk in with.

Protecting your momentum is how you protect your mindset.

What to actually do this week

If you've read this far and want to do something tonight:

• Take the most recent practice test you've done and review it properly. Block out two hours
• Start an error log if you don't already have one (a Google Doc is fine, don't overcomplicate it)
• Buy or borrow a USB number-pad keyboard and use it for every practice test from now on
• Try the read → plan → execute framework on your next 10 questions
• Spend 10 minutes a day on Math Trainer or similar for the next two weeks

Don't try to do all of these at once. Pick one. The wins compound faster than you'd expect.

One last thing

QR genuinely is one of the most improvable subtests in the UCAT. It's not a content problem , it's an execution problem. And execution problems are the ones that respond best to deliberate practice.

If you're sitting in the 500s or 600s right now and feeling like your score is stuck, I want to be honest with you: three weeks of properly applied work can move your score more than four months of unfocused practice. I lived it.

Keep an eye on out for more insights from our experienced HBE team.