# Yearly Review Examples: The Questions People Actually Ask Before Writing Theirs Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/yearly-review-examples/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/yearly-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 Yearly review examples that help: what to write, how long it should be, how honest to be about weaknesses, and what to do when you can't remember your year. ## Key facts - Title: Yearly Review Examples: The Questions People Actually Ask Before Writing Theirs - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Influence - Primary keyword: yearly review examples - Source page: https://headwayskills.com/knowledge/working-with-your-manager/yearly-review-examples/ ## What this page covers - Yearly review examples that help: what to write, how long it should be, how honest to be about weaknesses, and what to do when you can't remember your year. - Practical guidance for yearly review examples - How this topic connects to Working with Your Manager ## Detailed explanation The box asking what you achieved this year is blank, the deadline is on Friday, and most of what you find when you search for yearly review examples is a list of pre-written phrases. A useful yearly review answers four things in order: the goals you were set and what you delivered against them, two or three achievements described with evidence, one honest development area with a plan attached, and what you want to focus on next year. Around 300 to 500 words covers it. The part worth copying from a good example is that shape. What goes inside it has to come from your year rather than from a phrase list, which is why the questions below are mostly about finding the material instead of finding the words. ## What do you actually write in a yearly review? Four things, in the order most forms ask for them. First, the goals you were set at the start of the cycle and what happened to each one: hit, missed, changed, or overtaken by something more urgent. Second, two or three achievements, each with a result attached rather than an adjective. Third, one development area, stated plainly, with what you are doing about it. Fourth, what you want from the coming year. That four-part shape recurs across employer templates, from HR guides like AIHR's annual review template to university systems like Stanford's year-end review process. One warning about what you will meet while searching: a large share of the pages ranking for review examples are written for managers rating their staff, not for you writing about yourself. Check who a page is addressing before you borrow anything from it. ## How long should a yearly review be? Shorter than most people fear. For an open-ended box, roughly 300 to 500 words is the convention the guidance settles on. Where your employer uses a structured form with a section per competency, the recommended target is two to four sentences of specific, evidence-backed commentary per section, not a paragraph each. There is a practical reason behind those numbers. Your manager is reading a stack of these, often in one sitting, and length is not what makes a review persuasive; retrievable detail is. Two sentences naming a project and its outcome get remembered when the meeting comes round. A dense page of general commentary gets skimmed. If the form gives you a small box, treat that as the real instruction. ## What does a good yearly review example look like? The structure almost every guide recommends is STAR — situation, task, action, result — borrowed from interview preparation. Its value here is mechanical rather than stylistic: it forces you to end on a result, which is the part self-reviews most often leave out. The difference shows up immediately in a contrast the sources return to again and again. "Exceeded Q3 sales by 18% against a 12% team target" says something. "I'm a strong communicator" says nothing, and could have been written by anyone in the building. A fuller entry looks like this one, quoted in the self-assessment guidance: "I led the customer onboarding revamp this quarter, reducing time-to-first-value from 14 days to 6 and freeing two support reps for higher-value work." That example also settles the worry about sounding arrogant. Boasting comes from adjectives about yourself, because those are opinions your reader has not agreed to. A fact is not a boast. Where you have a number, use it; where you do not, name the concrete change instead — what stopped happening, what got faster, who no longer has to chase you — and let the result do the claiming. ## What if you can't remember what you did all year? Then you do what the university HR guides put first, ahead of any writing. Michigan State's preparation guide and UAB's self-evaluation tips both open the same way: before drafting a sentence, list everything — every project you contributed to, every assignment you were handed, everything you learned, every problem that landed on you. Memory is the wrong tool for this. Evidence is the right one. Work backward through the review period using records you already have: your calendar, your sent mail, whatever tracker your team uses, the thread where somebody thanked you. Expect the list to come out long and messy, because that is raw material rather than an answer. Cutting twenty items down to four good ones is a far easier job than starting from an empty box. ## How honest should you be about your weaknesses? Honest enough to name one real thing. Every credible source insists on including a genuine development area, and the reason given is reputational rather than moral: a self-assessment with nothing to improve reads as defensive, and that costs you credibility on the parts you did want believed. There is an upside most people miss. UC Davis's guidance frames the development section as the natural place to ask for support — training, a different kind of project, time to build something you are missing. Written that way, the weakness box stops being a confession and becomes a request. Pick a gap that genuinely affects your work, say what happened, say what you took from it, and say what you have already changed. If you are unsure which gap is the real one, it is worth [checking where your skills stand](https://assessment.headwayskills.com/) rather than naming whichever one feels safest to admit. ## What do you write if you had a bad year? The same three things, in order: what you did accomplish, where you ran into difficulty, and what you took from the experience. That is the structure the guidance recommends for exactly this situation, and it works because it reads like someone who has been paying attention rather than someone hoping nobody looks. Two things are worth separating. Circumstances outside your control — a cancelled project, a reorganization, a team that halved — are context, and stating them plainly once is not making excuses. What you did inside those circumstances is your part, and that is the half worth writing about. Avoid both failure modes: pretending the year went fine, which your manager can check, and over-confessing, which turns one difficult stretch into a general verdict on you. ## What if your manager's rating doesn't match yours? Ask about the evidence before you argue about the score. Career guidance on difficult reviews is consistent here: treat the gap as a question about what your manager was looking at and what they expected, not as a verdict to be overturned on the spot. A rating usually rests on particular examples and a particular reading of the goals, and those are the things you can actually discuss. A workable sequence is to hear it out fully, ask what specifically it was based on, then add your own view with the evidence you gathered. Disagreeing is legitimate. Disagreeing before you understand what you are disagreeing with is what turns a review into a standoff. And if the answer reveals your manager did not know about half of what you did, that is worth learning — it is a visibility problem, and it is fixable long before next year. ## Should you bring up a raise or promotion in your yearly review? Yes, in the forward-looking half. Guidance across employer templates treats goal-setting for the next period as a standard section, and the review as the natural moment to raise development, resources, and progression. It is also the section people fill in last and thinnest, which is a waste, because it is the part with actual leverage: the backward half is a record, the forward half is a request. Name what you want specifically — the scope, the responsibility, the training, the decision-making room — and put it in the document as well as saying it in the meeting, so it exists in writing when your manager is making cases for a group of people rather than for you alone. Managers cannot act on a preference you never stated, and this is the one moment in the year when the question is formally on the table. ## Why review season is easier for some people than others Read back across those answers and notice how few of them were really about wording. Almost every one turned on something that happened before the form arrived: what you recorded during the year, whether your manager already knew what you delivered, and how well you handle being assessed. Those are habits, and habits can be built. **Working with Your Manager** covers most of this ground. The review is one scheduled moment inside a relationship that runs all year, and the things that decide how it goes mostly sit outside the form — meeting one-on-one regularly, making results visible as they happen, agreeing what good looks like before you are measured against it, and staying future-focused enough to ask for what you want instead of waiting to be offered it. Preparing properly is part of the skill, not a trick sitting beside it. **Building Self-Awareness** is what makes the honest sections possible. Naming a strength you genuinely have, rather than something you are merely competent at, is harder than it sounds, and so is naming a gap without hiding it or over-apologizing for it. It also carries you through the feedback itself: understand it first, add your own view second, reflect on it afterward. Asking for specific, future-focused advice is what turns a rating into something you can act on. **Influence** is the part that shapes the outcome. A self-assessment is a case made to someone with a stack of other people's cases to read, so the ordinary rules apply: know what matters to your reader, keep it simple, argue with examples rather than adjectives, include the drawbacks instead of only the wins, and follow up on whatever was agreed. The standing it builds rests on delivered results, not on how the sentences sound. Every review closes by asking what you will work on next, and guessing is a poor way to answer that. It costs nothing to [get a baseline reading](https://assessment.headwayskills.com/) instead — a free score across **all twelve of the workplace skills** this last one belongs to, so next December's development area is something you chose in advance and worked on, rather than something you invented in the box. Some of this may already be how you work: a note kept when a project lands well, or the instinct to check last year's goals before writing about this year's. Whatever is not there yet is learnable, and building it does not require becoming a different person at work — mostly it means writing things down earlier. Looking for examples before you started drafting is itself the step the HR guides put first and most people skip, which is a better starting position than it feels like from where you are sitting. Reviews also get more consequential as you go: the further into a career you are, the more of your progress runs through documents and conversations like this one rather than through the work itself. Which makes the useful question not what to write by Friday, but which of these you want to be better at by next year. ## Find out which of these to work on There is one thing left worth doing before you go back to the form. The Job Skills Test is a **free** self-assessment of your workplace skills: it takes about 7 minutes, scores you across all twelve, and shows which one or two would make the biggest difference — to next year's review, and to the conversations on either side of it. **[Get my skills profile](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and your results appear straight away.* ## 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? Yearly review examples that help: what to write, how long it should be, how honest to be about weaknesses, and what to do when you can't remember your year. ### 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/yearly-review-examples/ Preferred summary: "Yearly review examples that help: what to write, how long it should be, how honest to be about weaknesses, and what to do when you can't remember your year." ## Change log - 2026-07-07: Content collection version published.