# Your Self Evaluation Performance Review: What to Write Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/self-evaluation-performance-review/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/self-evaluation-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 Facing a self evaluation performance review? Ten concrete ways to write one that is honest, specific, and actually shapes what your manager concludes. ## Key facts - Title: Your Self Evaluation Performance Review: What to Write - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Influence - Primary keyword: self evaluation performance review - Source page: https://headwayskills.com/knowledge/working-with-your-manager/self-evaluation-performance-review/ ## What this page covers - Facing a self evaluation performance review? Ten concrete ways to write one that is honest, specific, and actually shapes what your manager concludes. - Practical guidance for self evaluation performance review - How this topic connects to Working with Your Manager ## Detailed explanation A self evaluation performance review is the written self-assessment you complete before your review meeting: you summarize what you delivered over the period, say where you fell short, and propose goals for the next one. Written well, it doesn't just record the judgment your manager arrives at — it shapes it, because this is the one document in the process where you hold the pen. If the form has been open in a tab for three days, that's usually not a wording problem. It's that nine months of work has gone fuzzy, and nothing you type feels either accurate or safe to say. Both of those are fixable — and neither gets fixed by borrowing someone else's sentences. ## What your self evaluation is actually for Search this topic and the results are dominated by phrase banks: 30 examples, 70 sample answers, 200-plus phrases sorted by skill and rating. They solve the blank page and nothing beyond it, because a borrowed sentence can't point to evidence you never collected. The organizations that run the process describe it more plainly. The University of Maryland's HR guidance frames the self-assessment as the point where you seriously consider how you met expectations. Paylocity adds something more immediately useful to you: it's your chance to remind your manager of accomplishments they may have forgotten — an explicit counterweight to recency bias, the pull that makes the last quarter feel like the whole year. So the document is built to be influenced. Using it that way isn't gaming anything; it's the process doing what it was designed to do. Ten things separate a self-evaluation that lands from one that quietly disappears. ## 10 ways to write a self evaluation performance review that lands ### 1. Gather the evidence before you write a word Recency bias works on you exactly as it works on your manager: February is a blur, November is vivid, and the form asks about both. Before drafting anything, go collecting. Culture Amp and Uptick point to the same places — your [one-on-one notes](/knowledge/working-with-your-manager/one-on-one-meetings/), project retrospectives, delivery timelines, launch notes, feedback your manager gave you at the time, and any praise emails you kept. Clockify describes the ongoing version as a "me file," a running record you add to as things happen rather than reconstruct under deadline. What you deliver is only half the picture, though; the half that's hardest to reconstruct is *how* you worked — and [a read on your own working skills](https://assessment.headwayskills.com/) gives you that inventory in a form no project list will. ### 2. Pick three to five accomplishments and tell them in full The instinct under pressure is to list everything, so nothing important gets missed. It backfires. Monster and Sprad both recommend a hard ceiling of three to five accomplishments per cycle, each told through Situation, Task, Action, Result — what the circumstances were, what you were responsible for, what you actually did, and what came of it. The reasoning is about memory rather than modesty: a handful of fully told examples stay with the reader, while fifteen half-detailed bullets blur into one another. Choose the ones you'd want raised in a conversation about your work, and give them room. ### 3. Tie each achievement to something the organization cares about The most common gap between a competent self-evaluation and a strong one is the difference between *what you did* and *what it was worth*. Uptick and ThriveSparrow both stress connecting your examples to the team's goals, [company OKRs](/knowledge/influence/seeing-the-big-picture/), or whatever strategic themes your organization is actually working toward this year. A task described in isolation reads as activity. The same task set against a goal your manager is accountable for becomes legible — and it hands them the sentence they'll need when they explain your rating to someone above them. ### 4. Put numbers on what can carry them The standing advice is to include two or three accomplishments with a figure attached — volume handled, time saved, error rate reduced, a satisfaction score moved. It's worth doing where it's true. It's also worth saying that this is craft consensus rather than a measured effect: it recurs across practitioner guidance without a study behind it, so treat it as useful rather than decisive. And plenty of genuinely valuable work has no number on it — you covered for someone, you unpicked a mess nobody wanted to touch. For that work, describe what changed as a result. A specific outcome does the same job a metric does. ### 5. Name a real weakness, and what you're already doing about it This is the section most people write last and most nervously. The reframe Lattice recommends is small and does a lot of work: instead of "I struggle with time management," write that you've been working on prioritization and have started a specific course or practice. The gap paired with an action reads as self-awareness; the gap alone reads as a liability. And leaving it out entirely is the worse option — Built In and Qualtrics both report that what managers want from a self-evaluation is precisely the ability to name [your own wins and shortfalls](/knowledge/setting-goals/strengths-and-weaknesses/) and correct course, because an evaluation that admits nothing forces them to raise it themselves. ### 6. Describe setbacks without defending yourself Related, but not the same thing. Sounding defensive when discussing challenges is one of the most frequently named failure modes in the guidance, and it's easy to slip into: you explain the context, then the constraints, then who else was involved, and the paragraph turns into a case for the defense. State what happened, what you took from it, and what you do differently now. Nothing else is needed. Relitigating whose fault it was in writing, months later, costs you more than the setback did. ### 7. Write it for one specific reader Not HR, not a file. The audience is one person who is forming a view of your year and will have to justify it to someone else. That reframe answers most wording questions on its own: it tells you what to lead with, how much background to include for someone who was already there, and which achievements need explaining versus which they watched happen. It also means the document has a job beyond accuracy — Paylocity's framing again, that you're reminding a busy person of things they genuinely may not be holding in mind. ### 8. Cut it back before you submit Overexplaining is a named failure mode across Culture Amp, Rippling, and Uptick, and it usually comes from anxiety rather than thoroughness — the hedge added in case the claim sounds too strong, the extra detail added in case the point isn't clear. Length signals nothing to the reader. Go through the draft once looking specifically for sentences that serve your nerves rather than their understanding, and delete those. What's left will be sharper than what you started with. ### 9. End with goals specific enough to be checked The forward-looking section is treated as required rather than optional by Qualtrics, ThriveSparrow, and Culture Amp alike, and several note that managers read it as the signal of whether you're coachable. It's also the part most often left thin, because it comes last and the deadline is close. Write [goals that someone could actually assess](/knowledge/working-with-your-manager/performance-goals/) at the next review — a defined outcome, a rough timeframe, a link to something the organization is trying to do — rather than intentions to "improve communication" or "be more proactive." ### 10. Do the follow-through the form implies Of all the named failure modes, this is the only one that's invisible at submission. Nothing goes wrong when you name an improvement area and then do nothing about it — until the next cycle, when the same gap appears in the same words and the section stops meaning anything. Act on what you wrote. And start the next round of evidence the day after the review rather than the week before the next one — worth knowing that cadences vary, and that Paylocity notes plenty of organizations now run self-assessments quarterly or monthly rather than annually, which makes the gathering problem much smaller. ## The skills that make review season easier to handle Read back through those ten and it's noticeable how few of them are about writing. Gathering evidence, judging your own performance honestly, and framing your work for a specific reader are the same handful of capabilities showing up in different clothes — and they're the reason the review conversation goes better for some people than others, whatever the form looks like. **Working with Your Manager** treats the review as one moment in a partnership rather than a verdict you receive. The self-evaluation is where that shows most clearly: preparing properly, making your results visible, staying future-focused, and asking plainly for what you want next. It also runs upstream of the form — regular one-on-ones are where most of your evidence gets created in the first place, which is why people who hold them find review week so much less alarming. **Building Self-Awareness** is what lets you judge your own year without either inflating it or flattening it. It's the source of the honest answer to "where did I actually fall short," and it's what makes the manager's response usable rather than threatening — understanding the feedback fully before adding your own view of it. It's also worth knowing why that weakness box feels so exposed: exaggerated beliefs about achievement can turn an ordinary gap into a verdict about you, which it isn't. **Influence** is the part most people are quietly uncomfortable with, and it's less about self-promotion than preparation. It means understanding what the reader values, leading with your strongest evidence, presenting drawbacks honestly instead of airbrushing them — that's what makes the document credible — and following up on what you agreed rather than filing it and moving on. Good work rarely announces itself. The free Work Skills Test gives you a read on all three, along with the other nine it covers. If you're about to write development goals for the next period, [knowing which one to build](https://assessment.headwayskills.com/) beats picking whichever gap sounds most acceptable on a form. ## Where this leaves you Some of this may already describe how you work — the note kept after a project goes well, the instinct to hear the awkward feedback rather than dodge it. None of it is fixed, and none of it requires becoming a different person at work; these are habits, built at whatever pace the year allows. They also tend to matter more as your responsibilities grow, because the reviews get shorter and the stakes get higher, and the case for your work has to hold up in rooms you're not in. The fact that you're reading about the form rather than filling it in at eleven the night before already puts you in a different position from most people facing the same deadline. ## See where your skills stand before you write So the only thing left is to find out where you're actually strong — which is a much better starting point for a self-evaluation than a blank box and a memory search. The **free** Work Skills Test is a short self-assessment of the workplace skills this article has been circling: it shows you where you stand across all twelve, and which one or two would make the most difference to how your next review goes. **[Take the test](https://assessment.headwayskills.com/)** *It's free, takes about 7 minutes, and there's nothing to prepare.* ## 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? Facing a self evaluation performance review? Ten concrete ways to write one that is honest, specific, and actually shapes what your manager concludes. ### 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-evaluation-performance-review/ Preferred summary: "Facing a self evaluation performance review? Ten concrete ways to write one that is honest, specific, and actually shapes what your manager concludes." ## Change log - 2026-07-07: Content collection version published.