Peer Review

Peer Review is a collaborative learning activity in which participants exchange their work and give each other structured feedback against a defined rubric or set of criteria. The review is not open-ended opinion — it is criteria-anchored evaluation that trains both the reviewer's eye and the author's ability to process critique. The learning comes from both sides of the exchange at once: the reviewer builds the evaluative eye they need to audit their own work going forward, which is the mechanism that actually accelerates skill development, and the author gets specific, actionable feedback they can use to revise. Peer Review is sometimes called peer critique, especially in creative and design contexts; the structural moves are the same.

At its core, Peer Review is a skill-development activity that uses feedback as the vehicle, not a feedback-delivery activity that happens to involve peers. The act of auditing another participant's work with a specific rubric is how a practitioner builds the judgment to audit their own work — and self-audit is what separates participants who plateau from participants who keep leveling up the skill they are actually practicing in their professional lives.

Peer Review has deep roots in writing instruction. The process-writing movement of the 1970s and 1980s — Peter Elbow's Writing Without Teachers (1973), Donald Murray's work on revision — established peer response as a core learning activity long before it was formalized in the research literature. Keith Topping's 1998 Review of Educational Research meta-review consolidated the academic evidence, documenting strong effects on both giving and receiving ends of the review. Nancy Falchikov's Improving Assessment Through Student Involvement (2005) provided a book-length treatment of peer and self-assessment across higher education. David Nicol, Avril Thomson, and James Breslin's 2014 research in Assessment & Evaluation in Higher Education extended the findings to show that reviewing others' work is itself a strong learning mechanism — often stronger than receiving feedback on one's own.

Peer Review sits at a distinct point in the collaborative family. Where Gallery Walk produces breadth of cohort-wide engagement and Reciprocal Teaching builds comprehension through rotating leadership on shared material, Peer Review builds judgment through structured evaluation of peer work against explicit criteria. The rubric is what separates the activity from casual feedback exchange — it is the teachable object that travels with participants after the session ends.

What It Is

Four structural components define Peer Review.

• Participant-produced work. Each participant has brought or produced an artifact the cohort will review — a draft, a structure, a plan, a design, a piece of writing, a workflow. The work is reviewable, which means it is concrete enough to be evaluated rather than abstract or in-progress.
• A defined rubric or review criteria. The specific dimensions the reviewer evaluates against. The rubric is explicit, shared in advance, and teachable — naming it is itself part of the learning. Peer Review without a rubric collapses into opinion exchange; the rubric is the activity's load-bearing element.
• A structured exchange protocol. How work moves between participants, how feedback is given, and what form the feedback takes (written comments, rating against each criterion, ranked strengths and gaps). The protocol protects the review from drifting into general reaction.
• Reflection on both giving and receiving. The activity teaches both sides at once. The reviewer builds judgment by applying the rubric; the author gets specific feedback to use and, often, sees their own work more clearly after reviewing someone else's. The debrief names both.

When to Use It

Peer Review fits workshops where participants have produced concrete, reviewable work and where the cohort can meaningfully evaluate each other at a comparable level. It is especially strong when the rubric itself is part of what participants are learning — reviewing teaches them what makes the work good.

Good candidates:

• Cohorts where participants need to level up a skill they actively use in their professional work — the practice of auditing another participant's work with a specific rubric is the mechanism that builds the evaluative eye participants need to audit their own work going forward. This is the highest-leverage use of Peer Review.
• Participant-produced artifacts (drafts, structures, plans, workflows, designs) that are concrete enough to evaluate against criteria.
• Content where the rubric is teachable and transferable — participants leave the session with criteria they can apply to their own future work.
• Cohorts working at roughly similar skill levels, so peer evaluation produces useful feedback in both directions.
• Sessions of 45 to 90 minutes, with enough time for reviewing plus feedback exchange plus reflection.

Less suitable:

