# Employee Response to Performance Review Examples: What to Actually Write Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/employee-response-to-performance-review-examples/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/employee-response-to-performance-review-examples.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Employee response to performance review examples: what to write when you agree, disagree, or get vague feedback, plus how to keep it future-focused. ## Key facts - Title: Employee Response to Performance Review Examples: What to Actually Write - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Communication - Primary keyword: employee response to performance review examples - Source page: https://headwayskills.com/knowledge/working-with-your-manager/employee-response-to-performance-review-examples/ ## What this page covers - Employee response to performance review examples: what to write when you agree, disagree, or get vague feedback, plus how to keep it future-focused. - Practical guidance for employee response to performance review examples - How this topic connects to Working with Your Manager ## Detailed explanation Your review comes back, and underneath your manager's comments there is an empty box with your name on it. Whatever you type there stays on the record, which is exactly why people freeze in front of it. A strong employee response does four things: it acknowledges the feedback you accept, adds factual context the review left out, addresses anything inaccurate with evidence rather than emotion, and closes with [specific goals](/knowledge/working-with-your-manager/goals-for-performance-review/), dates, and a follow-up. Short, calm, and future-focused beats long and defensive every time. The examples below cover the situations people actually get stuck on — praise, a rating you disagree with, feedback too vague to act on, and the request you were too nervous to make. ## What should an employee response to a performance review include? Four parts, in this order. First, acknowledge what you accept, and name the specific thing rather than the whole review. Second, add context the review is missing — a constraint, a handover, a project that moved. Third, correct anything factually wrong, with evidence. Fourth, state what you will do next, with a date attached. A worked example: *"Thank you for the feedback on the Q3 handover. I agree the documentation went out late. I've moved the checklist to the day before release rather than the day of, starting with the November cycle, and I'd like to review whether that fixed it at our January [one-on-one](/knowledge/working-with-your-manager/effective-one-on-one-meetings/)."* Two details make the difference. University of Iowa HR's review guidance warns against absolutes — "always," "never" — because they read as exaggerated and invite a rebuttal of your rebuttal; tie every claim to a named project or a timeframe instead. And keep the count low. Guidance aimed at reviewers is blunt about this: a handful of detailed, evidence-based points is more useful than a long list of generic phrases. The same holds for your side of the box. ## How do you respond to a positive performance review? Thank the person, name the specific thing they noticed, then use the goodwill. According to Indeed's career-advice guidance, responding to a review is one of the few natural moments to request additional responsibilities and ask your supervisor directly how to reach your career goals — the response is a career conversation, not just a receipt. An example: *"Thank you — I'm glad the client onboarding work landed well, and I appreciate you calling out the follow-up calls specifically. I'd like to take on the onboarding for the two new accounts next quarter. What would you want to see from me before that's a reasonable ask?"* The mistake here is answering a good review with nothing but gratitude. You accept the praise and leave the opening unused. A short, specific ask is not arrogant; it is the response a manager can actually do something with. ## What do you write if you disagree with your performance review? Facts, not feelings — and not today. Guidance on handling a negative review consistently says the same three things: take time to reflect rather than [reacting in the moment](/knowledge/self-awareness/responding-to-feedback/), keep the tone professional even where you disagree, and support every disagreement with something checkable — project outcomes, delivery dates, documented conversations. One widely repeated tip is to show your draft to a trusted colleague or friend before you send it, because they will read the temperature of it more accurately than you can. An example: *"I'd like to add context to the rating on delivery. Of the six projects listed, four shipped on or before the agreed date; the Rivera project slipped by three weeks after the scope change we agreed on 12 May, which is documented in the change log. I'd welcome a conversation about how the scope change was accounted for here."* Notice what that does not contain: no "this is unfair," no comparison to a colleague, no accusation of bias. It gives your manager a factual thing to check rather than a mood to manage. ## Do you have to sign a review you disagree with? In most systems a signature confirms that you received the review and discussed it — not that you agree with it. If you are unsure what it means in yours, ask HR before you sign; it is a reasonable question and asking it costs nothing. The standard remedy is not refusal but the written record. SHRM's HR advice on unfair reviews points employees toward [writing a rebuttal](/knowledge/working-with-your-manager/poor-performance-review-examples/) or adding comments to the appraisal itself, stating clearly and specifically why you disagree. That way the disagreement lives in the same file as the rating, which is worth far more later than a blank signature line ever will be. ## What should you say in the review meeting itself? Ask questions and take notes; commit to nothing you have not thought about. If a rating lands badly, you are allowed to say that you want to consider it and respond in writing afterward. That is not evasion — it is what turns a reaction into a response. Two questions do most of the work: *"Can you give me a specific example of where you saw that?"* and *"What would it look like if I were doing this well?"* Then write down the answers. Documenting the discussion is what makes your written response accurate a week later, when the details have gone soft. ## How do you respond when the feedback is too vague to act on? Vague ratings are the most common complaint employees have about reviews — "needs to be more strategic," "should be more visible," a bare "meets expectations" with no examples underneath it. You cannot improve against a phrase, and you cannot write a useful response to one either. So convert it into something observable before you reply. Ask what the behavior would look like in a specific meeting or a specific project. Ask what would have to be different for the rating to move. Then put the answer in your response as a concrete commitment, which quietly holds both of you to the same definition. It also helps to know which skill the vague phrase is actually pointing at, and that is harder to see from the inside than most people expect. If a comment like "be more visible" leaves you guessing, it is worth [getting an outside read on your skills](https://assessment.headwayskills.com/) before you decide what to promise. ## How long should your response be? Shorter than you think. Three to five short paragraphs, or roughly 150 to 250 words, is plenty for most systems. A long response reads as defensive even when the content is reasonable, and length dilutes the two or three points you actually want on the record. Pick the points that matter most, give each one a fact, and stop. If there is more to discuss, discuss it in a conversation — not in the box. ## Can you ask for a raise, promotion, or more responsibility in your response? Yes, and the response box is one of the better places to do it, because it dates the request and puts it in writing. The framing that works is future-focused: name the responsibility you want, connect it to something in the review, and ask what would need to be true for it to happen. An example: *"Given the training work mentioned above, I'd like to formally own onboarding for new starters in the team from Q1. If that's not the right timing, I'd like to understand what I'd need to demonstrate first, and revisit it at the mid-year review."* Asking for guidance on how to reach a goal is not the same as demanding the goal. It gives your manager a role in the outcome, which makes agreement much more likely. ## The skills that make a review response easier to write Read back over those answers and the same underlying moves keep reappearing: separating the accurate part of the feedback from the inaccurate part, saying the awkward thing in a way that can still be heard, and treating the exchange as something you and your manager are building rather than something being done to you. Those are habits, not personality — and they are learnable. **Working with Your Manager** is the one doing the most work here. Performance reviews are a defined part of this skill: preparing properly, influencing your own evaluation rather than only receiving it, staying future-focused, and asking for what you want. It treats the relationship as a partnership with a shared purpose, which is why the response that works is rarely the one that wins an argument — it is the one that makes your results visible and your intentions clear. **Building Self-Awareness** is what lets you sort the review before you answer it. Receiving evaluative feedback well has a shape: understand what is being said first, then add your own view, then reflect on it — rather than collapsing all three into an immediate defense. It is also what helps you notice when a rating stings because it is wrong, and when it stings because it is close to something true. **Communication** decides how the response actually reads. Leading with your main point, staying brief, and disagreeing without making it personal are the difference between a rebuttal that gets considered and one that gets filed. It also covers a choice people miss: some things belong in the written box, and some belong in a conversation where tone can do half the work. Those three sit inside a set of twelve work skills the free **Job Skills Test** measures, and it is a useful counterweight to a review — one manager's read on one year, next to your own read across all twelve. Where a review leaves you unsure which gap is real, this is the [clearest way to check](https://assessment.headwayskills.com/). ## After the review Some of this will already sound like how you handle these conversations. The parts that do not are the ordinary kind of gap — something you have not been taught yet, not something fixed about you, and something that changes with practice rather than with becoming a different person. It matters more as you go. The higher the stakes of a review — a promotion cycle, a new manager, a role you are being considered for — the more the quality of your response counts alongside the work itself. The fact that you stopped to think about how to answer, instead of signing the form and moving on, is already the part most people skip. So the question is no longer what to write. It is which of these skills is worth your attention between now and the next review. The Job Skills Test is a **free** self-assessment of your work skills. It shows you where you stand across all twelve, and which one or two would make the biggest difference to how conversations like this one go. No preparation, nothing to arrange — you can do it quietly, on your own, before you decide what to commit to. **[Take the test](https://assessment.headwayskills.com/)** Free, takes 7 minutes, and your results appear the moment you finish. ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Employee response to performance review examples: what to write when you agree, disagree, or get vague feedback, plus how to keep it future-focused. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Communication. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/self-awareness.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/working-with-your-manager/employee-response-to-performance-review-examples/ Preferred summary: "Employee response to performance review examples: what to write when you agree, disagree, or get vague feedback, plus how to keep it future-focused." ## Change log - 2026-07-07: Content collection version published.