# How to Write a Self-Assessment for Your Performance Review Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/self-assessment-performance-review/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/self-assessment-performance-review.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 step-by-step guide to writing a self assessment for a performance review: gather the evidence, write about results, and name a development area. ## Key facts - Title: How to Write a Self-Assessment for Your Performance Review - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Influence - Primary keyword: self assessment performance review - Source page: https://headwayskills.com/knowledge/working-with-your-manager/self-assessment-performance-review/ ## What this page covers - A step-by-step guide to writing a self assessment for a performance review: gather the evidence, write about results, and name a development area. - Practical guidance for self assessment performance review - How this topic connects to Working with Your Manager ## Detailed explanation The self assessment landed in your inbox with the performance review a week out, it has four or five boxes on it, and you have no idea what belongs in them. That is the ordinary starting position, not a sign you are behind. A self assessment for a performance review is your own written account of the review period: what you achieved, where you struggled, and what you want next. You write it by reconstructing the period from evidence rather than memory, describing results instead of duties, and naming one development area with a specific request attached to it. The part that makes it feel harder than it should is rarely the wording. It is that most of the work happens before you write anything. ## How to write a self assessment for a performance review, step by step The eight steps run in order, and the order matters — each depends on what the last produced. Jumping straight to the writing is the common mistake, and why people end up hunting for example phrases to fill space that should hold their own year. ### 1. Find out what you are actually being asked Before you write a sentence, get three things in front of you: the blank form, the rating categories your manager will score you against, and the deadline. Most people know the deadline and none of the rest. That matters, because the categories decide which achievements are worth writing about. Excellent work described under a heading nobody rates does not move your evaluation; the same work filed against a category your manager scores does. It also helps to know what the process feeds. HR sources including Paylocity and SurveyMonkey describe the purpose plainly: the self-assessment gives you a voice in your own appraisal and acts as a counterweight to a manager's necessarily partial view of your year. Which means adding your account is not presumptuous — it is what the process is asking for. Cadence varies too, from annual packets to quarterly cycles, which changes how much reconstruction is ahead. ### 2. Rebuild the period from evidence, not memory This is the step people skip, and it decides whether you have anything to say. Guides from ClickUp and monday.com point at the same sources, all already on your laptop: your calendar, your sent mail, whatever project tool your team runs on, the relevant chat channels, notes from your [one-on-ones](/knowledge/working-with-your-manager/one-on-one-meetings/), feedback from the last review, any mid-year write-up. Work backwards through them month by month and build a plain list of what you did. The reason to reconstruct rather than think hard is that memory is weighted toward recent months. Write from recall in December and November arrives in detail while March is a blur — which quietly undersells the half of the period nobody else remembers either. The University of Maryland's HR guidance suggests allowing one to two hours to review your documentation and complete the assessment. Read that as a diagnostic rather than a target: it assumes documentation exists. If you kept none, the reconstruction alone will outlast the writing, and that is normal the first time. ### 3. Turn activity into outcomes Now go back through the list and ask of each item: what changed because of this? The advice recurring across Lattice, Culture Amp and Leapsome is a single shift — from what you worked on to what your work produced. The pattern is consistent: name the accomplishment, give the evidence, state the impact, with a measurement wherever the work allows one. Their examples follow that shape closely — take ownership of a project, deliver it on schedule, point to the improvement that followed. The contrast is what makes the effort worth it. "Managed the onboarding project" reads the same whether you did it brilliantly or badly, so it gives your manager nothing to rate upward. What the project changed does. Anything where nothing changed comes off the list. ### 4. Map your best material onto the rating categories Take the form one section at a time rather than writing a continuous narrative. For each section, work out what behavior it is rating, then choose the single strongest item from step 3 that proves it. ClickUp and Sprad both describe it this way. Your manager scores against those categories, so an achievement matching no category and a great achievement in the wrong box come to much the same thing. One well-evidenced example per section beats four thin ones, which dilute the strong one rather than adding to it. ### 5. Write the development section as a request This is the section most people want to fudge, and fudging costs more than honesty. UC Davis's HR guidance frames the annual review as exactly the right occasion to raise a skill you would like to develop, which changes what the section is for. It is not a confession to be used against you; it is the one place on the form where a real gap converts into training, exposure, or a different kind of assignment. The structure the sources converge on: name the area, say what you have already tried, and attach the specific thing you want — a course, a harder project, or time with someone who does it well. One area treated properly works better than three treated briefly. And choose something genuine: an area your manager has already noticed reads as [self-awareness](/knowledge/self-awareness/self-awareness-at-work/), while a safe-looking invention reads as evasion. Choosing that area is harder than it sounds, because the gaps you see clearly are rarely your largest. If you are unsure which to name, it is worth [seeing which skills need work](https://assessment.headwayskills.com/) before you commit one to paper — the free Work Skills Test gives you an outside read across your work skills, including ones you had not thought to check. ### 6. Say what you want for the next period Most people write something vague enough to be safe in the goals box. Wrong instinct: this is the one formal moment when next period's expectations get set with your input in the room. Propose goals that are [challenging but achievable](/knowledge/working-with-your-manager/performance-goals/); both conditions matter. Then name explicitly any change you want in the scope of your work, the decisions you are allowed to make alone, or the responsibility you carry. If you want it and do not write it down, the default is that nothing changes. ### 7. Cut it down and read it the way your manager will Sprad's guidance puts the useful length at roughly three to five substantive paragraphs across achievements, collaboration and development. Hold the number loosely — it is one source — but the principle holds. Length is not evidence of contribution, and a section your manager abandons halfway influenced nothing. So cut. Delete adjectives with no evidence behind them, then run one test over what is left: could a colleague have written this sentence about their own work? If yes, it is still generic, and it is not working for you yet. ### 8. Submit it early and prepare for the conversation Sprad recommends submitting two to three days before the meeting rather than at the deadline. Lead time lets your manager notice in advance where your account and theirs diverge, and think about it before you are both in the room. That single change alters the character of the meeting: instead of a verdict read out to you, it becomes a discussion of a gap your manager has already considered. Go in knowing your two or three strongest items well enough to talk about without reading, knowing the one thing you are asking for, and expecting at least one point where [their read differs](/knowledge/working-with-your-manager/performance-feedback/). That disagreement is the useful part of a review, not the failure of it. ## The skills that make this easier every time it comes around Look back at what those eight steps asked of you. Very little of it was writing. Most of it was knowing what your manager is being asked to score, judging your own work honestly enough to name a real weakness, and building a short case a busy reader will act on. Those parts get easier or harder depending on habits built outside review season — and they are habits, not fixed features of who you are. **Working with Your Manager** treats performance reviews as an explicit part of the relationship: prepare properly, influence your evaluation, stay future-focused, ask for what you want. The lever most people miss sits earlier than the form, in the regular one-on-one — meeting every week or two, keeping notes, making results visible while they are fresh. Do that and the self-assessment stops being reconstruction and becomes a summary of a record you already share. It also explains why an honest account outperforms a polished one: the relationship works as a partnership around a common purpose, and both of you can tell when it is being managed. **Building Self-Awareness** covers the two questions the form puts to you directly — what you are genuinely good at, and where your blind spots are. Getting past adjectives means asking yourself concrete questions about how you work, how it feels, and what results followed, rather than reaching for a label. Just as usefully, it covers taking feedback: understanding it first, adding your own view, then reflecting. That sequence keeps your manager's version from landing as an attack on the day it differs from yours. **Influence** — the kind you earn rather than hold — is what a self-assessment quietly trades in. It is a short written case aimed at one busy reader with a stack of them to get through, and what moves it is preparation, simplicity, concrete examples in place of claims, and a willingness to show the drawbacks alongside the wins. That last part is why an honest development section reads as credible rather than damaging. Then persistence: following up afterward on what you were promised, rather than waiting a year to raise it again. This review will not be your last, which is the argument for finding out where these stand now instead of the week before the next one. The free Work Skills Test scores you across **all twelve of the work skills this framework treats as learnable**, the three above among them, so you can [see where your strengths sit](https://assessment.headwayskills.com/) and which one would repay attention first. ## What this looks like a year from now Some of this may already describe how you work — keeping a note of what you finished, or asking early what "good" is going to mean rather than finding out at the review. Small habits, and the ones that decide whether the next self-assessment costs an hour or an evening. Wherever the gaps sit right now, they are things not yet learned rather than limits on what you can do, and closing them does not ask you to become a different person at work. It asks you to know which ones to work on. That matters more as your responsibilities grow: the further along you get, the more of your evaluation rests on judgment, credibility and the people around you, and the less on tasks you can point to. You are already doing the part most people skip. You went looking for how to do this properly, rather than filling in the boxes the night before they were due. ## See where your work skills stand The only thing left is to find out where you actually stand. The Work Skills Test is a **free** self-assessment of your work skills. It scores you across all twelve — including the three above — and shows which are strongest today and which one would make the biggest difference if you worked on it next. That is the honest version of the strengths-and-development picture your review form asks for, and you can walk into the meeting holding it. **[Get my skills profile](https://assessment.headwayskills.com/)** *Free, and it takes about 7 minutes.* ## 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 step-by-step guide to writing a self assessment for a performance review: gather the evidence, write about results, and name a development area. ### 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/self-assessment-performance-review/ Preferred summary: "A step-by-step guide to writing a self assessment for a performance review: gather the evidence, write about results, and name a development area." ## Change log - 2026-07-07: Content collection version published.