How to write your self-review from a brag document

A year of work, in a text your manager can take to calibration.

Why it is hard

You write a self-review once or twice a year, about months you no longer remember. Most people open a blank page the week it is due and end up describing the last month.

The self-review is often the main text your manager brings to the calibration meeting. What you leave out of it rarely comes back.

Start from the evidence

If you keep a brag document, the material is already there. If you do not, you can rebuild most of it in an hour: your merged pull requests, the docs you wrote, the tickets you closed, your calendar, and the threads where someone thanked you.

Before writing any prose, list one line per item with the date, what happened and a link.

How to write it

• Read the rubric first. Copy your company's competencies into the document as headings: delivery, technical quality, collaboration, leadership, or the names your company uses.
• Sort the lines under the headings. When a line fits two headings, put it where it is strongest.
• Keep three to five per heading. Choose by impact. A small fix that unblocked a release counts more than a large refactor nobody needed.
• Write each one as context, action and result. Two or three sentences, with a number when there is one.
• Link the evidence. Your manager will reuse your words in calibration, and the link lets them defend each claim.
• Name the invisible work. Reviews, mentoring, incidents and interviews rarely show up in metrics. Give them their own section.
• Say what did not go well. One honest paragraph on what you would do differently. Managers usually ask about it anyway.
• End with goals for the next cycle. Two or three, tied to the next level of the rubric.

A template

## Delivery
- Led the billing migration from design to rollout. It unblocked the March release and cut invoice errors from 40 to 3 a month. (link)

## Collaboration
- Reviewed 60 pull requests from the payments team while they changed their on-call. Their deploys before the freeze went out with no rollback. (link)

## Invisible work
- Ran the hiring loop for two backend roles and mentored the new hire through her first on-call. (link)

## What I would do differently
- I took the search rewrite alone for two months. Pairing earlier would have caught the indexing problem in the first week.

## Next cycle
- Lead a design across two teams, from proposal to approval.

Send it early

Send a draft to your manager one or two weeks before the deadline and ask what is missing. They may remember work you forgot, and they get time to prepare your case.

How Zebra helps

Zebra keeps your brag document filled during the year, so the self-review starts from a list that is already written.

Every Friday, the weekly summary adds one line for each top task you completed and each promise you kept, with what actually happened and a link to the pull request, thread or doc. Reviews you did for others, replies you owed and incidents go in a separate invisible work section.

When the cycle comes, ask your Claude to group those lines by your company's competencies and draft the self-review from them.