Self-Evaluation Examples: Write a Review You Can Back Up
Write a performance self-evaluation with six original examples, an evidence table, and a way to explain missed goals without inflated claims or empty phrases.
A useful self-evaluation explains what you did, why it mattered, what evidence supports the claim, and what you need to improve. Start with your actual work, then use examples to shape the wording. Copying a polished sentence about results you cannot demonstrate makes the review less credible, not more professional.
You are helping your manager see the year clearly. You do not need to sound like the employee of the century.
Table of contents
- What evidence should you gather first?
- What do useful self-evaluation examples look like?
- How should you describe missed goals?
- How do you fit the review form?
- What should you bring to the conversation?
- Frequently asked questions
What evidence should you gather first?
Review the expectations for your role and collect examples across the entire review period. Use completed work, feedback, agreed goals, and records of changes rather than relying only on what happened last week.
MIT's performance review guidance includes reviewing the job description, earlier reviews, check-ins, and notes accumulated during the year. Those records help separate a contribution from a vague impression.
Build this short evidence table before drafting:
| Claim you might make | Evidence to check | Boundary to preserve |
|---|---|---|
| Improved a process | Earlier and revised workflow, observed effect | Do not invent time saved |
| Delivered an important task | Agreed scope, completed artifact, acceptance | Credit collaborators |
| Helped colleagues | Specific assistance and feedback | Avoid naming private issues |
| Learned a new skill | A task completed using that skill | Attendance is not mastery |
| Improved reliability | Delivery records over a defined period | Include relevant exceptions |
Select the strongest evidence rather than the longest list. If a team delivered a project, distinguish your contribution from the team's outcome. “I prepared the validation checklist” is more credible than claiming sole ownership of everything the project achieved.
What do useful self-evaluation examples look like?
Use a concrete action, its effect, and a way to verify it. The six examples below are original fictional illustrations; their events and numbers are not results you should claim as your own.
Stanford's self-assessment guidance recommends specific examples, supporting data, and alignment with team goals. The point is to make a contribution understandable, not to put a percentage into every paragraph.
1. Delivering a project
I coordinated the help-center revision from the approved outline through publication. I owned the article inventory and review schedule, while the support team checked technical accuracy. We published the agreed set of articles before the product release. The final inventory and approval record show which sections I completed and which contributions came from colleagues.
2. Improving a recurring process
I replaced the separate weekly intake lists with one shared queue and documented how requests enter it. During the next four weekly checks, each new request had an assigned owner. I have not measured a reduction in processing time, but the queue history shows that ownership became visible in one place.
3. Collaborating across teams
I helped support and operations agree on the information required for escalations. I collected examples of incomplete requests, drafted a short intake guide, and revised it with both teams. The guide is now used in the shared channel. My main contribution was making the handoff requirements explicit; the teams jointly agreed on the process.
4. Communicating a difficult tradeoff
When the reporting scope expanded, I outlined which deliverables could still meet the original date and which required more time. I brought two options to the project lead and documented the decision. This allowed the team to make an explicit scope choice instead of discovering an unfinished section at the deadline.
5. Applying a newly learned skill
After learning the report validation process, I completed two routine checks with a colleague reviewing my work. I can now resolve the common category mismatch independently. Missing-source exceptions still require assistance. My next development step is to practice those exceptions on a supervised cycle and update the troubleshooting notes.
6. Contributing without a numerical outcome
I wrote the first walkthrough for the archive retrieval process and tested it with a colleague who had not used the system. Their questions revealed an unclear permission step, which I revised. The walkthrough and review comments demonstrate the contribution. I do not yet have enough usage evidence to claim that retrieval is faster.
Notice what these examples leave out: “always,” “excellent at everything,” and unsupported savings. They name work another person can inspect. MIT describes performance review as an ongoing dialogue; a useful paragraph should give that dialogue something concrete to discuss.
How should you describe missed goals?
State the gap directly, explain relevant context, and identify what you changed or will test. Avoid both hiding the miss and turning one outcome into a sweeping judgment about your ability.
Use four sentences as a drafting exercise:
- What was agreed?
- What actually happened?
- What part was yours to address?
- What will change, and how will you check it?
For example:
I planned to finish the draft guide before the quarterly review, but delivered it three working days later. I underestimated the time needed for a second reviewer and did not flag the risk early enough. I have added an explicit review checkpoint to the next schedule. I will check the draft's readiness with the reviewer before confirming the final delivery date.
This fictional example gives context without transferring all responsibility to someone else. If a priority change made a goal obsolete, document that change instead of presenting an agreed cancellation as failure.
Stanford recommends being specific about development areas and proposed steps. “Improve communication” is hard to assess. “Flag a dependency as soon as it threatens the agreed date” describes a behavior people can observe.
For a difficult discussion, the feedback question guide can help you ask what needs to change without fishing for reassurance.
How do you fit the review form?
Answer the actual criteria and word limits in your employer's form. A strong paragraph in the wrong section still makes the manager do unnecessary interpretation.
If the form asks about teamwork, select a teamwork example. If it asks for progress against a goal, show the original goal, current result, and any agreed revision. Do not reuse the same achievement under every competency unless a different aspect is genuinely relevant.
Stanford also advises keeping the assessment concise. A practical editing pass is to remove an adjective whenever a concrete detail can do its job.
| Vague wording | More useful direction |
|---|---|
| I am a great communicator | Name the audience, message, and decision clarified |
| I consistently exceed expectations | Identify the expectation and documented difference |
| I am a team player | Describe help that made someone else's work possible |
| I need to be more confident | Identify the behavior you want to practice |
Use the organization's rating definitions if a score is required. Do not assume that a familiar label means the same thing at every employer. Ask for clarification when the criteria are unclear.
What should you bring to the conversation?
Bring the submitted assessment, a few supporting artifacts, and questions about future expectations. The document starts the discussion; it does not settle every difference in perspective.
MIT's review process includes aligning expectations and discussing development. If your manager sees an outcome differently, ask which evidence or expectation explains the difference. Record any agreed next step and the resources needed to carry it out.
A performance review is separate from asking for a promotion, although the evidence may support both conversations. Keep appropriate, nonconfidential summaries for your career portfolio. Land the Offer with AI helps you use real accomplishments to explain your fit when another opportunity appears.
Frequently asked questions
What if I have no numerical results?
Use completed artifacts, decisions, quality checks, feedback, and documented responsibilities. Numbers are helpful when accurate; invented precision is worse than a clear qualitative account.
How many accomplishments should I include?
Follow the form and choose enough examples to cover the important expectations. A few well-supported contributions are more useful than a long diary of routine activity.
Should I mention mistakes?
Include relevant missed expectations and what you learned or changed. Keep the description factual and proportionate. Do not turn the assessment into either a confession list or a sales pitch.
Can AI help write my self-evaluation?
It can help organize or clarify text, but you must verify every claim. Follow your employer's rules and avoid entering confidential information into an unapproved tool. Keep your own evidence and voice.