Many Sula unit plans focus heavily on reading schedules and discussion questions, then treat the final essay as an afterthought. A better approach designs the writing assessment first and works backward, so every lesson prepares students for the analysis they will eventually produce. This shifts the unit from a collection of activities into a coherent progression. Students also see a clearer connection between what they read and what they are asked to write.

Begin by choosing the central essay prompt and sharing it in the first week. Even a rough version tells students what to watch for as they read, such as how Morrison shapes the friendship between Nel and Sula or how the community responds to Sula's return. Annotation becomes purposeful when students know which patterns matter. Teachers can refine the prompt as the unit develops if discussion reveals stronger angles.

Sula is a short novel, but its chapters are dense and organized by year, which lets teachers divide the reading into manageable sections. Many classes move through it in three to four weeks, pairing two or three chapters with a brief writing task. These small assignments build a bank of evidence students can draw on later. They also give teachers early data about who is following the text and who needs support.

Low-stakes writing checkpoints

Short checkpoints such as a paragraph on the novel's opening description of the Bottom or a reflection on the events of 1919 give students regular practice without heavy grading pressure. Score these on a simple three-point scale focused on one skill, like using a specific detail to support a claim. Return them quickly so feedback arrives while the material is still fresh. A fast turnaround matters more than elaborate comments at this stage.

• Week one: annotation and a paragraph on setting and community
• Week two: a character comparison paragraph on Nel and Sula
• Week three: a short analysis of a symbol such as fire, water, or the birthmark
• Week four: a thesis workshop and outline for the final essay
• Final week: a full draft, peer review, and revision before submission

Feedback that moves students toward the final essay

Feedback on checkpoint tasks should point forward to the final essay. If a student summarizes the drowning of Chicken Little instead of analyzing its effect on the girls, a useful comment asks what the scene shows about how each girl handles guilt. That prompt connects directly to the thesis work coming later. Generic praise or correction of minor errors does less to prepare students for the larger assignment.

Keep a simple tracker noting which skill each student needs most, such as evidence selection or analysis depth. By the time final drafts arrive, you will already know who is likely to struggle and can offer targeted conferences. This also makes grading final papers faster because you are confirming patterns you have seen. Digital tools that store rubric-aligned comments across assignments can help maintain this record.

Designing the final assessment

The final essay should require students to draw on the whole novel rather than a single chapter. Good prompts ask them to trace a motif or idea across time, such as how the community's relationship to Sula changes from her childhood to her death. Provide the rubric with the prompt so expectations are transparent. Offer a planning template that asks for a claim, three pieces of evidence, and the reasoning that links them.

Allow time in class for drafting so teachers can observe the process rather than only the product. Conferences during this time catch misunderstandings early and discourage last-minute panic writing. Students who revise after feedback usually produce noticeably stronger work. Building revision into the schedule signals that writing is a process worth investing in.

Reflecting on the unit

After grading, look at where scores clustered and which criteria caused the most difficulty. If many students wrote strong plot summaries but weak analysis, the fix is probably more modeling of how to explain evidence. If thesis statements were vague, add a dedicated thesis lesson next time. These patterns give you concrete changes to make before the unit returns the following year.

Ask students for feedback too, particularly about which checkpoints helped and which felt redundant. Their responses often reveal that a particular scaffold, such as the outline template, made the difference. Keeping notes from year to year turns a good unit into a refined one. Over time, the assessment structure becomes the backbone of how you teach Sula.