Mistake Log
Record what went wrong, understand why it happened, and turn errors into targeted revision material instead of just feeling bad about them.
1What Mistake Log is for
Mistakes feel terrible, especially the ones you keep repeating. Most people just move on and hope. Mistake Log does the opposite: every error becomes a small piece of revision you can actually learn from.
Each entry captures what happened, what the right thinking was, and what kind of gap it points to. Over time the patterns surface, like calculation slips under time pressure, or a concept you only thought you knew.
Log three errors that all turn out to be “misread the question”, and the fix becomes obvious: slow down and underline what's actually being asked.
2How to log a mistake
Tap the plus button and fill in a short form.
- Add the subject and the question or context.
- Say what you did wrong, then write the correction, what you should have done.
- Pick an error type and a Bloom level, and save.
The correction field matters most. Writing out the right approach, not just naming the wrong one, is where the learning actually happens.
3Reviewing mistakes
Your log isn't a list of regrets. It's revision material. Search by subject or wording, and filter to separate what still needs work from what you've fixed.
When you review one, read the correction first, then ask: what cue would have caught this in time? That question trains you to spot the warning signs before the mistake repeats.
Several errors clustering on one topic is a signal, that gap is worth a full Focus session, a few cards, or a quick check with Spark.
4Using Spark with mistakes
Tap Spark on any mistake and the AI reads the pattern for you. It names the likely root cause, suggests a self-check question for next time, and can recommend a targeted exercise, like a tutor pointing out why something keeps happening and what to do about it.
Spark needs sign-in and a connection. Offline, your mistakes are still safely stored, just come back to Spark when you reconnect.