There’s a quiet, demoralising moment most IGCSE teachers know well. You spend a Sunday marking a stack of past papers — careful, specific, mark-scheme-aware comments in every margin — hand them back on Monday, and watch students flip straight to the grade, scan the red, and file the paper away. The same student makes the same mistake on the next paper. The feedback was good. It just wasn’t used.

That gap — between feedback given and feedback acted on — is the real problem, and it’s almost never solved by writing more or better comments. This guide is about the part everyone skips: how to give better feedback on past papers so it actually changes what students do next. Not feedback that’s clearer or kinder, but feedback that gets used.

The action gap: why most past-paper feedback is read once and ignored

Be honest about what happens to a marked paper. The student looks at the grade, feels something about it, glances at a comment or two, and moves on. Your annotations were a message; the student treated them as information received, not action required. Nothing in the handover obliged them to do anything.

This is the action gap. And it explains why the quality of your comments matters far less than you’d think. A perfect mark-scheme-aligned comment that nobody acts on improves precisely zero grades. A blunter comment that triggers a redraft improves one. The whole game of giving past-paper feedback students act on is moving feedback from something students read to something they do.

The rest of this guide is the four things that close that gap.

Make feedback a task, not a comment

The single highest-leverage change you can make: stop treating feedback as the end of the marking cycle and start treating it as the start of a work cycle. A comment is a verdict. A task is an instruction with an expected output.

In practice this means every meaningful piece of feedback ends in an action the student has to complete and hand back. Not “your conclusion doesn’t evaluate” — that’s a diagnosis they’ll nod at and forget. Instead: “Rewrite this conclusion to reach a justified judgement using two pieces of evidence from your answer. Resubmit by Friday.” Same insight, completely different fate. The first gets read; the second gets done.

This is the principle behind DIRT — Dedicated Improvement and Reflection Time: timetabled time, in lesson, where the only task is acting on the feedback you’ve just given. Ten or fifteen minutes where students aren’t moving on to new content but reworking the answers you’ve marked. The crucial detail is that it’s protected time you schedule, because “do this at home” is where feedback goes to die. If acting on feedback isn’t on the timetable, it isn’t happening.

A few ways to make the task-not-comment shift concrete:

• Phrase feedback as imperatives. “Add a unit to every numerical answer.” “Define the command word before you start.” Verbs, not observations.
• Give one to three actions, not ten. A paper covered in red gives the student no idea where to start, so they start nowhere. Pick the highest-impact fixes and let the rest go.
• Set a deadline and a place for the redo. “Redraft Q4 on the back of the sheet” or “resubmit Q4 online by Thursday.” An action without a destination is a suggestion.

Be specific about the next step — not just what’s wrong

Most feedback names the problem. Feedback students act on names the next move. The difference is the gap between “weak analysis” and “for each point, add a sentence beginning ‘this matters because…’ that links it back to the question.”

Diagnosis tells a student they’re lost. A next step tells them which way to walk. Students very rarely refuse to act on feedback out of laziness — far more often they simply don’t know how to fix what you’ve flagged. “Improve your evaluation” assumes they already know what better evaluation looks like; if they did, they’d have written it the first time.

So tie every flag to the mark scheme and to a concrete action: “The mark scheme awards a mark for a balanced argument — you’ve given three points for and none against. Add one well-developed counterpoint here.” That’s specific enough to act on without you having written the answer for them. This is the same examiner-style precision covered in what examiner-style feedback actually looks like and in mark-scheme-aligned feedback versus red-pen comments — the difference here is that you’re explicitly turning that precision into a do-able next step, not just an accurate description of the gap.

One caution: specific does not mean finished for them. If your next step is so complete that the student just transcribes your sentence, you’ve graded your own writing, not built their skill. The sweet spot is an action precise enough to attempt but open enough that they have to think. (Getting that balance right with AI assistance is the whole subject of using AI feedback without dumbing down your teaching.)

Build in accountability and follow-up

Here’s the uncomfortable truth: if a student knows nobody will check whether they acted on the feedback, most won’t. Accountability isn’t distrust — it’s just how human attention works. The feedback that gets used is the feedback someone follows up on.

Follow-up doesn’t have to be heavy. The lightest version that works:

• Require the redraft to come back to you. “Fix this and resubmit” is the most powerful four-word phrase in feedback because it creates a loop. The student knows you’ll see the second version, so they actually do the work.
• Mark the improvement, not just the original. Give credit — even informally — for the redraft. If acting on feedback earns nothing, students learn that the grade on the first attempt was the only thing that mattered.
• Close the loop out loud. A quick “I read your redrafts — three of you nailed the counterargument this time” tells the class that acting on feedback is noticed and valued. Silence tells them it isn’t.
• Carry actions forward. Keep a short note of the action you set, and check the next paper for it specifically. “Last time I asked you to add units — you’ve done it on Q1 but not Q5” is how feedback compounds instead of resetting every paper.

