Why “Summarizing My Peer’s Draft” Feels Safe but Misses the Mark
Most sophomore English majors assume that a tutorial response is just a polite recap of what their classmate wrote. You might think, “If I restate the thesis and outline the argument, I’m showing I understood the paper.” That feeling is understandable—summaries are easy, they avoid conflict, and they let you finish quickly before a deadline. The real problem is that the professor’s rubric explicitly rewards critical analysis, not a neutral description. When you only tell your peer, “Your argument about Hamlet’s madness is clear,” you’re not helping them see gaps, contradictions, or opportunities for deeper reading. The rubric’s “analysis” criterion looks for evidence‑based judgments, connections to secondary scholarship, and suggestions that push the draft toward a more nuanced thesis.
In practice, the misconception persists because many students have never been asked to “talk back” to a peer’s ideas in a structured way. High‑school essays often ended with a simple “good job,” and the habit carries over. The professor’s strict requirement flips that habit on its head: you must interrogate the draft, not just echo it. You are not a mirror reflecting the text back to the author; you are a lens focusing light on specific, often overlooked, details. If you find yourself summarizing, stop. Ask yourself: “What is the unstated assumption here?” or “Where does the evidence fail to support the claim?” These questions force you out of passive reading and into active critique.
Breaking Down the Rubric: What Counts as “Critical Analysis”
Take a moment to map the rubric’s language onto concrete actions. Below is a quick decision framework that turns vague terms into specific steps you can check off while you read. This table helps you translate abstract grading criteria into tangible feedback points.
| Rubric Phrase | What It Means in Practice |
|---|---|
| Evaluates argument strength | Identify at least two claims, ask whether the evidence truly supports them, and note any logical leaps. |
| Engages with scholarly sources | Point out where a citation could be expanded, or where an alternative scholar offers a different view. |
| Offers constructive suggestions | Propose a concrete revision—e.g., “Replace ‘obviously’ with a specific textual example.” |
| Demonstrates depth of reading | Connect the draft’s argument to a broader theme in Shakespeare studies, such as gender or power. |
When you see a rubric item, ask yourself: “What specific evidence can I cite from the draft? What alternative reading can I suggest?” If the answer is “none,” you’re still in summary mode. True analysis requires you to stand back from the text and evaluate its architecture. Are the load-bearing walls solid? Is the roof leaking? You don’t need to rebuild the house, but you do need to identify structural weaknesses. This shift from “what did they say?” to “how well does it work?” is the core of critical feedback. It moves you beyond appreciation into evaluation, which is what your professor is actually grading.
Step‑by‑Step Process to Turn a Summary into an Analysis
Follow this workflow for each tutorial response. It’s designed to fit into a two‑hour window, which is realistic for a deadline tomorrow night. This method forces you to engage with the text at a deeper level, preventing the drift back into simple summary.
- Skim for Structure (10 minutes) – Highlight the thesis, topic sentences, and any quoted lines from Shakespeare. Note where each paragraph begins and ends. This creates a map of the argument’s skeleton.
- Identify Two Core Claims (15 minutes) – Write them in your own words. Ask, “What is the writer trying to prove?” If you can’t state the claim clearly, the peer needs help clarifying it.
- Gather Evidence (20 minutes) – For each claim, pull out the supporting quotations or secondary sources the draft uses. Put them in a two‑column list: Claim | Evidence. This visual separation makes gaps obvious.
- Spot Gaps or Weak Links (20 minutes) – Look at each claim–evidence pair and ask:
- Does the evidence directly support the claim?
- Is there an important counter‑argument that’s ignored?
- Could a different passage from the play strengthen the point?
- Draft Analytic Comments (30 minutes) – For every gap you found, write a sentence that:
- Names the issue (“The link between Ophelia’s madness and the political chaos is under‑developed”).
- Explains why it matters (“Without this connection, the essay risks treating Ophelia’s condition as purely personal”).
- Suggests a concrete fix (“Consider adding a brief discussion of the Danish court’s instability in Act IV, scene 5”).
- Polish Tone (5 minutes) – Replace any “I think” or “Maybe” with confident language. Use “you might strengthen” rather than “you should change everything.” Confidence signals authority.
This checklist keeps you from slipping back into a summary. Each bullet forces you to evaluate, not just recount. By breaking the task into timed segments, you avoid getting stuck on minor details and ensure you address the core arguments. This structured approach turns a daunting critique into a manageable, systematic process.
Real Student Stories: From Summaries to Insightful Feedback
Case 2: Liam, a peer reviewer initially wrote, “Great use of quotes!” for every paper. He received low marks because he wasn’t analyzing the function of those quotes. He changed his approach to: “You quote Lady Macbeth’s ‘unsex me here’ effectively, but you don’t analyze the gendered language. How does this invocation of masculinity relate to your broader argument about power?” This shift from praise to inquiry transformed his feedback from generic to critical. He stopped being a cheerleader and started being a collaborator in the intellectual process.
“I used to think critique meant finding flaws. Now I see it as helping the argument breathe. When I ask ‘why’ instead of ‘what,’ my peers actually improve their drafts.” — A junior English major
These stories show that analysis isn’t about being harsh; it’s about being precise. Maya and Liam both learned that specificity is the antidote to summary. By focusing on the mechanics of the argument, they provided feedback that was genuinely useful. This is the key takeaway: your goal is to help the writer think deeper, not just to judge their work.
Common Pitfalls: How to Avoid the “Summary Trap”
Even with a good process, it’s easy to slip back into old habits. Here are three common pitfalls to watch for, especially when you’re tired or pressed for time. Recognizing these traps early can save your grade.
- The “Nice Job” Trap: Starting with excessive praise can dilute your critical edge. While positivity is good, leading with “Great paper!” often signals that you haven’t found anything substantive to critique. Instead, start with a specific observation: “Your thesis clearly identifies the conflict between fate and free will.”
- The “Vague Suggestion” Trap: Saying “You should add more evidence” is unhelpful. It places the burden of research back on the writer without guidance. Instead, be specific: “Consider adding a quote from Act 2, Scene 2 to support your point about guilt.” This shows you’ve engaged with the text and have a concrete idea.
- The “Personal Opinion” Trap: Phrases like “I didn’t like this paragraph” or “I think this is boring” are subjective and unprofessional. Critique the argument, not the writer. Instead of “I didn’t like this,” try “This paragraph’s transition feels abrupt. How does this point connect to the previous claim?” This keeps the focus on the intellectual work.
Avoiding these pitfalls requires discipline. When you feel yourself drifting into summary or vague praise, pause. Ask: “Is this comment helping the writer improve their argument?” If the answer is no, rewrite it. Focus on the logic, the evidence, and the structure. This shift in focus transforms your feedback from a polite note into a critical tool. It’s the difference between saying “The cake is sweet” and “The sugar overwhelms the lemon flavor; consider reducing it by half.”
The Single Most Important Truth: Analysis Is a Conversation
The core truth you must walk away with is this: Critical analysis is not a verdict; it is a conversation. Your tutorial response is not a final judgment on your peer’s worth as a writer. It is an invitation to think deeper, to question assumptions, and to refine arguments. When you approach feedback as a collaborative dialogue, you remove the pressure of being “right” and replace it with the goal of being “useful.”
This mindset shift changes everything. Instead of fearing that you’ll hurt someone’s feelings, you see yourself as a partner in their intellectual growth. You are helping them see blind spots they couldn’t see alone. This perspective makes the task less intimidating and more meaningful. It also aligns perfectly with your professor’s expectations. They want to see that you can engage with ideas critically, not just consume them passively.
So, tonight, as you write your response, remember: you are not a judge. You are a fellow scholar. Ask hard questions. Point out gaps. Suggest alternatives. Be specific. Be kind. But above all, be analytical. Your peer’s draft is a work in progress, and your feedback is a crucial part of that process. Embrace the role of the critical friend, and you’ll not only meet the rubric’s requirements—you’ll actually help your classmates become better writers. That is the true value of a tutorial response.