•
10 Mins Read.

A useful performance review explains what an employee contributed, where performance needs to change, and what happens next. The examples below give managers adaptable language for recognizing strengths, addressing shortcomings, and agreeing on development goals. Use them as starting points for a conversation grounded in evidence, not as substitutes for judgment, preparation, or listening.
What should managers write in a performance review?
Write about observable behavior, its impact, and the expectation going forward. Strong employee performance evaluation comments identify work the employee can recognize, explain why it mattered, and describe what to continue or change. Avoid turning an isolated incident into a judgment about someone’s character.
These two illustrative comments show the difference:
Recognizing a strength: “Your project handover identified unresolved decisions and assigned owners, giving the delivery team a clear starting point. Continue using that structure for cross-team transitions.” Use this when a handover genuinely supported execution. The wording connects a repeatable behavior to its value; adapt it by naming the actual document, project, and recipients.
Addressing a weakness: “The last two handovers omitted outstanding customer questions, so the receiving team had to investigate them again. For the next handover, include open questions, owners, and escalation dates.” Use this for a documented completeness issue. It describes the gap without labeling the employee careless; adjust the required fields to match the role.
All performance review examples in this article are fictional templates. Replace their details with verified observations, and remove any outcome you cannot substantiate.
What an effective performance review should achieve
Treat the review as a working agreement, not simply a completed form. Aim to leave the conversation with a shared understanding of performance and a practical route forward.
A useful review should establish:
An accurate account of contributions: Identify results, judgment, collaboration, and less-visible work that mattered during the review period.
Clear performance expectations: Explain how the employee’s work compares with agreed responsibilities, rather than with a colleague’s personality or working style.
Focused development priorities: Select the changes that matter most instead of producing an unmanageable improvement list.
Mutual commitments: Record what the employee will do and what support the manager will provide.
A follow-up plan: Decide when to examine progress and what evidence will demonstrate improvement.
CIPD’s evidence review emphasizes that employees’ perceptions of an appraisal’s fairness and usefulness influence its effectiveness. It also recommends distinguishing developmental conversations from administrative discussions about matters such as pay and promotion. Explain the purpose of your meeting rather than assuming it is obvious. (cipd.org)
Prepare for the conversation, not just the form
Successful performance reviews require preparation, judgment, active listening, clear language, and skillful navigation of difficult conversations. A polished paragraph cannot compensate for weak evidence or an unwillingness to hear another perspective.
Build an evidence base and exercise judgment
Review the full evaluation period: objectives, work samples, project records, previous feedback, and relevant stakeholder observations. For each concern, distinguish what you observed from what someone reported and what you inferred. Ask whether the employee had clear expectations, appropriate resources, and meaningful control over the outcome.
CIPD’s feedback evidence review recommends using credible information gathered through a reasonable, reliable process and giving employees an opportunity to respond. Apply that principle by checking disputed details before treating them as settled facts. (prod.cipd.org)
Use role expectations as your reference point. For a new hire, assess progress against agreed onboarding milestones; for an experienced employee, examine the independence and complexity the role requires. For remote or hybrid colleagues, look for documented contributions rather than rewarding visibility in the office.
Prepare to listen and speak clearly
Invite the employee to bring achievements, obstacles, and development priorities. Prepare open prompts about what helped or hindered delivery, where expectations differed, and what support would be useful. During the meeting, summarize their explanation before deciding whether it changes your assessment.
Edit vague language before the conversation. Replace “be more strategic” with the planning behavior you need, such as identifying dependencies before proposing a delivery date. State concerns directly, then pause; do not bury the main message beneath qualifications or fill every silence with another criticism.
Rehearse difficult feedback with Oraton
Oraton offers AI-powered roleplay simulations for leadership conversations, including performance issues and tough feedback. Its custom scenarios and follow-up questions provide a way to rehearse a realistic review before speaking with the employee. The platform also offers feedback and opportunities to listen back and practice again. (speakwithoraton.com)
Use a fictionalized scenario to practice four tasks: communicating difficult feedback, responding to pushback, expressing clear expectations, and maintaining authority with empathy. Listen for whether your main point remains clear when the simulated employee challenges it. Try acknowledging an objection without withdrawing a justified expectation.
Treat rehearsal as preparation, not proof that the real conversation will unfold the same way.
Remove identifying or confidential information, follow your organization’s tool policies, and retain responsibility for the assessment.
A practical framework for specific feedback
Structure each important point around evidence, impact, expectation, support, and review. This is a practical drafting framework, not a research-validated scoring model.
Evidence: Identify the observable action and relevant situation. Separate a recurring pattern from a single event.
Impact: Explain the consequence you can substantiate. If the impact is uncertain, ask about it rather than inventing one.
Expectation: Describe what acceptable or stronger performance looks like in this role.
Support: Offer a resource, decision, coaching session, or access needed to make progress.
Review: Agree when and how you will examine the next work sample or outcome.
Use the framework selectively. Recognition may need only evidence, impact, and encouragement to continue; an ongoing performance gap usually needs all five elements. Leave room for the employee’s explanation before finalizing the plan.