• Work where only an expert can give meaningful feedback — if the rubric requires judgment participants do not yet have, peer review produces false confidence.
• Cohorts with large skill disparity — advanced participants receive little from less advanced reviewers, and the review dynamic becomes uneven.
• Abstract or in-progress work that is not yet concrete enough to evaluate.
• Sessions too short to run meaningful review plus exchange plus reflection (under 45 minutes).

In-Person and Virtual Delivery

Peer Review runs in both in-person and virtual delivery, with virtual delivery offering a distinct advantage: work can be distributed and reviewed asynchronously before the live session, which lets the live time focus on the exchange and reflection rather than on reading. In-person delivery keeps the whole activity inside the session but depends on work that can be read quickly.

In person. Participants bring printed copies of their work, or the work is posted on flip chart paper around the room. The rubric is handed out or posted visibly. Pairs exchange work and review in place, with handwritten comments on the artifact itself. After the review, pairs exchange verbal feedback in a structured protocol — strengths first, then gaps, then one specific suggestion per criterion. The workshop leader circulates to keep the exchange on the rubric. In-person delivery has a small advantage in the feedback exchange: the back-and-forth is live, and the author can ask clarifying questions in real time.

Virtual. Work is distributed through a shared platform before the session — a document, a slide, a worksheet — with the rubric included. Participants review their assigned partner's work asynchronously between the assignment and the session, which means the live time is spent on feedback exchange and reflection rather than on reading. During the session, breakout rooms of two host the structured feedback exchange. Written comments can persist on the shared document, which gives each participant a durable record of the feedback they received. Virtual delivery's advantage is the separation of reading from exchanging — participants come to the exchange having already done the review work, which usually produces sharper feedback than time-pressured in-session reading.

Choosing the modality. Virtual is often slightly stronger for Peer Review, specifically because the asynchronous-review + live-exchange split uses both time well. In-person delivery works cleanly when the work is short enough to be read in the session or when the cohort is meeting face-to-face for other reasons. For mixed-modality cohorts, run Peer Review in a virtual-first hybrid — distribute the work before the session, hold the exchange live regardless of whether participants are in the same room.

How to Run It

Before the Session

1. Draft the rubric (leader design work). The rubric is the activity's load-bearing element (see Design Considerations). Draft it so each criterion is specific, teachable, and produces similar evaluations when two reviewers apply it to the same work.
2. Ask participants to bring or produce reviewable work. Either request participants bring a current draft, structure, or artifact to the session, or build production time into a preceding session segment. Each participant needs one concrete reviewable piece.
3. Consider asynchronous review for virtual cohorts. In virtual delivery, distribute the work and reviewer assignments before the session with the rubric attached. Participants review their partner's work in advance, which means the live session time can focus entirely on the feedback exchange and reflection — the higher-value parts.

During the Session

1. Share the rubric and teach it (8–12 minutes, if not already done async). Name the criteria explicitly. For each criterion, explain what meeting it looks like, what partial-meeting looks like, and what missing it looks like. Give a brief example. Participants need to understand the rubric before they can apply it.
2. Distribute and pair (3 minutes). Pair participants and exchange work. Assign first-round and second-round roles clearly — who reviews first, who reviews after.
3. Review against the rubric (12–20 minutes per direction, skipped if done async). Each reviewer reads their partner's work and marks it against the rubric. For each criterion not fully met, the reviewer writes one specific suggestion.
4. Feedback exchange (8–12 minutes per direction). Pairs exchange verbal feedback. The reviewer walks the author through what they marked, the author reacts and asks clarifying questions, the reviewer offers the specific suggestion for each gap. Then roles reverse for the second direction.
5. Reflection on both sides (10–15 minutes). Full-cohort debrief surfaces patterns. Ask two questions: what did you learn from reviewing someone else's work that you did not know before, and what did receiving feedback reveal about your own work? The two-sided reflection is the activity's deepest learning.

After the Session

