Making Feedback Actually Useful: What to Say So Students Can Improve

Teachers spend enormous amounts of time writing feedback that students don't use. A marked-up essay goes home, the student looks at the grade, and the comments stay unread. Even when students read comments, they often don't know what to do with them. "Good structure" tells them nothing about what to repeat. "Unclear" tells them something is wrong but not what to fix.

This isn't because students don't care. It's because the feedback doesn't give them anything actionable. The problem is structural, and it's fixable.

What Research Says About Effective Feedback

The most important finding from feedback research: feedback that only informs students of their performance level (a grade, a score, a "good job") is less effective than feedback that informs them of what to do differently. This seems obvious, but most school feedback is performance feedback rather than improvement feedback.

Effective feedback is:

• Specific — about particular aspects of the work, not the whole thing
• Actionable — tells students what to do, not just what's wrong
• Timely — arrived close enough to the work that the student can act on it
• Connected to criteria — referenced to the actual learning goals, not just teacher preference

The research also shows that extensive feedback on everything tends to be less effective than focused feedback on one or two things. Students can only hold so much attention and make so many changes at once.

Stop Grading Everything You Comment On

One of the structural problems with school feedback is that comments and grades arrive at the same moment. When a grade is present, students attend to it and the comments become noise. The grade is the answer; the comments are footnotes.

One solution: give feedback without a grade on drafts, then grade the final version. Students who receive feedback without a grade have to engage with the comments to understand how they're doing. When the grade comes later, on a revised version, the comments are what produced the better grade — which makes their value clear.

Another approach: give a grade with a brief note and require students to write a response to the feedback before moving on — articulating what they're going to do differently and why.

Make Feedback Forward-Looking

Most feedback is backward-looking: it describes what the student did or didn't do on the assignment in front of you. Forward-looking feedback describes what the student should do on the next thing.

"Next time you write a claim, try stating your specific position before giving your reason — that order tends to be stronger in academic argument" is forward-looking. It's connected to this paper, but it's a transferable instruction. The student can use it on the next essay.

Forward-looking feedback transforms a single assignment into a data point in a longer learning arc. That's what makes feedback a teaching tool rather than just an evaluation tool.

Use Feedback in Class, Not Just On Paper

Written comments on returned work are one channel for feedback. They're not the only one, and they're not always the most effective.

In-class feedback loops — where students do work, share it briefly, get immediate response, and revise — are often more effective than written comments because the response is fast and the student is still in the work. A partner giving specific verbal feedback using a structured protocol. A teacher conferring with one student for three minutes. A whole-class discussion of a common pattern observed in student work (anonymized). These in-class feedback structures are quick, direct, and promote real revision.

When you plan lessons that include meaningful feedback cycles — not just a submission and return, but an actual revision loop — LessonDraft can help you build that structure into the lesson plan so the time is allocated and the process is designed in advance.

Feedback on Process, Not Just Product

Feedback on the final product tells students what the work produced. Feedback on process tells them how to work differently. Both matter, but process feedback transfers: a student who learns to revise before submitting, to re-read their argument for internal consistency, or to ask "so what?" after each body paragraph has a strategy they can apply to every piece of writing.

Process feedback sounds like: "I can see you made a strong claim at the beginning — what happened in the middle? Did you check whether each paragraph is answering the same question your introduction set up?" This feedback is about the thinking process, not just the output.

When Students Don't Use Feedback

If your feedback is consistently being ignored, don't just write more of it. Investigate why. Common causes:

Students don't understand the comment. "Underdeveloped" means nothing without an example of what development would look like.

Students don't believe revision will produce a better outcome. If grades don't change when students revise, revision has no stakes.

Students don't have time or structure to revise. Feedback given on Friday on work that was graded and done is structurally unable to produce revision.

Each of these is a system problem, not a student motivation problem. Fixing the system produces more revision than additional comment-writing.

Your Next Step

On your next assignment, try this: pick one piece of student work that's representative of a common error or gap. Make it anonymous. Show the class the feedback you'd give on it — one specific, actionable thing — and discuss together what revision of that work would look like. That exercise teaches feedback literacy: how to read, understand, and act on feedback. It's more valuable than most students reading your comments alone.