How to Write a Self-Review When You Can't Remember What You Did
Your self-review is due, you open the form, and your mind goes blank. That's normal. You did far more than you remember. The evidence is just scattered across the tools you already use.
This guide walks you through rebuilding your year in about 45 minutes, then turning what you find into a self-review your manager can actually use.
The 45-minute method at a glance
- 120 min
Collect the evidence
Search the tools that already recorded your year.
- 210 min
Walk the year month by month
Use memory prompts to fill the gaps the tools missed.
- 310 min
Turn fragments into accomplishments
Rewrite each note as action, result, and why it mattered.
- 45 min
Pick your top 3 to 5
Lead with the wins your manager cares about most.
Step 1: Collect the evidence your tools already kept
Open a blank note and spend about 20 minutes on these sources. Write one line per thing you find. Don't polish anything yet.
| Source | What to search | What it reveals |
|---|---|---|
| Calendar | Scroll back one month at a time. Look for recurring meetings that started or stopped, launch reviews, workshops, and offsites. | Projects you joined or finished, and when |
| Sent email | Search your sent folder for "launched", "shipped", "attached", "final", "approved", and "thank you". | Deliverables, decisions, and who you helped |
| Slack or Teams | Search your own messages plus words like "thanks", "great work", "live", and "fixed". Check channels for projects you led. | Praise, unblocking, and quick wins nobody wrote down |
| Project tool | In Jira, Asana, Trello, or Linear, filter by assignee = you, status = done, and this review period. | Completed work you can count |
| Docs and Drive | Sort files you created or edited by date. | Plans, proposals, reports, and playbooks you wrote |
| Goals and past reviews | Open the goals or OKRs you set at the start of the period, your last review, and your 1:1 notes. | What you're measured on and what you promised |
| Your role's tools | CRM, analytics dashboards, support desk, design files, or code history, whichever you use. | The numbers: revenue, conversion, tickets, users, speed |
Step 2: Walk the year with memory prompts
Tools miss the work that happened in conversations. Go month by month and ask yourself:
- What did you take over from someone else this year?
- What broke, and who did people call to fix it?
- What did you start that is now how the team works?
- Who did you train, onboard, or mentor?
- What did your manager or a customer thank you for?
- What would have gone worse without you?
- What did you stop doing, automate, or say no to that saved time?
- What were you working on during the company's biggest moment this year?
Step 3: Turn fragments into accomplishments
Rewrite each line as what you did + the measurable result + why it mattered. If you don't have an exact number, use an honest estimate and say so.
Calendar: "Vendor review" every week from March to May
Led a three-month vendor evaluation across four options and recommended the one we signed, which cut our annual tooling cost by about 20%.
Slack: "thanks for jumping on this!" from the support lead in August
Resolved a billing bug escalation in two days that was generating roughly 30 support tickets a week.
Drive: "Onboarding checklist v3" doc you created
Wrote the onboarding checklist the team now uses for every new hire; the three people who joined after it were working independently within their first month.
Step 4: Pick your top 3 to 5
You'll likely end up with 15 to 30 lines. Most review forms only have room for a few. Put these first:
- Wins tied to your team's goals or the metrics your manager reports on
- Work only you did, or that wouldn't have happened without you
- The biggest numbers: revenue, cost, time saved, customers, users
- One growth story: something that went wrong and what you changed
Need wording ideas? Browse the self-evaluation examples for your role below.
Free self-review template
# [Your Name] — Self-Review ([Review period])
## Summary
The one or two results I most want my manager to remember:
## Key accomplishments
Formula: what I did + the measurable result + why it mattered.
1.
2.
3.
## How I worked with others
- Helped, mentored, or unblocked:
## Areas for growth
- What didn't go to plan, what I learned, what I'm changing:
## Goals for next period
- Paste your notes. Get a review-ready brag sheet.
In WinStash, pick a past week, paste what you found for it, and save. Repeat for each project, then generate a brag sheet for the year, half, or quarter. After review season, a one-minute note every Friday keeps next year's review ready.
Frequently Asked Questions
How far back should a self-review go?
Cover the review period your company sets, usually the last 6 or 12 months. Check your review form or ask your manager before you start digging.
Is it okay to estimate numbers?
Yes, as long as you say so. Phrases like "about 20%" or "roughly 30 tickets a week" are fine. Never invent a number you can't stand behind if your manager asks.
What if I truly can't find the details?
Describe the scope and your role instead: what the project was, who it served, and what you owned. Then ask a teammate or your manager what they remember about the outcome.
Should I ask my manager what they remember?
Yes. A short message such as "Before I write my self-review, what work of mine stood out to you this year?" often surfaces wins you forgot and shows you what they value.
How do I avoid this next year?
Write a one-minute note every Friday about what you shipped, fixed, or helped with. By review season you have a full record instead of a blank page.