You spent 4 hours on a set of essays last Sunday. Specific comments. Genuine effort. The kind of feedback that took real thought to write.
You handed them back on Monday. By Tuesday you'd watched most of the class flip straight to the mark, scan the page for about 4 seconds, and close the book.
If you've been teaching for more than a year, you've seen this. It's one of the most demoralising moments in the job, not because students are ungrateful, but because you know the feedback was good and you know it's not going to move anything.
The problem isn't the students. It's where in the process the feedback lands.
Why feedback doesn't stick
The research on feedback is consistent on this. NSW CESE's What Works Best guidance and the NSW Curriculum's advice on feedback point the same way: feedback works when it's specific, tied to clear success criteria, and given while the student still has time to act on it. The same evidence finds students engage with feedback far more when it lands before the mark, not alongside it. Most school feedback does the opposite. It arrives at the end of a task, after the grade is assigned, with no structured opportunity to do anything with it before the next assessment begins.
That's not a student motivation problem. That's a timing problem.
When the mark arrives at the same time as the feedback, the mark wins. Every time. It's how attention works. The mark is concrete, immediate, and socially meaningful. The feedback is abstract, future-facing, and requires effort to apply. Students ignore your comments because the system gives them no reason to do anything else.
Three things make feedback land:
- It arrives before the grade, if possible
- It's specific enough to be actionable
- The student has a structured moment to respond
Most school feedback hits none of those 3.
The timing problem
The standard feedback loop in most schools looks like this: student submits work, teacher marks it, teacher returns it with a grade and comments, student moves on to the next task.
That loop puts the feedback at the end of the process. By the time the student sees it, the work is over. There's no draft to revise, no follow-up task that uses the same skill, no structured reason to do anything except read it and close the book.
Changing the timing is the highest-impact move available to most teachers. Feedback given on a draft, before the final submission, is acted on almost immediately because the student still has something to do with it. Feedback given after the final grade is, for most students, information about the past.
I started doing this with my Year 11 English classes 2 years ago. Draft feedback before the final submission, focused entirely on the Explanation section of their TEEL paragraphs because that's where the marks were moving. The improvement between draft and final was visible in almost every script. Not because the students suddenly cared more. Because they had something to do with the feedback before it was too late to matter.
The problem is time. Giving feedback on drafts and on final submissions doubles the marking load. Most teachers know draft feedback works. Most teachers also know they don't have the hours to do it consistently across every class, every assessment, every term.
The specificity problem
Timing isn't the only issue. Even when feedback arrives at the right moment, vague feedback doesn't move students.
"More analysis needed" is true of half the essays in any Year 11 class. It tells the student nothing about which sentence to fix or how to fix it. "Your explanation stops at naming the technique. You need one more sentence that says what effect it creates on the reader and why Orwell chose it" is actionable. The student knows exactly where to go and what to do.
The gap between those two comments isn't effort. It's specificity. And specificity takes time, which brings us back to the same problem.
Tired markers write vaguer feedback. Precise language requires more cognitive effort than general language, and that effort is exactly what runs out at the end of a marking session. The feedback that arrives latest in the pile, for the students who most need it to be specific, often gets the most general version of it.
What actually closes the gap
The feedback gap closes when students get specific, actionable feedback before the grade is assigned and before the work is finished.
That's what MarkMate is built to do. Students submit a draft. MarkMate reads it against the rubric and marking criteria and returns annotated feedback tied to the actual sentences in front of it, not generic comments. The student sees exactly where the explanation is thin, which paragraph needs more precise evidence, where the link doesn't connect back to the question.
They get it while there's still something to do with it. Before the final submission. Before the grade.
I started using the draft feedback workflow with my Year 12 Ancient History class last term. The quality of final submissions lifted noticeably, not across every student, but across enough that the pattern was clear. The students who used the draft feedback and revised before submitting consistently produced stronger final work than the ones who submitted cold.
The bigger change was in my own marking. When students have already worked through a draft feedback loop, the final submissions are tighter. The obvious errors are gone. The feedback I write on the final is sharper because the surface-level issues have already been addressed. I'm writing better feedback in less time because the students have already done some of the work of improving.
The shift worth making
You can't fix the feedback gap by writing more comments or working faster. The system that delivers feedback after the grade, at the end of the process, after the student has moved on: that system produces the 4-second scan every time, regardless of how good the feedback is.
The shift worth making is structural. Get the feedback earlier. Make it specific enough to act on. Give the student a reason to use it.
MarkMate handles the first two. The third, the structured moment to respond, is yours. 5 minutes at the start of the next lesson to revisit the draft feedback, asking students to identify the one comment they acted on and the one they didn't, is often enough to close the loop.
Start before the next assessment lands
The draft feedback workflow works best when it's built into your assessment design from the beginning: a draft submission date a week before the final, with MarkMate running the feedback loop in between.
Start your free trial at MarkMate and set up your first draft feedback assignment before the next task goes out.
Worth sharing with a colleague who's written the same comment on 30 essays and watched none of them land.
