How do I prepare for a performance review?

Build the evidence file the week before: your objectives as written in January (and as amended, with dates), three to five delivered pieces of work with names, dates, and figures that are verifiably yours, one honestly named dip with what changed after it, and two or three proposals for next year. One page, two copies. The preparation is not about performing — it's that the better-documented account tends to become the meeting's record.

What should I say when asked about my weaknesses or development areas?

Name one real, work-shaped weakness with its management plan — a habit you've already started correcting, with a named change — rather than a disguised strength or a shrug. In a review, unlike an interview, the audience has watched you all year: a fake weakness insults their observation, while an honestly owned one plus visible adjustment is the single strongest credibility move the meeting offers.

Can I disagree with my performance grade — and how?

Yes, and the route matters: argue it on the objectives as written, in the meeting, with specifics — then, if you still disagree, register it calmly for the record and ask what the formal route is, which many organisations set out in a performance or appeals policy. ACAS guidance covers how performance processes should fairly run. What rarely works is relitigating the grade in mood rather than evidence, or accepting it in the room and disputing it in December.

Should I raise pay in my performance review?

Know your organisation's machinery first: in many, the review feeds a separate pay round, and the meeting's job is to get the evidence and grade onto paper — in which case raise pay as a flag ('I'd like a proper conversation about pay once the review's written up; when does that cycle run?') rather than a negotiation. Where the review genuinely is the pay conversation, bring the case as its own agenda item with its own evidence, not as a coda to the feedback.

What if my manager gives me a review with no specifics at all?

Ask for them, warmly and repeatedly — 'that's useful; can you give me a recent example so I know exactly what to keep doing / change?' — and where specifics genuinely won't come, supply your own record and ask that it be attached to the write-up. A specifics-free review helps nobody: you can't act on it, and its grades are hard to defend in any later conversation. Making yours specific is self-defence done politely.

Review

Performance review questions and answers: the annual meeting, worked

Updated 12 August 2026

A performance review compresses a year of work into an hour of conversation, and whoever arrives with the better records runs the meeting. That is the uncomfortable arithmetic: your manager is reviewing eight people this fortnight from skimmed notes and recency, while you have lived every week of your own year — and most people still walk in with less evidence than the person marking them. The answers below are built on the one preparation that changes the meeting: your year, reassembled into named work, dated outcomes, and figures that are checkably yours.

It helps to be honest about what the meeting is for, because it is usually three meetings wearing one diary slot: an evidence review (what happened), a calibration input (what grade, feeding a process you never see), and a forward negotiation (objectives, development, sometimes the first move of a pay conversation). Each has its own register, and the worked answers flag which one you are in — arguing calibration with feelings, or taking criticism as if it were the whole verdict, are the two commonest register mistakes.

One framing carries the whole page: the review is a working meeting about the work, not a verdict on you as a person. Managers soften, hedge, and generalise under the same discomfort you feel — which is why the strongest move in almost every answer below is the same one: convert generalities into specifics, warmly, in both directions. Praise you can't name is unusable; criticism you can't name is unanswerable. Specifics are the whole game.

Your career — see how Review closes the loop and informs what comes next.

What your reviewer is weighing

Whether your account of the year survives their notes. Managers arrive with a skim of January objectives and whatever the last six weeks left in memory. An account built from dated, named work — with the objective each piece served — quietly becomes the meeting's reference document.
How you metabolise criticism in real time. One piece of critical feedback is close to structurally certain. They are watching the thirty seconds after it lands: curiosity and specifics, or defence and counter-attack. That half-minute colours the write-up more than most of the year does.
Whether your self-assessment is calibrated. Marking yourself top on everything reads as unselfaware; marking yourself down on everything reads as unconfident, and both make your evidence easier to discount. A self-account with one honestly named weak patch buys credibility for every strength beside it.
What you're like about the future. The backward half of the meeting is fixed; the forward half is negotiable — objectives, development, scope. Managers note who arrives with proposals for next year rather than only a defence of last year, because that is who they can build plans around.

'Talk me through your year — how do you think it's gone?'

Why it's asked: The opener, and a genuine fork: your answer becomes either the meeting's agenda or a warm-up they talk over. The version that works is structured and short — headline verdict, three evidenced beats against the objectives you were actually set, one named dip with its fix — delivered from a page you can hand over, not recalled from feel.

Model answerAnnual review, customer success manager, SaaS firm

