Performance reviews: a manager’s guide to evaluating staff

Most managers inherit the performance review as a form to complete, not a conversation to run well. This guide sets out how to evaluate staff fairly, keep the process useful, and turn each review into something an employee can act on.

A performance review is a structured conversation between a manager and an employee that assesses recent work against agreed objectives and sets clear expectations for the period ahead. In the UK it is also called an appraisal or a performance appraisal, and it usually pairs a look back at results with a look forward at development.

A review sits inside a wider performance management cycle: setting objectives, giving feedback through the year, and reviewing outcomes. It is not a one-off verdict. CIPD describes appraisal as one part of continuous performance management rather than a single annual event.

Formats vary, but every review answers three questions for the employee: how am I doing, what does good look like, and what happens next. A review that answers those clearly earns its place in the calendar. One that leaves them unanswered becomes a form-filling exercise that neither side values.

The purpose of a performance review is to give an employee an accurate, evidence-based picture of their contribution and a clear plan to improve. It aligns individual effort with team and organisational goals, informs decisions on pay, promotion and development, and creates a documented record of expectations and support.

For the organisation, reviews surface capability gaps, protect fairness in reward and progression decisions, and provide a written trail if performance concerns escalate later.

For the employee, reviews reduce uncertainty. People perform better when they understand how you judge their work and where they stand. A vague sense of managerial approval motivates far less than a clear account of what worked and why.

Purpose shifts by context. A developmental review focuses on growth, while an evaluative review informs reward and promotion. Deciding which one you are running before you sit down prevents mixed messages and protects trust.

Performance reviews drive employee development when they convert feedback into specific, agreed actions instead of general praise or criticism. A review identifies the gap between current and expected performance, names the skills or behaviours to work on, and sets a timeframe and support to close that gap.

Development stalls when feedback stays vague. Telling someone to improve their communication gives them nothing to do. Asking them to send a written summary after each client call by Friday gives them a target they can hit and you can check.

The strongest reviews link individual goals to a visible route forward, because employees who can see a path tend to stay. This is where a review connects to a career path framework and to wider employee career development. Cadence matters too: a single annual review cannot shape behaviour across twelve months, so regular check-ins let managers adjust support while it still counts.

The main types of performance review are the annual appraisal, continuous or quarterly check-ins, 360-degree feedback, and self-assessment. Most UK organisations now combine several of these rather than relying on one annual meeting.

Type	What it is	When to use it
Annual appraisal	A formal yearly review of objectives, results and rating	Reward, promotion and record-keeping decisions
Continuous check-ins	Short, regular one-to-ones through the year	Adjusting priorities and catching issues early
360-degree feedback	Input from peers, direct reports and managers	Developmental insight on behaviour and collaboration
Self-assessment	The employee rates their own performance before the meeting	Prompting reflection and opening a two-way conversation

Choose the mix to fit the decision you face. 360 feedback works as a development tool, not a scoring mechanism; tying it to pay tends to make raters cautious and their input less honest.

Structure a performance review in five steps: prepare with evidence, open with the purpose, review results against objectives, listen to the employee, and agree specific next actions. A clear structure keeps the meeting balanced and stops it drifting into a one-way monologue.

1. Prepare. Gather examples, notes from one-to-ones and any relevant data beforehand. Opinion without evidence reads as bias.
2. Open. State the purpose and how the meeting will run, so the employee is not guessing at your intent.
3. Review results. Compare actual outcomes against the objectives you set, covering strengths first and development areas second.
4. Listen. Ask open questions and let the employee respond. A review the employee cannot speak in becomes something done to them, not with them.
5. Agree actions. Close with specific, time-bound commitments and the support you will provide to meet them.

Record the main points and share a copy with the employee. Keeping a written record of performance conversations protects both sides if a concern later becomes formal.

In a performance review, a manager should describe specific behaviours and their impact rather than personality traits or vague impressions. Effective phrasing names what happened, the effect it had, and what to do next, which keeps feedback objective and easy to act on.

Ground praise in a concrete result. For example: “You rebuilt the onboarding checklist this quarter, and new starters reached full output two weeks sooner. Keep owning that process.” That tells the employee exactly what to repeat.

Frame development the same way. Instead of “you need to be more proactive,” say “I would like you to flag risks in our Monday call before a deadline slips.” Feedback tied to observed events, not opinion, is the principle that keeps an appraisal fair and defensible.

Avoid absolute labels such as “always” or “never,” which invite argument and rarely hold up. Describe the pattern, give a recent example, and state the change you want to see. Phrasing of this kind gives the employee something to work on and gives you a clear point to check at the next meeting.

Common areas for improvement in a performance review include communication, time management, ownership, collaboration and technical skill. The value lies in how you phrase each one, because a useful example pairs the gap with a concrete action and a timeframe.

Area	Example wording a manager can use
Communication	Summarise decisions in writing within a day of each meeting so the team has a shared record.
Time management	Break large tasks into weekly milestones and review progress in our one-to-one.
Ownership	Raise blockers as they appear, not at the deadline, so we can solve them together.
Collaboration	Invite input from the design team before finalising scope on the next project.
Technical skill	Complete the advanced reporting module by the end of Q2 and apply it to the monthly report.

Frame every area as a forward action the employee can start on. Listing faults without a next step lowers confidence and rarely changes behaviour.

In a performance review, an employee should arrive with specific examples of their work, questions about expectations, and one or two development goals. Managers get better reviews when they invite this input in advance instead of expecting it on the spot.

You can shape what an employee brings by setting the ask clearly. The points below describe what good employee input looks like and how to prompt it.

• Ask for examples. Invite the employee to bring two or three pieces of work they are proud of and one they found difficult.
• Encourage questions on expectations and progression, so the employee can raise what matters to them.
• Invite a development goal from the employee, since people commit more readily to goals they helped set.
• Share the agenda or self-assessment beforehand. Preparation turns a review from an inspection into a conversation.

The most common performance review mistakes are recency bias, delivering surprise criticism, talking more than listening, and relying on a single annual meeting. Each one weakens the fairness and usefulness of the review.

• Recency bias: judging the whole period on the last few weeks. Notes taken through the year correct this.
• Surprises: raising a serious problem for the first time at the annual review. Address concerns as they arise instead.
• One-way delivery: filling the meeting with your own assessment. A fair review needs the employee’s voice in it.
• Annual-only cadence: expecting one meeting to shape a year of work. Regular check-ins do the real work.
• Ratings without evidence: a score with no examples invites disputes and claims of unfair treatment.

Most of these errors share one root cause: a review treated as a single annual event rather than the end point of an ongoing conversation. Managers who take brief notes after each one-to-one, and who raise issues as they surface, avoid almost all of them and walk into the formal review with the evidence already in hand.

At minimum annually, though regular check-ins through the year make the formal review more accurate and less stressful. CIPD favours ongoing performance conversations over a single yearly event.

In practice, none. In the UK, people use the terms interchangeably, and both describe a structured assessment of an employee’s performance against agreed objectives.

They can be, but combining evaluation and reward in the same meeting can make employees defensive and less open. Many organisations separate the development conversation from the pay decision to keep both honest.

The employee and their line manager at minimum. A 360 approach adds peers and direct reports to give a fuller, developmental view of behaviour and collaboration.

Let them add their comments to the record, discuss the evidence together, and agree next steps. A review works as a conversation, not a verdict handed down.