The standard explanation for why students ignore teacher comments is motivational: they don’t care, they’re grade-focused, or they’d rather move on than look back. Teachers who believe this write better comments anyway and get the same result: the comments land and nothing changes.
The motivational explanation is wrong, or at least incomplete. Most students who fail to act on feedback are not making a deliberate choice to disregard it. They are operating in a workflow that has no slot for what the feedback is asking them to do. Like the teacher, they have mentally moved on to the next assignment and don’t have the time to closely analyze the comments and critically think through how they would apply them in a revision. And this gap applies to presentations and spreadsheets—really anything that takes time and requires iteration to get done right.
The comment arrives after the deadline
A paper is due Friday. The teacher returns it the following Monday with margin notes and a summary comment at the end. The student reads it, or doesn’t, and then does what the workflow requires next: starts the reading for Tuesday, drafts the response for Wednesday, studies for Thursday’s test. There is no revision slot. No scheduled time to work the comment into a second draft. The feedback arrived after the assignment closed, so the assignment is, from the student’s perspective, finished.
This is not apathy. It is a rational response to the actual structure of the course. Feedback delivered at the end of an assignment and followed immediately by a new assignment produces a clean record of what went wrong and zero practice correcting it.
Students need a target, not a verdict
Even when a revision slot exists, students often don’t know what to do with it. A comment that says “your argument is underdeveloped” tells the student what is wrong. It does not tell the student what a developed argument looks like in this paper, on this prompt, against this rubric.
John Hattie and Helen Timperley’s 2007 meta-analysis on feedback identified the distinction clearly: effective feedback specifies what to change and what correct performance looks like. Most teacher comments do the first. The second requires the teacher to articulate a target state—which is harder to write and more useful to the student than the diagnosis alone—but takes time, a resource teachers already are critically short of.
Knowing something is wrong is not the same as knowing what right looks like.
Students who cannot picture the target state respond to revision invitations the same way they respond to any open-ended task: they do the minimum visible thing and declare it done. A misspelling is fixable because the correction is obvious. A structural argument problem is not fixable without knowing what the structure should look like.
Revision needs to be built in, not bolted on
There is a difference between permitting revision and building revision into the workflow. Permitting revision means writing “revise and resubmit” at the top of the paper and accepting a second draft if the student chooses to submit one. The students who most need the revision cycle are the least likely to initiate it voluntarily.
Building revision into the workflow means the assignment structure requires a second pass: the student receives criteria-specific feedback, revises that criterion, and submits again. The teacher’s job is not to check whether revision happened—the workflow produces it. What the teacher evaluates is whether the revision addressed what the comment asked for, which is a more useful and more efficient use of instructional time than re-reading a paper hoping something changed.
Research on the writing-process movement—Graves, Calkins, the National Writing Project—established this decades ago: writing improves through cycles of drafting, receiving feedback, and revising. What eroded that model in most schools was not a change in what works. It was the practical impossibility of running structured revision cycles across 120 students without infrastructure to manage them.
The comment is not the product. The revision is. Until school writing workflows are designed around that distinction, the most carefully written margin notes will continue to produce the same result: a student who read what you wrote, slid the paper in a folder, and started the next assignment.
Comments welcome.
Further reading
John Hattie and Helen Timperley. “The Power of Feedback,” Review of Educational Research 77, no. 1 (2007): 81–112. The meta-analysis that identified the conditions under which feedback produces learning gains versus no effect. SAGE Journals.
Donald H. Graves. Writing: Teachers and Children at Work (Heinemann, 1983). The foundational text of the writing-process movement, establishing drafting, conferencing, and revision as the structure of writing instruction rather than the product. Heinemann.
Lucy Calkins. The Art of Teaching Writing (Heinemann, 1986). Codified writing-workshop methods for K–8 classrooms, grounding the revision cycle in student ownership of the writing process. Note: this citation is specific to her writing-workshop pedagogy; her later reading curriculum is contested in the current science-of-reading debate. Heinemann.
National Writing Project. A national professional-development network founded in 1974 that grew from the same writing-process research and continues to support teachers of writing across the United States. nwp.org.