📋 Contents
- What a good self-evaluation actually does
- The sentence pattern that makes any claim specific
- How to answer the standard self-review questions
- Results and goal achievement: example phrases
- Collaboration and teamwork: example phrases
- Ownership and initiative: example phrases
- Growth and learning: example phrases
- Areas to improve: honest phrases that don’t hurt you
- How to rate yourself (and what not to say)
- Mid-year vs. annual self-reviews
- Where to find the material before you write
- A simple self-evaluation template
PART 1
What a good self-evaluation actually does
Your manager is likely writing reviews for several people at once, often from memory and a few notes. Your self-evaluation is the most complete record they will see of your year or half. At many companies it also travels further than you think: managers lift lines from it into their own write-up, and those lines get read aloud in calibration, the meeting where managers compare ratings across a team or department before anything is final.
So a good self-review does three things: it reminds your manager of work they may have missed, it connects that work to the goals or OKRs the team was measured on, and it shows that you see your own gaps clearly. Write every line as if your manager might paste it, word for word, into a document their own boss will read.
A weak self-evaluation lists activities ("attended weekly meetings, handled tickets, supported the launch"). A strong one shows outcomes and judgment ("cut the ticket backlog from about 40 to under 10 by changing how we triaged incoming requests"). The difference is not writing talent. It is having specific material and a pattern to put it in.
💡 Write for a busy reader
Assume your manager will skim. Lead each section with your strongest single sentence, then add one or two supporting details. If they read only the first line of each section, they should still get the picture.
PART 2
The sentence pattern that makes any claim specific
Almost every strong self-evaluation sentence follows the same shape: what you did + how you did it + what changed because of it. If you only have the first part, the sentence sounds like a job description. Add the second and third parts and it becomes evidence.
| Part | Question it answers | Example |
|---|---|---|
| Action | What did you do? | Rebuilt the onboarding checklist |
| Method | How, or what choice did you make? | by interviewing the last four new hires about where they got stuck |
| Result | What is different now? | New hires now ship their first change in their first week instead of their third |
Numbers in examples are illustrative. Use your own figures, or a clear before → after description when you have no figures.
When you cannot name a result yet, name the signal: "early feedback from the sales team says the new pricing page answers the questions they used to get on calls." That is honest and still specific.
PART 3
How to answer the standard self-review questions
Whether your company runs reviews in Workday, Lattice, 15Five, a similar tool or a plain shared doc, the self-review form usually asks some version of the same handful of open questions. Here is what each one is really asking and a short example answer.
| Form question | What it is really asking | Example answer (illustrative) |
|---|---|---|
| What were your key accomplishments this period? | Which results should your manager defend in calibration? | Led the billing migration to completion on the agreed date; no customer-facing incidents during cutover. |
| How did you progress on your goals? | Did you hit what you committed to, and if not, why? | Hit two of three goals. The third slipped a quarter after we reprioritized toward the security audit, agreed with my manager in March. |
| What could you have done better? | Do you see your own gaps? | I flagged schedule risk too late on the partner project. I now raise risks in my weekly update as soon as a date looks shaky. |
| How did you demonstrate our values? | Can you tie behavior to the company’s stated values? | For "customer first": rewrote the refund FAQ after reading a month of support tickets. |
| What do you want to focus on next? | Where are you trying to grow, and what do you need? | Lead a cross-team project end to end; I’d like to own planning for the Q3 launch. |
💡 Fill the boxes unevenly on purpose
Put most of your words into accomplishments and goals. Keep "what could you have done better" short and specific. Long answers in the weakness box pull the whole conversation toward it.
PART 4
Results and goal achievement: example phrases
This is usually the first section managers read. Tie each line to a goal you were given, or to a problem the team cared about.
- Delivered the Q2 reporting dashboard two weeks ahead of the agreed date, which let the finance team close the quarter without manual spreadsheets.
- Met my target for new accounts in three of four quarters; in the quarter I missed, I identified the cause (a pricing change mid-quarter) and adjusted my outreach list for the next one.
- Took over a stalled vendor migration and completed it by breaking it into weekly milestones that the vendor signed off on.
- Reduced the average response time on customer tickets in my queue from roughly two days to same-day by setting up saved replies for the ten most common questions.
- Shipped four of the five features on my roadmap; the fifth was deprioritized in agreement with my manager in favor of a security fix.
✍️ Before → after
Before: Worked hard on the website redesign and helped it launch on time.
After: Owned the content migration for the website redesign (about 300 pages), set up a review rotation with three teams, and finished one week early, which gave QA a full extra week before launch.
PART 5
Collaboration and teamwork: example phrases
Collaboration claims are easy to make and hard to believe. Name the people or teams, and describe what you did for them, not how you felt about working together.
- Set up a shared weekly handoff note with the support team, so engineering stopped hearing about urgent bugs secondhand.
- Paired with two newer teammates on their first projects; both now run their own releases without review from me.
- Resolved a recurring conflict over request priorities with the design team by agreeing on a single intake form and a weekly 15-minute triage.
- Covered a colleague’s accounts for six weeks during their leave and kept every scheduled renewal on track.
- Gave structured feedback on peers’ proposals; three of them told me it changed their final recommendation.
⚠️ Avoid the "team player" trap
Phrases like "great team player" or "always willing to help" tell your manager nothing they can repeat in a calibration meeting. Replace every adjective with one concrete thing you did.
PART 6
Ownership and initiative: example phrases
Ownership means doing things nobody assigned, finishing what you start, and raising problems early. Show the moment you stepped in.
- Noticed that our monthly invoice run depended on one person’s manual steps, documented the process, and automated two of the five steps.
- Flagged a likely delay on the partner integration three weeks before the deadline, proposed a reduced first version, and we shipped that on time.
- Volunteered to own the quarterly planning document and turned it from a slide deck into a living tracker the team now updates weekly.
- Followed up on every open item from the incident review until all six were closed, rather than leaving them in the notes.
- Took responsibility for a reporting error I made in March, corrected the figures within a day, and added a check that would have caught it.
That last example matters. Owning a mistake and showing the fix is one of the most credible things you can put in a self-evaluation, because it proves you are being honest everywhere else.
PART 7
Growth and learning: example phrases
Growth is not a list of courses. Show what you learned and where you used it.
- Learned SQL basics this year and now pull my own campaign data instead of waiting for the analytics queue.
- Asked for feedback on my presentations after each quarterly review and changed my structure to lead with the decision needed; the last two reviews ended with a decision in the meeting.
- Took on my first project as the lead, including scope, timeline and stakeholder updates, and delivered it within the original estimate.
- Shadowed the account management team for two weeks to understand renewal conversations, which changed how I write onboarding emails.
PART 8
Areas to improve: honest phrases that don’t hurt you
This is the section people dread. The goal is not to confess weaknesses; it is to show self-awareness and a plan. A useful formula is pattern you noticed + what it cost + what you are doing about it.
- I tend to say yes to too many requests at once, which delayed two of my own deliverables this year. I now block planning time on Mondays and check new requests against my current list before agreeing.
- My written updates were often too long for senior readers. I am moving to a three-line summary at the top of every update and asking my manager whether it is working.
- I avoided giving direct feedback to peers when things went wrong. In the next cycle I want to practice this in our project retrospectives.
- I relied on one data source for forecasting. I want to learn the second system so my numbers can be checked against each other.
💡 Pick one or two, not five
One or two real areas, each with a concrete next step, reads as maturity. A long list reads as a lack of confidence, and a fake weakness ("I care too much") reads as avoiding the question.
PART 9
How to rate yourself (and what not to say)
Many forms ask you to pick a rating on the same scale your manager uses, often something like "below expectations / meets expectations / exceeds expectations," sometimes with five points instead of three. This is the question people agonize over most.
- Rate where your evidence points. If you met every goal, "meets" is honest and fine. "Meets expectations" means you did the job well; it is not a polite failing grade.
- Claim "exceeds" only with proof. Exceeds usually means results beyond the goal, scope beyond your level, or impact outside your team. Point to the specific line in your self-review that supports it.
- Don’t lowball out of modesty. A self-rating below your manager’s view can anchor the discussion downward, and it rarely earns credit for humility.
- Explain any gap in a sentence. "I’ve rated myself exceeds on delivery because I absorbed the second region mid-year in addition to my original goals."
⚠️ Phrases that hurt you
Avoid "I tried my best," "I think I did okay," "I wasn’t given the chance," blaming named colleagues, and "nothing to improve." Also skip "I’m a perfectionist." Each one either undercuts your evidence or signals you are dodging the question.
PART 10
Mid-year vs. annual self-reviews
Plenty of companies run a lighter mid-year check-in and a fuller year-end review. Write them differently.
| Mid-year self-review | Annual self-review | |
|---|---|---|
| Main purpose | Course-correct while there is time | Record results that feed rating, merit increase and promotion decisions |
| Length | Short: progress per goal, risks, one ask | Full: results, beyond-goals work, growth, areas to improve |
| Tone | "Here is where I am and what I need" | "Here is what I delivered and what it changed" |
| Best move | Ask what "exceeds" would look like by year-end | Reference what you agreed at mid-year and show you followed through |
PART 11
Where to find the material before you write
Most people struggle with self-evaluations because they are trying to remember twelve months of work in one evening. Gather material first, then write.
☐ Your goals or objectives from the start of the period, and any changes agreed since.
☐ Sent emails and chat messages where you delivered something or solved a problem.
☐ Calendar: launches, presentations, workshops, customer meetings.
☐ Thank-you messages and positive feedback from colleagues or customers.
☐ Project trackers, tickets and documents you authored.
☐ Your own notes or work log, if you keep one.
If you write down one line a day about what you did and what it changed, this step takes minutes instead of hours. That habit is covered in detail in the guide to writing a brag document.
PART 12
A simple self-evaluation template
Summary (2–3 sentences)
Your biggest contribution this period and the one thing you are proudest of. Write this last.
Results against goals
One short paragraph or 3–5 bullets per goal, each using action + method + result.
Beyond the goals
Work that was not on your plan but mattered: problems you prevented, processes you improved, people you helped.
Growth
What you learned and where you applied it.
Areas to improve
One or two patterns, each with a specific next step.
Looking ahead
What you want to take on next period and what support would help.
Frequently asked questions
Q. What should I write in my self-evaluation?
Your results against each goal, important work beyond your goals, what you learned, one or two areas for improvement with a plan, and what you want to focus on next. Back each claim with a specific example.
Q. How long should a self-evaluation be?
Long enough to cover each goal with specific evidence, short enough to skim. For most roles, one to two pages, or 3–5 strong bullets per competency, is plenty. Follow any character limits your review tool sets.
Q. How should I rate myself on a performance review?
Rate yourself where your evidence points. If you met your goals, "meets expectations" is an honest, solid rating. Rating yourself low out of modesty can anchor the conversation lower than your work deserves; rating "exceeds" without evidence hurts credibility.
Q. What are good areas for improvement to put on a self-evaluation?
Real, fixable patterns: flagging risks earlier, delegating, concise writing for senior readers, saying no to low-priority requests, or a technical skill your role increasingly needs. Pair each one with a concrete next step.
Q. What if I missed a goal?
Say so directly, explain the cause briefly without blaming others, and show what you learned or changed. A missed goal handled honestly is often viewed better than a vague claim of success.
Q. Can I mention work my manager already knows about?
Yes. Managers forget details, and your self-evaluation may be read by others in calibration. Include your important work even if it seems obvious.
Q. How do I write about soft skills like communication?
Describe a situation and its outcome: "Ran the weekly client call during the migration and kept every open issue in a shared list, so the client never escalated." The skill is shown by the scene, not named.
Q. Is it okay to use the same phrases as these examples?
Use them as patterns, not copy. Replace every detail with your own project, people and outcome. Generic phrases are exactly what makes self-evaluations forgettable.
Q. When should I start writing?
Start gathering material two to four weeks before the deadline, and write the draft at least a few days early so you can reread it with fresh eyes.
This article is general guidance. Review formats, rating scales and expectations vary by company — check your own company’s guidelines alongside it.
PLAN2FOLIO
Evidence for reviews, raises and job moves — starting with one line today
Write what you did today in one line. PLAN2FOLIO sorts it into the outcomes of your role, drafts your weekly report on Fridays and gathers evidence by outcome at review time. Free to start.
Start free →