Google Docs Peer Feedback for Courses: Comments & Rubrics (2026)

Each student needs their own Google Doc containing the work to be reviewed. You have two options: students create their own documents and share them with you, or you create a set of blank documents in a shared Google Drive folder and assign one to each student. The second approach gives you more control over permissions. Either way, name the documents consistently — something like "Assignment 3 — [Student Name]."

This is the step that makes or breaks the workflow. The document owner needs to share the document with their assigned reviewer as a "Commenter." Not Viewer, which blocks feedback. Not Editor, which lets the reviewer change the original text directly. Commenter is the right permission level — it allows comments and suggestions without giving full editing access. If you created the documents in a shared folder, you can set folder-level permissions so that everyone in the cohort can comment on any document in the folder.

Don't skip this step. Without a rubric, peer feedback tends to be vague, polite, and not particularly useful. Create a short document — half a page is plenty — that tells reviewers exactly what to evaluate. For a writing assignment, you might ask: "Does the introduction clearly state the problem being solved? Is there at least one specific example in each section? Is the conclusion actionable?" Share the rubric as a separate Google Doc that reviewers keep open alongside the work they're reviewing.

Post the assignments clearly — a simple list in your course discussion area or a shared spreadsheet showing who reviews whom. For most courses, pairing each student with two reviewers works well. You can assign pairs randomly, strategically (pairing students with different strengths), or let students choose. Random assignment is the simplest to manage. Make sure every student is both giving and receiving feedback — the learning happens on both sides.

Give students a clear window — typically three to five days — to complete their reviews. Specify both a start date and an end date. Without a firm deadline, peer feedback drags on indefinitely and loses its value. A tight window also creates a shared rhythm that makes the activity feel like an event rather than a chore.

After the feedback window closes, bring the group together — in a live session, a discussion thread, or a short video — to reflect on what they learned from the process. Ask questions like: "What was the most useful piece of feedback you received?" or "What did you notice about your own work after reading someone else's?" The debrief is where peer feedback becomes a learning activity rather than just an editing exercise.

Before asking students to review each other, show them what useful feedback looks like. Take a sample document (not a real student's work) and walk through your own commenting process. Show how you anchor a comment to a specific passage, how you phrase a suggestion constructively, and how you use suggestion mode to propose a concrete edit. Five minutes of modeling saves hours of vague comments later.

Asking a peer reviewer to evaluate everything about a document is asking too much. Narrow the focus to two or three specific dimensions per review round. "This week, focus on whether the examples are specific enough and whether the structure flows logically." A focused review produces deeper comments than a broad one, and it's less intimidating for students who are new to giving feedback.

Google Docs lets the document author mark a comment as "resolved," which collapses it without deleting it. Encourage students to resolve each comment after they've either acted on it or decided not to. This creates a visible record of engagement with the feedback. As the instructor, you can reopen the comment history to see both the original feedback and the author's response.

Google Docs comments are not anonymous. Every comment shows the reviewer's name and profile picture. For many course activities this is fine — it builds community and accountability. But for situations where honest critical feedback might be inhibited by social dynamics, the lack of anonymity can soften feedback to the point of uselessness. If anonymity matters, you'd need a dedicated peer review tool.

The commenting interface can feel awkward for delivering critical feedback. There's no tone of voice, no facial expression — just text in a margin. Students who are uncomfortable giving negative feedback may avoid it entirely, or phrase it so gently that the author misses the point. The rubric helps here, but it doesn't fully solve the problem. Remind students that specific, constructive criticism is a gift, not an attack.

Google Docs has no built-in rubric or scoring system. You can't attach a rating scale to a comment or generate a summary score from multiple reviewers. The feedback is qualitative and unstructured unless you impose structure through your rubric document. For courses that need formal peer grading with numerical scores, a tool like Peerceptiv or your LMS's built-in peer review feature will be a better fit.