How to ace your performance review at work

A performance review is a structured conversation between you and your manager about how your work is going. It typically looks at your achievements, progress against previous goals, areas for development and priorities for the months ahead. Generally, it should go beyond a manager praising your work or recommending areas for improvement.

Performance reviews give you an opportunity to discuss your own experience, highlight contributions that may otherwise be overlooked and talk openly about where you want your career to go next.

When used efficiently, the review becomes a two-way conversation about your performance, development and future within the organisation.

The difference between a performance review and an appraisal

Performance reviews and appraisals are often used to describe the same process, and there is no universal distinction between them. However, an appraisal traditionally refers to a more formal assessment of an employee’s performance over a set period, often annually.

A performance review can be broader and more ongoing, with greater emphasis on regular feedback, development and future goals.

For employees, the terminology matters less than understanding the purpose of the meeting. Find out what will be discussed, whether your performance will be formally rated and how the outcome could influence decisions about your development, responsibilities or progression. Going in with that information makes it much easier to prepare effectively.

How performance reviews influence pay, promotion, and development

Performance reviews can influence decisions about pay, promotion and professional development, although exactly how they are used will depend on your employer.

A strong review may provide evidence to support a salary increase or promotion, particularly when you can demonstrate that you have taken on additional responsibility or delivered measurable results. It can also highlight skills you need to develop before progressing to the next level.

Career development is equally important. Your review is an opportunity to discuss training, qualifications, mentoring or new responsibilities that could support your longer-term goals. Even where pay or promotion is not immediately available, you should leave the conversation with a clearer understanding of what progression looks like and what you need to do to achieve it.

Good preparation can make a significant difference to how confident you feel going into a performance review. Instead of trying to recall an entire year’s work the night before, give yourself time to reflect on what you have achieved, the challenges you have faced and how your role has developed.

Review any goals set previously, gather evidence of your contributions and think about what you want to gain from the conversation. This is also your opportunity to consider what you would like to achieve next.

Preparing in advance means you can enter the meeting with specific examples and priorities rather than relying on what comes to mind in the moment.

Gathering evidence of your achievements and contributions

Avoid going into your review with a general statement that you have ‘had a great year’. Consider building a small portfolio of evidence that shows your specific contributions.

A good rule of thumb is to start with measurable results. Depending on your role, these could include revenue generated, targets exceeded, projects completed, deadlines met, costs reduced or improvements in customer satisfaction. Compare results with the original target where possible: increasing a metric from 70% to 85%, for example, tells a much stronger story than simply saying it ‘improved’.

That said, not every contribution has a number attached to it. Include positive feedback from clients or colleagues, examples of problems you solved and occasions when you took on additional responsibility. Add dates and project names so you can refer to specific examples during the conversation.

The aim is not to produce an exhaustive list. Choose your strongest examples and be ready to explain what you did, why it mattered and what changed as a result.

Evidence-gathering checklist:

• Results and targets achieved
• Key projects and your contribution to them
• Positive feedback from clients, customers or colleagues
• Problems you solved or processes you improved
• Additional responsibilities you took on
• Training, qualifications or new skills gained
• Dates, figures and other details that support your examples

Identifying your strengths and areas for development honestly

It is important, and useful to create a balanced self-assessment. Presenting yourself as having no weaknesses is unlikely to make a convincing case, but neither is arriving with a list of everything you think you could be doing better.

Look for patterns in the evidence you have gathered. Which responsibilities consistently produce strong results? Where do colleagues seek your input? Which skills have helped you handle difficult projects or solve problems? These examples can help you identify genuine strengths rather than relying on broad descriptions such as ‘hard-working’ or ‘a good communicator’.

Apply the same approach to areas of development. Instead of saying, ‘I need to be more confident’, identify the situation in which confidence becomes an issue and what would help. You might, for example, want more experience presenting to senior stakeholders or leading larger projects.

Framing development this way turns a perceived weakness into something specific and actionable. It also gives your manager a clearer opportunity to suggest training, experience or support that could help you progress.

Setting your own goals and priorities ahead of the conversation

Your manager may already have objectives in mind, but you do not have to wait for them to define what comes next. Before the review, identify two or three goals you would like to work towards and consider how they connect with your team’s priorities and the wider organisation.

Make each goal specific enough to discuss properly. ‘Develop my leadership skills’ gives you little to work with, whereas ‘lead the next client implementation project’ identifies both the skill you want to develop and an opportunity to demonstrate it.

Think beyond immediate performance targets, too. You might want greater responsibility, exposure to a different area of the business, formal training or a clearer route towards promotion. Consider what support would be needed to make each goal realistic, such as mentoring, budget, additional training or time to develop a particular skill.

Arriving with your own priorities changes the dynamic of the conversation. Rather than simply responding to objectives set for you, you can contribute to a development plan that reflects both what the organisation needs and where you want your career to go.

