Grove HR
Back to Blog
HR Best Practices

Performance Review Best Practices: How to Run Reviews That Actually Work [2026]

Performance reviews do not have to be dreaded. This guide covers how to set clear objectives, give meaningful feedback, plan development, and run reviews that motivate your team.

RR

Rachel Richardson

Head of Growth & Marketing, Grove HR

Updated 22 March 202614 min read
Share:

Performance reviews are one of the most powerful tools a manager has β€” yet they are also one of the most frequently botched. Done well, they align employee goals with business objectives, surface development opportunities, and strengthen the relationship between manager and team member. Done badly, they become a bureaucratic box-ticking exercise that leaves everyone frustrated.

This guide covers how to run performance reviews that genuinely improve performance, based on current best practice from CIPD research and real-world experience with UK businesses.

Why Performance Reviews Matter

A 2025 CIPD survey found that only 36% of UK employees believe their performance review process is fair and effective. The most common complaints are:

  • Reviews feel like a one-way lecture rather than a conversation
  • Feedback is too vague to act on
  • Objectives are set and then forgotten until the next review
  • The review focuses on the past rather than the future
  • Managers are unprepared and rush through

When reviews work well, the benefits are significant:

  • Clarity: Employees understand what is expected of them and how their work contributes to the organisation
  • Motivation: Recognition of good work and clear development pathways keep people engaged
  • Early intervention: Performance issues are caught and addressed before they become entrenched
  • Retention: Employees who feel their development is supported are less likely to leave
  • Legal protection: A documented history of performance conversations protects the organisation in the event of a capability dismissal

Before the Review: Preparation

The quality of a performance review is determined long before the meeting itself.

Set Clear Objectives at the Start of the Period

Good objectives are:

  • Specific: "Reduce customer complaint response time from 48 hours to 24 hours" rather than "improve customer service"
  • Measurable: Attach numbers, percentages, or concrete deliverables wherever possible
  • Achievable: Stretching but realistic given the employee's experience and resources
  • Relevant: Aligned with the team's and organisation's goals
  • Time-bound: With a clear deadline or review date

Aim for 3–5 objectives per review period. Too many dilute focus; too few leave gaps.

Gather Evidence Throughout the Period

Do not rely on memory. Keep a running record of:

  • Key achievements and milestones
  • Positive feedback received from colleagues or clients
  • Areas where the employee struggled or missed targets
  • Training completed or development activities undertaken
  • Any relevant incidents (positive or negative)

Encourage employees to keep their own record too. This makes the review a comparison of notes rather than a surprise.

Use 360-Degree Feedback Where Appropriate

For more senior roles or roles involving significant cross-functional work, consider gathering feedback from peers, direct reports, and other stakeholders. This provides a fuller picture than the line manager's perspective alone.

Keep 360-degree feedback:

  • Anonymous (so people are honest)
  • Structured (use consistent questions)
  • Balanced (ask for strengths and development areas)
  • Contextualised (the manager interprets and filters before sharing)

Schedule Properly

  • Book the meeting at least one week in advance
  • Allow 45–60 minutes (do not rush)
  • Choose a private, comfortable setting
  • Send a self-assessment form to the employee beforehand
  • Block out time for yourself to prepare notes

During the Review: The Conversation

Structure the Discussion

A good performance review follows a clear structure:

1. Opening (5 minutes)

  • Set a positive, collaborative tone
  • Explain the purpose and structure of the meeting
  • Confirm both parties have prepared

2. Review of Objectives (15–20 minutes)

  • Go through each objective from the previous period
  • Discuss what went well and what was challenging
  • Let the employee speak first β€” their self-assessment often surfaces insights you would miss
  • Acknowledge achievements specifically and sincerely

3. Feedback (10–15 minutes)

  • Share your observations, supported by evidence
  • Use the SBI model: Situation, Behaviour, Impact
  • Balance positive feedback with development areas
  • Be direct but kind β€” vague feedback helps no one

4. Development Planning (10–15 minutes)

  • Discuss career aspirations and growth areas
  • Identify specific development actions (training, mentoring, stretch assignments, qualifications)
  • Agree who is responsible for each action and by when

5. Forward-Looking Objectives (10 minutes)

  • Set objectives for the next review period
  • Ensure the employee has input into their objectives
  • Confirm how progress will be tracked

6. Close (5 minutes)

  • Summarise key points and agreed actions
  • Confirm the next check-in date
  • Thank the employee for their contribution

Giving Constructive Feedback

The most common mistake managers make is being too vague. Compare:

Vague FeedbackSpecific Feedback
"You need to communicate better""In last Tuesday's client call, you presented the data without context. The client asked three follow-up questions that could have been prevented by opening with the business impact."
"Great job this quarter""You reduced the average ticket resolution time from 4 hours to 2.5 hours, which directly improved our customer satisfaction score by 8 points."
"You seem disengaged""I've noticed you've declined the last three team socials and haven't contributed to the product brainstorm sessions. I wanted to check in β€” is everything OK?"

The SBI model helps structure feedback:

  • Situation: When and where did the behaviour occur?
  • Behaviour: What specifically did the person do or say?
  • Impact: What was the effect on the team, project, or business?

Handling Difficult Conversations

Sometimes a review involves addressing serious performance concerns. Key principles:

  • Be honest: Avoiding the issue does not help anyone
  • Be specific: Cite concrete examples, not generalisations
  • Be forward-looking: Focus on what needs to change, not just what went wrong
  • Listen: There may be personal circumstances, training gaps, or workload issues you are not aware of
  • Document: Record the conversation and agreed actions
  • Follow up: Set a shorter review cycle (e.g. monthly check-ins) to monitor progress

If performance concerns are serious, this may feed into a formal capability process. Ensure you follow your organisation's capability procedure and seek HR advice.