1. Revise own work based on the feedback received (within one week). Participants take the feedback and make actual changes to their artifact. Revision is where the feedback becomes usable; a session that generates feedback without a revision step produces notes rather than improved work.
2. Apply the rubric to future own work — the self-audit discipline. This is Peer Review's highest-leverage outcome. Having internalized the rubric through applying it to someone else's work, participants turn it on their own future drafts in the weeks and months that follow. The self-audit is what separates participants who plateau from participants who keep leveling up the skill the session was designed to develop.
3. Bring the revised work to the next session (in multi-session cohorts). The cohort sees the revision against the original, which reinforces both the rubric and the self-audit discipline.

An Example in Practice

A 90-minute workshop for a cohort of twelve coaches working on their discovery calls. Each coach has brought the current structure of their first conversation with a prospective client — an outline, a script, or a notes template, whichever they actually use.

The workshop leader hands out a specific four-criterion rubric. Does the structure: (1) open with an explicit invitation for the prospect to describe their situation before the coach does any talking, (2) include at least three diagnostic questions that surface the real problem rather than accepting the stated one at face value, (3) move from diagnosis to a proposed working relationship rather than jumping straight to a pitch, and (4) close with a concrete next step the prospect can confirm or decline before the call ends.

The leader spends ten minutes teaching the rubric — what each criterion looks like when met, partially met, or missing, with a brief example for each. Pairs exchange their discovery call structures and begin reviewing.

Review runs fifteen minutes per direction. Each reviewer marks the four criteria, notes which are clearly met and which are gaps, and writes one specific suggestion for each gap they identified. The room is quiet.

Feedback exchange runs ten minutes per direction. The reviewer walks the author through what they marked. The author reacts, asks clarifying questions, pushes back where they disagree. Several pairs realize during the exchange that their own discovery calls have the same gaps they just identified in their partner's structure.

Full-cohort debrief runs fifteen minutes. The leader asks: what did you learn from reviewing someone else's discovery call that you did not know before, and what did receiving feedback reveal about your own. The patterns surface: most coaches realized they under-weight the opening invitation and over-weight the pitch-like close, and most coaches learned more from reviewing than from being reviewed.

Variations

• Blind Peer Review. Work is distributed without author names attached. Removes social dynamics — participants review on the rubric alone without social pressure to soften feedback for colleagues they know well. Used when the cohort is close-knit enough that identifiable review would compromise candor, or when the workshop leader wants to foreground the rubric over relationships.
• Double-Pass Peer Review. Each artifact receives two reviewers rather than one. Produces triangulated feedback — where two reviewers converge, the finding is robust; where they diverge, the author sees two legitimate reads. Used when the work warrants more review depth or when the cohort is large enough to allow two reviewers per piece without stretching time.
• Self-and-Peer Review. The author reviews their own work against the rubric before the peer review. The comparison between self-assessment and peer assessment often surfaces blind spots — places the author rated themselves high that the peer rated low, or vice versa. Used when metacognitive awareness is itself a target outcome.
• Expert-Anchored Peer Review. The workshop leader reviews one artifact first in front of the cohort, modeling the rubric application explicitly, before pairs review the remaining artifacts. Used when the cohort is new to the rubric or when the review requires judgment participants need to see demonstrated before they can apply it.

Which Method It Serves

Peer Review is primarily a Collaborative Learning activity. The paired exchange and rubric-anchored evaluation distribute real work across every participant, activating positive interdependence (each participant's feedback depends on the other's work, and the learning compounds across both), individual accountability (every participant carries out a full review and a full feedback exchange), structured interaction (the rubric and exchange protocol), and group processing (the two-sided reflection).

Peer Review also functions inside other methods. In Project-Based Learning, peer review is the iteration mechanism that moves artifacts from first draft to refined output across a multi-session program. In Case-Based Learning, peers can review each other's case analyses against a defined analytical rubric. In Inquiry-Based Learning, peers can review each other's investigations and proposed conclusions. In almost any method that produces participant artifacts, Peer Review is the natural mechanism for structured feedback.

