# End of Year Performance Review Examples: What to Write in Each Section Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/end-of-year-performance-review-examples/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/end-of-year-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 Nine end of year performance review examples - goal outcomes, quantified wins, missed targets, development areas - and what makes each one land with your manager. ## Key facts - Title: End of Year Performance Review Examples: What to Write in Each Section - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Influence - Primary keyword: end of year performance review examples - Source page: https://headwayskills.com/knowledge/working-with-your-manager/end-of-year-performance-review-examples/ ## What this page covers - Nine end of year performance review examples - goal outcomes, quantified wins, missed targets, development areas - and what makes each one land with your manager. - Practical guidance for end of year performance review examples - How this topic connects to Working with Your Manager ## Detailed explanation The form is open, the deadline is somewhere this week, and twelve months of work have collapsed into one blank text box. Useful end of year performance review examples all share the same internal shape: they name the situation, state what you specifically did, and give the result it produced. Everything else — the competency headings, the phrasing, the register — is arrangement around that core. Which is why phrase banks rarely unblock anyone. The wording was never the difficult part. ## Before you write a word: which review are you writing? Most pages on this topic blur two very different documents. A manager writing about a report writes in the third person and is accountable for a rating. An employee writing a self-assessment writes in the first person and is making a case. Borrowing manager phrasing for your own self-review is why so many first drafts read strangely — you end up describing yourself as though observing a stranger. Two practical constraints before you start. Self-evaluations conventionally run 300-600 words, according to Windmill's 2026 self-review guide — long enough for real evidence in each area, short enough that your manager actually reads all of it. And it pays to mirror your organization's own competency headings and rating vocabulary. If your scale separates "meets expectations" from "exceeds expectations," your text should make visibly clear which side of that line you believe you are on. That is a translation job, not a writing job, and it is the reason a phrase copied from a blog so often lands flat. ## Nine end of year performance review examples, and what makes each one work ### 1. The goal-outcome example: every agreed goal, labeled Rather than writing prose around the goals that went well, list [the goals as they were agreed](/knowledge/working-with-your-manager/performance-goals/) at the start of the year and label each one: exceeded, met, partially met, or missed. Then attach the actual number against the target — a goal to grow channels by 20 percent, recorded as exceeded at 40 percent. The labeling is doing more work than it looks. It tells your manager you are working from the same list they are, before any interpretation of results begins. Reviews that open with a curated highlight reel invite the question of what got left out; reviews that open with the full list do not. ### 2. The quantified achievement example: situation, action, impact This is the workhorse. Guru's performance review guide puts the instruction plainly: pick the phrase that matches the behavior, then attach one real event from the year — the situation, what you did, and what changed as a result. The impact clause is the part most people drop and the part managers read for. Compare "I worked hard on client delivery" with "I ran 12 client projects, delivered all of them on time or early, and closed the year at 95 percent satisfaction." Same twelve months, two entirely different documents. If you cannot supply a number, supply a consequence — a deadline that held, a complaint that stopped recurring, a handover that did not need redoing. ### 3. The invisible-work example: the contribution no metric captured Mentoring the new joiner nobody assigned you. Spotting a process that quietly wasted an hour a week. Absorbing a departed colleague's work for two months during a restructure. Guides from PerformYard and Culture Amp both flag this category, and the mechanism is simple: none of it appears in a dashboard, so it exists in the review only if you write it in. For anyone whose measurable numbers are solid rather than spectacular, this is usually the highest-value paragraph in the document — it is the only section nobody else can supply on your behalf. ### 4. The missed-goal example: the shortfall, then the correction Name what fell short. State briefly why, without constructing a defense case. Then state what you are doing differently. Sources are unanimous that glossing over a missed mark reads worse than the miss itself. The correction sentence is what converts an admission into evidence of judgment. The shortfall is history and your manager almost certainly already knows about it; your response to it is current information about how you operate. A review that reports a missed target alongside the change you have already made is a stronger document than one that quietly omits the target. ### 5. The development-area example: a real weakness, not a disguised strength According to PerformYard's self-evaluation guidance, this is the section managers read most closely — and fake humility ("I care too much about quality") is registered as a credibility problem rather than as modesty. A genuine development area is one a colleague would recognize if they read it. The obstacle is usually not honesty but accuracy: it is genuinely hard to name your own gaps from the inside, which is why this section so often defaults to a safe non-answer. If you are staring at it, it can help to see [where your real gaps are](https://assessment.headwayskills.com/) before you commit anything to the form. Pair whatever you name with what you have already tried, so the section reports on work in progress rather than announcing a flaw and stopping. ### 6. The new-skill example: the learning, and where it landed A completed course or certification is an activity, not an achievement. The example only works when it names the skill and the real piece of work it changed — the qualification finished in spring, and the specific project it was applied to by summer. The second half carries all the weight. Training that never touched anything is a line on your calendar; training that changed how a piece of work was done is a line in your review. ### 7. The collaboration example: a team result, with your part named The failure mode here is a paragraph in which "we" did everything and you are invisible. State the team outcome, then the part that was yours: the coordination, the system you built, the difficult conversation you took on so nobody else had to. A modeled version from the self-evaluation guides runs roughly like this — a streamlined tracking system that let the team hit its holiday-rush target weeks early. Team result, individual mechanism, both visible in one sentence. [Claiming your specific contribution](/knowledge/influence/build-good-reputation-work/) is not the same as claiming the team's credit, and managers can tell the difference immediately. ### 8. The next-year goals example: specific, measurable, asked for out loud Close with what you actually want next year — [the responsibility, the exposure](/knowledge/working-with-your-manager/how-to-ask-for-a-promotion/), the skill. "Take on more" reads as filler. A named project, a defined scope, or a specific piece of ownership reads as a request your manager can act on, or at least argue with. This is where a self-assessment stops being a report and becomes a proposal. It is also the section first-time writers most often leave blank, which means filling it in well is one of the cheapest ways to stand apart from the other reviews on your manager's desk that week. ### 9. The manager's version: one achievement, one growth area, one next step If you are the one writing reviews rather than receiving them, balance is functional rather than diplomatic. An entirely positive review develops nobody; an entirely critical one motivates nobody. The pattern that recurs across manager-facing guides names a specific success and a specific limit in the same breath: led a named project ahead of schedule, needs to delegate better under pressure. OnPay's year-end review guidance also recommends [opening the conversation itself with accomplishments](/knowledge/self-awareness/constructive-feedback/) before moving to development areas — partly for tone, and partly because it gives the person a stable footing from which to hear the harder half. ## The skills that make this review easier to write Notice what most of these examples have in common. None of them are really writing problems. The person who finds the form easy in December is the person who spent the year making their work visible, checking their read of it against someone else's, and asking for what they wanted before the deadline made it awkward. **Working with Your Manager** is the skill this whole event sits inside. It treats the review as something you prepare for and shape rather than something that happens to you: preparing properly, influencing your own evaluation, keeping the conversation future-focused, and asking directly for what you want. The examples above are far easier to write when results have been visible all year and expectations were aligned in your regular one-on-ones — the document then becomes a record rather than a reconstruction. **Building Self-Awareness** is what makes the two hardest sections survivable. Receiving evaluative feedback well has a sequence to it — understand what is being said, add your own view, then reflect — and that sequence is the difference between hearing a development area as information and hearing it as a verdict. It is also what lets you write about your genuine strengths specifically rather than reaching for whatever sounds respectable. **Influence** is the one nobody names but everyone uses here, because a self-assessment is a pitch. Understand what matters to the person reading it, keep it simple, lead with concrete examples, and present the drawbacks alongside the wins rather than only the flattering half. That last move is exactly why the guides insist on quantified achievements paired with an honest development plan — a balanced case is more persuasive than an unbroken one. These three sit inside a wider set of twelve work skills, all of them buildable rather than fixed, and the free Work Skills Test measures where you currently stand across the whole set — worth [checking before next year's cycle](https://assessment.headwayskills.com/), when the difference will have had twelve months to compound. ## Beyond this year's form Some of this may already describe how you work. If you have kept notes on what you delivered, or asked your manager mid-year how a piece of work landed, you have been doing the part that makes December straightforward — most people only start assembling evidence when the form appears. None of these are fixed abilities you either have or lack. They are ordinary behaviors that get easier with repetition, and you can build them without becoming a different person at work. The reason they are worth attention now is that the stakes attached to them grow: as your scope widens, more of what you are evaluated on is work that nobody was standing next to you to observe. Knowing which of these skills is already strong for you, and which is currently costing you, is the useful thing to walk out of this review cycle with. The form in front of you closes one year. The question underneath it is what you want to be able to write next December — and that one you can still influence. You can see where you stand right now. The **free** Work Skills Test is a 7-minute self-assessment of your work skills that shows you your position across all twelve, and which ones would make the biggest difference to how the next review reads. ## 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? Nine end of year performance review examples - goal outcomes, quantified wins, missed targets, development areas - and what makes each one land with your manager. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Influence. ### 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/influence.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/end-of-year-performance-review-examples/ Preferred summary: "Nine end of year performance review examples - goal outcomes, quantified wins, missed targets, development areas - and what makes each one land with your manager." ## Change log - 2026-07-07: Content collection version published.