Evaluating employee performance starts with picking a structured method, defining clear rating criteria, and writing feedback that’s specific enough for the employee to act on. Whether you’re building a review process from scratch or improving an existing one, the samples below cover rating scales, evaluation phrases, role-specific metrics, and frameworks you can adapt to your team.
Choose an Evaluation Framework
Before you write a single review, decide how you’ll measure performance. The framework you pick shapes what questions you ask, who provides input, and how you score results. Here are the most widely used approaches.
Management by Objectives (MBO): You and the employee set specific goals together at the start of a review period, then measure progress against those goals. Because both sides agree on targets upfront, objectives tend to be realistic and easy to quantify. The downside is that a narrow focus on hitting goals can overlook important factors like teamwork or workplace conduct.
360-Degree Feedback: Performance ratings come from multiple directions: the employee’s manager, peers, direct reports, and sometimes clients or vendors. This gives a fuller picture than a single manager’s perspective, but it takes more time to collect and synthesize.
Behaviorally Anchored Rating Scale (BARS): You define a set of performance standards with specific, observable behaviors at each level. For example, a “3 out of 5” on customer service might be anchored to “responds to client emails within 24 hours and follows up on unresolved issues.” BARS reviews are consistent and impartial once built, but developing the behavioral anchors for every role is time-consuming.
Graphic Rating Scale: You list desired traits for a role (teamwork, accountability, time management, job knowledge) and rate the employee on each one using a numeric or descriptive scale. It’s the simplest method to implement and the most common in small and midsize organizations. The tradeoff is subjectivity, since different reviewers may interpret traits differently.
Peer Review: Coworkers who interact with the employee daily provide the feedback. Peers often have the clearest view of day-to-day strengths and weaknesses, though personal relationships can color the results. Peer review works best as a supplement to manager evaluations, not a replacement.
Sample Rating Scales
A 1-to-5 numerical scale is the most popular format. You assign a label to each number so every reviewer interprets the scores the same way. Here are three variations you can use directly or customize.
- Standard five-point: 1 = Unsatisfactory, 2 = Needs Improvement, 3 = Meets Expectations, 4 = Exceeds Expectations, 5 = Outstanding
- Development-focused: 1 = Unacceptable, 2 = Requires Development, 3 = Satisfactory, 4 = Good, 5 = Excellent
- Standards-based: 1 = Rarely Meets Standards, 2 = Inconsistently Meets Standards, 3 = Meets Standards, 4 = Meets High Standards, 5 = Exceeds High Standards
A four-point scale (Regularly Low Performance, Developing Skills, Highly Valued Performance, Top Performance) removes the neutral midpoint and forces reviewers to lean positive or negative. This can reduce the tendency to rate everyone as “average,” but it can also frustrate managers who feel a middle rating is genuinely accurate.
Whichever scale you choose, keep it symmetrical: an equal number of options below and above the center. Write a one-sentence definition for each level and share it with all reviewers before reviews begin so scores are calibrated across teams.
Sample Evaluation Phrases
Vague feedback like “good communicator” or “needs to do better” doesn’t help anyone improve. Anchor your comments to observable behavior. Below are sample phrases organized by competency and performance level that you can adapt to your reviews.
Communication
Exceeds expectations: “Coworkers and clients feel comfortable coming to this employee with questions. When unsure of an answer, they escalate to the appropriate person rather than guessing, which keeps information accurate and builds trust.”
Needs improvement: “Has received multiple complaints about unclear or contradictory information. Phone messages left for colleagues are often incomplete, leading to delays and follow-up calls.”
Teamwork
Exceeds expectations: “Consistently demonstrates team-player behavior and views individual success as connected to group success. Is direct, straightforward, and polite in interactions.”
Needs improvement: “Displays occasional negativity when collaborating with others. Rarely offers to help colleagues and sometimes makes comments that strain working relationships.”
Productivity and Quality
Exceeds expectations: “Regularly completes assignments ahead of deadline with minimal errors. Proactively identifies process improvements that reduced the team’s average turnaround time this quarter.”
Needs improvement: “Missed three of five project deadlines in the review period. Submitted work frequently requires revision due to avoidable errors.”
Notice the pattern: each phrase names a specific behavior or outcome, not a personality trait. “Missed three of five deadlines” gives the employee something concrete to address. “Lacks motivation” does not.
Role-Specific Metrics to Track
Generic competencies like teamwork and communication apply everywhere, but the most useful evaluations also include measurable outputs tied to the employee’s actual job. Here are sample KPIs (key performance indicators) for common departments.
Sales
- Lead conversion rate: What percentage of inbound leads turn into qualified opportunities, and what percentage of those become orders?
- Average sales cycle time: How many days from first contact to closed deal?
- Pipeline value: Total dollar value of deals in progress.
- Upsell and cross-sell percentage: How often does the rep expand revenue within existing accounts?
- Sales target percentage: Actual revenue compared to quota.
Customer Service
- First response time: How quickly does the employee reply to a new ticket or call?
- First contact resolution rate: What share of issues are resolved in a single interaction, without needing a follow-up?
- Issue volume by type: Tracking which categories of problems the employee handles reveals specialization and workload distribution.
Technical and Project-Based Roles
- On-time delivery rate: Percentage of tasks or sprints completed by the agreed deadline.
- Defect or rework rate: How often does completed work need to be corrected?
- Code review turnaround or documentation accuracy: Measures quality and collaboration speed in engineering or technical writing roles.
Pick two to four KPIs per role. More than that dilutes focus. Make sure each metric is something the employee can directly influence, not a number driven mostly by external factors like market conditions or staffing levels outside their control.
Reducing Bias in Your Evaluations
Even well-intentioned reviewers fall into patterns that skew results. Recency bias means you overweight whatever happened in the last few weeks and forget strong performance from six months ago. The halo effect means one impressive trait (say, charisma) inflates scores across unrelated categories. Here’s how to counteract these tendencies.
Start by calibrating goals at the beginning of the review period. Employees in similar roles should have goals set at a comparable level of difficulty. Define upfront what “meets expectations” and “exceeds expectations” look like for each goal so you’re not inventing the standard after the fact.
Collect input from multiple sources who have direct knowledge of the employee’s work. A single manager’s view is inherently limited. Peer feedback, project leads, and internal clients all add data points that balance individual blind spots.
Keep a running log of performance notes throughout the review cycle. Even a brief weekly note (“handled the vendor dispute calmly, resolved in one call” or “missed the Tuesday report deadline”) protects you from recency bias and gives you concrete examples to reference during the review.
Finally, calibrate ratings across managers before finalizing them. When multiple managers review their scores side by side, it becomes obvious if one team’s “exceeds expectations” is another team’s “meets expectations.” This step is especially important in larger organizations where consistency across departments matters for promotions and compensation decisions.
Putting It All Together: A Sample Review Template
Here’s a simple template that combines the elements above into a single-page evaluation form you can adapt.
- Employee name, role, review period, reviewer name
- Goals from prior period: List each goal, the target outcome, and whether it was met, partially met, or not met.
- Core competencies (rated 1-5): Communication, Teamwork, Quality of Work, Reliability, Problem-Solving. Include one to two sentences of behavioral evidence for each rating.
- Role-specific KPIs: Two to four measurable metrics with actual results vs. targets.
- Strengths summary: Two to three sentences highlighting what the employee does well, with examples.
- Development areas: Two to three sentences identifying where improvement is needed, with specific behaviors or outcomes to work on.
- Goals for next period: Collaboratively set two to four objectives with clear success criteria.
- Employee comments: Space for the employee to respond or add context.
Keep each review focused. A page or two of well-chosen evidence and clear ratings is more useful than a ten-page document that tries to cover everything. The goal is a conversation starter, not a legal brief. When the employee walks away knowing exactly what they did well, what needs to change, and what’s expected next, the evaluation has done its job.