Career Growth Tools

Manager & Peer Review Helper

Write fair, specific and constructive performance reviews as a manager or colleague. Based on observed behaviours and real contributions — not vague impressions.

Review Details

You Are Writing A *

Writing Tone

Who You Are Reviewing
About You (The Reviewer)
Your Observations
Be specific — describe what you saw, not general impressions

Your Review Will Appear Here

Select your reviewer role, fill in your observations and click Generate Review to get a professional, ready-to-submit review.

Manager & peer formats Fully editable Fair & specific
Review Best Practice

How to Write Reviews That Are Fair and Useful

Describe behaviours, not traits
Do not write "James is lazy." Write "James missed three sprint commitments this quarter without proactively flagging blockers." Specific behaviours are observable, discussable and actionable. Personality judgements are not.
Use recent, specific examples
Recency bias is real — we remember the last 2-3 months most clearly. Keep notes throughout the year. Cite specific projects, dates and outcomes. "In Q3, during the platform migration..." is far more credible than general impressions.
Balance strengths and development
A review with only positives is not credible. A review with only criticism is demoralising. Every employee has both — a balanced review shows you have thought carefully and care about their growth, not just their shortcomings.
Focus on impact, not effort
"Sarah worked hard" is unmeasurable. "Sarah's refactoring of the authentication module reduced login failures by 40%" is impact. Focus on what changed as a result of their work — not how busy they appeared to be.
Avoid bias — check your language
Watch for language that reflects proximity bias (remote workers), affinity bias (people like you), or gender bias (women are "assertive", men are "confident"). Review your text before submitting and ask: would I write this differently for someone else?
Share the review before submitting
The best practice in performance management is no surprises. If your review contains critical feedback, it should not be the first time the employee hears it. Ongoing coaching throughout the year makes the formal review a summary, not a shock.

Related Career Growth Tools

Self-Assessment Generator
Write your own performance review
Raise Calculator
Model the impact of any raise
Salary Negotiation Script
Word-for-word negotiation guide
Salary Benchmark Tool
Know your team's market worth

Frequently Asked Questions

A manager review is written by someone with supervisory responsibility for the employee — it typically includes a performance rating, goal setting and decisions about compensation or promotion. A peer review is written by a colleague at the same level and focuses on observed collaboration, communication and contribution. Peer reviews do not usually include formal ratings.

Manager reviews: 400-700 words covering performance summary, 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.

Every person has areas where they could grow — even top performers. The question is how you frame development areas constructively. Instead of criticism, phrase it as opportunity: "I would love to see Sarah take on more cross-functional leadership — her instincts are strong and the broader team would benefit." This is honest without being damaging.

For peer reviews, this is usually anonymous — check your company's process. For manager reviews, best practice is to discuss the content with the employee in a 1:1 conversation rather than just submitting it. A review should never contain surprises — anything written should have been discussed or at least signalled during the period.

Be honest about the scope of your observation. You can write: "My interaction with James has been primarily through the Q3 cross-functional project." Only comment on what you have directly observed. A shorter, honest review from limited exposure is more useful than a longer one filled with assumptions.

Be specific, factual and unemotional. Cite specific instances, not general impressions. Frame development areas as expectations that were not met, with clear examples. Always include what support or resources were available. Avoid phrases like "attitude problem" or "difficult personality" — stick to observable behaviours and measurable outcomes.