Design Considerations

• The quality of the rubric determines the value of the activity. Peer Review is defined by the rubric. A vague or generic rubric — "is this clear? Is it effective?" — produces vague feedback that does not help the author revise and does not build the reviewer's eye. A specific, teachable rubric — criterion-by-criterion language for what meeting each looks like, what partial-meeting looks like, what missing looks like — produces feedback that is immediately usable and teaches participants what makes the work good as they apply it. Before running Peer Review, pressure-test the rubric: is each criterion specific enough that two reviewers applying it to the same work would arrive at similar evaluations, and does the rubric teach the reader something about the domain even before they apply it? If either answer is soft, the rubric needs revision before the activity is worth running.
• Keep review pairs small — two participants per review direction. The rubric-anchored evaluation works best with one reviewer per artifact per direction, and two participants per pair for the bidirectional exchange. Three or more reviewers per artifact fragments accountability and dilutes the feedback. The activity's pairing structure is tighter than the general home-group rule: pairs are ideal, triads work if the cohort count forces an odd number, four or more per review group is always wrong.
• Teach the rubric explicitly before any review happens. Participants who do not understand the rubric cannot give useful feedback, and they also cannot receive it well. Eight to twelve minutes of explicit rubric teaching — naming each criterion, giving an example of what meeting and missing look like — is not overhead. It is the preparation that makes the review work.
• Design the reflection around the skill being built, not just the feedback being exchanged. Peer Review's deepest learning is the evaluative eye the reviewer builds by auditing someone else's work against the rubric — an eye they can then turn on their own work long after the session ends. That skill is what separates participants who plateau from participants who keep leveling up. Debrief questions must draw out both sides of the exchange: what the reviewer noticed about their own work through the act of auditing someone else's (the skill-building half), and what receiving feedback revealed about work the author had previously felt satisfied with (the revision half). A reflection that only asks "what feedback did you get?" collapses the activity to half its value and hides the skill the participants just built.
• Do not substitute peer review for expert feedback when expert feedback is what the work needs. Peer Review teaches the review skill, surfaces common issues, and produces useful revision direction. It does not replace expert judgment on work that has grown past the level the cohort can evaluate. Peer review is a learning mechanism; it is not an assessment instrument at the edge of participants' skill.

Where this goes next: Peer Review anchors collaboration around structured feedback against a rubric. The final collaborative activity moves the dynamic into structured advocacy — participants are assigned positions on a question and defend them against each other under named protocols. See Structured Debate.

Related

Read this next:

• Structured Debate — the final collaborative activity; moves the dynamic into structured advocacy where participants defend assigned positions against each other under named protocols.

Foundations of this activity:

• Collaborative Learning — the primary method Peer Review serves; the two-sided rubric-anchored exchange is itself the collaboration.
• Project-Based Learning — the method Peer Review most often operationalizes when iteration is the design structure.
• Gallery Walk — the collaborative activity that produces breadth across cohort work; compare with Peer Review's depth on paired evaluation.
• The Guiding Principles of Active Learning — the principles Peer Review activates, especially honest reflection and focused outcomes.

Where this leads:

• Which Active Learning Method Fits Your Workshop? — Peer Review is the strongest sub-activity when iteration, rubric-based evaluation, or peer judgment-building is a target outcome.
• Project-Based Learning — the primary method Peer Review most often supports as the structured feedback cycle between drafts.

References

Falchikov, N. (2005). Improving assessment through student involvement: Practical solutions for aiding learning in higher and further education. RoutledgeFalmer.

Nicol, D., Thomson, A., & Breslin, C. (2014). Rethinking feedback practices in higher education: A peer review perspective. Assessment & Evaluation in Higher Education, 39(1), 102–122.

Topping, K. (1998). Peer assessment between students in colleges and universities. Review of Educational Research, 68(3), 249–276.