I'll give you the shape first, then we can go deep wherever you want.

Headline: a strong year on retention, a mixed one on expansion, and one quarter I'd do differently.

Against the objectives we set in January: renewals on my book came in at forty-one of forty-three accounts, including the two we'd flagged as at-risk in March — the Fenwick save is the piece of work I'm proudest of, and I've brought the before-and-after notes. Expansion is the mixed part: I closed £68,000 of the £90,000 target, and I want to talk about why honestly — two of the misses were accounts where I read the renewal risk as too high to push an upsell, and I'd make the same call again; one I simply started too late.

The dip: Q2's response times, when I was covering Dan's book alongside mine. I should have flagged the overload in week two rather than week seven — that's the process change I've already made.

Where would you like to start?

'I want to raise something — the feedback is that your written updates can be hard to follow.'

Why it's asked: The criticism moment, arriving here in its commonest form: secondhand ('the feedback is…'), generalised, and about a habit rather than an event. The worked answer does the only three things that help: asks for a specific instance, separates what's true from what's noise without litigating the messenger, and converts it into one checkable change — while declining, politely, to accept a vague charge as a settled fact.

Model answerMid-year review, project engineer, utilities contractor

OK — I want to take that seriously rather than defensively, so can I ask for a bit of shape on it? Is this about the weekly programme updates, the board summaries, or something else — and is there a recent one that prompted it?

