The method every high-performance field uses except school

When a pilot has a rough landing, there's a debrief: what happened, why, what changes next flight. When a footballer loses a contest, the team watches the film and names the exact moment it went wrong. When a med student misses a question on a qbank, the answer doesn't just get read — it gets logged, tagged, and scheduled for re-test, because their exams are too high-stakes to make the same mistake twice.

Now compare what happens when a student gets a practice question wrong: they get a mark, feel bad for four seconds, and move on. The single most informative event in their study session — a demonstrated, specific gap between what they think they know and what they can actually do — is thrown away. Then, weeks later, the same gap costs them marks in the real exam and they call it bad luck.

The error log study method is just the debrief, imported into studying. Every field that performs under pressure converged on it independently because it works.

The loop

The method is a four-step loop, and the loop matters more than any individual step:

  • Capture. The moment you get something wrong — past paper, question bank, homework, a step in your working — record it. The question, your answer, the right answer.
  • Diagnose. One honest sentence on why. Not "I'm bad at integration" — that's a feeling, not a diagnosis. "Chose integration by parts when substitution applied" is a diagnosis; it tells you what to practise.
  • File. The entry goes into one consistent place, categorised, per subject. Scattered screenshots in your camera roll do not count as a log.
  • Re-test. On a schedule, re-attempt old entries cold. Right without help → resolved. Wrong again → it stays in rotation, now flagged as a real weakness.

The full mechanics — entry format, the three mistake categories, the weekly routine — are in our pillar guide: how to keep an error log for studying.

Why med students specifically

Medical entrance and licensing exams (UCAT, GAMSAT, the med school qbank grind) have two properties that make the error log non-optional: the syllabus is too large to revise uniformly, and the questions are written to punish predictable reasoning errors. Under those conditions, the only rational allocation of study time is toward your demonstrated weaknesses — and the log is the only reliable record of what those are.

Here's the thing: HSC, VCE, SAT and A-Level exams have exactly the same two properties, just at smaller scale. A Year 12 student six weeks out from trials cannot re-revise everything. The students who feel calm in that window are the ones holding a personal list of every question type that has ever beaten them — because that list is the revision plan. Everyone else is re-reading notes and hoping, which is its own failure mode (see why you blank on questions you've revised).

Why school never taught you this

School grades mistakes; it doesn't process them. A returned test tells you that you lost marks, rarely why in a form you can act on, and never follows up to check the gap actually closed. The feedback loop is left as an exercise for the student — and since reviewing your own failures is emotionally unpleasant, almost nobody volunteers for it.

That's also exactly why it works. Reviewing mistakes is the highest-value, least-crowded study activity available: your competition finds it uncomfortable, so they don't do it. The marks are sitting there. The argument for treating wrong answers as your primary study asset is laid out in your mistakes are worth more than your notes.

Running the loop without the clerical work

The honest weakness of the method is that steps one and three are chores. Capturing a question, writing the diagnosis, filing it under the right topic, remembering which entries are due for re-test — none of it is hard, all of it is friction, and friction is what kills study systems by week three. You can run it manually with a template, and plenty of students do.

errorboard exists to automate the chore layer: it captures the mistake where you're working (screen, handwriting, or a photo of paper), writes the diagnosis, categorises it, files it into a per-topic automatic error log, and re-quizzes you on old entries until they're resolved. The loop runs itself; you just study. It's free to start.

Either way, the method is the point. Debrief your failures like every other high-performance field does, and the same mistake stops costing you twice.