How to Respond in Writing When You Disagree With a Performance Review

The review lands, you read your rating, and one line does not match what you believe happened this year. Maybe a project you led got credited to someone else, maybe “needs improvement on communication” arrives with zero examples, maybe the overall score dropped even though every specific comment reads as positive. You have a choice most people do not think through: say nothing and let the document stand, vent in a meeting that gets summarized in one line of someone else’s notes, or put your own account in writing.

The written response is the only one of the three that becomes part of the permanent record on the same footing as the review itself. That also means it is the one most likely to be read months later by someone deciding on a promotion, a layoff list, or a reference, so it has to do more than express that you are unhappy. It has to read as a document, not a complaint.

Separate the Rating From the Relationship

Your manager wrote the review; they did not necessarily design the process, the calibration meeting, or the rating scale that forced a number onto something that does not reduce cleanly to a number. Write as if a different person, maybe HR, maybe your manager’s manager, will read your response without any of the context of your working relationship. That person cares about facts and dates, not about whether you feel your manager likes you.

This also protects you when the relationship is fine and the review is just wrong on one point. A measured rebuttal is easy for your manager to agree with afterward. One that reads as a referendum on the relationship forces them to defend the whole document to save face, a worse outcome even when you are right.

Attack the Evidence, Not the Verdict

The single biggest mistake in these responses is arguing with the rating itself: “I don’t think ‘meets expectations’ is fair.” A rating is an opinion, and opinions are hard to dispute in writing. The specific claims underneath the rating are usually not opinions: a date, a deliverable, an outcome. Dispute those, one at a time, with what actually happened.

Before:

I disagree with my rating this cycle. I worked extremely hard all year and feel this doesn’t reflect my contributions. I was surprised and honestly a bit hurt by the “needs improvement” comment on communication, since I always try to keep people in the loop.

After:

I’d like to add the following to the record regarding two specific points in my review. First, the note that the Q2 migration “slipped without warning”: I flagged the risk in the March 14 status update and again in the April 2 planning meeting, both documented in the project channel. Second, on communication: I sent weekly written updates to the team from January through August (attached). I’d welcome specific examples of where communication fell short so I can address them directly.

The second version wins because it can be checked. It names dates, points to artifacts, and asks a direct question instead of making a general claim about effort or feelings. A reader who was not in the room can evaluate it in under a minute.

Know What You’re Actually Asking For

A response that only disagrees, without stating what you want done about it, gives the reader nothing to act on. Decide before you write whether you want a correction to a specific line, a statement attached to the file as your side of the record, or a follow-up conversation before the review is finalized. Say which one.

What happens to that request depends on where you work. The right to attach a written rebuttal to your personnel file is not universal in the United States, but it is explicit law in some states: Washington’s RCW 49.12.250 gives an employee who disagrees with information in their file the right to have a rebuttal statement placed in it. Other states and countries handle this only through company policy, so check your handbook or HR before assuming a right that may not apply where you work. Either way, naming the outcome you want is what turns a complaint into a request someone can grant.

If your review is really an entry point into a formal improvement process rather than a routine cycle, the document you are responding to may become the basis for a performance improvement plan, and it is worth reading how those are supposed to be structured so you know what a fair one looks like before you are handed one.

Keep the Tone Cooperative Even When the Content Isn’t

You can dispute every fact in a review while still assuming good faith on the other side: a miscommunication, a manager writing under deadline, a rating scale that flattens nuance. That framing costs you nothing and is often accurate. Reserve firmer language, “this does not match my documented performance”, for claims that are actually contestable, not the review as a whole.

The same discipline that helps you disagree with your boss in writing on a day-to-day decision applies here at higher stakes: lead with what you agree on if anything is genuinely fair, state your case with evidence, and propose a next step rather than just registering a protest.

A Wrivio Context for performance review responses could say:

Rewrite this as a calm, specific written response to a performance review. Keep every date, project name, and figure exactly as written. Do not soften disputed claims into vague agreement, and do not add an apology I did not write. Keep the requested outcome (correction, attached statement, or follow-up conversation) explicit.

Press Ctrl+Shift+Space, paste your draft, and check the diff before you send it. Watch especially for a first draft that reads angrier than you intend, that is the version a rewrite should calm down without erasing the substance of your disagreement.

Common Questions

Should I respond to every performance review I disagree with, even minor points?

No. Save a written response for claims that are factually wrong, that could affect a future decision like a promotion or a layoff, or that you genuinely cannot let stand uncorrected. Responding to every minor phrasing issue dilutes the response you actually need someone to take seriously.

How long should the response be?

Shorter than you think. Three to six paragraphs covering the specific points in dispute and the outcome you want is usually enough. A long response reads as an argument rather than a record.

Should I send it to my manager, HR, or both?

That depends on your company’s process, and most have one for exactly this situation. If you are unsure, ask HR how disagreements with a review are typically documented before you write anything.

What if my manager asks me to soften or withdraw the response?

You can decline. A request to soften a factual correction is worth noting in writing yourself, but keep that note separate and calm rather than folding it into the original response. If the request feels like retaliation for disagreeing, that is worth raising with HR directly.

Can I include how the review made me feel?

One sentence, at most, and only if it is tied to something concrete, such as feeling blindsided by feedback that was never raised earlier in the cycle. A response built mostly around feelings reads as venting rather than a correction, even when the feelings are completely reasonable.

Download Wrivio for Windows to turn a first draft written while you are still frustrated into a response that reads as calm and specific instead.