Employee performance evaluation comments for strengths and weaknesses
The paired comments below cover common competencies. Choose only those relevant to the employee’s responsibilities; a performance review does not need an observation about every possible skill.
Communication: Make information usable
Strength: “Your weekly updates distinguish completed work, emerging risks, and decisions needed, helping stakeholders identify where to act.” Use this for updates that genuinely support coordination. The wording recognizes useful structure rather than charisma; adapt it to written updates, customer calls, or technical documentation.
Development: “Your updates describe activity but do not consistently identify decisions needed. Include the decision, owner, and requested response date in your next project update.” Use this when stakeholders lack actionable information. It defines the missing behavior without criticizing personality; for a new hire, provide a model update and review the first draft together.
Teamwork: Recognize contribution without rewarding overextension
Strength: “You shared the troubleshooting notes and walked the support team through unresolved issues, making your expertise accessible to others.” Use this when knowledge sharing is documented. It credits collaboration through concrete work; adapt it for mentoring, shift transitions, or cross-functional problem-solving.
Development: “You accepted additional requests without checking existing commitments, leaving teammates uncertain about delivery dates. Confirm capacity and agree priorities before taking on more work.” Use this when helpfulness has created coordination problems. It preserves recognition of intent while addressing impact; if competing managers assign work, clarify those priorities yourself rather than placing the entire burden on the employee.
Leadership: Set direction and enable decisions
Strength: “You clarified decision ownership before the launch and gave team members room to resolve issues within those boundaries.” Use this when a leader has delegated effectively. It identifies how leadership operated, not merely whether the launch succeeded; adapt it for a project lead without direct reports by naming the decisions they coordinated.
Development: “Routine approvals continued to come back to you after delegation, leaving ownership unclear. Agree which decisions team members can make independently and when escalation is required.” Use this for a documented delegation gap. It makes improvement observable; for a first-time manager, offer help defining boundaries rather than assuming they know how.
Problem-solving: Examine reasoning as well as outcomes
Strength: “You compared the available options, tested the highest-risk assumption, and explained the trade-offs before recommending a solution.” Use this when sound reasoning is visible in the work. It rewards a repeatable approach rather than luck; adapt it to operational troubleshooting, analysis, or customer issues.
Development: “Your recommendation moved directly to implementation without checking the underlying assumption. Before the next proposal, identify the main uncertainty and explain how you will test it.” Use this where premature conclusions are documented. It gives a manageable next step; adjust the testing requirement to the decision’s risk and available time.
Accountability: Close the loop
Strength: “When the dependency changed, you alerted the team, proposed a revised sequence, and followed the issue through to resolution.” Use this when the employee took responsibility for coordination despite not causing the problem. It distinguishes ownership from blame; adapt it by naming the escalation or recovery action that mattered.
Development: “After escalating the issue, you did not confirm who owned the next action. Keep responsibility for tracking progress until another owner explicitly accepts it.” Use this for incomplete follow-through. The wording specifies a handoff standard; adapt it where formal escalation procedures limit what the employee should manage personally.
Productivity: Balance delivery, quality, and priorities
Strength: “You completed the agreed priority work and flagged lower-priority requests before accepting them, keeping delivery aligned with the team’s commitments.” Use this when prioritization is supported by records. It recognizes judgment rather than constant busyness; adapt it for service roles by including relevant quality requirements.
Development: “Several low-priority requests were completed while the agreed deliverable remained unfinished. Review competing requests with me before changing the sequence.” Use this when priorities were previously clear. It targets allocation of effort rather than assumed motivation; if instructions were contradictory, acknowledge that and reset the priorities together.
Professional development: Connect learning to application
Strength: “You applied the new analysis method to the planning report and explained its limitations to the team.” Use this when learning has translated into work. It recognizes application and judgment, not just course completion; adapt it to technical training, mentoring, or a stretch assignment.
Development: “The training is complete, but we have not yet seen the method used in your work. Choose an appropriate assignment, apply it, and bring the result to our next coaching discussion.” Use this when application is an agreed objective. It creates a practical bridge from learning to execution; provide an opportunity if the employee has not had one.
Performance review examples for four performance levels
These employee performance review examples demonstrate how an overall assessment can remain balanced without blurring the performance category. Use your organization’s rating definitions, and make sure the narrative supports the rating.
Outstanding performance
“You exceeded the role’s expectations by identifying a recurring handover problem, coordinating a shared solution, and helping other teams adopt it. Your contribution extended beyond your own assignments. Next, document the approach and coach a colleague to maintain it without relying on your continued involvement.”
Use this when evidence shows sustained contribution beyond normal role requirements. The wording explains the distinction rather than relying on superlatives. Adapt the development step to the employee’s interests; broader influence need not mean promotion into people management or an indefinite increase in workload.
Meeting expectations
“You delivered the agreed work to the required standard, kept stakeholders informed, and raised blockers appropriately. Your reliability supported the team’s commitments. For the next period, develop greater independence in resolving routine exceptions, with coaching available for unfamiliar cases.”
Use this when the employee consistently fulfills the role. It recognizes solid performance without presenting an ordinary development opportunity as a deficiency. Adapt the next step to the role’s scope; meeting expectations should not automatically require taking on responsibilities belonging to a higher-level position.
Inconsistent performance
“Your analysis has been thorough when milestones were planned early, but several assignments required late corrections after rushed reviews. The priority is making your quality checks consistent. Schedule a review point before submission, and we will examine the next completed assignments together.”
Use this when the evidence shows variation rather than a uniform shortfall. The wording acknowledges demonstrated capability while naming the unreliable behavior. Adapt it after examining workload, task complexity, and changing instructions; do not assume inconsistency reflects effort when assignments had materially different conditions.
Underperformance
“The role requires complete case records before transfer. Recent records omitted required information despite earlier guidance, leaving the receiving team unable to proceed. This is below the expected standard. We will review the requirements together, use the agreed checklist, and examine subsequent records at scheduled check-ins.”
Use this when an established requirement remains unmet and the evidence supports the assessment. The wording makes the seriousness clear without attacking character. Adapt support and review timing to the work; if formal performance procedures apply, coordinate with the appropriate internal team rather than improvising consequences.
Handling difficult performance review conversations
Constructive feedback should not conceal the problem. State the evidence, invite relevant context, and explain the next expectation without making the employee agree with every interpretation before progress can begin.
Missed targets
“The agreed target was not met. Let’s examine the pipeline decisions, available opportunities, and obstacles so we can distinguish what you could influence from what needs management action.”
Use this when the result is clear but its causes need examination. It avoids equating a missed target with poor effort. Adapt the discussion to the role’s leading indicators, then agree corrective actions only after identifying the relevant gap.
Poor communication
“The schedule changed, but the affected teams were not informed before they planned their work. For future changes, notify the named contacts when the decision is confirmed.”
Use this for a specific notification failure, not a broad dislike of someone’s communication style. It identifies the timing and audience required. Adapt the channel to the team’s workflow, and confirm that the employee knew who needed the update.
Lack of ownership
“You identified the blocker but left the next action unassigned. I expect you to propose an owner or escalate the decision, then confirm the handoff.”
Use this when responsibility stopped at identifying a problem. It explains ownership without demanding that the employee solve everything alone. Adapt the expectation to their authority: a junior employee may need to escalate, while a manager may be expected to allocate resources directly.
Resistance to feedback
“You disagree with this assessment. Let’s examine the examples and any information I may have missed. The requirement remains that customer commitments are recorded before handoff.”
Use this when disagreement threatens to derail a documented expectation. It separates openness to evidence from uncertainty about the standard. Adapt your response if new information changes the assessment; disagreement itself is not proof of a poor attitude or unwillingness to improve.
Turn feedback into goals and development objectives
Choose goals that follow directly from the review. For straightforward work, define the expected result; for unfamiliar or complex work, include learning and experimentation rather than insisting on an outcome the employee cannot yet reasonably predict. CIPD’s research distinguishes between goal-setting approaches for straightforward and complex tasks and emphasizes the importance of feedback. (cipd.org)
The following are illustrative goal structures, not universal targets:
Review finding | Goal to adapt | Manager support and evidence |
Updates lack decision requests | Use an agreed update format for the next project cycle | Provide a model; inspect whether decisions, owners, and dates are explicit |
Handoffs omit information | Complete the required checklist before each transfer during the agreed review period | Clarify required fields; review a sample of completed records |
Delegation remains unclear | Establish decision boundaries for one recurring team responsibility | Coach the planning conversation; examine how exceptions were handled |
New skills remain unused | Apply the learned method to a suitable assignment and explain the result | Provide access to the assignment; discuss choices and limitations |
Agree a review date and define what satisfactory progress looks like before leaving the meeting. Avoid imposing arbitrary numbers merely to make a goal appear measurable. A work sample, documented decision, or demonstrated skill may provide more relevant evidence.
Help employees prepare a useful self-review
Invite a self-assessment that connects contributions to responsibilities and identifies lessons. Ask employees to distinguish their own work from the team’s collective achievement. Use their account to identify evidence you missed, not as a test of confidence or writing ability.
Achievement example: “I clarified the intake requirements and coordinated agreement between support and operations. The revised checklist became the shared handoff reference.” Use this when the employee can show the document and their contribution. Its strength is attribution; adapt it by separating what the employee led from what others delivered.
Development example: “I delayed escalating a dependency because I expected to resolve it independently. Next time, I will use the agreed escalation point and bring options.” Use this for honest reflection on a real decision. It combines accountability with a change in practice; adapt the escalation point to the employee’s authority and workflow.
Common performance evaluation mistakes to avoid
When adapting performance appraisal examples, check the underlying judgment as carefully as the wording. A polished sentence still needs accurate evidence and a defensible expectation.
Letting recent events dominate: Review evidence across the full period before deciding whether an incident represents a pattern.
Using personality labels: Replace “difficult,” “lazy,” or “not leadership material” with observable behavior and its relevance to the role.
Softening the message beyond recognition: Recognize strengths honestly, but state a material shortfall directly rather than hiding it between unrelated compliments.
Comparing employees with each other: Assess against role expectations. Different assignments, resources, and opportunities make casual comparisons a poor basis for your explanation.
Attributing everything to the individual: Examine unclear direction, dependencies, and resource decisions alongside employee actions.
Saving important feedback for the annual meeting: Address current issues when they arise, then use the formal review to assess the broader pattern.
CIPD places structured reviews within a wider performance-management approach, rather than treating them as the entire process. Use ongoing conversations to keep expectations and feedback current. (prod.cipd.org)
A manager’s checklist before, during, and after the review
Before the meeting
Check objectives, previous commitments, and evidence from across the review period.
Compare your narrative with the rating definitions and remove unsupported conclusions.
Invite the employee’s perspective and identify questions you genuinely need answered.
Prepare clear language for the hardest point and rehearse likely responses.
During the conversation
Explain the purpose and give a clear overall assessment.
Discuss specific examples, then listen without immediately defending your interpretation.
Separate disputed facts from established expectations and note what needs checking.
Agree priorities, support, evidence of progress, and a follow-up date.
After the conversation
Share an accurate record of the assessment, commitments, and unresolved questions.
Correct factual errors and follow through on promised resources or decisions.
Review actual work against the agreed expectations at check-ins.
Recognize improvement, address continuing gaps, and adjust support when circumstances change.
FAQ: Review wording and ratings
How should comments explain a mixed rating?
Explain which responsibilities were fulfilled and which were not, then connect the overall rating to your organization’s definitions. Do not average unrelated impressions or let a single strength erase a material shortfall. If the rating remains unclear, seek internal calibration before presenting it as final; the employee should receive a coherent explanation, not your unresolved debate.
What can managers write when reliable metrics are unavailable?
Use verifiable work samples, documented decisions, quality requirements, and specific observations. Explain what the evidence demonstrates and where its limits lie. Performance evaluation examples do not need invented percentages to be credible; when evidence is insufficient, acknowledge the limitation and agree how future performance will be observed rather than manufacturing certainty.
Make the next conversation more useful
A strong performance review connects evidence with expectations and turns those expectations into supported action. Select the examples that fit, replace hypothetical details with facts, and give the employee room to contribute. Then keep the commitments visible through regular follow-up.
For the conversation you are least comfortable having, practice before the meeting. Use Oraton’s AI-powered roleplay to rehearse difficult leadership feedback, test your clarity, and work on responding with both authority and empathy. Bring that preparation, not a rigid script, into the real discussion.
Download the app now and rate us on the App Store and Google Play.
Thanks for reading!

















