A once-a-year formal performance evaluation that summarizes an employee's contributions, goal achievement, and development over the preceding 12 months, often tied to compensation and promotion decisions.
Key Takeaways
An annual review is the traditional once-per-year performance evaluation. The manager and employee sit down, look back at the past 12 months, and assess what went well, what didn't, and what should change. It's formal. It's documented. And for decades, it was the only structured performance conversation most employees had. The format hasn't changed much since its origins in the U.S. military during World War I, when the Army created the "man-to-man" rating system to evaluate officers. Corporate America adopted similar approaches in the 1950s and 1960s, and by the 1980s, the annual review was standard practice at virtually every large company. Today, the annual review is under pressure. A 2024 CEB/Gartner study found that only 5% of managers believe the process is worth the time invested. Employees agree: 47% say annual reviews don't reflect their actual performance (Gallup, 2024). The core issue isn't the evaluation itself. It's trying to compress a year's worth of feedback, coaching, and development planning into a single meeting.
This comparison drives most of the debate about performance evaluation today. Neither approach is inherently better. Each has trade-offs.
| Factor | Annual Review | Continuous Feedback |
|---|---|---|
| Frequency | Once per year | Weekly, biweekly, or as needed |
| Formality | Highly structured, documented in HRIS | Informal to semi-structured, may or may not be documented |
| Time investment | Concentrated: 2-4 weeks of intense effort | Distributed: small amounts throughout the year |
| Recency bias risk | High: managers remember recent months best | Low: feedback is given in real time |
| Compensation linkage | Strong: often directly tied to raises and bonuses | Weak: development-focused, compensation decided separately |
| Course correction speed | Slow: problems can persist for months before being addressed | Fast: issues are identified and addressed in days or weeks |
| Legal documentation | Strong: creates formal record | Variable: depends on whether feedback is documented |
| Employee anxiety | High: "judgment day" perception | Lower: normalized as routine conversation |
| Manager skill required | Moderate: follows a structured template | High: requires strong coaching and communication skills |
A well-structured annual review covers five areas. Skipping any of them creates gaps in the record and misses opportunities for meaningful conversation.
A brief narrative covering the employee's major accomplishments, challenges faced, and overall trajectory during the year. This isn't a month-by-month log. It's a story of the employee's year in 3-5 sentences. Was it a breakout year? A rebuilding year? A year of consistent execution? Setting the narrative frame before diving into specifics gives both parties shared context for the detailed discussion.
Review each goal set at the beginning of the year. Document the target metric, actual result, and factors that influenced the outcome. For goals that were met, note what contributed to success. For goals that were missed, distinguish between factors within the employee's control and external factors (budget cuts, team changes, shifting priorities). If goals were adjusted mid-year, assess against the updated targets.
Rate the employee on 4-6 core competencies defined by the organization or the role. This might include communication, leadership, technical skill, collaboration, initiative, and problem-solving. Each rating should be supported by at least one specific behavioral example. Competency assessment captures how someone achieves results, not just what results they achieve. A salesperson who hits quota by burning client relationships shouldn't receive the same overall rating as one who hits quota by building long-term partnerships.
Identify 1-3 areas where the employee can grow in the coming year and define specific actions to support that growth. Examples: complete a leadership development program by Q2, shadow the VP of Product for two weeks to understand cross-functional decision-making, present at an industry conference. Tie development goals to both the employee's career aspirations and the organization's needs. This section is where annual reviews create the most long-term value.
If your organization uses ratings, provide the overall score with a clear justification. If rating-free, write a summary assessment. Then outline specific next steps: new goals for the upcoming year, development actions with timelines, any changes to role or responsibilities, and the date of the next check-in. Both the manager and employee should leave with an identical understanding of where things stand.
Most organizations run annual reviews on a calendar-year cycle. Here's a typical timeline showing how the process unfolds across the year.
| Month | Activity | Owner |
|---|---|---|
| January | Set individual goals aligned to company objectives | Manager + Employee |
| February-March | First quarter check-in on goal progress | Manager |
| June-July | Mid-year review: assess progress, adjust goals if needed | Manager + Employee |
| September-October | Third quarter check-in, pre-review data gathering begins | Manager |
| November | Self-assessments distributed and completed | Employee |
| November-December | Manager writes evaluations, calibration sessions held | Manager + HR |
| December-January | Review meetings conducted, ratings finalized | Manager + Employee |
| January-February | Compensation decisions communicated | Manager + HR/Finance |
If your organization uses annual reviews, these practices can dramatically improve their accuracy and impact.
The annual review works well in some contexts and poorly in others. Here's how to decide whether to supplement or replace it.
Employees regularly say they're surprised by their ratings. Managers can't recall specific examples from earlier in the year. High performers leave because they feel unrecognized between reviews. Projects fail or drift because performance issues aren't addressed until the annual cycle. Goals set in January become irrelevant by March due to business changes. If any of these patterns are familiar, the annual cadence is too slow for your organization.
Government agencies and regulated industries where formal documentation is legally required. Organizations with stable, predictable work where goals don't shift frequently. Companies with highly tenured workforces who prefer formal, structured processes. Academic institutions with fixed annual calendars. Even in these settings, supplementing the annual review with quarterly check-ins improves outcomes.
Data on how organizations use and perceive the annual review process.