How to Track UCAT Question Bank Progress

Create the minimum useful record

Every entry needs a date, resource name, subtest, question range or test label, raw outcome and time used. For Verbal Reasoning and Quantitative Reasoning, record questions correct and attempted. For Decision Making, record raw marks earned and available because some multiple-statement questions allow partial credit. For Situational Judgement, record full-credit, partial-credit and incorrect responses, or raw marks earned and available if the official feedback provides them. Add whether the attempt was untimed, timed, paused or completed with an approved access format. Record support, such as a tutorial, note or repeated set. These fields let you compare like with like without hiding partial credit.

Add one brief learning note in your own words, such as “confused could be true with must be true”. Do not paste questions, passages, diagrams or official rationales into the log.

Build a baseline without overinterpreting it

After completing the official tutorials, attempt a small representative set from each current subtest. Use similar conditions and record them. This is a starting sample, not a prediction of test-day performance. Differences may reflect question mix, unfamiliar tools, tiny sample sizes or ordinary variation. The baseline is useful because it exposes processes that deserve attention.

Write one process target per subtest. For Verbal Reasoning, it might be separating passage evidence from outside knowledge. For Decision Making, it could be diagramming conditions before testing conclusions. For Quantitative Reasoning, it might be identifying the requested unit before calculating. For Situational Judgement, it could be distinguishing the importance of an action from its appropriateness. Check the official tutorials for the distinctions and question types used in the current test.

Track what matters in each subtest

One overall percentage hides both different decisions and different marking rules. In Verbal Reasoning, separate passage-location errors, unsupported inferences and time lost on difficult text. In Decision Making, preserve raw partial marks and tag the question type and logical step that failed. In Quantitative Reasoning, distinguish setup, arithmetic, units, calculator entry and time. In Situational Judgement, preserve partial credit and record whether you misunderstood the scenario, the relevant professional principle or the response scale.

Keep five to eight consistent tags and prioritise the first error. Mark guessed or uncertain correct answers so the dashboard does not treat them as secure reasoning.

Read timing data carefully

The current standard subtests are separately timed, and the standard test is just under two hours. Use the exact current timings from the official format page when rehearsing. For shorter sets, record elapsed time but avoid pretending that four questions reproduce a full section. Passage length, question type, fatigue and transitions all affect pace.

Note where time went and test skip-and-return decisions in official material. Faster is useful only when reasoning remains sound. If you have approved access arrangements, track against the format you will sit.

• Label sets as unseen, repeated or partly familiar.
• Record pauses and interruptions rather than hiding them.
• Separate reading or setup time from tool-use delays where possible.
• Compare similar question types before drawing a speed conclusion.
• Use the current official timing or approved access format for rehearsals.

Turn every entry into a review loop

A log that only stores percentages becomes a diary. After each set, select one or two errors with the greatest reach. Check the official rationale, restate the correct reasoning without copying it and complete a short matched practice later. Add a review date. When the date arrives, use different questions. Mark the skill secure only when it works after a delay and under the relevant timing.

Use four statuses: open, corrected, retry due and secure. “Corrected” means you understand the explanation now; it does not mean the process will transfer. “Retry due” makes the unfinished work visible. “Secure” should require successful independent use, ideally on more than one spaced attempt. If a mistake returns, reopen it without treating the earlier work as wasted. The recurrence tells you the method needs a stronger cue, a clearer representation or more varied practice.

1. Diagnose

   Name the earliest decision that caused the wrong or uncertain answer.

2. Correct

   Use the official explanation and restate the method in your own words.

3. Schedule

   Choose a date and question type for an independent retry.

4. Retest

   Use different official material and record the new conditions.

5. Secure or reopen

   Extend the interval after success or change the repair after recurrence.

Run a ten-minute weekly review

Once a week, filter by subtest and compare similar attempts. Which error cause appeared most often? Which process improved under comparable timing? Which official resources remain unseen? Which retries are due? Choose no more than two main targets for the next week and keep all four current subtests in rotation. This protects the plan from following whichever result feels most dramatic.

Look for interactions, such as faster Quantitative Reasoning alongside more calculator errors, or Verbal Reasoning accuracy falling only late in a long block. Write the weekly decision beside the evidence.

Use the progress tracker without giving away your privacy

The free UCAT Progress Tracker is designed for this workflow. It stores entries in your current browser, does not need a name, school, email or account, and can export your own data. Use a simple label for each official resource rather than entering personal information. If you share a device, export a backup when needed and erase the local data after saving it somewhere you control.

The tracker is not connected to the UCAT Consortium and cannot predict a score. Keep registration, booking, access arrangements and results in official systems. Export and check a backup before changing device or resetting the browser.

Know what your tracker cannot tell you

An improving raw practice trend does not guarantee the same live result. Sets differ, repeated questions become familiar, and the live cognitive scores are scaled. Small samples can swing sharply. Use trends within the same section and marking model to choose training tasks, not to make claims about admissions outcomes. Universities use the UCAT in different ways and can change their processes, so check each institution's official information separately when making application decisions.

Do not chase a smooth graph with easy repeats. Tracking has done its job when it shows what to practise next, why it is the priority and what evidence will demonstrate change.

• Do not convert raw marks into a promised scaled score.
• Do not compare repeated and unseen sets as if they were equivalent.
• Do not combine Situational Judgement with the cognitive sections into one percentage.
• Do not infer university selection outcomes from a practice dashboard.
• Do use the record to choose, review and retest specific processes.