Resources · Review prep

Performance review prep: build the record before you write the review

When review season arrives, the first job should be deciding what matters, not searching for what happened.

There are two ways to sit down to a self-review.

You can try to reconstruct the year. Open the calendar. Search old messages. Scroll through project folders. Try to remember what you were doing in February and whether that thing in June turned out to matter.

Or you can start with a record you already have.

The difference isn't that one person has a better memory or is more disciplined. One simply kept the details while they were still easy to know.

But either starting point can lead to a useful review. You don't need to account for every week. You need to identify the work that best represents your contribution, understand how it relates to what was expected of you, and be ready to explain it.

Start with what your review is asking

Before searching for examples, look at what you're being asked to review.

Check the period being evaluated, the form you'll be completing, your role expectations, and any goals or development plans from your last review. These give you a reference for deciding what belongs.

Then consider what changed.

Maybe a project was canceled, priorities shifted, or your responsibilities grew beyond what was originally agreed. A goal that made sense in January may no longer have reflected what the organization needed by June.

Those changes matter when accounting for your work. So does the distinction between what you were responsible for and what you contributed beyond it.

If you weren't given written goals, start with the responsibilities you actually carried and the expectations discussed with your manager. Don't invent a set of targets after the fact.

Gather what you have, or reconstruct what you can

If you've kept a record: Read through the entries from the review period. Mark those that relate to your responsibilities, show a meaningful contribution, or reveal a change in what you were able to handle. You don't need to turn each one into a finished paragraph.

If you're starting now: Look back through your calendar, completed projects, status updates, previous check-ins, and feedback available in your work systems. Begin with the milestones you can identify, then work backward to recall your part in making them happen. Give the earlier months some attention, too.

A calendar can tell you that a meeting happened. A project tracker can tell you that something shipped.

Neither necessarily tells you what was difficult, what you changed, why your part mattered, or what someone said afterward. Those are the details most likely to disappear.

You solve the recurring problem and then stop having the problem. You take on something that once felt like a stretch and six months later it simply feels like your job. You help someone through a difficult situation, and the work carries on.

By review time, those moments may seem ordinary. That doesn't make them irrelevant.

As you gather, notice what's missing. A goal may have changed, a responsibility may have grown without appearing in your notes, or a project's outcome may still be unclear. Check the gaps that would affect how you explain your contribution; you don't need to reconstruct every detail. If you can't establish a result, don't fill it in with a guess.

When review season comes, select before you write

Start with the examples you've gathered and notice what repeats.

Maybe several of your strongest examples involve simplifying work that had become unnecessarily complicated. Maybe you kept stepping into difficult customer situations. Maybe your role quietly expanded from doing the work to helping other people do it well.

Those patterns are more useful than a month-by-month recap. A chronological review often gives everything equal weight. But a year of work rarely makes sense because of the order in which it happened.

Now compare those examples with your responsibilities and the goals or expectations you reviewed earlier.

Which ones best explain the work you were accountable for? Which demonstrate a contribution that might otherwise be overlooked? Which show how you responded when priorities changed?

Group the strongest examples around the ideas they support. Depending on your work, that might be customer impact, better operations, technical depth, collaboration, judgment, leadership, or expanded responsibility.

Don't decide the themes first and force the year into them. See what the record actually says.

You won't use everything you gathered. That's the point of selecting: deciding what deserves attention, rather than giving every completed task the same weight.

The week you write it

  • Gather. Bring together the relevant examples from the review period, whether from an existing record or what you've reconstructed.
  • Notice. Look for recurring kinds of contribution rather than reading only by date.
  • Select. Choose the examples that best answer what your review actually asks.
  • Expand. Give the strongest examples enough detail to make sense without the rest of your notes.
  • Check. Compare your selection with the goals and expectations for the period, including anything that changed along the way.
  • Look forward. Notice what you want to keep doing, do more of, or grow into next.

Show what changed, including when nothing shipped

Compare these illustrative examples:

"Helped with the quarterly plan."

"When priorities changed midway through the quarter, I reviewed the commitments already underway, identified what couldn't reasonably fit the new timeline, and helped the team decide which work to postpone. We agreed on a revised plan instead of treating the original deadlines as unchanged."

The difference isn't polish. The second version gives the reader something the first one doesn't: the problem, your contribution, and what changed.

Use numbers when they genuinely tell the story, and don't manufacture one because an accomplishment seems more legitimate with a percentage attached. Some work is naturally measurable and some isn't.

The same approach works for contributions that produced no obvious launch or finished artifact.

The problem you prevented. The decision you helped clarify. The person you got unstuck. The difficult conversation you handled well. The context you carried between teams when nobody else had the whole picture.

These can sound vague when you describe them as traits.

"I'm good at cross-team collaboration."

"When a new approval rule raised questions about how exceptions should be handled, I collected the situations teams were encountering, worked with the policy owner to clarify the guidance, and shared the answers with the affected teams before the rule took effect."

You don't need to label yourself collaborative. The example does the work.

These are illustrations, not accounts of verified outcomes. In your own review, use the details you can support and give collaborators their share of the credit.

Keep the parts that didn't go perfectly

A useful record shouldn't contain only wins.

Consider the project that missed. The approach you changed. The call you would make differently now. The responsibility you weren't ready for at first.

Not because every mistake belongs in your self-review. Because sometimes the most useful evidence of growth is the distance between how you handled something then and how you would handle it now.

You may find that a goal was only partly met, that circumstances limited what could be accomplished, or that you made a decision you later reconsidered.

Account for what happened, what was within your control, and what you would do differently. You don't need to turn an unsuccessful result into a success story.

If writing about your contributions feels like self-promotion, that's what a brag document for people who hate bragging is about.

See where the year points

A good record can answer questions the review form never asks.

What work did you keep volunteering for? Where did people repeatedly turn to you? What became easier over the course of the year? What responsibility gradually became yours? Which examples still make you think, I want more of that?

Sometimes the clearest clue about what you want next isn't a goal you wrote six months ago. It's the pattern in what you've already been doing.

Before the review conversation, use those patterns to decide what you'd like to discuss with your manager. If you repeatedly gravitated toward a certain kind of work, bring an example and ask where you might do more of it. If a responsibility has gradually become yours, consider whether its scope or expectations should change. If there's a skill you want to develop, identify the experience or feedback that would help.

Consider what you'd like to keep doing as well as what you'd change. Some of that may involve clearer priorities, support with an obstacle, or more room to take ownership of work that interests you.

You don't need a prepared answer for every possible question. A few specific subjects, grounded in the work you've been doing, can make the conversation more useful.

Make review season an editing job

Worth Noting is built for the part that happens before the self-review.

Keep a line when something happens. Add the context that's likely to disappear. Save feedback you're allowed to keep while you can still find it.

Then, when review season comes around, you can search and filter your record and export it as a free Record PDF. With Pro, you can create a Review PDF containing only the fields you choose.

You still have to decide what the year meant. You just don't have to remember it from scratch.

A note about work information: Materials you can consult for a review aren't necessarily yours to keep. For personal notes, follow your employer's policies and agreements, and describe your contribution without copying confidential, customer-specific, or otherwise restricted information.

Next: how to track accomplishments without creating more work, or 70+ work accomplishment examples.

← All resources

Make your next review an editing job. Start your record.

Download on the App Store

Free for your first 20 wins. Pro is $6.99 a month or $49.99 a year. See what's in Pro

iPhone and iPad · On your device · No sign-up