# Performance Appraisal Communication Examples: What to Say and When Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/performance-appraisal-communication-examples/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/performance-appraisal-communication-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 Performance appraisal communication examples for each stage of your review: what to write in your self-appraisal, how to open the meeting, and how to disagree. ## Key facts - Title: Performance Appraisal Communication Examples: What to Say and When - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Building Self-Awareness - Primary keyword: performance appraisal communication examples - Source page: https://headwayskills.com/knowledge/working-with-your-manager/performance-appraisal-communication-examples/ ## What this page covers - Performance appraisal communication examples for each stage of your review: what to write in your self-appraisal, how to open the meeting, and how to disagree. - Practical guidance for performance appraisal communication examples - How this topic connects to Working with Your Manager ## Detailed explanation The form is open, the meeting is already on the calendar, and the box asking you to describe your own performance is still empty. Most performance appraisal communication examples fall into two piles: sentences a manager writes about someone else, and sentences you write about yourself. The ones that hold up share one structure — a specific behavior paired with an outcome another person could observe — and that structure matters far more than any wording you borrow. Examples become useful once you know where in the review each one belongs, so what follows runs in order, from the weeks before the form is due to the day after the meeting. ## Performance appraisal communication, step by step Eight stages, in the sequence they happen. Each has a different job, and language that works at one will land oddly at another. ### 1. Find out how your review actually works Before you write a sentence, establish the mechanics. University HR pages, such as Baylor University's staff review process, lay the cycle out as named stages with dates attached: self-assessment, manager assessment, review meeting, feedback and development planning, and a midcycle check-in. Your employer will have its own version. Find out which rating scale is used, when the self-assessment is due, and who reads the finished document besides your manager. This is an ordinary question, not a nervous one: *"Before I fill this in — is the scale the same as last year, and does anyone outside the team see the final form?"* Everything else depends on the answers, which is why it comes first. ### 2. Rebuild the record before you write anything Guidance aimed at the person being reviewed, from sources including Upwork and Exec, consistently says the same two things: keep a running record of what you deliver across the year, and re-read both your job description and the commitments made at your last review before drafting. The mechanism behind that advice is memory. Managers weight recent months heavily, so work you did in February is effectively invisible in November unless you supply it. Spend an hour pulling out dated items — what shipped, what you were asked to fix, what you took over from someone else. This list is not the self-appraisal. It is the raw material the self-appraisal draws on, and without it you will write adjectives. ### 3. Write the self-appraisal in behavior-plus-outcome sentences This is the highest-leverage stage, which surprises most people — the meeting feels like the main event, but the document is what gets filed. As ManageBetter points out, the self-evaluation becomes part of the permanent record that both your manager and HR read, and it feeds the final rating. So it is worth writing properly. The rule that runs through the better phrase collections is the one Lattice states plainly: pair a specific behavior with an observable outcome. Their illustration is turning "you communicate well" into "you send project updates with enough context that the team rarely needs to follow up." In the first person, that shape looks like: *"I sent a written summary after each sprint review, which reduced follow-up questions from the client team to about one a month."* The second version can be checked. The first cannot, which is why it reads as a claim rather than evidence. The same rule has a mirror image that matters when you receive comments. The AMA, Echometer and Rippling all warn against feedback aimed at personality rather than work. Rippling's contrast is a useful one to hold onto: "you have a negative attitude" versus "in the last two planning meetings, you raised concerns about the roadmap without offering an alternative — next time, pair the concern with a suggestion." The second is discussable on facts. The first can only be accepted or resented. One more thing explains why the phrase banks run to hundreds of entries. As Echometer and Status.net both show, they work by breaking a broad competency into parts — clarity, listening, written updates, handling disagreement, adapting to who you are talking to — because feedback only becomes actionable once it names a component. You can use the same move on yourself: instead of rating your communication, write one sentence about each part of it. If putting your own strengths into concrete words is the part you get stuck on, a [read on your own strengths](https://assessment.headwayskills.com/) gives you language you can lift straight into the form. ### 4. Decide what you are asking for A review is not only backward-looking, and this is the stage most people skip. Before the meeting, settle on two or three things you want from the next period: a piece of work you would like to own, a goal worth agreeing on, a decision you would like the authority to make without checking, or specific advice on something you are weak at. Write them down. Rippling describes managers using a "stop, start, keep" structure to give feedback inside a review; you can run it in reverse as a request — *"What is one thing you would like me to stop doing, one to start, and one to keep?"* — which produces far more usable direction than "do you have any feedback for me?" ### 5. Open the meeting with your own summary Do not wait to be assessed. Open with a short, plain account of the period, main point first, and then stop talking. Something like: *"Three things I would point to from this year: the migration, the client reporting handover, and the two months covering Sara's accounts. The one I would most like your read on is the handover."* Brief is the operative word here — a couple of sentences, not a presentation. What it does is set the conversation running on evidence rather than impression, and it tells your manager where you would like their attention to go. ### 6. Understand the feedback before you answer it When an evaluative comment arrives, the instinct is to respond immediately. Resist it long enough to understand what is actually being said, because a general judgment is almost always standing in for one or two specific incidents. Ask for them: *"Can you give me an example of where that showed up? I want to be sure I am picturing the same situation you are."* Then add your own view, and leave the reflecting for afterward rather than doing it out loud. Arguing before understanding tends to close down a manager's willingness to elaborate, and the elaboration is the part you can actually use. ### 7. Disagree about facts, not about the rating If something in the evaluation is wrong, contest the specific claim rather than the number attached to it. Name the instance, supply what you have, and keep the tone flat: *"That is not how I remember the March deadline — the brief changed on the 14th and we agreed the new date with the client. Can I send you the thread?"* Separately, there is a process point worth knowing. Guidance for managers, from Rippling to Quantum Workplace, is emphatic that a review should contain no surprises — it recaps feedback already given during the period. So if a criticism is genuinely the first you have heard of it, you can say exactly that, without accusation, and turn it into a request: *"This is the first time it has come up. Could we put a mid-cycle check-in in the diary so I can correct something like this earlier?"* ### 8. Close with something written down, then follow up A review is meant to end with a plan rather than a verdict, as guidance from Nailted and others makes clear. Before the meeting ends, agree out loud on what the next period's goals are and what, if anything, was promised in terms of development or support. Then send a short message the next day confirming it: *"Thanks for yesterday. Writing down what I took away: I am picking up the reporting line from January, and we will look at the scope question again in April. Tell me if I have misread anything."* Two sentences, no ceremony. It creates the record you will open at the start of the next cycle, and closes the gap between what was said and what either of you remembers in six months. ## The skills a review conversation actually tests Read back over those eight stages and notice what almost none of them were about: vocabulary. Preparation, evidence, listening, timing, and knowing what you want are doing the work — and those are things you get better at, not things you either have or do not have. **Working with Your Manager** is the skill the whole cycle sits on. The people who come out of reviews well treat the relationship as a partnership rather than a verdict handed down: they make their results visible long before anyone opens a form, they influence their own evaluation by supplying the evidence, and they stay pointed at what happens next instead of defending the year behind them. It is the difference between attending your review and preparing for it. **Communication** is what the meeting itself runs on, and appraisal-specific communication is a narrower thing than it sounds. State the main point first. Be clear and brief when you would rather be thorough. Know when a topic needs a conversation rather than a line in a form. And handle the two hardest moments — receiving criticism, and saying you think an assessment is wrong — without the exchange turning into either an argument or a retreat. **Building Self-Awareness** decides what you do with evaluative feedback once it arrives. The sequence that works is understanding it first, then adding your own view, then reflecting on it later — and asking for specific, future-focused advice rather than accepting a summary judgment about how you did. It also means noticing when one critical sentence is quietly being promoted, inside your head, into a verdict on your competence. You get better at all three the slow way, one review at a time. If you would rather not wait for the next cycle to discover which one is costing you, the free Job Skills Test covers **all twelve of the skills in this set**, these three among them, and shows you in a few minutes [which of yours needs work](https://assessment.headwayskills.com/). ## Where this leaves you If a few of those steps described something you already do — keeping notes through the year, or asking for the example behind a comment — that is worth registering rather than dismissing. The ones you do not do yet are not a judgment on you either. They are review habits you have not picked up, and you can pick them up without becoming a different person in the room; the language stays yours. They also get harder to skip as you go. The further into a career you get, the less of your work is countable and the more of what your manager knows about your year comes from what you put in front of them. And you have already done the part most people leave until the night before: working out what the conversation is made of, instead of hunting for sentences to paste into a box. ## See where your own skills stand The last thing left is finding out which of these you are actually strong at. The **free** Job Skills Test is a short self-assessment of your work skills — about 7 minutes of honest answers, nothing to prepare — and it shows you where you land across all twelve, and which one or two would make the most difference to how your next appraisal goes. You can take it on your own and sit with the result before deciding whether to do anything about it. **[Get my skills profile](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? Performance appraisal communication examples for each stage of your review: what to write in your self-appraisal, how to open the meeting, and how to disagree. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Communication, Building Self-Awareness. ### 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/communication.md - https://headwayskills.com/knowledge/self-awareness.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/performance-appraisal-communication-examples/ Preferred summary: "Performance appraisal communication examples for each stage of your review: what to write in your self-appraisal, how to open the meeting, and how to disagree." ## Change log - 2026-07-07: Content collection version published.