AI in Schools
Turn Saturday's marking into Monday's re-teach lesson
Turn Saturday's marking into Monday's re-teach lesson
You have just finished marking. You already know most of the class got Q4 wrong, and you have already decided to "go over it Monday". That's the problem. Going over it Monday is not a lesson. It's a rerun of the original explanation, which is the one that already did not land. The move a good head of faculty would make, sitting next to you at the kitchen table, is to name the misconception behind each wrong answer, then build Monday around addressing those two or three misconceptions specifically. That takes forty-five minutes and a clear head. Nobody has forty-five minutes and a clear head at the end of a marking session. Here is the prompt.
The prompt
You are helping me turn a set of just-marked test results into a targeted re-teach lesson. The goal is not to re-explain the topic. The goal is to name the specific misconceptions the wrong answers reveal, then design a lesson that addresses those, not the topic as a whole.
You are the senior teacher on the other side of the kitchen table. You are working in the tradition of:
- Dylan Wiliam's formative assessment work: wrong answers are evidence, not noise, and the next lesson is driven by that evidence.
- Harry Fletcher-Wood on responsive teaching: the plan bends to what actually happened, not to the sequence.
- Craig Barton's diagnostic question work: every wrong answer maps to a specific, nameable misconception.
CONTEXT
- Year level: [YEAR LEVEL, e.g. Year 8]
- Subject: [SUBJECT, e.g. Maths]
- Topic: [SPECIFIC TOPIC, e.g. adding fractions with unlike denominators]
- Class size: [NUMBER]
- Re-teach lesson length: [MINUTES]
- Time between now and the re-teach: [e.g. 2 days]
THE TEST
For each question, I will give you:
- The question itself.
- The correct answer.
- Roughly how many students chose each option (for multiple choice) or the two or three most common wrong answers (for short answer).
Paste of the test and results:
[PASTE THE QUESTIONS AND THE WRONG-ANSWER FREQUENCIES]
WHAT I NEED BACK
1. MISCONCEPTION MAP. One table. Columns: Question, Common wrong answer, Named misconception (in one clear sentence, in the language a student would say it if you asked them), How confident you are this is the misconception (high / medium / low), Estimated share of the class holding it.
2. RANKED PRIORITIES. Cut to the top three misconceptions. Rank by (a) share of the class affected and (b) how much the rest of the unit depends on getting this one right. If two are equally important, prefer the one that will get worse the longer we leave it.
3. THE MONDAY LESSON, in the time budget above. Structure it as:
- Do Now (5 min): a low-stakes retrieval item that does NOT re-explain, but forces students to commit to an answer that will reveal which misconception they hold.
- Reveal (5 min): show the class the pattern in the wrong answers, name the misconception out loud (no shame, just naming), and predict where it will trip them up next.
- Contrast pair (10 min): two carefully chosen worked examples, side by side, where the only difference is the exact place the misconception fires. Talk students through the difference.
- Guided practice with immediate check (15 min): three questions I can circulate on, each designed to fire the misconception if it is still there.
- Exit ticket (5 min): one hinge-style question that tells me tomorrow whether the misconception is gone or whether I need another round.
4. WHAT NOT TO DO. Name one or two things it would be tempting to do in this re-teach that would waste the lesson (re-explaining the whole topic, running fresh content, moving on because "we're behind"). Be blunt.
CONSTRAINTS
- Do not re-teach the topic. Re-teach the misconception.
- Do not invent wrong answers I did not paste in. If a question has no wrong-answer data, say so and leave that row blank.
- Australian English, plain sentences, no headings in the lesson plan longer than four words.
What it does well
It refuses to treat marking as a grade-generation exercise and treats it as diagnostic data, which is what it is. Naming the misconception in a sentence a student would say ("you can add the tops and add the bottoms") is the move that turns "they got it wrong" into "here is the specific idea to attack".
Where it falls over
It cannot tell a genuine misconception from a careless error, and it will treat one as the other unless you push back. If a question got a scatter of unrelated wrong answers, that is usually not a misconception, it is a badly written question, and you have to name that yourself. It also cannot see the student in front of you, so the "share of the class affected" numbers are ballpark, not decisions.
Try it like this
- For Year 7 Maths (fractions test): paste the six questions and the frequency of each wrong answer, and the misconception map will almost always separate "does not simplify" from "adds numerators and denominators" from "cannot find common denominator", each of which needs a different Monday.
- For VCE English (practice text response): paste the question, the top-band descriptor and two or three student responses at different bands, and ask for a misconception map on argument, not on writing quality.
- If you only have five minutes tonight: paste the top three highest-error questions and skip the lesson plan section. Come back to it Sunday.
Do this once tonight and Monday is a real lesson. Do it every assessment cycle and by end of term the class is meeting you halfway.