How to Use the Manager & Peer Review Helper

Overview

What Does the Manager & Peer Review Helper Do?

The WorkersPool Manager & Peer Review Helper is for writing a performance review about someone else — a team member you manage or a colleague you work alongside. You describe what you observed during the review period — their contributions, strengths, areas for development — and the AI produces a structured, professional review tailored to your role and relationship.

Two review types are supported: Manager Review (written by someone with supervisory responsibility — includes a performance rating and goals for the next period) and Peer Review (written by a colleague — focuses on collaboration, communication and observed contribution, without a formal rating). The output sections, AI framing and available fields differ between the two types.

Writing your own review? If you are an employee writing about your own performance, use the Self-Assessment Generator instead — it has the correct fields and output structure for a self-assessment.

Manager vs Peer Review

Which Type Should I Select?

Type	Written By	Includes	Does Not Include
Manager Review	Someone with supervisory responsibility — direct manager, skip-level, team lead	Performance rating, goal-setting for next period, full contribution assessment	N/A — all fields available
Peer Review	A colleague — same team, cross-functional, or internal stakeholder	Observed collaboration, communication, specific contributions	Formal performance rating, next period goals (manager-only fields are hidden)

The form adapts automatically when you switch between types — the Performance Rating and Goals for Next Period fields appear only for Manager Reviews, and are hidden for Peer Reviews. This keeps the peer review scope appropriate to what a colleague can credibly assess.

Relationship Types

The 6 Reviewer Relationship Options

Relationship	When to Choose It
Direct Manager	You have formal supervisory responsibility — you set their goals, approve leave, and conduct their annual review
Skip-Level Manager	You manage their manager — you have indirect oversight and see their work through your direct reports
Team Lead	You lead their day-to-day work and technical direction without formal HR management authority
Peer (same team)	You work on the same immediate team — you see their daily contributions and work side by side
Peer (cross-functional)	You are in a different team or department — you interact on shared projects or initiatives
Internal Client / Stakeholder	They deliver work to your team or function — you experience their output as a recipient or customer of their services

The relationship selection shapes the AI framing — a skip-level manager's review uses different language and scope than a same-team peer review. Always select your actual relationship for accurate output.

Writing Tones

Which Writing Tone Should I Choose?

Tone	Language Style	Best For
Constructive	Warm, development-focused — balances recognition with forward-looking growth framing	Strong performers; standard manager reviews; cultures that value coaching
Balanced	Even-handed and professional — gives equal weight to strengths and development areas	Most situations — particularly appropriate when performance is mixed
Formal	Precise and authoritative — appropriate for formal HR processes and documented performance management	Performance improvement situations; formal HR documentation; corporate cultures

Instructions

Step-by-Step Instructions

Select your review type — Manager or PeerChoose Manager Review if you have supervisory responsibility. Choose Peer Review if you are a colleague. This determines which fields appear and which output sections are generated.
Select your writing toneChoose Constructive, Balanced or Formal. Constructive is the default and suits most positive or mid-range performance situations. Formal is appropriate when the review will be used in HR documentation or performance management processes.
Enter the employee's detailsTheir full name (required), job title (required), department/team (optional) and review period. These appear in the review header and shape the AI's understanding of the person's role and seniority level.
Enter your reviewer detailsYour name (optional — appears in the result header), and your relationship to the employee. The relationship selector is critical — it determines the perspective and scope of the review. Select your actual relationship, not the most senior-sounding option.
Enter your key observations (the most important field)Describe the specific contributions and achievements you personally observed during the review period. Be specific — cite projects, outcomes, behaviours and interactions you actually witnessed. "Consistently delivered high-quality work" is generic and weak. "Led the API migration project and delivered it two weeks ahead of schedule despite a mid-project scope change" is specific and credible. You can only write credibly about what you actually saw.
Add strengths you observed (optional)2–3 specific strengths with behavioural evidence. Not personality labels ("she is great") but demonstrated qualities ("she consistently communicates blockers early and clearly, which has protected timelines on three consecutive projects").
Add areas for development (optional)Frame development areas as opportunities, not criticisms. "Would benefit from more structured stakeholder communication before escalating issues" is actionable and constructive. "Has an attitude problem" is not. Only include development areas you would say directly to the person in a 1:1.
Manager Review only — performance rating and goalsSelect the rating you are assigning (Exceptional through Below Expectations) and enter goals you are setting for the next period. These fields are hidden for peer reviews and appear automatically when Manager Review is selected.
Click Generate ReviewYour structured review appears with the appropriate sections for your review type. Each section is editable — click directly to personalise.
Personalise and verify before submittingAdd specific project names, dates and precise outcomes. Verify that every statement reflects something you actually observed — not something you heard secondhand or assumed.

Output Sections by Type

What the Tool Generates — Manager vs Peer

Manager Review Sections

Performance Overview — overall assessment framed at the right level for the rating assigned
Key Contributions & Results — specific achievements observed during the period
Strengths & Capabilities — demonstrated qualities with behavioural evidence
Development Areas — constructive growth opportunities
Goals for Next Period — manager-set goals and expectations for the coming cycle

Peer Review Sections

Collaboration & Teamwork — how they work with and alongside others
Key Contributions You Observed — specific contributions from your vantage point
Strengths — demonstrated qualities you personally witnessed
Areas for Growth — constructively framed development suggestions (no formal rating)

Worked Example

Example: Sarah Writes a Manager Review for James

Form Inputs — Manager Review

