Quest Ladder
TeachFORGE.ai
Quest Ladder / Sprint mode
Sprint mode
Pace and energy, for the recall that has to become automatic.
Fluency is a different thing from understanding. Train it differently.
What it does
Sprint is fast rounds against a countdown. It is the mode for fluency — number bonds, vocabulary, formulas, anything that needs to be fast rather than merely correct.
It is deliberately unlike the rest of the Quest Ladder. There is no room for a hint, a learning block or a reflective pause at this speed, and trying to have both produces something that does neither well.
The settings
| Setting | What it does |
|---|---|
| Lives (default 3) | How many wrong answers before the run ends. |
| Warm-up questions | Easy ones first, before the clock matters. |
| Questions per sprint | The length of a run. |
| Question source | Topic (ladder / selected types), or Interleaved (mix earlier topics). |
| Class leaderboard | Off, Named (class alias / token), or Anonymous. |
| Adaptive topic weighting from mastery gaps | Draws more from what this learner is weakest on. |
| Category countdown overrides (seconds) | Different time limits for different kinds of question. |
The leaderboard decision
Three options, and the middle one uses the class alias or token rather than a name, because a class holds handles, not names.
Named leaderboards motivate the learners who are already fast and discourage the ones who are not, which are usually the learners the sprint was for. Anonymous keeps the energy of a shared scoreboard without putting the same three names at the bottom every week. Off is the right answer more often than people expect.
Adaptive weighting
Adaptive topic weighting from mastery gaps makes the sprint personal: it draws more heavily from the topics this learner is weakest on, using the same mastery data as the rest of the platform.
It is what turns a sprint from a general drill into targeted practice, and it costs nothing to switch on. It needs a named learner to have gaps to read.
Category timing
Category countdown overrides (seconds) exists because not all fast questions are equally fast. A single-digit sum and a two-step conversion do not deserve the same countdown, and one shared limit makes one of them trivial and the other unfair.
Also worth noting: a sprint's pressure comes from its own countdown, so the question types' own time bands are usually best left out of the grade for this delivery.