← All posts

How to Grade Less and Give Feedback That Actually Changes the Next Attempt

4 min read

You know the stack. Forty-two lab reports on projectile motion, sitting in your bag since Thursday, radiating guilt. You will spend six hours writing comments that students will glance at, check the grade, and recycle. If the feedback does not change what a student does next time, you are grading for a filing cabinet.

Here is what has actually worked in my classroom, and what I have watched work for colleagues who refuse to take papers home on weekends.

Grade the thing that will show up again

Before you mark a single paper, ask a small question. What skill on this assignment will students use again in the next two weeks? On a lab report, that might be error analysis. On a stoichiometry problem set, it might be unit tracking. Grade that one thing carefully and skim the rest.

When I switched to this on chemistry labs, my grading time dropped from about 12 minutes per report to 4. Student error analysis on the next lab got noticeably better, because the feedback pointed at something they were about to do again.

Use a three-code margin system

Long comments are for you, not them. Most students read the first line and stop. So I use three codes in the margin, and nothing else.

  • A circled number means "math or unit error, fix and resubmit this line."
  • A question mark means "I cannot follow your reasoning here, add a sentence."
  • A star means "this is the move I want you to repeat."

That is it. No paragraphs. Students spend the first five minutes of the next class fixing circled items in a different color pen. I check for the color, not the correctness, and record completion. The learning happens in that five minutes, not in my kitchen at 10pm.

Give feedback before the grade, not with it

The moment a number appears at the top of a page, the feedback is dead. Research on this is annoyingly consistent, and my own experience matches. So on the assignments that matter, like unit tests and full lab writeups, I return them with codes only. Students do a correction pass, then I release grades in the gradebook that evening.

Two things happen. Students actually read the comments, because that is the only signal available. And I write fewer comments, because I know they will be read.

Batch the common errors into a mini-lesson

If eight kids confused mass and weight, do not write "remember mass vs weight" eight times. Write it zero times. Open the next class with a two-minute recap, then have those eight students revise in place. You just replaced 15 minutes of writing with a two-minute talk that also caught the students who got it right by luck.

I keep a running list on my desk called "say this Monday." Every time I catch a pattern across three or more papers, it goes on the list. That list is my next warm-up.

Let some assignments be practice

Not every problem set needs a grade. Some things are reps. Check for completion, walk the room while students self-check against a key, and spend your attention on the two or three students who look stuck. You are still teaching. You are just not transcribing your teaching onto paper afterward.

The quiet part

Most of the grading load is not from students needing feedback. It is from a plan that produced too many gradeable artifacts in the first place. When your unit is built with a clear arc, you can see which two or three tasks are worth deep feedback and which are practice. If building that arc across a whole year is the part that keeps eating your Sundays, Rested Teacher plans the sequence for you so the assessments you do grade are the ones that matter.

Try one of these next week. Not all five. Pick the smallest one, the margin codes maybe, and see if your Sunday looks a little different.