Below are ready-to-use examples of peer reviews you can copy today for workplaces, classrooms, and academic manuscripts, along with simple fill-in-the-blank templates. Use a proven structure like SBI (Situation–Behavior–Impact–Next step) to keep feedback specific and actionable—for example: “In Monday’s client call (Situation), you summarized the scope changes concisely (Behavior), which kept the meeting on track (Impact). Next time, send a recap to stakeholders within 24 hours (Next step).”
If you came here searching for examples of peer reviews you can copy today, start with the quick examples and templates below, then adapt them with specific details: what happened, what the person did, what result you saw, and one practical next step. Keep it short (two to six sentences), send within 48 hours, and balance one strength with one growth suggestion so the message reads as supportive rather than personal.

15 examples of peer reviews you can copy now (plus templates)
Use these short, copy-ready comments as-is or tweak the details. Each example follows an evidence-based pattern to make your feedback clear and constructive.
Six quick workplace examples (SBI format)
- Communication – positive: In Tuesday’s sprint review (Situation), you explained the backlog trade-offs in plain language (Behavior), which helped the team align quickly (Impact). Next time, consider adding a one-page summary before the meeting (Next step).
- Communication – constructive: During Wednesday’s status update (Situation), you used several acronyms without defining them (Behavior), and a few stakeholders looked confused (Impact). Next time, define key terms or add a glossary slide (Next step).
- Collaboration – positive: On the Q2 launch (Situation), you coordinated design and QA handoffs smoothly (Behavior), which reduced last‑minute fixes (Impact). Let’s document your handoff checklist so others can reuse it (Next step).
- Collaboration – constructive: In our cross-team thread last week (Situation), your replies came a day late (Behavior), which delayed approvals (Impact). Consider setting a daily 15-minute window to clear requests (Next step).
- Leadership – positive: When morale dipped after the incident (Situation), you opened the retro with empathy and specifics (Behavior), which kept discussion productive (Impact). Keep using that opener; maybe add anonymous prompts to gather more voices (Next step).
- Leadership – constructive: During the vendor meeting (Situation), we jumped into solutions before aligning on the problem (Behavior), and we reworked the plan twice (Impact). Next time, start by restating the problem in one sentence and confirming it (Next step).
Three student/classroom examples (WWW/EBI)
- Essay clarity – WWW/EBI: What went well: your thesis is clear and the topic sentences guide the reader. Even better if: add a counterargument paragraph with a citation to strengthen your claim.
- Lab report – WWW/EBI: What went well: your methods are reproducible and variables are labeled. Even better if: include a short error analysis and one graph per key result.
- Group project – WWW/EBI: What went well: you kept the team calendar accurate. Even better if: add brief agendas before meetings so everyone arrives prepared.
Three academic manuscript snippets (respectful and evidence‑based)
- Summary: The paper addresses a timely question and offers a clear conceptual model. The literature review is thorough, though recent work from 2023–2025 could be added.
- Major concern: The sample size limits generalizability. Please report a power analysis and describe any sensitivity checks that support the estimates.
- Minor concern: Figure 2 labels are hard to read. Consider larger fonts and consistent color scales for readability.
Three fill-in-the-blank templates
- SBI (workplace): In [time/place] (Situation), you [specific behavior] (Behavior), which [result or impact] (Impact). Next time, [one practical next step] (Next step).
- WWW/EBI (student): What went well: [strength]. Even better if: [one concrete improvement].
- COIN (code/engineering): Context: [module or PR]. Observation: [what you saw]. Impact: [how it affects users or maintainers]. Next: [action].
Mini guide: Ideal length is two to six sentences; send within 48 hours of the event while memory is fresh; and run a quick bias check by removing subjective labels and focusing on observable behavior.
For a broader refresher on giving effective feedback and structuring formal reviews, see our guide Master Performance Reviews & Give Effective Feedback, which complements the examples on this page.
Examples of peer reviews by context
Different settings call for different language and lengths. Use the examples below to match your scenario, then adapt specifics. When the context shifts, the tone, depth, and expected formality shift with it—adjust your wording accordingly.
Workplace: collaboration, communication, leadership
Collaboration
- Positive: On the onboarding revamp (Situation), you paired developers with support staff for shadowing (Behavior), which surfaced four friction points early (Impact). Next: repeat the pairing in the next cohort.
- Constructive: In the handoff to marketing (Situation), requirements changed three times without an update (Behavior), which created rework (Impact). Next: post a brief change log in the shared channel after decisions.
- Balanced: You invite diverse views (Behavior), which improves decisions (Impact). Next: time‑box debates to preserve delivery cadence (Next).
- Constructive: On the roadmap sync (Situation), side threads pulled focus (Behavior), which extended the meeting (Impact). Next: park tangents in a follow-up doc.
- Positive: When the project slipped (Situation), you proactively scheduled a recovery plan review (Behavior), helping the group align on priorities (Impact). Next: keep a simple “risks” column in the tracker.
Communication
- Positive: In the client kickoff (Situation), your agenda and pre‑reads (Behavior) kept the call within 30 minutes (Impact). Next: attach a one‑slide timeline to your pre‑reads.
- Constructive: Yesterday’s email summary (Situation) mixed decisions with open questions (Behavior), and a few readers missed the ask (Impact). Next: add a header with “Decisions / Open Questions / Requests.”
- Constructive: During daily standups (Situation), updates sometimes skip blockers (Behavior), which delays support (Impact). Next: end with a 10‑second “blockers/no blockers” round.
- Positive: In Thursday’s demo (Situation), you used customer quotes to frame features (Behavior), which improved stakeholder buy‑in (Impact). Next: save those quotes in a shared library.
- Constructive: In the design review (Situation), we spent time on color debates (Behavior), and decisions stalled (Impact). Next: anchor to criteria first, then iterate options.
Leadership
- Positive: After the incident review (Situation), you assigned clear owners and dates (Behavior), which restored confidence (Impact). Next: include a two‑week follow‑up on action items.
- Constructive: In Q1 planning (Situation), we set 11 priorities (Behavior), and focus suffered (Impact). Next: choose a top five and say what we will not do.
- Positive: You share credit publicly (Behavior), which elevates the team (Impact). Next: keep a running list of shout‑outs for the monthly meeting.
- Constructive: In a tough 1:1 (Situation), your feedback arrived as a surprise (Behavior), and the conversation turned defensive (Impact). Next: schedule lighter monthly check-ins to avoid pile‑ups.
- Positive: When the new teammate joined (Situation), you paired them with two buddies (Behavior), which sped up onboarding (Impact). Next: write a short welcome doc template others can reuse.
For more on leading conversations that stick, see Leadership Communication for Clearer Teams and Better Decisions and our guide to building collaborative habits, Collaborative workers: a practical guide for small businesses.
Student/classroom: thesis clarity, structure, evidence
- Thesis clarity: What went well: your thesis statement is precise and answers the prompt. Even better if: connect paragraphs 2 and 3 with a transition and a brief signpost.
- Structure: What went well: each paragraph has a clear topic sentence. Even better if: consolidate overlapping points and keep one idea per paragraph.
- Evidence: What went well: citations follow MLA and quotes are framed. Even better if: add one source that challenges your view and explain why your claim still stands.
- Voice and style: What went well: verbs are active and sentence lengths vary. Even better if: cut filler phrases (“in order to,” “at this time”) to increase clarity.
- Visuals: What went well: figures are labeled. Even better if: add descriptive captions and reference them in text.
Academic/research: summary, major/minor concerns, figures
- Summary: The research question is original and the design supports credible inference; the discussion connects findings to theory.
- Major concern: The identification strategy needs clearer assumptions. Please describe exclusion restrictions and provide robustness checks in an appendix.
- Major concern: The instrument’s validity is uncertain. Report first-stage F‑statistics and discuss potential violations.
- Minor concern: The introduction repeats methods details. Consider moving those lines to the methods section to streamline the narrative.
- Minor concern: Figure 3’s legend duplicates axis labels. Simplify to avoid redundancy.
Engineering/code review: readability, performance, tests (COIN)
- Readability: Context: auth middleware. Observation: variable names shadow env vars. Impact: future readers may misconfigure secrets. Next: rename with a consistent prefix and update docs.
- Performance: Context: report generator. Observation: the query runs N+1 times. Impact: latency spikes in large accounts. Next: use a join and preload associations.
- Tests: Context: PR #248. Observation: edge cases for null inputs aren’t covered. Impact: risk of 500s during import. Next: add two unit tests and one integration test.
- Security: Context: uploads controller. Observation: missing content‑type validation. Impact: possible execution of disallowed files. Next: enforce a whitelist and add server‑side checks.
- Docs: Context: API breaking change. Observation: changelog lacks migration notes. Impact: clients may ship regressions. Next: add a migration guide with examples.
Frameworks that make feedback easy (SBI, STAR, COIN, BOOST, WWW/EBI)
Each framework gives you a skeleton so you can write feedback in minutes. Choose one that fits the time you have and the complexity of the situation.
- SBI: Situation, Behavior, Impact, Next step—fast, factual workplace feedback.
- STAR: Situation, Task, Action, Result—useful when the person had a defined task.
- COIN: Context, Observation, Impact, Next—great for code and engineering changes.
- BOOST: Balanced, Observed, Objective, Specific, Timely—reminds you to balance and time feedback well.
- WWW/EBI: What Went Well, Even Better If—simple, kind structure for students and peer workshops.
Before/after rewrites
Vague to SBI: “Great job on the meeting.” → “In Friday’s stakeholder meeting (S), you paused to confirm decisions (B), which avoided rework (I). Next time, send action items within a day (N).”
Vague to STAR: “Nice project work.” → “On the onboarding redesign (S), your task was to reduce time‑to‑value (T). You simplified the tour (A), and activation rose 8% (R).”
Vague to COIN: “Code looks fine.” → “Context: payment handler. Observation: retry logic falls back to default after three attempts. Impact: possible double charges. Next: move the fallback behind an idempotency check.”
Vague to BOOST: “You’re always late.” → “Observed: twice this week standups started after 9:05. Objective: we lose 10 minutes daily. Specific: arrive by 9:00 or post a delay note. Timely: let’s start tomorrow.”
Vague to WWW/EBI: “Good draft.” → “What went well: your introduction hooks the reader. Even better if: compress paragraph two and add a counterpoint.”
How to choose a framework
- Little time? Use SBI or WWW/EBI. They fit in two to four sentences.
- Need to capture a whole task? Use STAR to spotlight the task and result.
- Technical change? Use COIN so observations and next steps are explicit.
- Balance and timing concerns? Use BOOST as a reminder checklist.
Frameworks vs. use cases (comparison table)
| Framework | Structure | Best for | Tone | Typical length | Example sentence | When not to use |
|---|---|---|---|---|---|---|
| SBI | Situation–Behavior–Impact–Next | Workplace | Direct | 2–4 sentences | In the demo, you clarified scope, which avoided rework; next time share notes. | Deep, multi‑month projects—use STAR. |
| STAR | Situation–Task–Action–Result | Workplace, student | Supportive | 3–6 sentences | On migration, your task was risk reduction; your rollback plan saved time. | Quick incidents—use SBI. |
| COIN | Context–Observation–Impact–Next | Code/engineering | Direct | 2–5 sentences | Context: cache layer; observation: stale keys; impact: wrong data. | Nontechnical reflections—use SBI or STAR. |
| BOOST | Balanced–Observed–Objective–Specific–Timely | Workplace | Supportive | 2–4 sentences | Observed two delays; objective impact 10 min; specific expectation shared. | Academic manuscripts—use structured review formats. |
| WWW/EBI | What Went Well / Even Better If | Student, workshops | Supportive | 2–3 sentences | WWW: vivid intro. EBI: add counterexample. | High‑stakes incidents—use SBI. |
Peer review phrases by competency (copy/paste)
Keep phrasing neutral, specific, and behavior‑focused. Copy these and customize the details.
Communication
- Positive: You restated the decision points at the end of the meeting, which kept everyone aligned.
- Constructive: Your email mixed proposals with decisions; separating them will help readers act.
- Neutral starter: When you presented the roadmap, you paused for questions every slide, which increased engagement.
- Constructive: Slide text ran long; moving detail to the appendix may help.
Collaboration
- Positive: You invited ops early, which surfaced risks before we shipped.
- Constructive: Thread replies came late this week; setting a daily check‑in could speed decisions.
- Neutral starter: Pairing with QA on test plans reduced defects.
- Constructive: Decision notes weren’t posted; a short recap would support cross‑team awareness.
Leadership
- Positive: You shared context first, which made the decision smoother.
- Constructive: We had too many priorities; choosing a top five would keep focus.
- Neutral starter: You redirected debate back to the objective when it drifted.
- Positive: You connected individual goals to the team’s outcomes, which motivated the group.
Problem‑solving
- Positive: You framed the outage as a hypothesis list and tested the top two quickly.
- Constructive: We jumped to solutioning; next time, write a one‑sentence problem statement first.
- Neutral starter: Your decision tree clarified trade‑offs.
- Constructive: Risk log entries missed dates; adding owner + date will clarify urgency.
Time management and initiative
- Positive: You batched approvals before lunch, which reduced context switching for the team.
- Constructive: Several tasks carried over; time‑boxing similar work may help.
- Neutral starter: You flagged a timeline risk early, which allowed us to adjust scope.
- Positive: You blocked a focus window daily, which increased throughput.
For more routines that support strong time habits, see Maximise productivity: 12 time management tips.
Common mistakes and bias‑free rewrites
Mistake: vague praise
- Instead of: Great work
- Say: In Thursday’s retro, you summarized themes crisply, which helped us pick two actions.
Mistake: personality labels
- Instead of: You’re disorganized
- Say: The last two updates arrived after the deadline; adding a daily reminder may help.
Mistake: absolutes
- Instead of: You always interrupt
- Say: In Monday’s meeting, you spoke while two others were mid‑sentence; pausing raised others’ participation.
Mistake: subjective comparisons
- Instead of: You’re the best communicator on the team
- Say: Your pre‑reads consistently include context and decisions, and stakeholders respond quickly.
Mistake: stacking feedback
- Avoid dumping multiple issues in one message. Pick one topic and one next step per note.
- Spacing feedback over time helps people act without feeling overwhelmed.
Mistake: risky references
- Avoid comments about protected classes (age, race, religion, etc.), family status, or off‑duty life.
- Keep feedback tied to work behavior and outcomes, not identity or personality.
Mistake: sarcasm or loaded words
- Instead of: Nice of you to show up on time for once
- Say: Today’s on‑time start kept us on schedule; let’s repeat that this week.
When peer review isn’t appropriate
- Serious misconduct or safety issues should not be handled via peer review comments. Use formal reporting channels.
- If you suspect retaliation, harassment, or policy violations, document facts and escalate according to your HR policy.
- If you feel unsafe giving feedback, choose a written channel or involve a manager.
A 5‑minute peer review workflow and checklist
Here is a quick routine you can run after any significant interaction. The steps help you capture facts quickly, reduce bias, and deliver a clear, respectful message.
- Capture Situation (60 seconds): Note the date, meeting, or artifact (PR, document, class).
- Describe Behavior (60 seconds): Use neutral verbs: explained, asked, shared, delayed.
- Explain Impact (60 seconds): Time saved, confusion reduced, risk lowered, rework created.
- Add one Next step (30 seconds): Be specific and doable within a week.
- Check bias (60 seconds): Remove labels and subjective adjectives; keep verifiable facts.
- Send or deliver (60 seconds): Choose chat/email if simple; meet if sensitive.
- Follow‑up plan (60 seconds): Document in your notes; revisit in two to four weeks.
Reviewer checklist
- Define the situation (time/place).
- Describe observable behavior.
- Explain impact with a result.
- Add one clear next step.
- Check for bias/loaded words.
- Balance strength + growth.
- Confirm a follow‑up date.
FAQs: people also ask
How do I give feedback to a peer review (or reviewer)? Thank them for the effort, restate what you heard, and respond point‑by‑point. If you disagree, share evidence and propose an alternative. Keep tone factual and appreciative.
What is a performance appraisal vs. a peer review? A performance appraisal is a formal evaluation led by a manager, often tied to compensation. A peer review is one colleague’s feedback to another, usually focused on behaviors and outcomes from shared work. Peer reviews feed into appraisals but do not replace them.
Can you give me some examples of good review comments? Yes—see the sections above for communication, collaboration, leadership, problem‑solving, and time management examples, plus templates like SBI and WWW/EBI.
How do I write good feedback for a colleague? Focus on a single event, describe what you observed, explain the impact, offer one next step, and send within 48 hours. Balance one strength and one growth area.
What are short positive comments for evaluation? Try: “Your pre‑reads clarified decisions,” “You invited the right voices,” “Your test plan caught two edge cases,” or “You flagged a timeline risk early.”
Downloadable templates and the side‑by‑side comparison table
Use this section as a quick snapshot or screenshot for your team. Pair it with your internal review norms and keep it close to your workflows. If you want a broad complement to these tools, see Tips for keeping your best employees motivated, which fits well with peer feedback programs.
| Context | Primary goal | Typical length | Where delivered | Example snippet | Common pitfalls |
|---|---|---|---|---|---|
| Workplace | Reinforce effective behavior; suggest one next step | 2–6 sentences | Chat, email, 1:1 | In yesterday’s call you summarized scope; next time send a recap | Vague praise; personality labels; absolutes |
| Student | Encourage learning with kind, specific guidance | 2–3 sentences | Peer workshop, class notes | WWW: strong thesis. EBI: add counterargument | Grading tone; focusing on person, not work |
| Academic | Evaluate rigor; recommend revisions | Short paragraphs | Journal system | Sample size limits; add power analysis | Harsh language; unsubstantiated claims |
| Code | Improve maintainability, correctness | 2–5 sentences | PR tools | Context: cache; observation: stale key; next: expire policy | Nitpicking style; unclear action items |
If you want a one‑page printable pack with SBI, COIN, and WWW/EBI templates plus the checklists above, save this page and share it with your team.
