The Problem
Students glance at feedback, check the grade, and put the paper away. The next assignment starts from zero. This is not a motivation problem. It is a process problem.
High school writers default to surface editing because nothing in their experience has taught them that revision is the actual work. Research by George Hillocks Jr. (1986) established that feedback alone does not produce revision. Students need structured opportunities to act on feedback within a system that makes revision visible and expected.
Why Revision Habits Break Down
- Students don’t know what revision means. If the only model is “fix what the teacher marked,” students respond to corrections. They don’t develop judgment.
- Feedback arrives too late. Hattie and Timperley (2007) found that delayed feedback produces significantly less revision behavior. By the time comments return, the student has mentally closed the assignment.
- Revision is structurally optional. When it is an add-on rather than a built-in phase, students treat it as optional—because it is.
What Changes When Revision Is Built In
Teachers who report consistent revision behavior share one structural feature: revision is not a separate step after writing. It is part of the writing sequence itself. That means:
- Feedback arrives while the draft is still open
- Students respond to feedback before moving forward, not after receiving a score
- The teacher can see whether revision happened—not just whether a new draft was submitted
The ACT Writing Connection
Three of the four ACT Writing domains—Ideas and Analysis, Development and Support, and Organization—reward exactly what substantive revision builds. Students who have never been required to revise an argument do not suddenly produce strong analytical writing under timed conditions. The ACT writing score reflects a writing process, not just a writing moment.
- 1. Separate feedback from grading—students stop reading when they see the grade.
- 2. Make revision comparison visible—require students to highlight and explain what changed.
- 3. Build revision into the sequence, not onto it—make it a required phase, not an option.
- 4. Reduce the feedback lag—any system that compresses the window produces more revision.
- 5. Define revision explicitly—post the difference between surface editing and substantive revision.
Sources: Hillocks, Research on Written Composition (1986); Hattie & Timperley, Review of Educational Research (2007) | guidedscholar.ai | © 2026 Brau Consulting LLC