Feedback most students never read
Picture a Year 9 essay handed back with careful notes in the margin. "Expand this." "Evidence?" "Good point." The student flips to the mark, reads the grade, and closes the book. Hours of your weekend, gone in four seconds.
This happens in classrooms across NSW every week. The problem is not that teachers write bad feedback. It is that a lot of feedback is written to justify a grade, not to change what a student does next. Those are two different jobs.
What the research keeps finding
John Hattie's work put feedback near the top of the influence list, but with a big asterisk. The effect size swings wildly. Some feedback helps a lot. Some does nothing. A fair amount actually makes performance worse.
The pattern is clear enough. Feedback works when it tells a student where they are going, how they are going, and what to do next. It fails when it is vague, when it arrives too late to matter, or when it lands as a verdict rather than a next step.
Praise attached to the person is one of the weakest forms. "You're so clever" tells a student nothing about the work. Worse, it makes them cautious about tasks where they might not look clever. Comments about the task and the strategy do the heavy lifting.
Point at the work, not the person
Compare two comments on the same paragraph.
- •"Weak analysis. Try harder next time."
- •"You've quoted the source but not explained it. Add one sentence after the quote that says what it proves about the character."
The first is a judgement. The second is an instruction the student can follow tomorrow. It names the gap and it names the move. That is the whole game.
A quick test before you write anything: could the student do something different in the next five minutes because of this comment? If not, you are describing the problem, not fixing it.
Fewer comments, better ones
Marking every error is exhausting and counterproductive. A page covered in red tells a student everything is wrong and nothing is fixable. They shut down.
Pick the one or two things that will move the work the most. In an extended response that might be evidence and explanation. In a maths solution it might be setting out the working so the method is visible. Name those. Ignore the rest for now.
This is not lowering standards. It is triage. A student who fixes one real thing well has learned more than a student who skims twenty ticks and crosses.
Build in time to act on it
Here is the part that gets skipped. Feedback only changes learning if the student does something with it. Handing it back at the end of a topic, right before the next unit starts, guarantees it goes nowhere.
Try this instead. Return the work, then give ten minutes of class time with one clear task:
- •Read the comment on your evidence.
- •Rewrite that one paragraph now.
- •Show me before you leave.
Some teachers hand back scripts with no marks at all, only comments, and give the grade the following lesson once students have acted on the notes. The grade stops competing with the feedback for attention. Students actually read the words.
Whole-class feedback saves your weekend
You do not need to write the same comment thirty times. When you mark a set, patterns show up fast. Half the class forgot to define key terms. A cluster misread the question. A few nailed the structure but ran out of detail.
Note the common errors on one sheet as you go. Then teach to it. Put up two anonymous samples, one strong and one that missed the mark, and work through the difference with the class. Model the fix live. Students learn more from watching you repair a real error than from reading a private note.
This cuts marking time hard, and the feedback is often better because it is specific and immediate. You spend your energy teaching the fix, not transcribing it.
Make the standard visible first
Students cannot close a gap they cannot see. Before they hand anything in, show them what good looks like. A worked example. An exemplar paragraph with the moves labelled. A checklist in plain language.
When the standard is clear up front, your feedback has something to point at. "Remember the exemplar had a linking sentence between each idea. Add those." The student already knows what you mean, because they have seen it.
Where planning fits
None of this works if you are inventing feedback structures at 9pm on a Sunday. It works when the task is built with the standard, the exemplar and the likely errors already in view.
That is the connection to explicit instruction. If a lesson has a sharp learning intention and a clear model, feedback almost writes itself, because you already know exactly what you were asking students to do. Vague tasks produce vague feedback. Precise tasks produce precise, usable feedback.
When Smart Syllabus Assistant builds a lesson, it ties the learning intention, the worked example and the success criteria together from the start. That means the feedback you give later is anchored to something concrete, not improvised. Less time deciding what good looks like. More time helping students get there.
None of this is new to good teachers. But good teachers are tired, and the marking pile does not shrink on its own. The point is to spend your feedback effort where it changes learning, and stop spending it where it does not.
Want to see how a lesson comes with the standard and success criteria built in? Take a look at a sample lesson.