July 2026 / 13 min read
How to Write a Self-Evaluation for a Performance Review
Explain what you accomplished, what you learned, and what you want to do next. Includes a complete example and a template.
A self-evaluation gives your manager your account of the review period: what you accomplished, how you worked with others, and where you need to improve.
Include examples your manager can check, explain how they relate to your goals, and mention work your manager may not have seen. If you are still reconstructing the period from memory, start with the weekly accomplishment-tracking guide.
What a useful self-evaluation needs to answer
Your company’s form may ask about competencies, goals, strengths, challenges, or ratings. Underneath those variations, a reviewer is usually trying to answer the same questions.
What changed?
Name the customer, business, team, quality, cost, speed, or risk outcome—not only the activity.
What was your contribution?
Make your ownership visible while preserving credit for the people who worked with you.
What supports the claim?
Use a metric, milestone, artifact, before-and-after comparison, adoption signal, or specific feedback.
How did it match expectations?
Connect the work to a goal, KPI, competency, company priority, or expectation for your level.
What comes next?
Show what you learned, where you are improving, and the scope or result you intend to own next.
Give the reviewer enough detail to understand your contribution and assess it against the expectations for your role.
Start from evidence
Keep your achievements in one place.
Bring your saved achievements, supporting evidence, and review goals into one draft instead of rebuilding the period from scattered notes.
Gather the evidence before writing
Before drafting, collect your results and feedback. Then decide which examples answer each question on the form.
Read the form and rating criteria
Answer the prompts your company actually uses. Note the review period, word limits, competencies, rating definitions, and whether your manager expects bullets or narrative responses.
Collect goals and role expectations
Collect the goals, KPIs, role expectations, and project commitments you were working toward during the review period.
Build a timeline of evidence
Scan your accomplishment log, calendar, sent messages, project updates, dashboards, feedback, and finished artifacts. Capture facts before trying to write polished prose.
Group the evidence into themes
Look for three to five patterns: outcomes delivered, scope increased, customers helped, systems improved, leadership shown, or capabilities developed.
Choose a few main accomplishments and explain them well. A year-round Brag Document can hold the broader record; the self-evaluation should answer this review’s questions.
A practical self-evaluation structure
Use your employer’s required sections when they exist. If the form gives you one open text box—or you need to prepare a draft before seeing the form—this structure covers the material most reviewers need.
Summary
Use three to five sentences to state your role, the main scope you owned, two or three outcome themes, and the most important way you grew.
Key accomplishments
Choose the few examples that best represent the review period. For each one, explain the context, your contribution, the result, and the evidence.
Collaboration and leadership
Show how you improved decisions, alignment, team capability, onboarding, standards, communication, or execution beyond your individual tasks.
Goals and competencies
Connect the evidence directly to the expectations used in your review. State what you met, exceeded, changed, or did not complete—and why.
Growth and areas to improve
Name something you need to improve, how it affected the work, what you’ve changed, and how you’ll check your progress.
Next goals and support
End with the results or scope you plan to own next and the feedback, access, sponsorship, or resources that would help you deliver them.
Describe what you did and what changed
A reliable structure is: context + contribution + result + evidence. You do not need to force every example into one sentence, but the reader should be able to find all four parts.
Compare these versions:
- Vague: I demonstrated strong leadership and improved our onboarding process.
- Evidence-backed: I led the onboarding redesign across Support, Operations, and Finance, aligning the teams on one intake checklist. Median onboarding time fell from 8.4 to 5.6 business days, and incomplete submissions declined by 31%.
Use precise verbs: led, created, decided, analyzed, resolved, coordinated, or improved when those words accurately describe your role. Use partnered, contributed, or supported when the result was shared. Strong writing clarifies ownership; it does not claim the team’s entire outcome.
For more models, use the 50 work accomplishment examples. If your role has no revenue target, the guide to quantifying work achievements shows how to use time, reach, quality, adoption, cost, risk, and team outcomes.
How to write about weaknesses and growth areas
Choose an area you need to improve that matters to your role. Explain how it affected your work and what you’re doing about it.
Area
Name the skill, behavior, decision, or result that needs to improve.
Impact
Explain where the gap affected the work without exaggerating the damage.
Action
Describe what you have already changed, practiced, requested, or put in place.
Measure
State the signal that will show the improvement is working next period.
Avoid disguised strengths such as “I care too much” and broad statements such as “I need to communicate better.” A stronger answer names the moment the gap appeared, the adjustment you made, and the next signal you will watch.
If a goal was missed, state that clearly. Separate the factors you controlled from those you did not, explain the consequence, and show the decision or change that follows. Accountability is more useful than defensive detail.
Complete self-evaluation example
This fictional example is for an operations professional, but the structure works across roles. Notice how each section stays selective, credits collaborators, and connects claims to observable evidence.
Performance review / Senior Operations Analyst
Self-Evaluation: January–June 2026
Summary
Summarize the main results and what you learned.
This period, I led changes to customer onboarding and reporting that shortened setup time, reduced incomplete submissions, and saved the team time each week. I also helped onboard two analysts. I need to flag delays earlier: after the reporting migration slipped, I started a weekly review of dependencies so we could address problems sooner.
Key accomplishments
Choose a few examples with results you can check.
Standardized the customer-intake process across Support, Operations, and Finance. I mapped the existing handoffs, aligned the teams on one required-data checklist, and built the rollout plan. Median intake time fell from 8.4 to 5.6 business days over the following quarter, and incomplete submissions declined by 31%. This work supported our goal to improve onboarding speed without adding headcount.
Rebuilt the weekly KPI reporting workflow used in four leadership meetings. I consolidated six source files, documented metric ownership, and partnered with Data to automate the recurring refresh. The change removed approximately six hours of manual preparation each week and gave leaders one consistent definition for activation and retention reporting.
Collaboration and leadership
Make team impact and influence visible.
I onboarded two new analysts by creating a 30-day learning plan, pairing with them on their first reporting cycles, and documenting the five recurring judgment calls that were missing from the runbook. Both analysts completed the next monthly cycle independently, and the decision guide is now used by the wider operations team. I also facilitated the cross-functional intake review, making sure the final process reflected constraints from all three teams rather than optimizing only for Operations.
Growth and area to improve
Acknowledge the gap and show changed behavior.
I need to escalate cross-team delivery risk earlier. During the reporting migration, I waited too long to raise an unresolved data dependency because I expected the team to close it within the existing schedule. That contributed to a one-week delay. I now keep a visible dependency log, review it weekly with owners, and escalate any item that remains unresolved for two review cycles. No later milestone missed its date because of an unowned dependency. Next period, I will track the age of open dependencies and ask my manager for feedback on whether my escalation timing is appropriate.
Next goals and support
Connect future work to clear outcomes.
Next period, I plan to reduce onboarding rework by another 15%, move the remaining manual reporting checks into documented automated tests, and lead quarterly planning for the Operations workstream. I would value early feedback on the planning proposal and the opportunity to observe one executive planning cycle before I facilitate the next review.
Keep the supporting documents and dashboards available so your manager can check the details without including all of them in the review.
Self-evaluation checklist before you submit
Take one editing pass for evidence and one for clarity. Stop when the review answers the prompts and your strongest work is easy to understand; additional length does not make it more credible.
- Answer every required prompt and respect the requested format or word limit.
- Make the strongest three to five accomplishments easy to find.
- Support major claims with a metric, artifact, milestone, adoption signal, or specific feedback.
- Use “I” for your contribution and “we” where the team genuinely owned the result together.
- Connect examples to goals, competencies, or expectations for your role.
- Include a real growth area with action already underway and a measure for progress.
- Choose next goals that describe results or scope—not vague intentions to improve.
- Remove inflated adjectives, confidential details, unsupported numbers, and repeated points.
Free self-evaluation template
The Markdown template includes the complete structure, prompts for three evidence-backed accomplishments, a growth framework, next goals, requested support, and the final checklist. Copy it into your notes app or adapt its headings to your company’s form.
Markdown template
Performance Review Self-Evaluation
# Performance Review Self-Evaluation
## Review period and role
- Review period:
- Role:
- Goals, KPIs, or competencies:
## Summary
## Key accomplishments
- Context:
- My contribution:
- Result:
- Evidence:
## Collaboration and leadership
## Growth and areas to improve
## Next goals and supportKeep the final review concise, but keep the underlying evidence. That record becomes useful again when you prepare a manager update, compensation conversation, or promotion case.
Turn the record into a review
Draft your review from the work you’ve saved.
Select the achievements that match your review period and goals, keep the supporting proof, and generate a structured Brag Document you can refine into your final self-evaluation.