Reading a class's mock results without drowning in data

Score a mock for twenty students and you get a wall of data: totals, section scores, per-question results, timing. It's easy to stare at all of it, feel vaguely informed, and change nothing. The point of the data is to produce a small number of teaching decisions. Here's a routine that gets you there fast.

Start with the class, not the student

Before you open any individual report, look at the group. Which questions did most of the class miss? A question half the room got wrong is usually pointing at a shared gap, and one lesson fixes it for everyone at once. This is the highest-leverage thing in the whole dataset, and it's invisible if you go student by student first.

Sort the shared misses by cause

For the questions the class struggled with, ask why, the same way you would for a single student. Was it a content gap, a timing problem, or a trap answer that kept drawing people in? Each one leads somewhere different. A content gap is a reteach. A timing pattern is a pacing drill. A distractor that keeps winning is worth putting on the board and taking apart, because it's teaching the class a bad instinct. (There's a fuller version of this in turning wrong answers into a lesson.)

Then find the outliers

Now go individual, but only for the students who don't fit the class pattern. The student who's far ahead needs harder material, not the group reteach. The one who's far behind, or whose profile looks nothing like the rest, needs a separate conversation. Most of the class moves on the group lessons, so your individual time is best spent on the handful who won't.

Keep a running list, not a fresh panic each time

• Track the same few skills across mocks, so you can see what's actually improving instead of just this week's scores.
• Watch the distractors that repeat. A trap that keeps working on your class is a lesson you haven't taught yet.
• Note who's improving and who's flat. A flat strong student and a flat weak student need very different responses.

None of this needs fancy tooling. A teacher with a printout and twenty minutes can do it. What good software adds is speed: it groups the misses, flags the repeat distractors, and surfaces the outliers automatically, so the twenty minutes goes to deciding what to teach instead of building the table first.