
A performance evaluation is a structured review of an employee’s work, achievements, competencies and development needs during a defined period.
An evaluation may assess:
Organizations may conduct evaluations annually, quarterly, at the end of a probationary period or after an important project.
Well-written evaluation phrases can:
Evaluation phrases should be customized with relevant examples and evidence. Templates can provide structure, but they should not replace a manager’s judgment.
1. “Consistently arrives prepared and completes scheduled responsibilities without requiring additional reminders.”
2. “Provides appropriate notice when an absence may affect the team and helps arrange coverage for time-sensitive work.”
3. “Can be relied upon to follow through on commitments and communicate promptly when circumstances change.”
4. “Has improved attendance during this review period and is now meeting the team’s reliability expectations.”
5. “Needs to improve punctuality by arriving at the scheduled start time and notifying the manager before an anticipated delay.”
6. “Produces accurate work that consistently meets the department’s quality standards.”
7. “Reviews important details carefully and identifies errors before materials reach customers or stakeholders.”
8. “Maintains quality while handling a high volume of assignments.”
9. “Responds constructively when an error is identified and takes appropriate action to correct it.”
10. “Would benefit from using a final review checklist to reduce recurring formatting and data-entry errors.”
11. “Communicates project status, risks and required decisions clearly to relevant stakeholders.”
12. “Explains complex information in language appropriate for both technical and nontechnical audiences.”
13. “Listens carefully to questions and confirms understanding before responding.”
14. “Provides clear written instructions that help colleagues complete assignments efficiently.”
15. “Should communicate possible delays earlier so that the team has sufficient time to adjust priorities.”
16. “Contributes useful ideas while remaining open to alternative perspectives.”
17. “Supports colleagues during high-demand periods and shares information that helps the team succeed.”
18. “Builds positive working relationships across departments and follows through on shared responsibilities.”
19. “Recognizes the contributions of others and helps create an inclusive team environment.”
20. “Can improve collaboration by allowing colleagues to complete their comments before responding during meetings.”
21. “Sets clear expectations and provides team members with the resources needed to complete their work.”
22. “Leads by example through consistent preparation, accountability and professional conduct.”
23. “Provides useful coaching and adjusts guidance according to each employee’s experience level.”
24. “Makes timely decisions while considering relevant evidence and stakeholder perspectives.”
25. “Would benefit from delegating more operational work to create time for planning and employee development.”
26. “Identifies the underlying cause of problems rather than focusing only on immediate symptoms.”
27. “Develops practical solutions by gathering evidence and consulting colleagues with relevant expertise.”
28. “Regularly suggests process improvements that reduce unnecessary work.”
29. “Balances creative thinking with careful consideration of cost, risk and implementation requirements.”
30. “Can strengthen decision-making by comparing several possible solutions before selecting an approach.”
31. “Prioritizes high-impact assignments and consistently meets agreed deadlines.”
32. “Manages several projects effectively without losing visibility into important details.”
33. “Uses project plans and interim milestones to maintain steady progress.”
34. “Has increased productivity while maintaining the expected level of quality.”
35. “Should develop more realistic time estimates and communicate when competing priorities may affect delivery.”
36. “Responds to customer inquiries promptly and provides accurate, easy-to-understand information.”
37. “Demonstrates patience and professionalism when resolving difficult customer concerns.”
38. “Uses customer feedback to identify opportunities for improving the service experience.”
39. “Sets realistic expectations and follows up until the customer’s issue is resolved.”
40. “Can improve customer communication by acknowledging concerns before explaining policies or limitations.”
41. “Actively requests feedback and applies it to future assignments.”
42. “Takes responsibility for decisions and addresses mistakes without shifting blame.”
43. “Has developed new technical capabilities that allow the employee to complete more complex work independently.”
44. “Demonstrates initiative by identifying useful actions before receiving detailed instructions.”
45. “Would benefit from establishing measurable development goals and reviewing progress with the manager each month.”
46. “Has made meaningful progress during this review period and is prepared to take on broader responsibilities.”
Focus on what the employee did rather than making a general judgment about personality.
Vague: “Jordan is careless.”
Specific: “Jordan submitted three reports without completing the required data review.”
Connect the behavior to customers, quality, deadlines, revenue or team performance.
Example: “Communicates possible scheduling conflicts early, allowing the project team to adjust resources before deadlines are affected.”
Use relevant examples, metrics and completed projects.
Example: “Reduced the average response time from eight hours to four hours by introducing a shared support queue.”
Constructive feedback should explain what successful improvement looks like.
Example: “For the next quarter, use the project checklist before submitting each client report.”
Recognize strengths while addressing meaningful development needs. Avoid hiding serious issues behind overly positive wording.
You can use this structure:
Observed behavior + effect on work + expected continuation or improvement
For example:
“Taylor provides complete weekly updates, which helps stakeholders identify risks early. Continue using this format and include budget variance in future reports.”
For development feedback:
“Taylor has missed two internal review deadlines, which reduced the time available for quality checks. Create interim milestones and communicate risks at least two business days before the deadline.”
“Casey consistently produces accurate financial reports and communicates unexpected variances clearly. During this review period, Casey redesigned the monthly reporting process, reducing preparation time by 20%. The next development opportunity is to document the new process and train another team member.”
“Casey demonstrates strong technical knowledge, but several project updates arrived after stakeholders needed them. During the next quarter, Casey will provide a written update every Friday and raise schedule risks as soon as they are identified. We will review progress during monthly one-on-one meetings.”
Avoid:
Important performance issues should generally be addressed when they occur rather than saved for an annual review.
Review goals, project results, feedback and previous development commitments.
Ask the employee to complete a self-review or identify important achievements.
Consider available resources, changing responsibilities and obstacles outside the employee’s control.
Select a manageable number of development goals rather than creating an extensive list.
Performance development should continue after the evaluation meeting.

Dokie can help managers turn performance data, employee achievements and development goals into clear review presentations. It can also help employees organize self-evaluations, project summaries and evidence of professional growth.
Use Dokie to prepare structured performance discussions and development roadmaps. Verify all metrics, protect confidential information and ensure final decisions remain grounded in fair human evaluation.
Effective performance evaluation phrases describe specific actions, business impact and future expectations. They recognize employee contributions while making development feedback easier to understand and apply.
Customize each phrase with evidence from the review period. A useful evaluation should create a shared understanding of performance and the next steps for growth.
It may include goals, achievements, competencies, development needs, employee comments and agreed next steps.
Comments should be long enough to provide evidence and direction. One to three focused sentences per competency may be sufficient.
Yes, but each comment should be customized according to the employee’s actual work and responsibilities.
Serious concerns should normally be discussed when they occur. An annual review should not be the first time an employee learns about a longstanding issue.
Many organizations conduct formal reviews annually or quarterly while providing informal feedback throughout the year.