HomeResourcesPeer Review Examples for Coworkers (Copy & Paste)

Peer Review Examples for Coworkers (Copy & Paste)

Copy-and-paste peer review examples for coworkers across cross-team help, quality, technical skill and constructive feedback, with a fill-in template.

6 min read

During performance review season, you are rarely asked to write only about yourself. Many 360-degree review cycles ask you to review three to five coworkers or cross-functional partners.

Writing peer reviews often feels stressful. Write something generic like "Alex is great to work with and a true team player," and you fail to give your peer the evidence they need for a promotion. Write something critical without tact, and you worry about creating tension next week.

A strong peer review is specific, professional, and grounded in real collaboration: what project you worked on together, what they did that made your job easier, and one practical suggestion for how you could work together even better.

Below are before-and-after rewrites, 16 copy-and-paste peer review examples across four common collaboration areas, and a fill-in template.

Before and after: from vague compliments to promotion-ready peer feedback

Weak (vague praise)Strong (specific collaboration proof)
Sarah is a great communicator and always friendly.Sarah's Friday status updates kept our cross-team rollout aligned without extra syncs; when legal requested late copy changes, she reorganized the review order so engineering never hit a blocker.
David is very technical and solves problems quickly.When our nightly export jobs failed in Q2, David traced the timezone bug within an hour, shipped the patch, and added regression tests so our on-call team stopped getting paged.
Elena works hard and helps the team.Elena created our team's first shared onboarding checklist and paired with two new hires this summer, which cut our ramp time and let new teammates take tickets in week two.
Marcus needs to improve communication.Marcus does great deep technical work, but sometimes goes quiet when a deadline is tight. Sharing rough drafts 48 hours earlier would give our design team more time to give feedback.

16 peer review examples by scenario

These are illustrative examples. Replace the details with your own work and only use numbers you can back up. Swap in your coworker's name and project details, and only reference work you directly observed.

1. Cross-functional partnership and handoffs

  • For a Product Manager / Project Manager peer: "Working with [Name] on the [Project] launch was seamless. They kept requirements clear, communicated scope trade-offs early when deadlines were tight, and shielded the build team from ad-hoc distractions. Thanks to their clear prioritization, we shipped on time with full cross-team alignment."
  • For an Operations / Support partner: "[Name] has been an invaluable partner for our team this half. Whenever customer escalations or billing questions arrived, they provided detailed repro steps and clear context rather than just tossing tickets over the fence, which helped us resolve issues in half the time."
  • For a Design / Content partner: "[Name] is exceptionally collaborative. On the [Campaign/Product] redesign, they walked engineering through early Figma iterations before specs were locked, which caught two technical edge cases early and saved us from rework later."
  • For a Business / Data Analyst: "[Name]'s pipeline dashboard gave our team complete visibility into weekly metrics for the first time. They took the time to explain the underlying logic during a 30-minute walkthrough, saving us hours of manual data pulls."

2. Execution, quality, and technical reliability

  • High quality and thorough testing: "[Name] consistently delivers robust, well-documented work. On the [System/Feature] release, they caught an edge-case permission issue in staging that would have affected enterprise users. Their attention to detail gives everyone confidence in what we ship."
  • Dependable under tight deadlines: "When dependencies slipped on [Project], [Name] stayed calm, re-prioritized the core checklist, and kept stakeholders informed every day. Their steady ownership was the main reason the team hit our commit date."
  • Removing recurring team friction: "[Name] doesn't just do their assigned tasks—they fix broken processes for everyone. Building the [new intake form / shared template] eliminated weeks of email back-and-forth for our entire department."
  • Clear, thoughtful code or spec reviews: "[Name] gives some of the most thorough and constructive reviews on the team. They explain the reasoning behind their suggestions and suggest practical alternatives, which has elevated the overall quality of our output."

3. Mentorship, onboarding, and team culture

  • Onboarding and unblocking new teammates: "[Name] went above and beyond as an onboarding buddy this half. They set up daily check-ins, documented answers to common setup questions in our wiki, and patiently unblocked new hires without making them feel rushed."
  • Generous with knowledge sharing: "[Name] is always willing to hop on a quick call to debug a tricky problem or explain complex legacy architecture. Their willingness to share context makes the whole group more effective."
  • Stepping up during coverage gaps: "When [teammate / lead] was out on leave, [Name] stepped in to triage incoming requests and run our weekly standups, ensuring our deliverables never lost momentum."
  • Fostering an open, constructive environment: "[Name] excels at encouraging different viewpoints during planning sessions. They make space for quieter team members to share ideas and keep discussions focused on the customer problem."

