--- title: Preparing a Year-End Self-Assessment for Performance Reviews description: Gather your evidence and shape it honestly in time for your performance review deadline. category: life tags: [performance-review, career, self-assessment] version: "1.0" updated: 2026-10-17 sources: - name: Culture Amp, Self-performance review examples: What to write url: https://www.cultureamp.com/blog/self-performance-review-examples - name: PeopleGoal, 10 Best Self Evaluation Examples for Performance Reviews url: https://www.peoplegoal.com/blog/10-annual-performance-review-employee-self-evaluation-examples/ - name: Indeed, Self-Performance Review (With Template and Examples) url: https://www.indeed.com/career-advice/career-development/self-performance-review - name: U.S. Office of Personnel Management, An Employee's Quick Guide to Writing a Strong Self-Assessment url: https://content.govdelivery.com/attachments/USOPM/2026/07/24/file_attachments/3725006/Quick%20Guide%20Employee%20Self%20Assessment%207-24-2026.pdf - name: Lattice, How to Write a Performance Review Self-Assessment url: https://lattice.com/articles/how-to-write-a-performance-review-self-assessment --- Writing your own performance review can feel awkward — too modest and you undersell yourself, too bold and you come off tone-deaf. This walks you through gathering the evidence, shaping it honestly, and getting it in with enough lead time to actually matter. ## Gather your evidence (2–3 weeks before it's due) - [ ] Pull up the goals or targets you set at the start of the period `{essential}` These are your anchors — they tell you what success is supposed to look like and give your reflection a clear structure to follow. - [ ] Collect your project records and milestones Delivery timelines, launch notes, and project retrospectives are all useful sources. - [ ] Reread your manager's feedback and 1:1 notes from across the whole year, not just the last month - [ ] Reread peer feedback or shout-outs, noting specific instances where colleagues praised your work - [ ] Pull the metrics tied to your role — KPIs, revenue, tickets closed, uptime, whatever your job actually measures - [ ] Note any formal recognition — awards, spot bonuses, positive client emails — and save the originals - [ ] List the mistakes or missed goals too, along with what you changed afterward You'll need these later. - [ ] Open your running "brag document" of wins now `{when: if-you-keep-a-brag-document}` Reconstructing twelve months from memory is harder than reviewing notes kept through the year. ## Decide what story you're telling - [ ] Group your accomplishments into a handful of themes rather than a flat chronological list - [ ] For each major accomplishment, write it as situation, task, action, result (STAR) `{essential}` Quality matters more than length — one strong STAR example beats three weaker ones. - [ ] Lead with outcomes and impact, not a list of tasks Go beyond listing what you worked on — emphasize results, impact, and progress, and ask what changed because of your work. - [ ] Credit collaborators by name where it's genuinely due Explain how you came to achieve success, including who else contributed and how responsibilities were divided. - [ ] Connect your individual wins to team or company goals, not just your own task list - [ ] Pick one or two real growth areas and pair each with a concrete step you're already taking Not just an acknowledgment that it's a weakness. - [ ] Check the actual review form or rubric before you write `{essential}` Matching the categories your manager scores against makes your evidence easier to credit, and skipping a required section can cost you a rating level. - [ ] Map your examples to your company's defined competencies or levels `{when: if-company-rates-against-defined-competencies}` ## Write and tighten the draft - [ ] Write the first draft without worrying about length or polish Get the evidence down first. - [ ] Cut anything that's just a task description with no outcome attached - [ ] Keep each section long enough to carry one solid example Don't pad it out for the sake of length. - [ ] Remove hedging language ("I think," "sort of") from claims you can actually back with data - [ ] Stay honest about shortfalls instead of spinning them `{essential}` Self-assessments get read alongside everyone else's during calibration, and inflated claims stand out immediately to a manager who knows the real story. - [ ] Avoid comparing yourself to specific coworkers or criticizing teammates by name - [ ] Read it once as if you were your manager Does the evidence actually support the rating you're hoping for? ## Before you submit - [ ] Check the submission deadline and format `{essential}` Missed self-assessment windows often mean your input gets left out of the rating entirely, with no way to add it after the fact. - [ ] Save a dated copy for yourself outside the company system `{essential}` You'll want your own record if there's ever a dispute later about what you submitted or when. - [ ] Spell-check and read it aloud once Typos undercut an otherwise strong case. - [ ] Ask your manager what extra context would help them advocate for you `{when: if-process-includes-calibration-or-committee-step}` - [ ] Send it to your manager a few days before the actual review conversation Not the night before, so they have time to read it properly. - [ ] Bring a short mental list of your top two or three points into the review meeting In case the written version gets skimmed.