# Bad Performance Review Example: What It Says and What to Do Next Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/bad-performance-review-example/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/bad-performance-review-example.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 A bad performance review example is usually vague and template-worded - about reliability, not ability. How to read yours, respond, and prevent the next one. ## Key facts - Title: Bad Performance Review Example: What It Says and What to Do Next - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Building Resilience - Primary keyword: bad performance review example - Source page: https://headwayskills.com/knowledge/working-with-your-manager/bad-performance-review-example/ ## What this page covers - A bad performance review example is usually vague and template-worded - about reliability, not ability. How to read yours, respond, and prevent the next one. - Practical guidance for bad performance review example - How this topic connects to Working with Your Manager ## Detailed explanation If you have just read a review of your own work that rated you "needs improvement," or listed problems you did not know you had, the most useful thing to know first is that most bad reviews look remarkably alike. A typical bad performance review example is thin on specific incidents, heavy on standard phrases about reliability or attitude, and written in language pulled from a template. That does not make it wrong. It does mean the wording tells you less than it feels like it does. Which is the whole difficulty of reading your own review: the lines that sting hardest are often the ones carrying the least information. ## What does a bad performance review example actually look like? Search for one and you will mostly find phrase banks written for managers, not for the person being reviewed. Business Management Daily publishes 90 sample phrases for negative reviews; JOP lists 42; the Manager Tools forums host threads of real ones. Read as someone who just received a bad review, those lists work as a decoder — they show the standard wording managers reach for, which is why so many reviews sound generic. The published examples cluster tightly. "She is frequently late to work." "She often runs behind schedule, negatively impacting the workday flow." "She responds to communication outside of the expected time frame." "She struggles to accept constructive criticism." Three of those four are about punctuality, pace, and responsiveness; the fourth is about how you take feedback. Notice what is missing: almost none of it concerns whether you can do the job. Most bad reviews are about consistency and coachability, and both are far more changeable than talent. ## Is my review unfair, or is my manager right? There is a test you can run on the document itself. Guidance written for managers — Factorial HR's is typical — insists that every criticism cite a specific instance, because vague feedback is confusing and ineffective. Employment-law firms such as Miller Cohen name the same thing from the other side, listing vague generic feedback as a red flag alongside ratings based on personal opinion or stereotype, and goals that changed without your knowledge. So go criticism by criticism and ask whether a named incident is attached. A criticism with no incident is not automatically false, but it is not yet actionable, and asking for the incident is a fair, unaggressive request. One rating error is worth knowing by name. The University of South Carolina's rater-training materials describe the "horns effect": one negative incident bleeding into unrelated categories, so someone who missed a single deadline gets marked down on overall reliability too. That explains a review that feels disproportionate — the boxes are not independent, and one bad month can pull several down at once. If you believe a rating was driven by your age, race, national origin, gender, disability, or religion, that is a different situation with formal complaint routes, and worth raising with someone qualified rather than handling alone. ## Does a bad performance review mean I am about to be fired? Usually not, but this sits underneath most of the other questions, so it deserves a straight answer. The formal step between a bad review and a termination is normally a performance improvement plan: a fixed list of goals, a set time window, and documented check-ins along the way. Practitioner and anonymous professional-forum accounts describe these plans running both ways — sometimes as a documented exit path, sometimes as a real second chance that motivated people complete — and describe stack-ranked systems where a bottom-20% cutoff can trigger one even for acceptable ratings. None of that is verifiable, so treat it as how these systems commonly work rather than as fact about yours. The resolvable version of this worry is a direct question to your manager: am I on a formal plan, or is this a rating to improve on by the next cycle? You are entitled to know which one you are in. If your reaction is that you want out either way, that is normal: a survey by Reflektive, a performance-management software company, found 85% of respondents would at least consider leaving over a review they saw as unfair — a vendor survey, so read it as directional. But wanting to leave tells you how the review landed, not whether it was accurate. One bad review after several good ones is information about a year; a pattern across managers is information about fit. ## What should I say in the meeting itself? Very little, and this is one of the few points where the advice is genuinely settled. Forbes, Crucial Learning, Indeed and Your Office Coach all land on the same protocol: do not respond reflexively, take written notes while your manager talks, and ask clarifying questions instead of mounting a defense. Several suggest treating it as an ordinary meeting, which sounds cold but creates enough distance to actually hear the content. Nothing good gets decided in that room: you cannot check a date, find an email, or think clearly while your rating is read out. If you already argued your way through it, that is recoverable. ## Can I write a rebuttal, and does it ever work? Yes, and it is a normal HR artifact rather than an escalation. Indeed publishes a structure for a written response, and every source that covers it attaches the same rule: argue with evidence, not emotion. One documented case shows the mechanism plainly — an employee criticized for sending a client report without clearance produced the email in which the manager had approved it. That case also shows the limit. A rebuttal works when a specific factual claim can be contradicted with a specific document. It does not work against a judgment call, and a long rebuttal aimed at a subjective rating tends to read as the very thing the review accused you of. Before you sign anything, it is reasonable to ask what your signature is taken to mean where you work, and whether a written response can be attached to the file. ## What should I do in the first few days after? The most consistently recommended action is also the simplest: ask for a follow-up meeting. Your Office Coach and Primalogik both treat it as the move that makes everything else possible. It separates the emotional moment from the substantive conversation, gives you time to check claims against your records, and lets you arrive with a plan instead of a defense. It is also the middle path. The two instincts after a bad review are to argue immediately or to never mention it again, and both go badly. A meeting a few days later is neither. Come with two or three specific questions and one proposal for what you will do differently, and the conversation stops being about the document. ## How do I stop this happening again next year? Almost nothing written about bad reviews addresses this, which is strange, because being blindsided is the part most people actually want to fix. A review that surprises you is rarely a single bad meeting. It is usually twelve months in which nobody told you where you stood and you did not ask. The prevention is unglamorous: regular one-on-one contact with your manager, short and frequent rather than annual, where you ask how your work is landing and make your results visible as you go. Managers write reviews from what they remember and what they were told. If the clearest thing they remember is the month you were late twice, that is the review you get. There is a second half to it. A review often names something nobody has ever actually taught you — how you handle disagreement, how you communicate under pressure, how you organize your week. Separating the real criticisms from the mis-rated ones is easier with your own read to compare against, so [which skills actually need work](https://assessment.headwayskills.com/) is worth checking rather than guessing at. ## What decides how the next one reads Read those answers back together and a pattern shows up. Almost none of the useful moves are things you do to the document — they are things you do in the room, in the days after, and across the year before. Which is why two people can receive the same review and end up somewhere completely different twelve months later. **Working with Your Manager** is the most direct of the three. A review is a moment inside that relationship, not a verdict delivered from outside it, and the version that produces surprises is the one where the only real conversation happens once a year. Treated as a partnership, it means regular one-on-ones, honest questions about how your work is landing, and a review you have partly authored — because you already knew what would be said and made your results visible while they were happening. **Building Self-Awareness** governs what you do with the feedback once you have it. The sequence that works is to understand the criticism fully before responding, then add your own view, then reflect — close to the opposite of what a difficult review makes you want to do. It is also what turns "needs improvement on communication" into something usable, by going back and asking for specific, future-focused advice rather than accepting a phrase you cannot act on. **Building Resilience** is what buys you the time to do either of those. The first days after a bad review are crowded with automatic thoughts — I am going to be fired, everyone knows, I am bad at this — and those are recognizable thinking errors: all-or-nothing, filtering out everything positive in the document, mind-reading your colleagues. Naming them lets you read what the review says instead of the version your head wrote, and separate the ratings you cannot change from the cycle you can. These are habits rather than fixed traits — worth holding onto if your review implied otherwise. A review rarely stays inside three of them, though, and the free Job Skills Test covers **all twelve**, so it is a quick way to [name the actual gaps](https://assessment.headwayskills.com/) before your next conversation with your manager. ## What this means for you Some of this may already feel familiar. You read a document about your own shortcomings all the way to the end and then went looking for what to do with it, instead of filing it somewhere and hoping next year goes better — that is the harder half of receiving feedback, and it is the half most people skip. None of the skills behind a good review are fixed. They are built at whatever pace the year allows, and you can build them without becoming a different person at work — what changes is a few specific behaviors, not who you are. They also carry more weight as the stakes attached to each review rise, which is an argument for starting now, while a single bad cycle is still a cheap lesson. So the question worth sitting with is not whether the review was fair. It is which two or three things you want to be different when the next one is written. ## Find out which ones to work on The only thing left is to find out where you actually stand — not according to one manager, in one review, in one year. The **free** Job Skills Test is a short self-assessment of the workplace skills this article has been circling. It scores you across all twelve and shows which one or two would make the biggest difference to how your next review reads. It takes about seven minutes, and your results come up the moment you finish. If you do one thing after a bad review, make it a small one. **[Take the test](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and your results appear as soon as 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? A bad performance review example is usually vague and template-worded - about reliability, not ability. How to read yours, respond, and prevent the next one. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Building Resilience. ### 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/resilience.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/bad-performance-review-example/ Preferred summary: "A bad performance review example is usually vague and template-worded - about reliability, not ability. How to read yours, respond, and prevent the next one." ## Change log - 2026-07-07: Content collection version published.