Performance ManagementProcess

Performance Review

Also called performance appraisal, annual review, performance evaluation, employee review, review cycle

Updated August 2, 2026

A performance review evaluates how an employee performed over a defined period against defined expectations, records the result, and feeds decisions about pay, development, promotion, and sometimes continued employment.

The review is the documentation event. The performance management that matters happens continuously between reviews, through goals, feedback, and one-on-ones. A review that surprises an employee is a symptom of a management problem rather than a working process.

How a cycle works

A cycle begins with a period and a population: who is being reviewed, over what dates, and who is excluded because they are too new. Most organizations exclude anyone hired within the last sixty to ninety days of the period and review them on a start-date anniversary instead.

Inputs are gathered next. The employee usually writes a self-assessment, peers or cross-functional partners may contribute feedback, and the manager pulls together goal outcomes and their own observations. The manager then drafts an assessment and a proposed rating.

Calibration comes before delivery, not after. Managers in a group review their proposed ratings together against the definitions and against one another, and adjust so that a given rating means roughly the same thing regardless of who the manager is. Only after calibration is the rating final.

Delivery is the conversation: what the rating is, what evidence supports it, and what changes for the next period. Compensation decisions follow, and are usually communicated separately so the development discussion is not swamped by the number.

Cadence varies. Annual cycles with a mid-year check-in remain the most common, quarterly cycles are used where work and priorities move quickly, and many organizations run lightweight continuous check-ins alongside a single formal annual documentation event.

A rating scale that actually differentiates

Scale design determines whether ratings carry information. Five points with written definitions is a common and workable choice.

RatingDefinitionTypical action
Does not meet expectationsConsistently below the requirements of the role during the periodStructured improvement plan with defined objectives and a review date
Partially meets expectationsMeets some requirements, with clear and specific gaps in othersTargeted development plan and closer manager follow-up
Meets expectationsDelivers the requirements of the role reliably. This is a good rating and should be described as oneStandard increase eligibility and continued development
Exceeds expectationsDelivers beyond the scope of the role, with impact visible outside the immediate teamHigher increase eligibility, stretch assignments
Substantially exceeds expectationsPerforms at the level of a larger role and has done so consistentlyPromotion consideration and retention attention
The most important line is the middle one. Where "meets expectations" is treated as a soft failure, managers inflate ratings and the scale stops carrying any signal.

What calibration is for

Calibration is the session where managers compare proposed ratings before anything is communicated. It is the step most often skipped and the one that does the most work.

  • It makes ratings comparable across managers, so a rating from a lenient manager and a demanding one mean approximately the same thing.
  • It exposes rating inflation, since a group where nearly everyone exceeds expectations is visible immediately when the group is viewed together.
  • It forces evidence. A manager who cannot describe what a rating is based on usually revises it in the room.
  • It surfaces pattern differences worth examining, including whether ratings vary by group in ways that performance evidence does not explain.
  • It builds a shared standard over time, which is the durable output. The individual adjustments matter less than the calibrated judgment managers carry into the next cycle.
  • It should happen before ratings are shared with employees. Adjusting a rating after it has been delivered destroys trust in the process.

Where review cycles break

The mechanics are simple. The failure modes are predictable.

  • Recency bias. Managers weight the last six weeks, which is why contemporaneous notes throughout the period matter more than the form.
  • Rating inflation. Avoiding hard conversations produces a distribution where almost everyone is above average, which makes pay differentiation impossible to justify.
  • Forced distribution applied to small teams. Requiring a fixed percentage of low ratings in a team of six manufactures a low performer who may not exist.
  • Ratings that arrive as news. If the review is the first time an issue is raised, the employee reasonably concludes it was invented to justify a decision.
  • Goals set once and never revisited, so the employee is evaluated against priorities that changed in month three.
  • Evaluating personality rather than performance. Comments about attitude, style, or being a culture fit are weak signal and, when they vary by group, are a liability.
  • Pay and development crammed into the same conversation, where the number reliably drowns out everything else.
  • Documentation that hedges. Reviews softened to avoid a difficult conversation become the record that contradicts a later termination decision.

Note

Review records outlive the cycle. They are routinely produced in disputes over termination, promotion, and pay, and a file of positive reviews followed by an abrupt separation is difficult to explain. The practical implication is not to write harsher reviews, but to write accurate ones and to raise problems in the period they occur rather than at the end of the year.

Why it matters operationally

The review cycle is where the organization decides what performance means, and that decision propagates into pay, promotion, succession, and separation. If the ratings do not differentiate, every downstream decision has to be made on some other basis, usually manager advocacy, which is less consistent and much harder to defend.

The cycle is also the only regular moment where every employee is guaranteed a documented conversation about their work. That guarantee is worth protecting even in organizations that have moved most feedback to a continuous model, because continuous feedback tends to reach the people whose managers were already good at it.

Who this applies to

A management practice rather than a legal requirement, though review records frequently become evidence in employment disputes.

Common questions

How often should reviews happen?

Annual with a mid-year check-in is the most common pattern and works for most organizations. Faster cycles suit environments where priorities change quarterly. What matters more than frequency is whether feedback happens in between: an annual review is fine if nothing in it is a surprise, and inadequate if it is the only conversation all year.

Should reviews be tied to compensation?

Most organizations connect them, because a rating that has no consequence loses credibility. The usual practice is to separate the conversations: deliver the performance discussion first, then the pay decision, so development feedback is actually heard rather than reduced to an explanation of the number.

Is forced distribution a good idea?

It reliably counteracts inflation and it reliably creates problems, especially in small teams where the required percentages have no relationship to the actual talent distribution. A softer approach is a guideline distribution used to prompt discussion in calibration rather than a quota that must be met.

What should a manager document during the period?

Specific, dated observations of work: what was delivered, what the impact was, what feedback was given and how the employee responded. A handful of concrete notes per quarter is enough to write an accurate review and is far more useful than trying to reconstruct twelve months from memory.

Should employees see peer feedback?

Usually in summarized and anonymized form. Verbatim attributed feedback discourages candor and turns the process into a political exercise. The manager should synthesize themes and own the assessment rather than presenting it as the verdict of the peer group.

Related

Performance Improvement PlanA performance improvement plan, commonly called a PIP, is a written plan that states specifically where an employee performance falls short, what has to change, how the change will be measured, and by when.Progressive DisciplineProgressive discipline is a practice of responding to performance or conduct problems with escalating steps, each documented, so an employee has notice and an opportunity to correct before the relationship ends.Job DescriptionA job description is the written record of what a role is responsible for, what it requires, and which of its functions are essential. It is the reference point for hiring, pay, performance, and accommodation decisions.Compensation PhilosophyA compensation philosophy is an employer written statement of how it decides what to pay: which markets it benchmarks against, where in that market it targets, and how pay moves once someone is hired.Structured InterviewA structured interview asks every candidate for a role the same predetermined questions, in the same order, and scores the answers against the same defined criteria.Employee OnboardingEmployee onboarding is the process of turning an accepted offer into a productive, fully set up employee: the required paperwork, the accounts and access, the role context, and the early relationships.Personnel FileA personnel file is the employer-maintained record of an individual employee's employment history, and it is only one of several files an employer keeps, because certain categories of information have to be stored separately from it.

Related terms: calibration, self-assessment, goal setting, forced distribution, continuous feedback