A full unit built around Death of a Salesman typically generates several distinct rounds of student work: comprehension checks during the reading, discussion or seminar notes, a rough draft, peer review feedback, and a final polished essay. Multiplied across several class sections, the cumulative grading load can quietly become one of the heaviest stretches of a teacher's semester.

The instinct many teachers have is to grade everything with the same level of detail, which is not sustainable across a full unit and often means the final essay, the assignment that matters most, gets rushed because energy has already been spent on earlier lower-stakes checkpoints. Deliberately varying the depth of grading across the unit protects energy for where it matters most.

Comprehension checks during the reading, for instance, can often be graded on a simple complete or incomplete basis rather than a detailed rubric, since their purpose is verifying engagement with the reading, not assessing analytical writing skill.

Reserving detailed, rubric-based feedback for the draft and final essay stages, where analytical skill is actually being assessed, keeps grading time proportional to what each assignment is designed to measure.

Mapping Grading Depth to Assignment Purpose

Before the unit begins, it helps to explicitly decide, assignment by assignment, how much grading depth each one warrants. This prevents the common pattern where early low-stakes assignments absorb disproportionate grading time simply because they arrive first, before the fatigue of a full unit has set in.

• Reading checks: complete or incomplete, minimal written comment
• Seminar notes: quick check for textual citation, not full narrative feedback
• Rough draft: focused feedback on thesis and structure only, not line editing
• Peer review: spot-checked rather than fully reviewed by the teacher
• Final essay: full rubric-based grading with detailed comments

Where Automation Helps Most in a Long Unit

The rough draft stage is often where automated first-pass feedback adds the most value across a long unit, since it can flag structural issues, thin evidence, or an unclear thesis quickly enough for students to revise before the final essay is due, freeing the teacher's own feedback time for the deeper interpretive judgment calls only a human reader can make.

Using automation for this specific stage, rather than trying to apply it uniformly across every assignment in the unit, respects that different stages of the unit are asking for different kinds of feedback.

Protecting the Final Grading Pass

By the time final essays arrive, a teacher who has managed grading depth carefully across the earlier stages of the unit should have more energy and attention available for the assignment that actually counts most toward the grade and that students have invested the most revision effort into.

This is ultimately a fairness issue as much as a time management one: students deserve their most careful, most detailed feedback on the assignment that represents their most developed thinking, not on whichever assignment happened to land when the teacher had the most energy.

Planning the Unit Calendar Around Grading Load

Spacing out the due dates for drafts and final essays across multiple class sections, rather than having every section's final essay due on the same day, spreads the grading load in a way that supports more consistent feedback quality across the entire stack rather than a rushed final week.

This kind of calendar planning is a small structural choice that compounds meaningfully over a unit that can otherwise consume several full weekends of grading time.