How to Write A Self Evaluation: Complete Guide with Examples

Learn how to write a self evaluation with this step-by-step guide. Includes templates, examples, and tips. Use Rephrasely's free AI tools to write faster.

Try It Free

How to Write A Self Evaluation: Complete Guide with Examples

Writing a self evaluation can feel awkward, but it's also one of the best opportunities to shape how your manager sees your work and growth. In this guide you'll learn exactly how to write a self evaluation that is clear, balanced, and persuasive.

You'll get a step-by-step process, a ready-to-use template and a full example you can adapt, plus common pitfalls and a printable checklist. If you want to draft faster, consider using Rephrasely's AI writer (Composer) to generate versions you can refine.

What Is a Self Evaluation?

A self evaluation is a structured reflection you write about your job performance, accomplishments, strengths, and areas for improvement. It's often used during performance reviews, promotions, or goal-setting meetings.

Good self evaluations combine evidence (metrics, projects, feedback) with honest analysis and concrete next steps. They communicate your contribution and your plan to grow.

Step-by-Step Guide: How to Write a Self Evaluation

  1. Prepare — Collect facts and feedback

    Start by gathering objective data: project results, KPIs, emails of praise, and any formal feedback. Pull dates, numbers, and deliverables to support claims.

    Also review job descriptions and goals set at the start of the review period so you can measure progress against expectations.

  2. Outline your accomplishments with evidence

    List 5–8 key accomplishments that had measurable impact. For each, note the situation, your actions, and the results (use the STAR method: Situation, Task, Action, Result).

    Quantify outcomes when possible: revenue influenced, hours saved, customer satisfaction improvements, or reduced defect rates.

  3. Be candid about challenges and lessons

    Identify projects that didn't go as planned and what you learned. Explain what you changed mid-course or what you would do differently next time.

    Admitting shortcomings, paired with specific corrective actions, shows maturity and a growth mindset.

  4. Describe skills and strengths

    Summarize core strengths that supported your work — technical, leadership, communication, or problem-solving. Use examples to show each strength in action.

    Connect strengths to business value (e.g., "My stakeholder management reduced approval cycles by two weeks").

  5. Identify development areas and set goals

    Cite 2–3 skill gaps or opportunities for growth, then propose concrete development goals and timelines. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound).

    Include specific training, projects, or mentorship you’ll pursue to address those areas.

  6. Request support and align on expectations

    State what you need from your manager or team to be more effective: resources, clarity, authorization, or coaching. Aligning resources shows you're solution-focused.

    Propose how you’ll measure progress and when you’ll check in (e.g., monthly check-ins or milestone reviews).

  7. Polish tone and proofread

    Use a confident, professional tone — neither boastful nor apologetic. Keep sentences concise and focused on outcomes.

    Run a final spell-check and read the document aloud. If you use AI tools to draft, run the text through Rephrasely’s humanizer and the plagiarism checker to ensure clarity and originality.

Template / Example

Below is a practical template you can copy and adapt. After the template, you'll find a filled example for an individual contributor in product management.

Opening summary: Briefly summarize your role and overall performance (2–3 sentences).

Key accomplishments:

  • Accomplishment 1 — Situation, Actions, Result (quantified).
  • Accomplishment 2 — Situation, Actions, Result (quantified).
  • Accomplishment 3 — Situation, Actions, Result (quantified).

Challenges & lessons: What didn’t go as expected and what you learned.

Strengths: 2–3 demonstrated strengths with examples.

Development goals: Goal 1 (SMART), Goal 2 (SMART).

Support needed: Specific asks for manager/team.

Closing: Short, forward-looking statement about priorities next period.

Full Example — Product Manager

Opening summary: Over the past six months as Product Manager for the onboarding flow, I focused on reducing user drop-off and improving activation. I successfully led cross-functional initiatives that reduced activation time and increased trial-to-paid conversion.

Key accomplishments:

  • Improved onboarding conversion by 18%: Conducted user testing, prioritized top three friction points, and launched an in-app walkthrough. This led to a 18% increase in week-one activation and a 9% lift in MRR from new users.
  • Reduced feature delivery timeline by 25%: Implemented a lightweight discovery checklist and aligned engineering and design on acceptance criteria; average cycle time dropped from 16 to 12 days.
  • Launched A/B test framework: Built a templated experiment plan that improved test reliability and shortened decision time from three weeks to one week.

Challenges & lessons: The referral program launch missed initial conversion targets due to an unclear value proposition. I learned to prioritize hypothesis validation before full implementation and now require a validated landing page and initial cohort testing for similar launches.

Strengths: Cross-functional facilitation — coordinated product, design, and engineering sprints; Data-driven decision making — used funnel analytics to prioritize work; User empathy — led sessions with 15 customers to capture qualitative insights.

Development goals:

  • Improve quantitative analysis skills: Complete an intermediate SQL course by Q3 and create a weekly dashboard to track activation metrics.
  • Grow leadership influence: Lead two cross-team initiatives next cycle and request quarterly feedback from stakeholders to measure progress.

Support needed: Access to a BI developer for one quarter to help build the activation dashboard, and sponsorship for an external analytics course.

Closing: I’m proud of our progress on activation and plan to focus on scalable experimentation and stronger analytics capabilities in the next six months.

Common Mistakes to Avoid

  • Vague claims without evidence: Saying "I improved performance" isn't as persuasive as "I improved conversion by 18% by implementing X." Fix: Always attach a metric or concrete result.

  • Either all praise or all criticism: Extreme tone sounds insincere. Fix: Use the sandwich approach — highlight accomplishments, honestly note one or two areas to improve, and finish with a plan.

  • Listing activities instead of outcomes: Describing tasks (e.g., "I attended meetings") doesn't show impact. Fix: Frame each task as part of a result (e.g., "Led weekly syncs that cut decision time by 30%").

  • Overly long or unfocused self evaluations: Block text makes it hard to skim. Fix: Break content into sections, use bullets for accomplishments, and keep paragraphs short.

  • Neglecting to ask for support or goals: If you don’t state what you need, you miss out on resources. Fix: End with clear asks and measurable objectives.

Checklist

  • Gather objective evidence: metrics, emails, and feedback.
  • Write 5–8 key accomplishments with STAR structure.
  • Quantify outcomes wherever possible (%, $ amounts, time saved).
  • Acknowledge 1–3 challenges and outline lessons learned.
  • List strengths with concrete examples.
  • Set 2–3 SMART development goals and timelines.
  • Request specific support or resources from your manager.
  • Polish tone; proofread and check originality using tools (optional).

Tip: If you want a fast first draft, use Rephrasely's Composer to generate a structured version based on your bullet points. Then run the draft through Rephrasely's humanizer and the AI detector to ensure natural tone and authenticity. Finish with the plagiarism checker to confirm originality.

Frequently Asked Questions

How long should a self evaluation be?

A concise self evaluation is best: typically 300–800 words depending on your role and company expectations. Focus on quality over quantity — clear accomplishments, evidence, and goals matter more than length.

Should I be honest about failures?

Yes. Admitting failures paired with lessons learned and corrective steps demonstrates accountability and growth. Frame failures as learning opportunities and describe the concrete actions you’ll take moving forward.

Can I use AI to write my self evaluation?

Yes — AI can help draft and refine your statements, but always personalize the content. Use tools like Rephrasely's Composer to create a starting draft, then edit for specific examples and your authentic voice. Run the text through the AI detector and humanizer if you want to ensure natural tone and transparency.

Related Tools

Ready to improve your writing?

Join millions of users who trust Rephrasely for faster, better writing.

Try It Free