4. Constructive feedback examples (Areas for growth)

Constructive peer feedback should always be actionable, respectful, and tied to workflow efficiency rather than personal judgment:

  • Sharing work earlier: "[Name] delivers high-quality final work, but sometimes keeps drafts private until they are fully polished. Sharing rough one-pagers or early wireframes earlier in the cycle would allow partner teams to give input sooner and avoid last-minute revisions."
  • Delegating and setting boundaries: "[Name] is so helpful that they frequently take on ad-hoc requests from other teams, which occasionally stretches their timeline on core commitments. I'd love to see them say no or push back more often to protect their focus time."
  • Providing executive summaries: "[Name]'s technical analyses are exceptionally thorough. To make their updates even more impactful for busy stakeholders, starting with a 3-bullet 'key takeaway & next steps' box would make their insights easier to digest."
  • Documenting decisions in writing: "[Name] is great in 1:1 discussions, but decisions sometimes stay in Slack DMs. Summarizing verbal agreements in the project doc or Jira ticket would help cross-functional teammates stay aligned."

Fill-in template for a complete peer review

Copy this structure to write a balanced, promotion-ready peer review in under five minutes:

Review for: [Coworker Name]
Projects collaborated on: [Project Name / Recurring Workflow]

Strengths & Core Impact:
Working with [Name] on [project or queue] this period was [positive adjective, e.g., incredibly reliable / a standout experience]. Their biggest strength is [skill, e.g., proactive communication / thorough documentation]. Specifically, when [situation or obstacle occurred], [Name] [what they did], which allowed our team to [positive result or time saved].

Collaboration & Team Multiplier:
Beyond their direct deliverables, [Name] consistently supports the wider group by [onboarding others / clarifying specs / unblocking handoffs]. Their [attribute, e.g., calm problem-solving] makes them a trusted partner across teams.

Constructive Growth Opportunity:
One area where [Name] could have even greater impact is [specific suggestion, e.g., sharing early drafts a few days sooner / delegating routine triage]. As our projects grow in scope, this will help [positive outcome for them and the team].

Build your own review record at the same time

While you are reviewing your peers, remember that they are also writing reviews about you.

The easiest way to make sure your peers and manager have plenty of positive, concrete examples to point to is keeping your own work visible. Sending a clean weekly status update every Friday and logging your cross-team wins in a work brag sheet ensures nobody forgets what you delivered.

If you need to finish your own self-review form, check our guides on self-evaluation strengths examples, teamwork and collaboration examples, and areas for improvement examples.

Want to turn a rough note about a cross-team win into a polished accomplishment bullet right now? Paste it into our free STAR method generator (no sign-up). Or start free on WinStash to log your week in a minute and automatically synthesize your notes into weekly updates, brag sheets, and review stories.

Free tool · No sign-up

Turn one work note into a STAR story

Paste a sentence or two about something you did. You get a STAR story and a resume bullet that only use what you wrote.

Try the STAR generator

Frequently asked questions

What should I write if I only worked with this coworker on one project?

Focus entirely on that project. Name the specific handoff, document, or problem where they unblocked you, how they handled communication, and what the final result was. A detailed review of one project is far more useful than guessing at the rest of their year.

How do I give constructive feedback to a peer without damaging our relationship?

Focus on process rather than personality. Frame the feedback around timing or handoffs—such as sharing draft specs a few days earlier or clarifying acceptance criteria up front—and state how it will help the project move even faster.

Should I mention metrics or numbers in a peer review?

Only if you were directly involved in the result (e.g. "our joint launch delivered on schedule"). Otherwise, focus on operational reliability: responsiveness, thorough documentation, catching bugs early, and keeping commitments.

How long should a peer review be?

Two short paragraphs (around 70 to 120 words) is the sweet spot: one paragraph highlighting their biggest strength or impact, and one brief paragraph offering constructive feedback or encouragement for next period.

Write it down this week. Use it at review time.

WinStash keeps a short note from each week and turns your notes into a weekly update, a brag sheet and STAR stories, using only what you wrote.

Start free on WinStashFree plan · No credit card required

Keep reading

Self-evaluation examples by role: Operations Manager · Project Manager · Marketing Manager · Account Executive · Customer Success Manager · UX Designer