After the Review: Follow-Through

The review is only valuable if it leads to action.

Document the Outcome

Record:

  • Objectives agreed for the next period
  • Development actions and timescales
  • Any concerns raised and how they will be addressed
  • The date of the next formal review

Both manager and employee should receive a copy. Store this securely in the employee's HR file.

Regular Check-Ins

Do not wait six or twelve months for the next review. Schedule regular 1-to-1 meetings (monthly or fortnightly) to:

  • Track progress against objectives
  • Address emerging issues early
  • Provide ongoing feedback and recognition
  • Adjust objectives if business priorities change

These check-ins should be brief (15–30 minutes) and informal. They prevent the annual review from becoming a surprise.

Act on Development Plans

If you agreed to arrange training, mentoring, or a stretch assignment, follow through. Employees quickly lose faith in the review process if development promises are not kept.

Common Mistakes to Avoid

MistakeWhy It Matters
Recency biasReviewing only the last few weeks instead of the full period
Halo/horns effectLetting one strength or weakness colour the entire review
Avoiding difficult feedbackPerformance issues worsen when not addressed
No employee inputReviews should be a two-way conversation
Setting too many objectivesDilutes focus β€” aim for 3–5
Not documentingNo record means no accountability and no legal protection
Annual-only reviewsToo infrequent to be meaningful β€” supplement with regular check-ins
Comparing employeesReview each person against their own objectives, not against colleagues

Performance Review Templates

Self-Assessment Questions (Send Before the Review)

  1. Which objectives did you fully or partially achieve? What evidence supports this?
  2. What are you most proud of this period?
  3. Where did you face challenges? What would have helped?
  4. What skills or knowledge would you like to develop?
  5. What support do you need from your manager or the organisation?
  6. What objectives would you like to set for the next period?

Manager Preparation Checklist

  • Reviewed the employee's objectives from the previous period
  • Gathered evidence of performance (metrics, feedback, observations)
  • Read the employee's self-assessment
  • Prepared specific examples for feedback (positive and developmental)
  • Drafted proposed objectives for the next period
  • Identified potential development opportunities
  • Booked a private room and allocated sufficient time

Review Summary Template

SectionNotes
Previous objectives achieved
Key strengths demonstrated
Development areas identified
Feedback from others (if applicable)
Development actions agreed
New objectives for next period
Next check-in date

Linking Performance Reviews to Pay

Many organisations link performance ratings to pay increases or bonuses. If you do this:

  • Be transparent: Employees should understand the connection between performance and reward before the review, not after
  • Separate the conversations: Ideally, discuss performance and development in one meeting and pay in a separate meeting. Combining them causes employees to focus on the pay outcome rather than the feedback
  • Calibrate across the organisation: Ensure ratings are applied consistently across departments. A "meets expectations" in one team should mean the same as in another
  • Document the rationale: Be able to explain why each rating and pay decision was made

Performance reviews create a paper trail that may be relevant if you later need to dismiss someone for capability reasons. To protect your organisation:

  • Follow a fair and consistent process
  • Give the employee a genuine opportunity to improve before moving to formal action
  • Document specific examples of underperformance
  • Set reasonable timescales for improvement
  • Consider whether there are underlying issues (disability, workplace factors) that need to be addressed first
  • Seek HR or legal advice before moving to a formal capability process

Under the Equality Act 2010, take particular care that performance expectations and review processes do not indirectly discriminate against employees with protected characteristics.

How Grove HR Supports Performance Reviews

Grove HR provides a complete performance review workflow:

  • Objective setting: Create, track, and update objectives for each employee
  • Self-assessment forms: Employees submit their self-assessment before the review
  • 1-to-1 meeting notes: Record regular check-in discussions alongside formal reviews
  • Review history: Full audit trail of all reviews, ratings, and development plans
  • Reminders: Automated notifications when reviews are due
  • Reporting: Analyse review completion rates and performance trends across teams

Summary

Effective performance reviews require preparation, honesty, and follow-through. Set clear objectives, gather evidence throughout the review period, structure the conversation around specific feedback, and commit to ongoing development. The review should never be a surprise β€” regular check-ins ensure both manager and employee are aligned throughout the year.

The best performance reviews are conversations, not lectures. They look forward more than they look back. And they result in concrete actions, not just completed forms.

Tags:

performance reviewsperformance managementfeedbackobjectivesemployee developmentHR best practices
RR

Rachel Richardson

Head of Growth & Marketing, Grove HR

Rachel leads growth and marketing at Grove HR, with over a decade of experience in UK HR technology. She writes practical guides to help small businesses navigate employment law and build better workplaces.

Frequently Asked Questions

How often should performance reviews be conducted?

Best practice is to hold formal reviews annually or bi-annually, supplemented by monthly or fortnightly 1-to-1 check-ins. Regular check-ins prevent the annual review from becoming a surprise and allow objectives to be adjusted as priorities change.

What should a performance review include?

A performance review should include a review of previous objectives, specific feedback on strengths and development areas, a discussion of career aspirations, agreed development actions, and new objectives for the next period. Both the manager and employee should prepare beforehand.

How do you give negative feedback in a performance review?

Use the SBI model: describe the Situation where the behaviour occurred, the specific Behaviour observed, and the Impact it had. Be direct but kind, focus on the behaviour rather than the person, and discuss what needs to change going forward.

Should performance reviews be linked to pay?

If you link reviews to pay, be transparent about the connection, consider separating the performance discussion from the pay discussion, calibrate ratings consistently across departments, and document the rationale for each decision.

Ready to transform your HR?

Let your team flourish

Get started with Grove and see how it can help you manage your team more effectively.

30-day money-back guarantee. Cancel anytime.