That last point is where the action gap finally closes. When students learn that an action you set will be checked on the next paper, feedback stops being a one-off comment and becomes a running thread they’re held to. This is also where analytics earn their keep: seeing whether the same error recurs across a class tells you whether the feedback landed or whether you need to reteach it to everyone — the kind of follow-through that makes assigning past papers for genuine impact actually pay off.

Hand the mark scheme to the student

The most underused move in past-paper feedback is to stop being the only person doing the marking. Before — or instead of — you commenting on everything, have students self-assess their answer against the mark scheme.

This works for two reasons. First, it forces the student to read the mark scheme, which is where the marks actually live, and most students have never looked at one closely. Second, the act of finding their own gap — “oh, I never stated the assumption, that’s the missing mark” — produces far more durable change than being told. They’ve done the diagnostic work, so the next step feels like theirs.

Practically: give students the mark scheme (or a simplified set of success criteria) and ask them to RAG-rate their answer against each point — green for nailed it, amber for partial, red for missing — before you add anything. Then your feedback becomes confirmation and challenge (“you marked Q6 green, but the mark scheme wants two effects — look again”) rather than a full audit you carry alone. Students who can mark their own work against the scheme have effectively internalised the examiner’s standard, which is the entire point of practising past papers in the first place.

How this looks in practice

None of this depends on a particular tool — it depends on closing the loop. But the loop is far easier to run when the feedback, the redraft, and the follow-up live in one place. A free Tutopiya for Teachers account gives students examiner-style feedback aligned to the mark scheme with specific next-step actions, lets them resubmit or redo the answer (so feedback is a task, not a comment), keeps your review and override in your hands, and shows you analytics on whether the fix actually landed on the next attempt. That’s the accountability and follow-up loop, built in. Use it, or build the same loop with paper and a deadline — the method is what matters.

FAQ

How do I give better feedback on past papers so students actually use it? Turn every comment into a task with a deadline and a destination. Instead of describing what’s wrong (“weak conclusion”), set a specific next step the student has to complete and hand back (“rewrite this conclusion to reach a justified judgement, resubmit Friday”). Then protect time in lesson for them to do it, and check the redraft. Feedback gets used when it’s an instruction you follow up on, not a verdict you file away.

What is DIRT and how does it help with past-paper feedback? DIRT — Dedicated Improvement and Reflection Time — is timetabled lesson time whose only purpose is acting on the feedback you’ve just returned. It works because the biggest reason feedback is ignored is that students are never given protected time to respond to it. Ten to fifteen minutes of in-class redrafting, where no new content is introduced, converts feedback from something read into something done.

Why do students ignore my feedback even when it’s detailed and accurate? Usually for two reasons: nothing obliges them to act on it, and the comment names the problem without showing the next move. A perfect diagnosis (“improve your evaluation”) leaves a student who doesn’t know how to evaluate exactly where they were. Pair every flag with a concrete, mark-scheme-linked next step, then build in a follow-up so they know the redraft will be checked.

How do I get students to act on feedback without redoing the whole paper? Don’t ask them to. Pick one to three highest-impact actions per paper, phrase them as imperatives, and have students redraft only those answers — not the whole script. A paper drowning in red gives no starting point; two precise “fix this and resubmit” actions are something a student can actually complete in a DIRT slot.

Should students mark their own past papers against the mark scheme? Yes — it’s one of the most effective ways to make past-paper feedback stick. Having students RAG-rate their answer against the mark scheme before you comment forces them to read the scheme and find their own gaps, which produces more durable improvement than being told. Your feedback then becomes targeted confirmation and challenge rather than a full audit you carry alone.

The bottom line

The hard part of past-paper feedback was never writing it — it’s getting it used. Close the action gap and everything else follows: make feedback a task, not a comment; name the next step, not just the fault; build in accountability so the redraft comes back and gets checked; and hand students the mark scheme so they learn to find their own gaps. Do that and feedback stops being something students read once and starts being something that moves a grade. That’s the only kind worth a Sunday.

Close the feedback loop — set actions, let students resubmit, check if the fix landed →

Ready to Excel in Your Studies?

Get personalised help from Tutopiya's expert tutors. Whether it's IGCSE, IB, A-Levels, or any other curriculum — we match you with the perfect tutor and your first session is free.

Book Your Free Trial