[On hearing it's the weekly updates:] That's fair, and I can even tell you which weeks: when the Hadley Road job went sideways in May, my updates got longer and more defensive at exactly the moment they needed to get shorter. The honest cause is that I was writing them to cover myself rather than to inform.

Here's the change I'd propose, and you tell me if it answers the feedback: one screen maximum — status, the two decisions needed, the one risk that moved — with the detail in an appendix nobody's obliged to read. I'll run that format for six weeks; would you look at week one's and tell me if it's landed?

One thing I'd ask in return: if an update misses for someone, I'd rather hear it that week than at the next review. Deal?

'I've graded you as 'meets expectations'. I know you were hoping for more.'

Why it's asked: The calibration moment. Two facts change how you play it: the grade usually arrives part-decided, moderated across a wider pool you never see; and it moves — this year on process grounds, next year on evidence laid down today. The worked answer argues the case on the objectives as written, asks the exact question that reveals the gap, and books the paper trail for next year rather than burning the meeting on a verdict that may be locked.

Model answerYear-end review, finance analyst, retail head office

I was, and I'd rather examine the gap properly than perform being fine with it.

Can we take it against the objectives as written? Month-end close came down from six days to four — that was the year's headline objective, delivered in October and held since. The forecasting handover from Amira landed clean; her maternity cover was named as objective three. So on the sheet we set in January, I'm struggling to see which line reads as 'meets' rather than 'exceeds' — genuinely tell me, because either I'm missing a gap or the bar moved.

[If the answer is calibration-shaped — 'exceeds is rare across the pool':] Understood — then two asks. First, what specifically would have put this year over the line? Not qualities — deliverables. Second, can we write those into this year's objectives now, so next January this is an evidence conversation rather than an impressions one?

And I'll say this plainly but without heat: I'll take this year's grade as given. I'm not planning to be having the same conversation about next year's.

'What development do you want — where do you see this going?'

Why it's asked: The forward question, chronically wasted with 'more training, maybe some leadership stuff'. It is actually the meeting's one open chequebook: development agreed here, in writing, tends to happen, because it enters the same document as your objectives. The strong answer asks for one or two named, dated things and ties each to work the team already needs — which converts your development from a favour into a plan.

Model answerAnnual review, senior administrator, university faculty

Two things, both specific, and I'll say what each is for.

First, the systems piece: I want to be the faculty's second pair of hands on the new records system before September's intake, which means the administrator certification — it's two days plus an assessment, and enrolment for the summer cohort closes in May. Right now Karen is the only person who can unpick enrolment errors, and we both know what August looks like when she's on leave. So it's development for me and cover for the team in the same spend.

Second, the chairing. I've been minuting the timetabling group for two years; I'd like to chair it from next term, with you observing the first one if that's useful. It's the smallest possible version of the coordinator role we've discussed — if I'm not right for that path, chairing will show us cheaply.

What I'd like from today is both of those in the written objectives with dates, rather than in the 'development areas' box that nobody reopens until next year. Can we do that?

'Is there anything you'd like to raise about the year — anything that didn't work?'

Why it's asked: The reciprocal question, and a genuine opening handled badly at both extremes: 'no, all fine' wastes your one structured chance to renegotiate how you're managed, while a saved-up grievance list turns the meeting adversarial in a minute. The middle that works: one or two process problems, named as process, each paired with a proposal — the missing one-to-ones, the objectives that changed verbally in June but never on paper, the work that arrives on Friday afternoons.

'You've marked yourself 'exceeding' here — talk me through that.'

Why it's asked: The self-assessment probe. It isn't an accusation; it's a request for the evidence file, and it goes wrong only when the file is feelings. Walk the specific objective, the delivered work with dates, and the figure that moved — then stop. If the manager's account differs, get their specifics beside yours: most self-assessment gaps are actually visibility gaps, and the fix is the record you're now creating.

'This came up from a couple of colleagues — I won't say who.'

Why it's asked: Anonymous feedback, the hardest shape to answer well. You can't interrogate the source, and trying reads as hunting them. What you can do: ask for the behaviour and the setting ('in meetings, or in writing? recent, or a while back?'), take the true part visibly, and — where the charge is genuinely unrecognisable — say so once, calmly, and ask that future instances come to you closer to the moment, since feedback that arrives at review, unattributed and aged, is nearly impossible to act on. That request is reasonable and managers know it.

'Objectives changed halfway through the year — how should we assess that?'

Why it's asked: The moved-goalposts conversation, common after restructures and priority swerves. The fair frame, which you may have to supply: the year gets assessed in two halves — the original objectives up to the change, the revised reality after — and work delivered against objectives that were later cancelled still counts, because you did it. Bring the dates; the paper trail of when things changed is usually yours alone.

'Let's set next year's objectives. What would you propose?'

Why it's asked: The question that decides next year's review, asked while everyone is tired at the end of this one. Arriving with three drafted objectives — each with a measure, a date, and one line on feasibility — means next year you are marked against a sheet you helped write. Push politely for two properties while the pen is out: measures counted by systems that already exist, and a mid-year check where the sheet can be revised in writing rather than by drift.

'Anything else before we write this up?'

Why it's asked: The close, and the last chance to shape the document — which is the part of the meeting that survives. Worth saying every time: ask when you'll see the written version and how corrections work; ask that the two or three agreed specifics (the grade's reasons, the development commitments with dates, any objection you registered) appear in it; and follow up the same week in a short email that plays back what was agreed. The review that matters is the one on file.

FAQ

How do I prepare for a performance review?: Build the evidence file the week before: your objectives as written in January (and as amended, with dates), three to five delivered pieces of work with names, dates, and figures that are verifiably yours, one honestly named dip with what changed after it, and two or three proposals for next year. One page, two copies. The preparation is not about performing — it's that the better-documented account tends to become the meeting's record.
What should I say when asked about my weaknesses or development areas?: Name one real, work-shaped weakness with its management plan — a habit you've already started correcting, with a named change — rather than a disguised strength or a shrug. In a review, unlike an interview, the audience has watched you all year: a fake weakness insults their observation, while an honestly owned one plus visible adjustment is the single strongest credibility move the meeting offers.
Can I disagree with my performance grade — and how?: Yes, and the route matters: argue it on the objectives as written, in the meeting, with specifics — then, if you still disagree, register it calmly for the record and ask what the formal route is, which many organisations set out in a performance or appeals policy. ACAS guidance covers how performance processes should fairly run. What rarely works is relitigating the grade in mood rather than evidence, or accepting it in the room and disputing it in December.
Should I raise pay in my performance review?: Know your organisation's machinery first: in many, the review feeds a separate pay round, and the meeting's job is to get the evidence and grade onto paper — in which case raise pay as a flag ('I'd like a proper conversation about pay once the review's written up; when does that cycle run?') rather than a negotiation. Where the review genuinely is the pay conversation, bring the case as its own agenda item with its own evidence, not as a coda to the feedback.
What if my manager gives me a review with no specifics at all?: Ask for them, warmly and repeatedly — 'that's useful; can you give me a recent example so I know exactly what to keep doing / change?' — and where specifics genuinely won't come, supply your own record and ask that it be attached to the write-up. A specifics-free review helps nobody: you can't act on it, and its grades are hard to defend in any later conversation. Making yours specific is self-defence done politely.