Performance Review Summary Examples for Your Self-Review

The overall summary is the short paragraph at the top or bottom of a self-review that tells your manager how to read the rest. It names the work that mattered most, how you contributed, and what comes next. This guide gives a four-sentence shape for the summary and six worked examples for different kinds of year: a strong year, a year with a missed goal, a first year in the role, a mid-year change in scope, a steady year of reliable work, and a year spent on work that is not finished. Each example is fictional. Use it for structure, then write your own from the evidence you have.

What the overall summary is for

Your manager may read a dozen self-reviews in the same week. The summary is the part they will remember and the part most likely to be copied into calibration notes or a promotion discussion. It should give an accurate, specific picture of the year in a few sentences.

That makes the summary different from the rest of the review. The detailed sections hold your examples and evidence. The summary chooses among them and explains what they add up to. If someone read only the summary, they should still understand what you focused on, what changed because of your work, and where you are going next.

A summary is not the place for a long list of adjectives. “Hard-working, collaborative, and dedicated” tells the reader very little. One clear sentence about the biggest result will do more.

Write the summary last

The U.S. Office of Personnel Management's self-assessment guide recommends organizing your accomplishments by the elements of your performance plan, focusing on results rather than activities, and treating the self-assessment as “evidence, not advocacy.” That advice applies to any employer, not only federal agencies, and it suggests an order of work: gather the evidence first, write the detailed sections, and only then write the summary.

If you write the summary first, it tends to become a statement of how you would like the year to be seen. Writing it last means it can only point to things you have already described and supported. It also makes the summary faster to write, because you are choosing, not remembering.

Before you start, put your goals or role expectations next to your detailed sections. The summary should mention the goals that mattered most, even the ones that did not go to plan.

A four-sentence summary shape

Most good summaries fit into four sentences. You can adjust the length to your company's form, but this order keeps the paragraph focused.

• Sentence 1, focus: What you mainly worked on this period and why it mattered to the team or business.
• Sentence 2, main result: The most important change your work produced, with a number or a concrete outcome if you have one.
• Sentence 3, how: The skill, judgment, or collaboration that made the result possible, or a second result of a different kind.
• Sentence 4, next: What you plan to develop or take on next, ideally connected to your manager's priorities.

If something important went wrong, add it in sentence 3 or as a fifth sentence. A summary that leaves out a known problem makes the reader wonder what else is missing.

Example: a strong year with clear results

Fictional situation: a customer support lead whose team met its goals and who led a project that reduced repeat contacts.

“This year I focused on making our support process faster for customers and easier for new agents. The new triage guide I led cut repeat contacts by about a fifth between Q1 and Q3, and our team met its satisfaction target in every quarter. I also trained four new agents, all of whom were handling the full queue within their first month. Next year I want to take on the knowledge base project and develop my skills in writing for self-service.”

Notice that the first sentence names a focus, not a list of duties. The second gives the result and its period. The third shows a different kind of contribution. The fourth is specific enough that the manager can respond to it.

Example: a year with a missed goal

Fictional situation: a product manager whose main launch slipped into the next year.

“My main goal this year was to launch the new reporting module, and it did not ship by the year-end date we set. The delay came from a data accuracy problem we found during beta; I chose to hold the launch rather than release numbers customers could not rely on, and the fix is now in final testing for a February release. In the same period I ran the pricing research that shaped our Q3 plan changes. I have learned to build earlier data checks into the plan, and I will apply that to the next two projects.”

This summary states the miss in the first sentence. It explains the decision behind it, gives the current status, and adds a separate result. The final sentence shows what changed in how the person works, which is often what a manager most wants to see after a setback.

Example: new in the role

Fictional situation: an analyst six months into a first job on the team.

“In my first six months I focused on learning our finance systems and taking over the weekly sales report from a departing colleague. Since July I have produced the report on time every week, and I found and fixed a formula error that had been overstating one region's revenue. I have relied on Priya and Marcus for reviews and have started checking my own work against the same checklist. Next period I would like to own the quarterly forecast model with support.”

When you are new, the summary can show how quickly you became reliable and what you now handle independently. Naming the people who helped is accurate and does not weaken the summary.

Example: the scope changed mid-year

Fictional situation: an engineer whose project was cancelled and who moved to another team in May.

“My year had two parts. Until May I worked on the partner integration, which the company stopped when the partnership ended; I documented the work so it can be restarted if needed. Since June I have worked on the billing team, where I delivered the invoice retry system that recovered failed payments in its first quarter of use. I would like my goals for next year to reflect the billing work, and to grow my ownership of the payments area.”

When the plan changed, say so plainly and briefly. Your manager knows about the change; what they need is an account of what you did with each part of the year.

Example: a steady year of reliable work

Fictional situation: an operations coordinator whose job is to keep processes running.

“This year I kept our vendor payments and contract renewals running on schedule, with every payment made on time across about 300 invoices. I found an automatic renewal three weeks before its deadline and negotiated a smaller plan that matched our actual use. I also documented the renewal process so others can cover it during holidays. Next year I would like to automate the invoice matching step, which still takes about a day each month.”

Reliable work often goes unnoticed precisely because it works. Give the scale of the work, one example where your attention prevented a problem, and something you improved for other people.

Example: a year spent on work that is not finished

Fictional situation: a researcher on a two-year study.

“Most of my year went into the first phase of the retention study, which runs until next autumn. I designed the interview plan, completed 30 of the planned 45 interviews, and shared an interim summary that the onboarding team has already used to change their welcome email. The final findings are not ready yet, and I have avoided presenting early patterns as conclusions. Next year I will finish the interviews and deliver the full report by October.”

For long projects, report the current stage and anything the work has already made possible. Being clear about what is unknown is part of the evidence.

Check the summary before you submit

Read your summary and ask four questions. Does each claim appear somewhere in the detailed sections, with support? Does it mention the goals your manager will look for, including any you missed? Have you described your own part accurately and credited others where they shared the work? And would a reader who only saw this paragraph understand what changed this year?

Then cut words that do not help. Phrases such as “went above and beyond” or “consistently exceeded expectations” are judgments your manager will make. Replace them with the result that would lead someone to that judgment.

The summary is much easier to write when your examples were saved during the year. Bloomly keeps your work notes, shared links, and feedback organized by Role, and it can draft a performance-review report from that record. Use any draft as a starting point: check each claim against your own evidence and write the final summary in your own words.

A good summary is short because the work behind it is already written down. Gather your evidence, write the detailed sections, then choose the focus, the main result, how you achieved it, and what comes next. Be plain about anything that did not go to plan. If your notes for this year are thin, start a simple record now, so that next year's summary takes an hour instead of a weekend.