A formal evaluation of an employee's job performance, contributions, and growth over a specific period, typically conducted by their direct manager using structured criteria and documented feedback.
Key Takeaways
A performance review is a scheduled conversation between a manager and an employee about how the employee has performed over a defined time period. It's documented. It's structured. And when done well, it drives both accountability and growth. Most reviews follow a predictable format: the employee completes a self-assessment, the manager writes their evaluation, and the two meet to discuss. They talk about goals met and missed, strengths demonstrated, areas for development, and priorities for the next period. The conversation often leads to updated goals or a development plan. Here's the problem. Most organizations treat the review as the entire performance management process rather than one component of it. When the annual review is the only structured conversation about performance all year, it carries too much weight. Managers try to condense 12 months of observations, feedback, and development guidance into a single hour. That's why 90% of HR professionals say the process doesn't produce accurate results (SHRM, 2024). The review itself isn't broken. The lack of ongoing feedback around it is.
Organizations use different review formats depending on their culture, size, and what they're trying to achieve.
| Review Type | Frequency | Who Provides Input | Primary Purpose | Best For |
|---|---|---|---|---|
| Annual Review | Once per year | Manager (sometimes with self-assessment) | Formal evaluation, compensation decisions | Traditional organizations, large enterprises |
| Semi-Annual Review | Twice per year | Manager and employee | Mid-year correction and year-end evaluation | Companies transitioning from annual-only reviews |
| Quarterly Review | Every 3 months | Manager and employee | Goal tracking and rapid adjustment | Fast-paced industries, startups |
| 360-Degree Review | Annually or semi-annually | Manager, peers, direct reports, self | Development and leadership assessment | Leadership roles, team-oriented cultures |
| Project-Based Review | At project completion | Project manager and stakeholders | Project performance evaluation | Consulting, agencies, contract work |
| Probationary Review | At 30, 60, or 90 days | Manager | New hire assessment and fit evaluation | All organizations during onboarding |
The quality of a performance review depends far more on preparation and follow-through than on the meeting itself.
Gather data throughout the review period, not just the week before. Pull from project outcomes, customer feedback, peer input, goal tracking tools, and your own notes from one-on-ones. Ask the employee to complete a self-assessment at least one week before the meeting. Review their goals from the beginning of the period and assess progress against each one. Prepare specific examples for every point you plan to make. "You need to improve communication" is vague. "In the Q3 client presentation, the data slides lacked context, which led to confusion" gives the employee something concrete to act on.
Start by establishing the purpose: this is a two-way discussion, not a verdict. Let the employee share their self-assessment first. Listen actively. Then share your evaluation, starting with strengths and accomplishments before addressing development areas. Use the SBI model (Situation, Behavior, Impact) for specific feedback. Discuss each goal individually: what was achieved, what fell short, and why. Spend at least 30% of the conversation on forward-looking topics: career development, new goals, and support needed. End with clear, documented next steps and a shared understanding of priorities.
Document the discussion and share written notes with the employee within 48 hours. Both parties should sign or acknowledge the review. Update goals in whatever system you use. If development actions were agreed upon (training, mentoring, stretch assignments), put them on the calendar immediately. Check in on progress during your next one-on-one. A review without follow-through is just a meeting.
Rating scales give structure to evaluations, but the wrong scale creates more problems than it solves.
| Scale Type | Example | Pros | Cons |
|---|---|---|---|
| 3-Point | Below / Meets / Exceeds | Simple, reduces overthinking, clear differentiation | Too few categories for nuanced performance |
| 4-Point (no middle) | Below / Approaching / Achieving / Exceeding | Eliminates safe middle ground, forces a directional choice | Can frustrate managers who want a neutral option |
| 5-Point | 1: Needs Improvement to 5: Outstanding | Most common, familiar, allows nuance | Central tendency bias (most ratings cluster at 3) |
| Behaviorally Anchored (BARS) | Specific behavioral descriptions at each level | Highly specific, reduces subjectivity | Time-consuming to develop and maintain |
| No Rating | Narrative feedback only | Focuses on development, reduces anxiety | Hard to calibrate across teams, compensation decisions are murkier |
A structured template ensures consistency across the organization and makes sure nothing important gets skipped.
Include: employee name, job title, department, manager name, review period, and date of review. This section also captures the review type (annual, quarterly, probationary) and whether this is a self-assessment or manager evaluation. Keeping this section standardized across the company allows HR to aggregate and compare data.
List each goal from the review period with its target metric, actual result, and a brief assessment. Example: Goal: Reduce customer ticket resolution time from 48 hours to 24 hours. Result: Achieved 26 hours average. Assessment: Strong progress. Missed target by 2 hours due to Q3 staffing shortage, but improved resolution time by 46% overall. Include a rating for each goal if your system uses them.
Assess 4-6 core competencies relevant to the role. Common competencies include communication, problem-solving, collaboration, technical expertise, leadership, and initiative. Rate each competency and include at least one specific example supporting the rating. Avoid generic statements. Instead of "demonstrates good communication," write "led three cross-functional meetings in Q2, clearly presenting technical requirements to non-technical stakeholders."
Strengths: highlight 2-3 areas where the employee excels. Be specific about the impact. Development areas: identify 1-2 areas for growth with actionable next steps. Action plan: document agreed-upon development activities (courses, mentoring, stretch projects) with owners and timelines. Overall rating (if applicable): provide the summary rating with a brief justification.
Bias is the biggest threat to review accuracy. Understanding these patterns helps managers catch them before they distort evaluations.
Performance reviews create legal records. Poorly handled reviews expose companies to discrimination claims, wrongful termination lawsuits, and regulatory issues.
Every review should be documented in writing, signed by both parties, and stored securely. If an employee is later terminated for performance reasons, these documents become critical evidence. Courts examine whether reviews were consistent, specific, and free of discriminatory language. A pattern of "meets expectations" ratings followed by sudden termination looks problematic. Reviews should reflect an honest, documented trajectory.
Apply the same criteria, process, and standards to all employees in similar roles. Inconsistency in how reviews are conducted across managers, departments, or demographics can be used as evidence of discrimination in legal proceedings. Calibration sessions, where managers review ratings together, help ensure fairness. Train managers to focus on job-related behaviors and outcomes, not personal characteristics or protected class traits.
Key data points showing how reviews are evolving and where they still fall short.