Julius Caesar's plot is eventful enough, a conspiracy, an assassination, two major public speeches, a civil war, that students naturally gravitate toward retelling it rather than analyzing it. A rubric that doesn't explicitly separate summary from analysis will end up rewarding students who write competent retellings dressed up with a thin layer of interpretive language.

The clearest signal of summary masquerading as analysis is a paragraph that moves chronologically through plot events, connected by transitions like "then" and "after that," rather than being organized around an idea. Analysis paragraphs should be organized by argument, with evidence pulled from wherever in the play best supports that specific point.

A rubric category explicitly labeled "paragraph organization: idea-driven versus event-driven" makes this distinction visible and gradable, rather than leaving it as an implicit expectation that students may not fully understand without a concrete example.

It helps to show students a side-by-side comparison: one paragraph that summarizes the assassination scene chronologically, and one that uses details from the same scene to support a specific claim about Brutus's psychological state. Seeing the same content handled two different ways makes the distinction concrete rather than abstract.

Rubric language that names the summary trap directly

Rather than a vague category like "analysis quality," a rubric benefits from explicit language distinguishing between paraphrasing what happens and explaining why it matters. Naming the specific failure mode, rather than only describing the ideal, helps students recognize the pattern in their own drafts before submission.

• Paragraphs are organized around an idea, not a chronological sequence of events
• Evidence is selected because it supports a claim, not because it comes next in the plot
• Analysis explains why a moment matters, not just what happens in that moment
• Transitions connect ideas logically, not just move the reader through time
• The essay could not be mistaken for a plot summary by someone unfamiliar with the assignment

Teaching students to self-audit for summary

Giving students a simple self-check before submission, reading each paragraph and asking whether it explains an idea or narrates an event, catches a surprising number of summary paragraphs before they ever reach the grader. This kind of self-editing skill, once built, transfers well beyond this single assignment.

Peer review focused specifically on this distinction, having a partner mark any sentence that reads as pure plot narration, also works well and gives students an outside perspective on a pattern that can be hard to notice in one's own writing.

Grading consistently across essays with varying summary levels

Essays exist on a spectrum from pure summary to genuine analysis rather than falling cleanly into one category or the other, and a rubric with clear scoring bands for this specific category makes it easier to place an essay accurately along that spectrum rather than defaulting to an average score out of uncertainty.

Reading a handful of essays first to identify where the class's summary-to-analysis spectrum actually falls this particular assignment helps calibrate scoring bands realistically, rather than applying an idealized standard that doesn't reflect what the actual class produced.

Feedback that moves a summary essay toward analysis

For essays that lean heavily toward summary, feedback that asks a direct question about one specific paragraph, such as what that paragraph's actual argument is supposed to be, gives students a concrete starting point for revision rather than a general instruction to "analyze more."

This kind of targeted feedback, focused on a single representative paragraph rather than the whole essay, is often more effective than a lengthy general comment, since it gives students one clear, manageable example to apply across the rest of their revision.