Feedback That Students Actually Use
You return 26 persuasive essays. You have written detailed comments on every essay - average 8 comments per student, covering grammar, structure, and content. A week later, you ask students to revise. Only 4 students make substantive changes; most fix a couple of spelling errors and resubmit. Several say they 'didn't understand' the comments. Your comments included phrases like 'develop your argument more' and 'this paragraph lacks cohesion.' You have one 45-minute lesson before the revision deadline.
1. Diagnose why the feedback failed, and propose what to do in the 45-minute lesson.
Read the worked answer
Diagnosis - two failures:
- Volume and vagueness: 8 comments per essay is overwhelming, and 'develop your argument' / 'lacks cohesion' are abstract - they name a problem but not an action.
- No revision process: students were never taught how to act on feedback, so they defaulted to surface edits.
45-minute lesson plan:
- (10 min) Model one comment. Take an anonymous sample: 'develop your argument' → show what a developed version looks like vs the original. Make the abstract concrete.
- (15 min) Prioritize. Tell students to ignore all but the two most important comments (mark these clearly, or have them choose). Fewer, deeper revisions beat many shallow ones.
- (15 min) Guided revision of one paragraph using a checklist: 'Did I add evidence? Did I explain how it supports my point? Does the next sentence connect?'
- (5 min) Peer check against the checklist.
Key move: convert comments into actionable instructions and reduce the count.
2. How would you change your feedback approach for the next essay to prevent this?
Read the worked answer
Shift from comprehensive marking to focused, actionable feedback:
- Limit to 2–3 comments tied to the current unit's focus (e.g., argument development), not everything at once.
- Use a consistent code or rubric so students recognize recurring targets.
- Phrase as an action: instead of 'lacks cohesion,' write 'Add a linking sentence between ¶2 and ¶3 that connects your two reasons.'
- Build in a revision step as part of the task (draft → feedback → revise → submit), so feedback is used, not just received.
- Check understanding: a quick 'what is your #1 revision target?' exit slip after feedback.
This reduces teacher workload while increasing uptake - the goal is revision, not coverage of every error.