Even with thorough preparation, a performance review can feel uncomfortable. You are discussing your own achievements, ambitions and weaknesses, potentially while receiving feedback you were not expecting. Communicating confidently does not mean having an answer ready for everything.

Treat the meeting as a two-way discussion rather than a verdict on your performance. Explain your contributions using specific examples, ask questions when something is unclear and give your own perspective where it adds useful context.

It is also reasonable to ask for more detail if you receive broad feedback. If you are told you need to be ‘more proactive’, for example, ask what that would look like in practice and for an example of where a different approach was expected.

The goal is to leave the review understanding not only how your performance is viewed, but what is expected of you next and how you can move forward.

Structuring what you want to say without sounding rehearsed

Preparing for a performance review does not mean memorising answers. Over-rehearsing can make the conversation feel unnatural and may leave you struggling if the discussion moves in an unexpected direction. Instead, prepare the key points you want to communicate and use a simple three-part structure: context, contribution and next step.

Start with the context: what was the situation, objective or challenge? Then explain your contribution, focusing on the actions you took and the impact they had. Finally, connect the example to what comes next.

For example, rather than saying, ‘I think I’ve become better at managing projects’, you could explain that you took responsibility for a project with a tight deadline, coordinated input from several teams and delivered it on schedule. You can then use that experience to support a conversation about managing larger projects or taking on greater responsibility.

You do not need to structure every answer this way. Think of it as a framework for your most important examples, helping you communicate their significance without turning the review into a rehearsed presentation.

Handling difficult feedback without becoming defensive

Difficult feedback can trigger an immediate urge to explain, justify or disagree. Even when you believe the criticism is unfair, responding before you fully understand it can make a productive discussion harder.

A better approach is to pause, clarify and respond. Give yourself a moment before answering, then ask for a specific example of the behaviour or outcome being discussed. If the feedback is vague, questions such as ‘Can you give me an example of when this happened?’ or ‘What would you have expected me to do differently?’ can turn a general criticism into something you can actually address.

You can then respond with relevant context or explain where your perspective differs. You do not have to agree with every piece of feedback, but focus on the facts rather than reacting to the wording or tone.

Before moving on, establish what improvement would look like. Agreeing on a specific change, measure or expectation gives you something concrete to work towards and reduces the risk of the same vague criticism resurfacing at your next review.

Most importantly, constructive feedback is a helpful tool. Try to remember that its sole purpose is to help you improve.

It is easy to treat the end of the meeting as the end of the performance review process. In practice, what happens afterwards can have a much greater impact on your development.

While the conversation is still fresh, review what was agreed and turn broad intentions into specific actions. If you discussed training, additional responsibilities, a potential promotion or changes to your objectives, make sure you understand what needs to happen next, who is responsible and when progress will be reviewed.

Follow-up also creates accountability on both sides. Your manager may have committed to arranging training, providing mentoring or revisiting a progression conversation at a particular point. Recording those commitments gives you something concrete to return to rather than relying on either of you to remember the details several months later.

Turning agreed actions into a concrete development plan

A development goal is only useful if you know what needs to happen next. After your review, translate each agreed priority into a written action with a clear outcome, timescale and way of measuring progress.

For example, if you have agreed to develop your management skills, the action might be to lead a specific project within the next three months, complete relevant training and discuss your progress with your manager at monthly check-ins. This gives both of you a much clearer benchmark than simply recording ‘develop leadership skills’.

Your plan should also identify who owns each action. Some steps will be your responsibility, while others may depend on your manager approving training, arranging mentoring or giving you access to particular opportunities.

Set milestones rather than waiting until your next annual review to assess progress. Regular check-ins give you the chance to demonstrate development as it happens and address any barriers before they derail the goal entirely.

Keeping a record of commitments made by both sides

After the meeting, make a written record of the key commitments you and your manager have made. This is particularly important where the conversation covered training budgets, changes to your responsibilities, salary discussions or a potential promotion timeline.

Be precise. If your manager has agreed to review your eligibility for promotion in six months, record that rather than simply noting ‘discussed promotion’. If training has been approved in principle, capture what still needs to happen, who needs to approve it and any expected timeframe.

Where appropriate, send a short follow-up email summarising the main actions and agreed next steps. This gives both sides an opportunity to correct any misunderstandings while the conversation is still fresh.

Keep the record somewhere you can easily revisit it. When your next check-in or performance review comes around, you will have a clear account of what was agreed and whether those commitments have been followed through.

Many performance review mistakes happen before the meeting even begins. If you rely on memory, avoid difficult conversations during the year or only start thinking about your performance when the review appears in your calendar, you are working with an incomplete picture.

The review should bring together an ongoing record of your performance and development rather than become the first time important issues are discussed. That applies to positive contributions as much as concerns. Achievements can be forgotten, priorities can change and events from the past few weeks can easily overshadow work completed earlier in the year.

