A useful performance review self-evaluation connects your work to results, acknowledges limits, and names a realistic next step. It does not need a long list of adjectives or a claim that every project was a success. The examples below are templates for structure; replace every detail with work you actually did.
Start with the form and criteria your employer uses. Some reviews ask for goals, competencies, or ratings; others ask for a narrative. UC Berkeley's performance-review guidance suggests that employees address accomplishments and what could have gone better. University of Washington HR similarly describes employee input on achievements, obstacles, and future goals. Your company's process may differ.
Build an evidence inventory before writing
For each major responsibility, record the goal, your actions, a result, and what you learned. Look at project notes, delivered work, feedback you are allowed to use, and prior goals. Distinguish work you led from work the team achieved together. If a result cannot be measured reliably, describe the observable change: a handoff became clearer, a process took fewer steps, or a stakeholder gained a consistent update.
A compact structure is: task or goal → action you took → evidence of impact → next step. This is more credible than “I am a strong communicator.” Use the same evidence discipline you would use for a career development plan.
Example: a completed project
“I coordinated the intake process for the spring launch. I introduced a shared issue log, assigned owners in weekly meetings, and checked unresolved items before each release. The team had a clearer record of decisions and fewer last-minute handoffs. Next cycle I want to document the escalation rule earlier so new contributors can use the process without my help.”
This works because it names the employee's part and a visible result. If you have verified numbers, add them with scope and dates. Do not manufacture a percentage from a vague impression. If the work was shared, say “I coordinated” or “our team delivered” rather than claiming sole ownership.
Example: collaboration without exaggeration
“I worked with the support and product teams to make customer themes easier to review. I summarized recurring questions, asked both teams to correct my interpretation, and added the agreed themes to the monthly planning note. I would like to improve how I flag uncertain data before it reaches the planning meeting.”
Collaboration can be specific even when you were not the project lead. Name the people or functions involved only when appropriate for the review. Avoid disclosing customer details or confidential metrics in a form that is more widely circulated than the original work.
Example: a missed goal or difficult period
“I did not complete the documentation refresh by the original deadline. I underestimated the time needed to review examples with two teams and raised the risk too late. I delivered the highest-use sections first, agreed on a revised schedule, and now plan review checkpoints before a deadline is committed.”
A balanced account takes responsibility for your part without accepting blame for factors you could not control. If a priority changed or resources were removed, state that fact neutrally and explain how you adapted. Do not use the review to attack colleagues or hide a recurring problem that your manager needs to address.
Example: a development goal
“Over the next quarter, I want to lead one small cross-team improvement from discovery through handoff. I will agree on the scope with my manager, identify a baseline measure, ask for feedback after the first milestone, and summarize what changed.”
A good goal has a task, timeframe, evidence, and support needed. “Become a better leader” is too vague to guide either person. If a promotion or raise is your goal, use this self-evaluation to make your evidence visible, then have a separate conversation about criteria and compensation. See our promotion guide and raise guide for those distinct decisions.
Before submitting, run a fairness check
- Can another person understand what you personally did?
- Does each claimed result have evidence or a clear limit?
- Have you included meaningful work that is easy to overlook, such as maintenance or support?
- Are obstacles described accurately without turning the document into a defense brief?
- Is the next goal realistic under the time and resources available?
Bring two or three points you want to discuss live, especially where your view and your manager's may differ. Ask what evidence would demonstrate stronger performance next cycle. A self-evaluation is a starting point for a more accurate conversation, not a guarantee of a rating, raise, or promotion.