# Writing Performance Reviews: 10 Rules That Beat a Phrase Bank Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/writing-performance-reviews/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/writing-performance-reviews.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 Writing performance reviews is an evidence problem, not a wording problem. Ten rules for self-assessments and manager reviews that are specific and useful. ## Key facts - Title: Writing Performance Reviews: 10 Rules That Beat a Phrase Bank - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Communication - Primary keyword: writing performance reviews - Source page: https://headwayskills.com/knowledge/working-with-your-manager/writing-performance-reviews/ ## What this page covers - Writing performance reviews is an evidence problem, not a wording problem. Ten rules for self-assessments and manager reviews that are specific and useful. - Practical guidance for writing performance reviews - How this topic connects to Working with Your Manager ## Detailed explanation The form is open, the deadline is Friday, and the box is asking for specifics about eleven months you did not write anything down about. Writing performance reviews well is an evidence problem, not a wording problem. A good review — your own self-assessment, or one you write about someone else — is built from specific things that actually happened, described as behavior and outcome rather than as praise or personality, and covering the whole period instead of the last few weeks. Most of that work happens long before the form opens. Here is what to do about it, including if you are reading this the night before it is due. ## Ten rules for writing performance reviews that are worth reading ### 1. Build the evidence file before you need it The one thing that separates an easy review from a painful one is whether you kept notes. A running file — projects finished, problems solved, feedback you received, numbers where they existed — turns the review from a memory test into an assembly job. Baylor University's HR guidance recommends going through those notes at intervals across the year rather than only at the end, so the picture builds gradually instead of all at once. If the deadline is already close, do the compressed version: open your calendar, your sent folder and your task tracker, and walk backward through the period writing down whatever you find. It is a worse method than notes taken at the time, and far better than nothing. ### 2. Cover the whole period, not the last six weeks [Recency bias](/knowledge/self-awareness/unconscious-bias-examples/) is the most-cited failure in the performance review literature, and it shows up in every mistakes round-up from HR publishers like ClearCompany and Windmill. The pattern is always the same: a strong first three quarters and a rough fourth one, rated as a rough year. The cause is not unfairness but memory — nothing was written down, so only recent events are available to write from. The fix is mechanical. Before you draft anything, walk the calendar month by month and note what happened in each. You will recover work you had genuinely forgotten, and it is usually the early-period work that gets lost. ### 3. Use SBI or STAR for every claim When you write about someone else, use SBI: Situation (when and where), Behavior (what they specifically did), Impact (what resulted). When you write about yourself, self-assessment guides from Culture Amp, Qualtrics and Lattice converge on STAR: Situation or Task, Action, Result. These are the same technique from opposite sides of the table, which is why manager-side and employee-side advice keeps arriving at the same shape. Both force one discipline — say what happened, say what was done, say what followed. A paragraph that cannot be written in that form usually turns out to be an impression rather than an observation. ### 4. Describe behavior and outcome, not personality "Is not proactive" and "has a great attitude" describe a person. "Raised the vendor risk two weeks before the deadline, which gave us time to switch suppliers" describes something that happened. Only the second one can be repeated, or changed. Character judgments also provoke the most defensiveness, because there is nothing concrete to discuss — the person being reviewed can only agree or disagree with a verdict about who they are. This applies to your self-assessment too. "I am a strong communicator" is unverifiable; the meeting you unblocked is not. ### 5. Attach numbers where they honestly exist As one practitioner guide puts it, a rating without evidence is an opinion, while a rating with evidence is a defensible assessment. Outcomes, volumes, timelines and before-and-after comparisons make a claim checkable by someone who did not watch you do the work — which, for most of the year, is your manager. Betterworks suggests roughly a 70/30 balance of objective content to behavioral content, offered as practitioner guidance rather than a research finding, so treat it as a direction rather than a rule. Where no number exists, name the consequence instead: who got unblocked, what shipped on time, what stopped going wrong. ### 6. Include at least one real strength and one real growth area A review that is entirely positive develops nobody; a review that is entirely critical motivates nobody. The working floor is [one genuine strength](/knowledge/working-with-your-manager/strength-for-appraisal/) and one genuine area for improvement in every review. "Genuine" carries the weight here. A weakness selected because it sounds safe — too detail-oriented, cares too much — is as useless as leaving the section blank, and it is transparent to anyone who has read a few of these. Pick the one you would name if there were no consequences, then write it as a behavior with a plan attached. ### 7. Write nothing that will be a surprise If a criticism appears for the first time in the annual review, the real failure happened months earlier, in the conversations that never took place. The mistakes literature treats surprise as a process failure rather than a writing failure, which is why the recommended fix is [a regular one-on-one](/knowledge/working-with-your-manager/one-on-one-meeting-with-manager/) rather than better phrasing. The same holds in the other direction. If your manager is going to learn about your best work by reading your self-assessment in November, the problem is not this document. Reviews confirm what has already been said out loud; they are a poor delivery mechanism for news. ### 8. Draft before you read the other side's version Reviewers are advised — by Baylor University HR and by Textio's guide for first-time managers, among others — to write their assessment before reading the employee's self-assessment, so the rating forms independently rather than anchoring to someone else's framing. The mirror-image rule for you is more interesting, and almost nobody states it: your self-assessment is read as input to a judgment that is already partly formed. That changes what belongs in it. Its most valuable content is the work your manager could not have seen — the quiet fix, the problem that never became an incident, the help you gave someone on another team. ### 9. Refuse the phrase bank The most abundant resource for this task is the ready-made comment. PerformYard publishes 200+ review phrases, Quantum Workplace 171, ThriveSparrow 180+, HRMorning 72, Indeed 45. Those same publishers run articles naming generic, interchangeable feedback as the top mistake managers make, often on adjacent pages. The contradiction is structural rather than hypocritical: copy-paste phrases produce exactly the vague feedback the mistakes lists warn about, because a sentence built to fit any employee describes none of them. Borrowed lines are also recognizable as borrowed. Use the banks to see the register if you want, then write your own sentences about your own year. ### 10. End facing forward The last section should be about the next period: what changes, what support you need, what [the goals](/knowledge/working-with-your-manager/performance-goals/) are. It is the part the review can actually influence, and in most drafts it is the thinnest — a few lines added once the writer has run out of energy. If you are writing a self-assessment, this is where you ask for what you want. Not the polite version of it: the actual project, the responsibility, the training, the title. The section is an opening rather than a formality, and it is the one place in the document where you set the agenda. If you are not yet sure what to ask for, getting [a read on your work skills](https://assessment.headwayskills.com/) is a reasonable way to work out which direction is worth pushing. ## What a review really measures Read back over those ten rules and most of them are not about writing at all. Tracking your own contribution. Saying the difficult thing in March rather than November. Asking, in writing, for something you want. The document mostly makes visible how well you have been doing those things all year. **Working with Your Manager** is where most of it sits. Performance reviews are part of this skill directly — preparing properly, influencing your own evaluation, staying future-focused, asking for what you want — but the part that decides the outcome happens earlier. Agreeing what good looks like, making results visible as they happen, and keeping the relationship a working partnership rather than an annual verdict is what leaves you with something worth writing down. **Building Self-Awareness** is what the blank boxes are actually testing. You are asked to state, in your own words, what you are good at and where you fell short — which needs an honest read on your natural strengths rather than a modest list of your duties, and the composure to take the evaluative feedback that comes back without treating it as a threat. **Communication** does the rest. A review is writing that has to survive being skimmed by someone with twelve more to read: main point first, clear and direct, brief, specific enough to act on. And when you are the one writing about somebody else, it is what makes a criticism land as workable rather than blunt or padded. None of that is fixed, and none of it is a personality type — these are behaviors people learn, usually by getting them wrong first. If you want a read on where yours stand before the next cycle comes around, the free Job Skills Test covers all twelve of the work skills this framework treats as learnable, these three included, and shows you [which gaps matter most](https://assessment.headwayskills.com/) right now. ## Your next review starts tomorrow Some of this may already sound like how you work — the note you made after a project went sideways, the thing you raised early instead of saving it. Those are the same habits the good version of this document is built from; they just have not been organized yet. The rest is learnable, and it is worth knowing which parts you would gain most from building, because these skills tend to count for more as the work gets bigger. A review is a small stake. Two or three years from now the same underlying behaviors are what a promotion conversation, a difficult project or a new manager will run on. You have already done the part most people skip, which is thinking about the review before the form is due rather than after. The useful next move is knowing where you actually stand. ## See where your work skills stand The only thing left is to find out which of these are already working for you and which are worth deliberate attention before your next review cycle. The **free** Job Skills Test is a self-assessment of your own work skills: it takes about 7 minutes, covers all twelve skills in the framework, and gives you a clear picture of where you are strong and which two or three would make the biggest difference to how your next year is judged. ## 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? Writing performance reviews is an evidence problem, not a wording problem. Ten rules for self-assessments and manager reviews that are specific and useful. ### 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/writing-performance-reviews/ Preferred summary: "Writing performance reviews is an evidence problem, not a wording problem. Ten rules for self-assessments and manager reviews that are specific and useful." ## Change log - 2026-07-07: Content collection version published.