Review TypeManager Review

ToneConstructive

EmployeeJames Wilson / Software Engineer / Engineering

Review PeriodAnnual Review (full year)

Reviewer NameSarah Chen

RelationshipDirect Manager

Key Contributions ObservedLed API migration project — delivered 2 weeks ahead of schedule despite scope change; resolved a critical production issue on a Saturday preventing estimated $80K downtime; consistently mentored two junior developers through their first production deployments

Strengths ObservedExcellent under pressure, communicates blockers early, deep technical knowledge of the auth stack

Development AreasCould improve visibility of work-in-progress to team; sometimes takes on too much independently before flagging that support is needed

Performance RatingStrong — Exceeds Expectations

Goals for Next PeriodTake ownership of the new onboarding API project; complete AWS Solutions Architect certification; grow into a technical lead role by Q3

What Sarah Does Next

Reviews outputFive-section manager review generated — reads as fair and evidence-based

PersonalisesAdds specific date of Saturday incident, exact project name "Hermes API Migration", name of junior developers mentored

Tone checkSwitches to Balanced to compare — prefers Constructive, keeps it

ResultSubmits via HR system; James notes in their 1:1 that it is the most specific and fair review he has received in five years

Writing Principles

How to Write a Review That Is Fair and Useful

Do This

Describe specific behaviours and outcomes — not personality traits
Use recent, concrete examples with dates or project names where possible
Only comment on what you directly observed — not hearsay
Balance strengths and development areas — both are necessary
Frame development areas as growth opportunities, not criticisms
Write only what you would say directly to the person in a 1:1

Avoid This

"Has an attitude problem" — not observable or actionable
"Always" or "never" — almost always inaccurate and hard to defend
Recency bias — rating based on the last month rather than the full period
Affinity bias — rating more positively because you like them
Writing about things you heard about secondhand without witnessing directly
Surprises — if it is in the review, the employee should have heard it before

Disclaimer

Important Disclaimer

The Manager & Peer Review Helper produces AI-generated content for informational and assistance purposes only. Always review, personalise and verify accuracy before submitting. Only include statements about behaviours and outcomes you personally observed. All performance ratings and development feedback should reflect your genuine assessment. For performance improvement plans, disciplinary processes or formal HR actions, consult your HR department or employment counsel before relying on AI-generated text. WorkersPool accepts no liability for employment outcomes based on this tool's output. No data entered is stored on WorkersPool servers.

FAQ

Frequently Asked Questions

What is the difference between a manager review and a peer review?

A manager review is written by someone with supervisory responsibility and typically includes a formal performance rating, goal-setting for the next period, and carries formal weight in compensation and promotion decisions. A peer review is written by a colleague at the same level — it focuses on observed collaboration, communication and contribution, and does not include a formal rating. The distinction matters because they carry different authority and scope. This tool generates the correct structure and tone for each type automatically.

How long should a manager review be?

Manager reviews: 400–700 words covering performance overview, key contributions, strengths, development areas and next period goals. Peer reviews: 200–350 words focused on collaboration, communication and specific contributions you observed. Longer is not better — specific and evidence-based is better. A 250-word peer review with three concrete examples is more useful than a 600-word review full of generalities.

What if I have nothing critical to say about someone?

Every person has areas where they could grow — even exceptional performers. The question is how you frame it constructively. Instead of criticism, phrase development areas as opportunity: "I would love to see James take on more cross-team technical leadership — his instincts are strong and the broader organisation would benefit." This is honest and useful without being damaging. A review with no development areas at all reads as either uncritical or uninspired.

What if I am asked to review someone I do not work with closely?

Be explicit about the scope of your observation. You can open with: "My interaction with James has been primarily through the Q3 cross-functional platform project." Only write about what you directly observed. A shorter, scoped review from limited exposure is more credible and more useful than a longer one that speculates beyond your actual knowledge. Select "Peer (cross-functional)" or "Internal Client / Stakeholder" as your relationship type to set the correct framing.

How do I handle a review for someone who is underperforming?

Select the Formal tone and the appropriate performance rating (Developing or Below Expectations). Be specific, factual and unemotional — cite specific instances with dates and outcomes, not general impressions. Frame development areas as expectations that were not met, with clear examples. Include what support or resources were available. For any formal performance management process, consult your HR department before finalising the document — AI-generated text should be reviewed and approved by HR for use in disciplinary or PIP contexts.

Should I share what I wrote with the person being reviewed?

For peer reviews, this is usually anonymous — check your company's process before sharing. For manager reviews, best practice is to discuss the content with the employee in a 1:1 conversation rather than just submitting it to the system. A formal review should never contain surprises — if the feedback is in the written review, it should have been raised verbally during the period. The review is a summary of an ongoing conversation, not the first time they hear it.

The Other Review Tool

Employee Writing Their Own Review?

Self-Assessment Generator

If you are an employee writing about your own performance, use the Self-Assessment Generator — different fields, first-person output, and sections designed for self-reflection.

Open Self-Assessment Generator →

Review Writing Checklist

Before You Submit

✅ Every statement reflects something I personally observed
✅ I have cited at least 2 specific projects or outcomes
✅ Development areas are framed constructively
✅ I have not included anything the employee has not already heard from me
✅ The rating reflects the full review period — not just recent weeks
✅ I have checked for proximity, affinity or recency bias
✅ I have discussed the content (or will discuss) in a 1:1 with the employee

Manager & Peer Review Helper — Help Guide