On this page
Start with the review period and the criteria
Before you search your memory, check what the self-evaluation is asking for. Confirm the dates it covers, the questions you need to answer, and the criteria your employer uses. Look for goals you agreed to earlier in the period, too.
A form asking about collaboration needs different examples than one focused on delivery or role expectations. The criteria are a guide for choosing evidence, not a reason to squeeze every piece of work into a grand achievement.
Recover the work before you try to write it
Memory is a poor filing system, especially for work that happened months ago. Search a few sources before deciding you have nothing to say. Use only records you are permitted to access and keep.
- Your calendar, including recurring meetings, launches, planning sessions, and handoffs.
- Sent messages or email that show decisions, coordination, explanations, and follow-through.
- Project records you are allowed to review, such as plans, status notes, tickets, or release summaries.
- Previous goals, check-ins, and feedback you are allowed to use.
- Your own notes, saved work samples, and public portfolio material.
If you no longer have access to company systems, you can still begin with what you remember. Think through the review period by project, season, team, or major change. Use a personal calendar, an old resume draft, notes you already own, or public work samples as prompts. You do not need an internal document to describe your own contribution in your own words.
Protect confidential information
Do not copy sensitive company material, customer details, private messages, or restricted project records into personal tools. Follow your employer’s rules. When access or permission is unclear, leave the source material where it belongs and write a high-level description from memory instead.
Make a rough inventory, not a highlight reel
Set a short timer and list the work that comes to mind. Keep the wording plain. At this stage, “untangled a confusing handoff” is more useful than trying to make every line sound impressive.
Use prompts like these to bring different kinds of work back to mind:
- What did you deliver, maintain, improve, or make easier to use?
- Where did you resolve confusion, unblock a project, or help people make a decision?
- Did you mentor someone, share context, or help a teammate get unstuck?
- Did you reduce a risk, catch a problem early, or make a process more dependable?
- Where did you coordinate stakeholders, clarify ownership, or keep a handoff moving?
- What work had to happen repeatedly for the team or service to keep running?
Ordinary work counts when it mattered. A careful handoff, a stable service, or a clear explanation can make a real difference even if it never became a launch announcement. That does not mean every task needs to become an achievement. Keep routine responsibilities in the inventory, then select the ones that best show how you met the role’s expectations or helped something move forward.
Still unsure what belongs? See what counts as an accomplishment at work, including everyday contributions and borderline cases.
Separate what you did from what the team achieved
Team results are real, but your self-evaluation should make your own part clear. Name the shared goal, then say what you contributed without claiming the entire result.
Illustrative example
Team outcome
“The team launched the new onboarding flow.”
Your contribution
“I clarified the next-step copy and coordinated the review with Support and Engineering.”
Use “I” for your actions and “we” for work that was shared. If you led a decision, say so. If you supported it, explain how. Being precise makes your contribution easier to trust.
Identify what changed and what you can support
For each useful item, ask: What was happening before? What did I do? What was different afterward? What can I point to that supports the answer?
Evidence can be a delivered change, a documented decision, feedback from a teammate, a smoother handoff, or a problem that was resolved. Results do not have to be numerical. If an outcome is qualitative, describe what you observed and where that observation came from. If the result is still unfolding or you cannot yet tell, say that plainly.
Do not estimate a number because a sentence seems stronger with one. “The new checklist made ownership easier to see” is more credible than an unsupported claim about time saved.
If you need help turning that evidence into a statement, see how to show impact without numbers or metrics, with examples that keep the limits clear.
Choose a few contributions that fit the criteria
Look over the inventory and keep the examples that best answer the employer’s questions. A useful set often shows more than one kind of contribution: delivery, collaboration, care for quality, or improvement to how the work gets done. Relevance matters more than having a long list.
Combine related small tasks when they tell one clear story. Leave out details that do not help explain your contribution. You are not required to turn a normal week into a heroic tale.
For each contribution, write one compact note with the context, your action, the observed result, and any feedback or evidence. The worksheet below gives you a place to start.
Turn the notes into a concise self-evaluation
Open with a sentence about the work you focused on during the period. Then give each selected contribution a short paragraph. Use the employer’s questions and word limit to decide how much detail belongs in the final version.
A useful sentence pattern
“To address [problem or context], I [personal contribution]. [Observed result and evidence]. [What remains unknown or what I will do next, if relevant].”
You do not need to repeat every field mechanically. Keep enough context to make your contribution understandable, then stop. Finish with a genuine growth area and a next-period goal if the form asks for them.
Read the draft aloud. Remove inflated adjectives, vague claims, and anything you cannot explain if your manager asks about it. Clear and specific is enough.
Before and after: make the contribution visible
These illustrative, fictional examples show how a general statement can become more specific without pretending to know more than the evidence supports.
Product
Before
I worked on the onboarding refresh.
After
I reviewed onboarding questions with Support, clarified the next steps on the screens people found confusing, and coordinated the copy changes with Design and Engineering. In a later team check-in, Support said those questions were easier to answer. I do not have a reliable count, so I am treating that as a useful signal, not a measured reduction.
Design
Before
I improved the design system.
After
I made a reusable empty-state pattern and documented when to use it, then paired with Engineering on the first implementation. Later project screens used the same guidance. That made the experience more consistent and gave the team a clearer starting point for new screens.
Operations
Before
I handled vendor issues.
After
I helped resolve recurring shipment mismatches by documenting the handoff, clarifying who confirmed corrections, and keeping the vendor and internal team aligned. The next issues were easier to trace because ownership and status were visible. I cannot quantify the time saved, so I am describing the change I observed rather than estimating a number.
A complete, realistic sample self-evaluation
This fictional sample uses specific actions, a qualitative signal, and an honest limit. It is an example of structure, not a claim about a real person or team.
Illustrative example
This period, I focused on helping the team move product work forward with clearer handoffs and fewer unanswered questions. I reviewed recurring onboarding questions with Support, helped clarify the next steps in the flow, and coordinated the changes with Design and Engineering. In a later team check-in, Support said the questions were easier to answer. I do not have a reliable count, so I consider that a useful qualitative signal rather than a measured reduction.
I also documented ownership for recurring vendor issues and kept the internal team and vendor aligned while corrections were being confirmed. That made the status easier to follow when a mismatch came up. I cannot say how much time it saved, but the handoff became clearer.
One area I want to improve is how I check whether process changes continue to help after the initial rollout. In the next period, I plan to agree with my manager on a simple baseline and a check-in point before making the next workflow change.
Your version can be shorter. Keep the examples that answer the review questions, and remove anything that does not sound like your own work.
Write about growth areas without erasing your progress
A growth area is most useful when it names a real skill or habit, explains where it showed up, and describes what you are doing next. It does not need to cancel out your contributions or turn into a list of apologies.
For next-period goals, connect the work to an outcome you and your manager can check together. Clarify what success would look like, what support or decisions you need, and when you will revisit it. If the result depends on other teams or is not fully in your control, say that too.
A small worksheet to get the first draft moving
Keep one line per contribution. Fragments are fine. You can decide what belongs in the final self-evaluation after the details are back in view.
Copyable contribution worksheet
Copy this into a note, then add one line for each piece of work worth considering.
You can also select the text above and copy it with your keyboard.
Make next year easier with a small recurring habit
After a meaningful piece of work, save a brief note with the date, what you did, what changed, and any feedback you are allowed to keep. A few minutes every week or at the end of a project can make the next review less dependent on memory. Keep personal notes within your employer’s confidentiality and record-retention rules.
For a copyable structure you can keep using, see the work accomplishments tracker template.
Keep the useful details together
If you want a place to maintain that record over time, Ownwrk has separate Impact entries for your work and Recognition entries for feedback from others. You can organize and find them later. Entries are private by default, and you decide what to share. Ownwrk can support your preparation, but it does not replace your employer’s review form or process.
Questions about writing a self-evaluation
What if I cannot remember anything I accomplished?
Start with the review dates, then look through permitted sources such as your calendar, personal notes, previous goals, and feedback you are allowed to access. Use projects and recurring responsibilities as memory prompts. You can begin with fragments and sort them later.
Do I need numbers in a self-evaluation?
No. Use a number only when you have reliable evidence for it. A concrete change, a documented decision, or specific feedback can describe a result. If the outcome is not known yet, say so rather than estimating.
What if I no longer have access to my old work systems?
You can write from memory and use records you own or are permitted to keep, such as personal notes, an old resume draft, or public work samples. Do not try to retrieve or copy restricted company material.
Should I list every task I completed?
No. Keep a broad inventory first, then choose the contributions that best answer the review criteria. Combine related routine work when it tells one clear story, and leave out details that do not help explain your contribution.
How should I write about a growth area?
Name a specific area, explain where it affected your work, and describe a practical next step. Be candid without dismissing the progress you made or promising an outcome you cannot control.