How to write a self assessment

A self evaluation isn't bragging and it isn't a confession. It's a clear, evidence-backed account of what you did and what you learned — here's how to write one that earns trust.

Most self assessments fail in one of two directions. Some read like a highlight reel with no substance: "I consistently delivered exceptional results." Others are so modest they disappear: "I did my job and tried my best." Neither helps your manager, and neither helps you. A good self evaluation does something specific — it gives your manager the evidence and framing they need to advocate for you, in your own words.

Treat it as a memory aid for a busy person. Your manager juggles a whole team and won't remember the quiet save you made in March. Your job is to remind them, accurately, and to show you understand your own growth. Here's how to do that without inflating or shrinking the truth.

Structure it so it's easy to read

You don't need anything elaborate. A reliable shape:

1. Summary — two or three sentences: your main areas of responsibility and the headline of the period.
2. Key accomplishments — three to five, each tied to a goal or business outcome.
3. Growth and challenges — what was hard, what you learned, what you'd do differently.
4. Looking ahead — what you want to develop next and the support you'd find useful.

If your company gives you a form with set competencies, map your examples onto those headings instead. Either way, lead with the point and keep paragraphs short.

Back every claim with evidence

The single biggest upgrade you can make is to replace adjectives with instances. "Strong communicator" is your opinion. "Rewrote the onboarding docs after three support tickets traced back to one confusing step" is a fact your manager can repeat to their boss. For each accomplishment, name the what, the how, and the result.

• Weak: "Helped improve the team's process."
• Strong: "Proposed moving standup to async on Slack, which gave the team back roughly two hours a week and cut meeting fatigue people had raised."

Quantify impact — even roughly

You don't need a finance-grade number. A defensible estimate is far better than nothing. Reach for whatever you can honestly measure: time saved, volume handled, errors reduced, revenue or cost touched, people helped. If you can't measure the outcome, measure the activity ("handled 40+ escalations") or describe the before-and-after concretely. When you estimate, say so — "approximately," "around" — so it reads as honest, not fabricated.

Handle weaknesses honestly

Skipping your development areas makes the whole document less credible. But there's a way to be honest that doesn't hand someone a stick to hit you with: name the gap, show you understand its impact, and state what you're doing about it. That framing turns a weakness into evidence of self-awareness.

"I underestimated timelines on two projects this period, which pushed delivery dates. I've started building in a buffer and flagging risk earlier, and the last release landed on schedule."

Pick real growth areas, not humble-brags. "I care too much" fools no one. "I avoid asking for help and it slows me down" is real, and it opens a useful conversation.

Eight example self-assessment sentences

Adapt these — swap in your real project, number, and outcome:

• "Led the vendor migration end to end; we moved 12 accounts with zero downtime and finished a week ahead of the plan."
• "Took ownership of the weekly report no one wanted, automated it, and gave the team back about three hours each week."
• "Mentored two new hires through onboarding; both were shipping independently within their first month."
• "Caught a pricing error before it reached the customer, which avoided a refund and a difficult conversation."
• "Improved my written updates after feedback last cycle — stakeholders have stopped asking for clarifying follow-ups."
• "My biggest growth area is delegation; I held too much myself early on and am now handing off the recurring tasks."
• "I'd like to develop my data skills next and would value time to take the analytics course we discussed."
• "A challenge this period was the reorg mid-quarter; I kept my projects on track by reprioritizing weekly with you."

Before you submit

• Cut anything you couldn't say out loud to your manager's face.
• Check that each accomplishment connects to a goal or a real outcome.
• Make sure your growth section is genuine and paired with an action.
• Keep it tight — a focused page beats four pages no one finishes.

Write it the way you'd want someone to advocate for you: specific, fair, and grounded in what actually happened.