Two particularly common problems are waiting until the review to raise an issue and allowing recent events to dominate your assessment of your overall performance.

Waiting for the meeting to raise important concerns

A performance review should not become a backlog of issues that have been building for months. If something is affecting your ability to do your job, such as an unrealistic workload, unclear responsibilities, insufficient resources or a lack of support, raise it when it becomes significant rather than saving it for the formal meeting.

Waiting can make the issue harder to resolve and may mean your manager has had no opportunity to address it. A concern raised for the first time during a discussion about your performance can also appear reactive, particularly if it is used to explain why a target was missed.

That does not mean every frustration requires an immediate meeting. The key is to distinguish between a temporary problem and something that is genuinely affecting your performance or development.

Raising significant concerns earlier also creates a useful record. By the time your review takes place, you can discuss what action was taken, whether the situation improved and what further support may be needed.

Letting recency bias define your self-assessment

It is natural to give greater weight to events that happened recently. In a performance review, however, this can distort your assessment of an entire review period.

A difficult project, missed target or particularly successful few weeks at the end of the year should not automatically outweigh everything that came before it. Look back across the full period and consider how your performance developed over time, including projects completed, objectives achieved, responsibilities added and challenges overcome.

This is another reason to keep a record of your work throughout the year. Rather than reconstructing your contribution from memory, you can draw on evidence collected at the time.

If recent performance has changed significantly, acknowledge it, but put it in context. A strong self-assessment should recognise patterns and progress across the whole review period rather than allowing the last four to six weeks to define the story.

One of the most stressful parts of preparing for a performance review is trying to reconstruct months of work from memory. Digital tools can make that process much easier by creating an ongoing record of information you can draw on throughout the year.

Depending on the systems available in your workplace, this might include records of working hours, schedules and absences alongside project management data, completed objectives, training records and feedback. Used consistently, these sources can help you build a more accurate picture of your contribution rather than relying on what you happen to remember before the meeting.

They can also make the review itself more evidence-based. Having access to reliable information allows you to check dates, identify patterns and support relevant examples with facts, giving you a stronger foundation for conversations about workload, performance and development.

Tracking your own performance data throughout the year

Keeping an ongoing record of your work removes much of the pressure of preparing retrospectively for a performance review. Instead of trying to reconstruct the previous six or 12 months, you already have evidence available when you need it.

Record significant achievements as they happen, including completed projects, milestones, targets, positive feedback and new responsibilities. Where relevant, keep track of hours or time spent on particular activities too. This can provide useful context when discussing workload, capacity or how your role has changed.

The record does not need to become another administrative burden. A short monthly update may be enough, particularly if your organisation already uses systems that capture relevant performance and workforce data.

Review what you have recorded periodically rather than waiting for the formal meeting. Doing so can reveal patterns in your workload and development, help you identify achievements that might otherwise be forgotten and give you stronger evidence for conversations with your manager throughout the year.

How self-service HR platforms like myProtime put you in control

Employee self-service platforms can give you direct access to information that would otherwise sit with HR or your manager. Protime’s myProtime, for example, allows employees to view information including worked hours, schedules and absence balances, as well as manage everyday requests such as leave.

That visibility can be useful when preparing for a performance review. If workload, attendance patterns, changing schedules or additional hours are relevant to the conversation, you can refer to your own records rather than relying on memory or asking HR to retrieve the information for you.

It also supports a more continuous approach to managing your working life. Having access to up-to-date information throughout the year makes it easier to spot patterns, check that records are accurate and build context around your performance.

Self-service does not replace the conversation with your manager. It gives you better access to the information you may need to take a more informed and active role in it.

How often should performance reviews take place?

There is no single schedule that works for every organisation. Some employers hold a formal annual review supported by regular check-ins, while others use quarterly or more continuous review cycles. What matters for employees is that feedback and development conversations do not depend entirely on one meeting each year.

What should I bring to a performance review?

Bring evidence that supports the points you want to discuss. This might include progress against objectives, measurable results, project outcomes, positive feedback and examples of additional responsibilities you have taken on. It is also useful to have two or three priorities or development goals you would like to discuss.

Can I disagree with feedback in a performance review?

Yes. You can explain your perspective or challenge feedback you believe does not accurately reflect your performance. Keep the discussion focused on specific examples and evidence. Ask your manager to clarify the feedback and explain what they would have expected to see instead.

Should I discuss salary during my performance review?

That depends on how your organisation handles salary reviews. In some businesses, performance and pay discussions take place together; in others, they are separate processes. If you want to discuss salary or progression, find out how decisions are made and come prepared with evidence of your contribution, increased responsibilities and results.

What if my performance review does not result in clear next steps?

Ask for them. If you leave with broad feedback but no clear actions, follow up with your manager to establish what is expected, how progress will be measured and when you will revisit the conversation. Where development, training or progression has been discussed, confirm who is responsible for the next action and any agreed timeframe.