How it works

What the platform does, in what order, and why some questions will feel too easy or too hard.

The starting diagnostic

You begin with a short pass: one question per competency of the blueprint, twenty at most, at the exam's registers — facts to know, cases to sort, arbitrations between two defensible courses of action. Nobody starts from the same place: some questions will feel easy, others hard, and that is expected. Answer without looking things up. No verdict is given question by question; the review comes at the end, and it seeds your competency map.

Today's sprint

Each day, the platform chooses what you work on: first the competencies under their floor, then those whose measure is aging, then those where the work pays off most. You do not choose the question; you choose your conditions — timer shown or hidden, pace, block size. After every answer, you read why each option is right or tempting, and the probable cause of a mistake: inattention, an unchecked calculation, a knowledge gap, or time lost on an answer that was right. At the Discovery tier, ten questions a day.

Reinforcing a competency

Your map shows the twenty competencies of the blueprint with the level of each. On a line never attempted, “Explore”; on the others, “Reinforce”: the session that opens draws only from that competency, and it counts in your map and your index like a sprint. The platform proposes, you can target; what does not change is the verdict: time is measured, and the targets per domain remain those of the exam. The questions of the mock exams remain a reserve apart, never served in training, focused or not.

Reflexes

A gap gets filled; a reflex gets worked on. Some questions of the exam ask for no reasoning: they ask for a known answer. From your first day, the Réflexes series serves 8 of them, drawn from the recall questions of the practice pool, across every competency, timer visible — those of the competencies whose foundations are not yet secured first, then the least seen. It refines itself with your answers: the recall that cost you — wrong, or right but over budget — goes first; and when the same trap comes back at least 3 times in your last 100 answers — a confused unit, a partial reading, a calculation right but over budget — the series names it and alternates it with recall. On every mistake, the review names the distractor's trap, how often it came back and the move that avoids it; a right answer over budget is said to be known, not automatic yet. The series is proposed, never imposed, and counts like a sprint: mastery, the map and the index read it like the others.

Why the questions climb in register

A recall question asks for a fact; an application question asks you to sort a case; a judgment question leaves two defensible options and turns on an arbitration. The exam mixes all three, and you meet them in the same proportions from your very first question. A competency whose foundations are validated no longer comes back to recall: what is secured is not re-taught. Getting it wrong is part of the training — that is where the review does its work.

The readiness index

Always visible, recomputed after every session. It crosses the coverage of the blueprint, the mock exams, stability over time and time management, and it shows three zones: building, progressing, confidence zone. Never a percentage, never a promise. One good result is not enough; a weak domain is not offset by a strong one. Until the index is calibrated on the real results of the first cohorts, it presents itself as what it is: an estimate.

The mock exams

Two hundred questions, under real conditions: timer, free navigation, « review later » flags, no correction before the end. Their reserve is sealed — these questions never appear in training, or the mock exam would measure nothing — and it does not renew: the index opens the door when the map is ready, and otherwise names what is left to work on.

Pioneer version

The service evolves with you. Every question can be reported in one gesture, from the screen where the doubt is born; you see what follows. And if something feels too easy or too hard, tell us: hello@rxsprint.ca.