Back to blog
8 min readKoru Team

Self-Evaluation Examples That Use Evidence

Self-evaluation examples for performance reviews, with a practical formula, before-and-after rewrites, and a worksheet for turning real work into specific review language.

performance-reviewachievement-trackingprofessional-development

The best self-evaluation examples do not sound polished first. They sound specific first.

Use this structure

Formula

Work + context + owned action + evidence + next step

Sentence

I worked on [specific work], under [constraint or context], by doing [action I owned]. The result was [evidence]. Next, I want to [growth step].

Example

"This cycle I improved the customer onboarding handoff. The main problem was that Sales, Support, and Implementation were using different setup notes. I consolidated the intake checklist, clarified ownership with each team, and reduced repeated setup questions in the launch channel. Next cycle I want to make this proactive by reviewing the first 30 days of every new account."

That is stronger than "I improved collaboration" because it gives your manager something to evaluate: the work, the context, your role, the result, and the next step. The U.S. Office of Personnel Management describes strong accomplishment records in a similar way: what was accomplished, the situation, the specific actions, and the results or outcomes (OPM).

Start with evidence, then write the sentence

Most weak self-evaluations start with a trait:

Trait first

"I am a strong communicator and a reliable team player."

Evidence first

"I wrote the weekly launch update during the beta rollout, which gave Product, Support, and Sales one shared source of truth and reduced repeated status questions in the project channel."

The second version is not more boastful. It is easier to check.

Performance reviews are supposed to summarize contributions across the review period, not just the last few weeks (UC Berkeley People & Culture). That is why the evidence matters. Memory will give you whatever happened recently. Your calendar, project notes, customer messages, docs, and feedback will give you the year.
If you have not tracked anything, use the 2-hour reconstruction process first. If you have notes already, pull from your weekly career journal template.

Self-evaluation examples you can adapt

Use these as shapes, not scripts. Replace the bracketed parts with the facts from your work.

Review areaWeak versionEvidence-based version
Delivery"I completed my projects on time.""I delivered [project] by [date] while coordinating [stakeholders]. The work mattered because [business/customer/team outcome]."
Collaboration"I worked well with other teams.""I partnered with [team] on [problem], owned [specific part], and helped the group reach [decision/result]."
Problem-solving"I solved several issues this year.""When [problem] blocked [goal], I [action], checked it with [evidence], and prevented [risk or repeated issue]."
Leadership"I showed leadership.""I took ownership of [unclear area], created [artifact/process], and helped [people/team] make progress without waiting for escalation."
Growth"I learned a lot this year.""I built skill in [area] by [practice/project]. The clearest sign of progress was [example], and next I want to [specific next step]."
Missed goal"Some goals were delayed.""[Goal] slipped by [amount/reason]. My part was [honest ownership]. I changed [process/behavior] so the next version has [specific safeguard]."

A one-page self-evaluation worksheet

Before you write the final paragraph, fill this out for each strong example.

Evidence worksheet
PromptYour notes
What happened?Project, customer issue, launch, process change, feedback, goal, incident
What was hard?Deadline, ambiguity, dependency, resource gap, conflict, unfamiliar domain
What did you personally do?Decision, analysis, writing, facilitation, build work, coordination, escalation
What evidence do you have?Number, date, stakeholder, artifact, customer note, manager feedback, before/after
Why did it matter?Time saved, risk reduced, quality improved, team unblocked, customer outcome
What comes next?Skill to build, process to repeat, scope to test, support needed

The finished sentence should not include every field. The worksheet gives you options. Pick the details that make the example credible.

Examples for common self-evaluation sections

Accomplishments

Weak

"I contributed to several important initiatives."

Stronger

"I owned the reporting cleanup for the Q2 planning cycle. The old process required three manual spreadsheet updates before every leadership review. I mapped the handoff, removed duplicate fields, and created one source file for Finance and Operations. The review deck now uses the same numbers both teams sign off on."

Collaboration

Weak

"I am good at collaborating cross-functionally."

Stronger

"I worked with Product and Customer Success to resolve the beta feedback backlog. My role was to group the open comments by customer impact, turn the top issues into tickets, and run the weekly triage until the launch decision was clear."

Ownership

Weak

"I took more ownership this year."

Stronger

"I became the main owner for the partner onboarding checklist after two launches exposed the same missing steps. I rebuilt the checklist, got sign-off from Legal and Support, and used it for the next launch without the same escalation."

Growth area

Weak

"I need to improve my communication."

Stronger

"I need to make risks visible earlier. In the Q3 migration, I waited too long to explain the dependency on the data cleanup work. For the next project, I want to send a written risk note in week one and review it in the project sync."

Missed goal

Weak

"The timeline slipped because other teams were slow."

Stronger

"The timeline slipped by two weeks. A dependency was late, but I also should have escalated the risk earlier. I have already changed the planning template so dependencies are named with an owner and check-in date at kickoff."

The goal is not to make every example sound heroic. A good self-evaluation can include missed goals if you explain what changed afterward.

If you do not have numbers

Numbers help, but they are not the only kind of evidence. Use scope when metrics are missing.

If you lack a metricUse this instead
No revenue numberCustomer size, account type, renewal stage, stakeholder level
No time-saved numberBefore/after workflow, number of manual steps removed, team affected
No quality metricBug category reduced, review comments changed, rework avoided
No people metricTeams involved, new hires supported, stakeholder group, recurring meeting
No official feedback scoreSpecific quote, decision made because of your work, artifact reused
We wrote a fuller guide on how to quantify achievements when your job is not about numbers. The short version: use honest evidence, not inflated precision.

What not to write

Some phrases make a self-evaluation weaker because they ask the reader to do the work.

Replace vague phrases
AvoidUse instead
"I helped with many projects.""The most useful project I supported was..."
"I showed leadership.""I took ownership of..."
"I improved communication.""I created/changed the communication rhythm by..."
"I handled ambiguity.""The unclear part was..., so I..."
"I want to keep growing.""The skill I want to build next is..., because..."
Also avoid claims you cannot support. OPM's performance management roadmap tells reviewers to focus on both results and behaviors and to base evaluation on evidence, not impressions (OPM). Write in a way that makes that possible.

How to use Koru's angle: preserve the raw material

Self-evaluation examples are useful in the moment, but they are much better when they come from notes you captured before the review was urgent.

A raw Koru-style entry might be:

Beta feedback got messy this week. Product wanted every request in the roadmap doc, Support wanted a customer-facing answer first, and Sales needed the launch date protected. I grouped the feedback into three buckets, wrote the decision note, and got everyone aligned on the five must-fix items. Priya said the summary made the launch call much easier.

Later, that becomes:

Review-ready sentence

"During the beta launch, I turned conflicting customer feedback into a clear triage process. I grouped requests by customer impact, wrote the decision note, and aligned Product, Support, and Sales on five must-fix items before launch."

That is the reason to keep a career journal. Not because reflection is nice, but because review language is only as good as the evidence underneath it.

If your review is soon, read what to say in a performance review. If you are building next cycle's evidence now, start with performance review prep.