Collaborative Margin Comments¶

Strategy · All strategies
Evidence · 2 claims (1 for, 1 mixed) · 4 studies (3 quant-synthesis, 1 causal), q3–q4 · 3 of 4 report an effect size

Description¶

Collaborative margin comments involve using collaborative document platforms (Google Docs, Microsoft Word Online, Hypothesis) to provide feedback anchored to specific passages of a document. Instructors and peers add comments, suggestions, and questions in the margin, tying each piece of feedback to the exact text it concerns and enabling iterative revision and dialogue in place.

Design Implications¶

Margin comments localize feedback at the point of need, which reduces the translation burden learners face when interpreting general comments and supports revision as an ongoing process rather than a terminal event Feedback is most effective when directed at the task and process levels. [+S]. Because comments are visible to all collaborators, they also expose learners to models of evaluative judgment — seeing how others diagnose a peer's draft builds the criteria they apply to their own writing.

Context¶

Requirements¶

• A collaborative platform with commenting/suggesting features (Google Docs, Word Online, Hypothesis for annotation of readings)
• Explicit criteria or a rubric so comments target substantive issues rather than surface edits
• A revision cycle in which learners must respond to comments — feedback without required revision rarely changes writing behavior
• Norms or training for constructive peer commentary (Coaching on comment quality early in a course)

Constraints¶

• Comments focused on surface features (grammar, formatting) produce minimal learning gains; without guidance, peer comments drift there Feedback is most effective when directed at the task and process levels. [-S]
• Comment overload — dozens of margin notes on one draft — can overwhelm working memory and lead learners to accept changes mechanically rather than reason about them Cognitive overload degrades learning. [~M]
• Learners unfamiliar with the platform or with giving critique produce thin or purely social comments ("nice job!") without initial training
• Asynchronous-only commenting can stall dialogue; unresolved comment threads leave confusion about which suggestions stand

Implementation Variability¶

• Instructor-only commenting on drafts, with revision required before grading
• Reciprocal peer review in pairs or small groups, each commenting on the other's draft
• Whole-class open commenting, where all students see and can build on each other's margin notes
• Social annotation of readings (Hypothesis, Perusall), where margin comments are the discussion itself rather than feedback on writing
• Audio or video margin comments (voice comments in Google Docs), which convey tone and reduce misinterpretation

Target Learners¶

• Secondary and higher-education students engaged in writing-intensive coursework
• Adult and professional learners revising reports, proposals, or code documentation collaboratively
• Developing writers benefit most from process-level, location-specific comments; strong writers may find heavy commenting intrusive Feedback is most effective when directed at the task and process levels. [~M]

Target Learning Goals¶

• Iterative writing improvement: drafting, receiving feedback, revising
• Evaluative judgment: internalizing criteria by critiquing others' work
• Collaborative knowledge construction: building shared understanding of a document in context

Instructions¶

1. Share the draft through a collaborative platform with commenting enabled and set a revision deadline.
2. Provide a rubric or comment prompt sheet so reviewers address ideas, structure, and evidence — not just mechanics (Annotating).
3. Assign reviewers (peers, instructor, or both) and require a minimum number of substantive, location-specific comments.
4. Have writers respond in-thread to each comment — accept, question, or push back — making the feedback a dialogue.
5. Require a revised draft and, ideally, a short reflection on which comments the writer acted on and why (Assessment of the revision, not just the comments).

Related Strategies¶

• Peer review with structured rubrics — margin comments are the medium; the rubric is what makes them substantive
• Social annotation of course readings — the same mechanism applied to texts rather than drafts
• Portfolio revision cycles — margin comments supply the formative layer between portfolio drafts

Examples¶

• Google Docs (https://docs.google.com) — instructors and peers comment in margins; suggestion mode tracks proposed edits that writers accept or reject individually.
• Hypothesis (https://web.hypothes.is) — social annotation layer used in many university courses for collaborative margin discussion of assigned readings.
• Perusall (https://www.perusall.com) — platform that scores annotation quality and uses margin comments as the primary reading-discussion mechanism.
• SWoRD Peer Review (Cho & Schunn, 2007) — web-based reciprocal peer review system in which scaffolded, location-anchored comments improved writing quality across large undergraduate classes.

Key Sources¶

• Cho, K., & Schunn, C. D. (2007). Scaffolded writing and rewriting in the discipline: A web-based reciprocal peer review system. Computers & Education, 48(3), 409–426. doi:10.1016/j.compedu.2005.02.004
• Graham, S., & Perin, D. (2007). A meta-analysis of writing instruction for adolescent students. Journal of Educational Psychology, 99(3), 445–476. doi:10.1037/0022-0663.99.3.445
• Hattie, J., & Timperley, H. (2007). The power of feedback. Review of Educational Research, 77(1), 81–112. doi:10.3102/003465430298487
• Topping, K. (1998). Peer assessment between students in colleges and universities. Review of Educational Research, 68(3), 249–276. doi:10.3102/00346543068003249