Every question in a Kairos mock is timed individually, not just
the section as a whole. Each answer is logged as solved,
flagged for review, or skipped, and the time spent on it is
recorded against that specific item, not just a section
average. An answer submitted with almost no time left is
treated differently from one submitted with time to spare,
which is how the app builds a picture of guess discipline
rather than only correctness.
Sprint mocks and full mocks run in real UCAT exam order: Verbal
Reasoning, Decision Making, Quantitative Reasoning, Situational
Judgement, each with its own live countdown, flag-and-review,
and, for Decision Making and Quantitative Reasoning, an
on-screen calculator. Because timing is captured per question
across an entire paper, Kairos can plot how accuracy and pace
change from the first item to the last, which is where fatigue
actually shows up.
The post-exam report and the readiness signal are built from
that same data: marks lost to time versus marks lost to
rushing, a pacing curve across the paper, and a next action
instead of a single predicted score. Readiness recalculates
after every mock rather than sitting fixed from onboarding, so
it moves as practice actually changes. Daily drills pull from
the same history to target whichever section and skill
currently costs the most marks. Practice history, drill and
mock results, the readiness signal, and exam date settings are
stored locally on the device and sync across a candidate's own
Apple devices through their private iCloud when enabled.
